“38972 objects with 973 plug-in data items, 51631942 bytes (offset 826872 to 52458814”
I am just another forum member, but just as a curiosity, what do you have for a computer?
Until this is sorted out, Rhino3D does have an auto-save feature where you just set it for how many minutes of work you might be agreeable to loosing. If there is a particular command that crashes your system, it may be set to auto-save before executing that command.
It is a bootcamped Macbook pro. I have worked on much bigger files on Rhino 5.
The geometry isn’t very complicated and when the file was open my computer was not struggling at all. Its just since the crash and what also concerns me
Personally, I think its one of the plugins. I was working with someone last month who had a beast of a machine and was having similar problems with Rhino 6.
I have sent several crash reports to Rhino but I have not really got much of a response. So I was hoping that reaching out through the forum could help.
I’ve received the file and I can confirm I can open it without crashes on VisualARQ 2.2.1 and Rhino 6.6, the last published versions.
Which version of VisualARQ are you using?
If you’re using VisualARQ 2.2.1, then I think the crash is not related to VisualARQ. That may be the reason I haven’t received any crash reports from you.