TightVNC 2.0 command line

Deadline
1

I’ve been having trouble viewing remote nodes using the old TightVNC v1.3 it’s going too slow so I tried the new beta 2.0 and there is an improvement on Windows 7.
But they have changed the command line options for vncviewer and it won’t work through Deadine Monitor.

Any way to configure the viewer command line options in Deadline?

Thanks.

2

Unfortunately, the viewer command line options are not configurable, but that’s a really good idea. We’ll take a look at adding support for this in Deadline 4.1 (which is currently in beta).

Cheers,

  • Ryan
3

I see this is implemented in 4.1 (yay) :slight_smile:

But I’m having trouble using it, what is the correct command line to get TightVNC to work??

Thanks.

4

The following should work:

-config "[CONFIG_FILE]"

Just specify this fro the VNC Viewer Arguments (Windows) in the repository options.

Cheers,

  • Ryan
5

Hmmm, that was the initial line, but it doesn’t work, the viewer nags about an invalid command-line… I’m trying the latest tightVNC v2.0.2

What’s even worse I can’t get the old version of tightVNC working either…

ummm, help? :slight_smile:

6

I just tested that command line here with tight VNC 2.0.2, and it worked fine. Can you send us a screen shot of your VNC settings in the Repository Options?

7

repository1.png
repository1.png811×490 19.6 KB

Here are the settings, and its on a freshly installed machine, default install of TightVNC, don’t know what could be causing this??
Also tried wrapping the path in quotes, still the same…

Where is deadline supposed to create the config file, I can’t find anything like that?

Thanks.

8

Thanks! Everything looks correct there. The config file is created in the system temp folder.

Just thought of something. In the Monitor, select Tools -> Options, and check to see if you have a VNC override specified in the Remote Monitoring settings. If you do, Deadline would be using that instead of the global option in the Repository Options.

Cheers,
Ryan

9

That was the problem! Deleted the Remote Monitoring settings path, and now it works.

Weird that it was pointing to the same exe, I guess the command line parameters weren’t passed along.

Thank you!