Jump to content


New member
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. having the same problem, was working fine 2 days ago but now I get the same behavior nevermind.. I should have just remember the Dogbert troubleshooting method.. shut up and reboot. This was cause because (and I'll try to avoid my rant about how much I hate python and the junk code that is written in it) python is using OpenGL which is fine, been around since, at least, the mid 90's but I use remote desktop to get into this machine from work and I made the horrendous mistake of thinking that I could access Cura through my RDP session (to a box that has a gforce 1080) which I of course can't, I'd really like a valid explanation of why not that averts my rant about the wonders of python since I can acces fusion/vetrix/and a majority of my (non-python) CNC applications. At any rate.. if you try to access Cura from an RDP session and then try to access it again from the physical box you're going to see that error. After I got it back running I tried to RDP from another box to this one and get the exact same behavior.
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!