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.
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
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.
I am also having random crashes,Rhino just crashes to desktop or sometimes it hangs and i have to end the task
This happens seemingly randomly.
When creating sections
Editing sections
i assumed it may be bad objects but none show up.
if i reload the file after a crash i can run the same command that crashed it and it’s fine
is there a log file anywhere?
Windows 10 (10.0.19044 SR0.0) or greater (Physical RAM: 32Gb)
Computer platform: LAPTOP - Plugged in [100% battery remaining]
Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA Quadro T2000 (NVidia) Memory: 4GB, Driver date: 6-23-2022 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 516.59
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Secondary graphics devices.
Intel(R) UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 2-18-2022 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- Secondary monitor is laptop’s integrated screen or built-in port
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 6-23-2022
Driver Version: 31.0.15.1659
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB
Rhino plugins that do not ship with Rhino
C:\Program Files\ADA 3D\Mesh2Surface for Rhino 6\m2s_for_Rhino.rhp “MESH2SURFACE”
Hello- thanks- I’ll test - is this repeatable with any geometry? If you have a file that relaiably shows the problem, please post it or send to tech@mcneel.com, with a link back to this topic in your comments. @rajaa , fyi…