SectionTools Rhino7 issues

I run Rhino 7 SR5 2021-4-10 (Rhino 7, 7.5.21100.03001) and latest update of SectionTools

Whilest playing around with the updated SectionTools, Rhino closes down at somehow random instances; once after running _stMake2d several times in a row and once after I used _stDeleteSections.
Got no crash report or option to restore after restarting, it just opens the last saved file.

Anyone else having similar issues?

That is very strange indeed. It only happened to you were using SectionTools and after installing it?
Another question, do you recall doing anything between stMake2D calls, like deleting layers, renaming then, delete objects, changing some properties? I’m trying to figure out the steps where I can repeat at my end to be able to pin point the issue.
Thanks for your help.

Thanks for replying. I tried to recreate the issue but not with succes so far, which is good also.
The only thing i noticed during _stMake2d is my processor usage jumps from 15 to 100% for 2-3 seconds during this make2d process, but not sure if thats odd or not. (intel core i7 6700)

If I bump into this problem again I’ll let you know :slight_smile:

Thanks. I’ll appreciate it.
If you run the Rhino Make2D command, do you also get a usage jump? ST calls the same compute SDK function that Make2D calls and it can be calculation intensive.

Yes, same jump indeed for rhino make2d. At that second peak Rhino actually crashed the same way i mentioned earlier. I think it might have to do something with my model (complex or bad surfaces?) icw this make2D. not a sectiontools bug i guess.

If you can get a repeatable crash with Make2D, then this will be great example to try and fix.
No matter how complex your model is (or even if it has bad objects), Rhino should not crash and we will be very interested to repeat at our end and fix.
Thank you for your time helping spot this one.

1 Like