CyprienParticipantCyprien November 8, 2015 at 3:57 pm
If I use the current Spike on an i5 NUC with a displayport monitor all works fine.
Now I login to the PC via remote desktop and Spike crashes with “Unhandled exception at 0x00007FFDC9E92007 (opengl32.dll) in Spike.exe: 0xC000041D: An unhandled exception was encountered during a user callback.”
I am using Windows 10 x64 with all available updates.
Any idea how to solve?
AndrewModeratorAndrew November 9, 2015 at 9:18 am
We are aware of this issue. The reason this happens is because we utilize the GPU in our application through the OpenGL library. This is not supported in Windows Remote Desktop unfortunately and is a known limitation. There are a few workarounds.
Some customers report that if they can launch Spike before logging in to remote desktop and it will work, but they cannot launch Spike through remote desktop. You can also use a VNC client/server. There is a free version called TightVNC which we have used with success. This lets you control the PC remotely. If you have the NUC with vPro functionality, there is a way to setup the device to be controlled remotely using vPro. This is more involved but is a very robust solution.
cizekmParticipantcizekm August 9, 2016 at 9:50 am
this is what worked for me:
I created a batch file in the spike program folder and named it RunFromRDP.bat.
Inside that batch file I placed the following commands:
tscon 1 /dest:console
The first command disconnects the remote desktop session and forces Windows to run in the local console. Then the Spike starts and OpenGL initializes correctly. After a few seconds I reconnect and everything works fine.
mpatinoParticipantmpatino June 15, 2017 at 11:14 pm
Hi, Ifound the same problem, Ihave installed Chrome RDP ad that work fine with the desired results…
My customer, just started Spike at boot time and it works fine.. they have a dedicated Laptop so starting spike at boot is no problem…
You must be logged in to reply to this topic.