After more 1 000 000 (one million) views on forum for 1.5.0.x development versions... and 1.6.0.0 version
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome

Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031

Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078

Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.3.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38091
Feedback is welcome

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Some UltraVNC feature requests...

Any features you would like to see in UltraVNC? Propose it here
Post Reply
scottcopus
Posts: 3
Joined: 2004-11-17 15:28

Some UltraVNC feature requests...

Post by scottcopus »

Hi,

Here's a few UltraVNC feature requests (using 1.0RC18 right now) ....

1. When the Windows VNC Viewer is trying to connect to a host that is down (offline, etc), the viewer will not respond to the "Cancel" button when the status is at "Connecting...". Also, it seems to take a long time (maybe a minute) before it will timeout.

2. Upon opening the VNC Viewer via a Windows shortcut, I would like to have the option "Auto Scaling" checked by default. However, using the command-line option /autoscaling only seems to work when specifying the actual host to connect to. Do most of these command-line options only take effect when you must specify the remote host on the command-line too? I don't think TightVNC has this problem.

3. File-transfer window:
a) Instead of just having the "Close" button inside the window, put back the "X" close button on the window title.
b) For the local computer, use the "Windows" explorer-type view hierarchy where "Deskop" is the root of the tree, followed by My Computer, etc. (instead of just listing A:, C:, D:)

Keep up the great work trying to get CPU usage down on the VNC server side!

Scott.
lizard
80
80
Posts: 171
Joined: 2004-05-03 07:43
Contact:

Post by lizard »

1:
known bug

2:
agreed. it should eventually be reorganized, indeed.
looks like VNC generally has somewhat vague commandline option processor.

3:
good idea.
small "Recent Folders" feature would rock, btw.

CPU:
for some computers I use "below normal" priority and it seems alright.
Lizard
NightRyder
80
80
Posts: 157
Joined: 2004-08-15 08:33
Location: WA, USA

Post by NightRyder »

for 3 and the cpu usage.
try the new test version, and the new video driver.
the new version has more to the file transfer,
and the new video driver is even better then before.
(and if your not useing one now.. wow hang on)
using latest code.... always... except when im not.
Post Reply