sdiScope, 4KScope, HDRScope, 2110Scope, videoQC, and other OpenGL based apps can have trouble displaying the video in an OpenGL plane when connected via Remote Desktop Protocol or other remote control protocols.  To fix this problem, we supply special start files to be used remotely.

Running OpenGL Remotely

Setting up Remote Desktop to use the primary GPU

Please note: Group Policy tools are not supported in Windows Home edition operating systems.

1. Open the Edit Group Policy tool from Control Panel or use the Windows Search dialog (Windows Key +R, then type in gpedit.msc).
2. Browse to: Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment.
3. Then enable “Use the hardware default graphics adapter for all Remote Desktop Services sessions.”

NVIDIA has an extra installer you can use to accelerate Windows remote desktop.  You can download it here (PhysX SDK page).

Selecting the GPU in a batch file

When an app is running on a system using OpenGL and you connect remotely, it will display what is being rendered by OpenGL to the remote client. If the app is not running, and it starts while the remote client is connected, then it will use the capablilities of their remote client display, which does not have OpenGL, and they will not be able to display the video portion of the GUI.  To get around this issue, batch files are supplied to remotely start the applications on the hardware GPU, enabling the video display.  The two batch files are: 

4kScope_RemoteStart.bat

videoQC_RemoteStart.bat

To use them, connect to the system.  Right click on the batch file in the install directory and select "Run as Administrator".  Click OK on any prompt.  When they run, you will be disconnected from your remote session.  When you reconnect, the app will be running and the video will be visible.