I am running Motive on a remote machine. On several occasions I've observed signs that Motive has crashed, and, when I remote into the Motive machine, I see a Motive error prompt that reads, "Direct3D does not work over a remote session." Normally I would assume this is a Remote Desktop issue, but I regularly remote into the Motive machine without any problems.
Is there something else, maybe something internal to Motive, that could be causing this error?
Is there any way to disable the error message? Because it is a Motive error prompt, it tricks my process monitor into thinking that Motive has not crashed.
Thanks in advance for any help.
Direct3D error
-
- Posts: 609
- Joined: Tue Mar 19, 2013 5:03 pm
Re: Direct3D error
Thanks for posting on the forums. I did a bit of research on Direct3D over a remote session. What remote desktop application are you currently using?
Dustin
Technical Support Engineer
OptiTrack | TrackIR | SmartNav
Technical Support Engineer
OptiTrack | TrackIR | SmartNav
Re: Direct3D error
Apologies for the late reply. I'm using Windows standard Remote Desktop Connection, v 6.3.9600.
I've been able to determine experimentally that the issue only happens if I remote in during Motive startup -- once Motive is up and running, all is well. Is there something that uses Direct3D in the launch process only?
I've been able to determine experimentally that the issue only happens if I remote in during Motive startup -- once Motive is up and running, all is well. Is there something that uses Direct3D in the launch process only?
-
- Posts: 609
- Joined: Tue Mar 19, 2013 5:03 pm
Re: Direct3D error
Motive does require Direct3D. Grayscale video mode may not work using Remote Desktop Connection.
Dustin
Technical Support Engineer
OptiTrack | TrackIR | SmartNav
Technical Support Engineer
OptiTrack | TrackIR | SmartNav