Multiple connections with different server sidescale factors

[Dreamy]

Hi rudi,

please, will this issue be ever fixed? When you connect to the same server twice, using different server side scale factor setting, the first connection's framebuffer becomes broken because the second one applies different scaling factor. I believe this happens because server works with only singe instance of framebuffer?

[Dreamy]

I believe I am being ignored?

[redge]

confirmed

short test:
vnc server scaling 1/1

vncviewer1 change server scaling 1/2
vncviewer2 change server scaling 1/3 or 1/1 or anything
vncviewer1 see screen 1/1 inside screen 1/2 and crash

[Rudi De Vos]

Please verify fix ( server update)

[post=85840][/post]

[Dreamy]

I can confirm it is working as you described, but I am unsure if this
is the wanted behavior as in our working environment server is often
used in different scales at once (for example someone is monitoring
and someone remote controlling), I hope this solution is temporary.

[Rudi De Vos]

Not possible, server site scaling modify the server framebuffer.
1920x1200 -> 960x600 (1/2)
That's way this parameter is callded "server site scaling". This parameter
limit the bandwidth, the server only send 25% of the pixels.

Viewer site scaling can be set on viewer base, each viewer can has his own scaling. You always get 100% of the pixels, viewer scale it down.

The vnc server has one capture engine (framebuffer), data is captured once for all viewers.

[Dreamy]

OK, thanks, so it's permanent thing, I'll deal with it somehow.

[redge]

i think... uvnc v2... great idea. most modern CPU have also hardware Virtualisation core and newer GPU also support VGPU (virtualGPU)
virtualize framebuffer as: (don't known real name)
winvnc_vmfb1 for viewer1 have his on scaling isolated.
winvnc_vmfb2 for viewer2 have his on scaling isolated, etc..

perfect for true computer or vm_workstation. everybody with his own scaling preference and safety without disturb next one