I found that RDC didn’t utilise the remote PCs graphics card at all (I think because it’s natively built into Windows, the OS knows that the GPU isn’t in use) - whereas Teamviewer seemed to still utilise all the hardware, provides you have a monitor or HDMI single attached.
Obviously Corona doesn’t need the GPU, but even for viewport speed I found it made a difference.
Window's remote Desktop:
It does use your graphics card and is currently the best integrated remote tool in windows. (Open up the task manager and drag a window around, you'll see quite a chunk for GPU usage). Nothing currently beats it in latency vs Quality.
The thing is, it does not expose the GPU in the classical way.
DirecX is not affected by this. OpenGL is - which is why it breaks many professional applications. The reason is a combo of Microsoft and Graphics Driver Teams being stubborn aholes. There are workarounds by the way, of which
I wrote up a bunch here.
3dsMax is btw unaffected and runs just fine.
VNC as a protocol is really not meant for low latency work. The most low latency implementation is TightVNC with's encoding + Jpeg and it updates only the inside of the window and not everything by default. Very neat, but it is still beat by Window's remote quick quality scaling and pretty smart "progressive updates".
There is also NX, which uses Video compression techniques and is the goto in *nix world and replaces VNC in terms of speed, but RDP is still faster on windows.
I have never used TeamViewer but from what I understand is that it routes the images through their servers, which would obviously kill latency, though I may be worong.
And of course, nothing of any of this matters if you have a bad upload speed. Then you won't have a good experience no matter what. My 10mbit upload is barely enough to work with 3dsMax with acceptable levels of jank.
« Last Edit: 2019-06-01, 11:21:21 by SairesArt »
Logged
I'm 🐥 not 🥝, pls don't eat me ( ; ; )