4 ms·
Because Windows 10 remotes as bitmaps, not as GDI commands, and also because you need a 3D accelerator card for rendering to be fast.
by orloffm 5y ago
Because Windows 10 remotes as bitmaps, not as GDI commands, and also because you need a 3D accelerator card for rendering to be fast.
- varjag 5y agoIt ain't that. With modern CPU clock speeds bitblt can be blazing fast without any accelerations.
- formerly_proven 5y agoMy impression is that some parts of Windows force animations to play out fully (probably not allowed to skip keyframes?) instead of real-time. So when something is animated, and the connection is bad, it takes ages for the animation to finish. Also, animations stay enabled in the first place in some places when using RDP is a bug in itself. This seems to be mostly the case in Microsofts own UWP apps. I distinctly remember the pain of the "!&§/$+ Edge full-screen logon "make me your browser already" nag, it literally took five minutes for that dumb IE-to-edge logo animation to play, blocking the entire desktop while doing so.