Use Enscape over Remote Desktop Connection

REMINDER! If you encounter any issues with Enscape (e.g. crashes, installation problems) or your subscription please reach out to our dedicated support team directly through the Help Center or by using the Support button as detailed HERE! Thank you for your understanding.
  • hello,

    as many in these days we also work in home office, but run Revit on our office PC. So we connect via Remote Desktop Connetion. And until recently usually Revit crashed when opening enscape over RDC. We used a TeamViewer connection to open Enscape. As soon as Enscape was running, one could close TeamViewer and go back to RDC, Enscape continiues working. But, after Windows 10 Upgrade to 20H2 this also did not work anymore

    today we found, the nvidia tweek does work, many thanks! but than, my IT Colleague found an even easier way we want to share with you:

    > Aktivate Hardware Graphics for all Remote Desktop Connections with a GPO <

    create or use an existing GPO for the Workstations in your domain, navigate to /Computer Configuration/Administrative Templates/Windows Components/Remote Desktop Services/Remote Session Environment and enable "Use hardware graphic adapters for all Remote Desktop Servies sessions"

    allow the GPO to deploy, reboot the PC, thats all! now we can open ENSCAPE via RDC on all remote Workstations !

    have fun, konrad

  • sorry, my post was too fast:

    we have the problem, that when one reconnects to a disconnected RDsession, the screen might remain black!

    the setting seems to have unwanted side effects. sorry, this seems not to be a solution, try out with caution


  • Enscape over RDC is entirely do-able, but comes with many caveats - latest drivers, managed expectations, etc

    The biggest "issue" (for me) is not the launching nor the pragmatic dialling back of viz. settings - but the actual sending of navigation commands - where input lag via RDC is the real killer.

    Essentially, unless we're batch exporting stills, remote Enscape - at least for live-runarounds - remains a no go.

    So, in the WFH-age of today we've got the folks with decent home rigs pulling standalones across to their machines - there, driven locally, it's "only" the pq of the screensharing app (and network connection) that holds things back...

  • Take a look at Parsec, it's designed for game's developers/ playing games, so it handles fast motion and inputs better than many platforms designed only for mouse cursors and static windows.

    Input latency is very good too

    Game, Work, and Play Together From Anywhere | Parsec