Anyone else getting this error? We’ve installed 7 seats of v38 on 3 different PC configurations, they all get it, all day, randomly. Losing hours and hours every day.
“The calling thread cannot access this object because a different thread owns it”
What’s the fix here? It makes the software borderline un-usable.
Thanks,
Nathan
I get it daily, especially when I close the application.
Get it all the time.
I find if you see the error message after you’ve closed, any changes you’ve made in your geometry or CAM tree may not be there when you re-open the BobCAD file. It’s a good indicator something isn’t how you thought you left it.
We tend to find a few extra operations in the CAM tree with no geometry selected and no toolpaths computed.
Yikes. I haven’t noticed that yet, but I’ll keep my eye on it. And maybe I could be a convenient excuse (that’s a joke of course).
I get it every time with V38 after closing the software. It doesn’t appear to affect anything though, maybe some extra lag closing the software.
V38 has problems. I’ve been working with bobcad support to fix or work around the ones keeping me from getting work done. One guy let slip that V39 is in the works to be released this fall. I would encourage bobcad to stop the endless annual release cycle and concentrate on long term releases. Release a stable version of bobcad, patch it as bugs are found and give customers a sense of security that the software will be maintained and supported for the foreseeable future. Say, a 5-year release cycle. I upgraded to V38 after 8 years of using V30. V38 has some of the same issues V30 had, they NEVER got fixed. The new UI looks modern, and we got new toolpaths by upgrading from mill pro to mill premium, but I really think V30 was more stable and easier to use. It is also very frustrating calling support for help and being told that your version is too old and no longer supported, but after you upgrade the same problem is still there. After spending thousands of dollars on a piece software I think I deserve to have it work correctly as advertised.