DarrenP
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
I have the same problem. First time installation with GTX 690 card latest drivers.
I have seen this all over the internet is anyone doing anything to fix it?
bump...
bump
Hi Joel,
Here is one for you. I decided to load a new copy of windows on my second hard drive on the same computer and it Motion Builder works fine. Any ideas why?
bump
Thanks for going to the trouble to keep hammering away at this. I don't know why a fresh installation of the OS would allow Mobu to startup. I'll have QA reproduce this. If they're able to reproduce it consistently, it will be straightforward to find the underlying issue.
Randomly getting this message using MotionBuilder 2016. Has been working fine for a year, then suddenly not!
Did anyone get to the bottom of this.
I've done the obvious stuff and installed latest drivers and getting the latest update to MotionBuilder.
Is it confirmed that this is a driver issue? Or could it be a windows update issue?
thanks
hello. one of my students is having the same issue in Motionbuilder 2019. is there a solution ?
i usually get this issue if i am using remote desktop with Motionbuilder
I stumbled upon a workaround, but not a fix.
Use 'chrome remote desktop', open Motionbuilder, switch back to 'remote desktop'.
Motionbuilder will work, if it is already open on the remote machine.
The issue with Motionbuilder seems to be to do with openGL and remote desktop using a slightly different version of openGL.
If you are using Nvidia graphics card, then here is solution for this issue https://developer.nvidia.com/designworks
https://developer.nvidia.com/designworks works like a charm ! thank you so much. only need to reboot after installing.
Can't find what you're looking for? Ask the community or share your knowledge.