The company I work for has a windows 10 design machine that completely isolated from the outside world, so there is no internet connection to this machine. (Company policy, I have no control over this). I recently installed to Rhino 8 to evaluate. Thankfully I didn’t remove Rhino 7. I’ll try to upload the most recent crashDump.
The new Rhino 8 seems to work with the exception of Sub D. As soon as I create any Sub D primitive such as a plane, Rhino immediately throws an error and closes. It seems to work fine with NURBS objects though..I’m also running RhinoCAM 2025. I haven’t read about any major conflicts with this.
Hi Steven, there is a SubD plane in the RhinoCrashDump.3dm file, this could mean that Rhino succeeds in creating these objects and saving them to a file. The crash would come later when for example a plugin reads that document and tries to do something with the SubD. RhinoCAM seems to be the only non-Rhino plugin that was enabled when that file was saved.
Can you try disabling the RhinoCAM plugin to see if SubDs work on that machine after that?
No, it actually never gets that far. At least I’m not opening a plug in to read. I should probably specify it that way. Yes, there’s a plane, and there should also be a box in the subD plane.
As as soon as the sub object is created, it immediately crashes, so I don’t know if it crashes, because there’s a plugin that reads it immediately as soon as it’s created, that’s quite possible.
Do you have any plugins that have shown this to be a problem, the only. Plug in that I installed was rhinocam. Other than that one, the only other existing plugins are the ones that come with rhino itself. And I would expect that the plugins that come with rhino have been tested thoroughly. You guys are very, very good at testing your products.
I did a couple of experiments today. I pulle a copy of the system information (attached). The only third party plugins are rhinoCAM and Rhino Art exporter. I tried disabling each separately and it still crashed every time. I also tried turning both off simultaneously and it still crashed.
Looking at the system information, could this be as simple as a low memory issue? Since this is a machine I pulled out of storage just to test out Rhino 8 I never bothered to check the machine configuration.