Color inaccuracy + "optimizing" details - how to suppress ?

[klenot]

I noticed that immediately after connecting to UVNC server, the viewer shows the image with slight color inaccuracy and "optimized" details, some kind of anti-aliasing.

Also I have found out, that if I choose "Connection options" from viewer's window system menu, and then immediately (without changing any setting) click "OK", the viewer starts to show an accurate image, both concerning the colors and details.

Best you will understand what I do mean by looking at screenshots I made.

Well, my question is: Is it possible to instruct the viewer to show accurate (colorwise accurate and details non-optimized/non-antialiased) image right from the start ? Some command-line switch ?

My server setup: UltraVNC Win32 Server v1.0.8.2 build Dec 6 2009, 16:45:17, running as a service on Windows 2000 with latest service packs.
My viewer setup: UltraVNC Win32 Viewer v1.0.8.2 build Dec 7 2009, 00:17:59, running on Windows 2000 with latest service packs.

[redge]

you can force vncviewer connect with your prefered settings at startup

doc.uvnc.com

you can save your settings connection.
you need success your connection before able to save your connection

vncviewer -config filename.vnc

[klenot]

redge,

Thank you very much for your quick reply. Thanks to your suggestion, I did found the magic.

I did saved the connection options both immediately after viewer start, and after doing that hack: Connection options + OK without changing any setting. Then I did compared the resulting files, and they do differ in one line:

Settings file immediately after viewer start:
Scaling=1

Settings file after Connection options + OK:
Scaling=0

Well, I prefer using the viewer without settings file, just by storing command-line switches into .lnk files, so I tried adding this switch:

-scale 1/1

and it did the trick. This way the viewer starts up in colorwise accurate, non-anti-aliased mode, without need to use .vnc file.

Though, I think, it is a bug in a viewer. Not acute one, but still a bug. Using -scale 1/1 is just a workaround for it.

Thank you again for the hint.