Simulate Early, Simulate Often... In Rhino
Tags:
James,
When there is SnS data attached to the file and our plug-in is loaded, Rhino uses our plug-in to read/write the SnS data from/to the file. You can disable our plug-in by renaming ScanAndSolve.rhp to something else temporarily so Rhino doesn't load it automatically.
I've seen your crash reports, but I have been experiencing difficulty duplicating the crash. If our plug-in crashes, it seems the SnS data is not written into the model file. It is possible there is some corruption in the file that causes SnS to choke. Can you email me the problem model separately?
Thanks,
Michael
James,
The latest beta (version2011.2.22) of Scan&Solve is now available for download. I think I've fixed a crash-inducing bug. Please try it out and let me know.
Thanks,
Michael
Ray,
Can you please send me the file so I can attempt to diagnose the problem?
Thank you,
Michael
Thanks Mike.
Unfortunately, in my frustration I kept trying to load the damaged file by ignoring the damage and was able to recover most of it, but the last model was missing. I saved the file off after recovery to un-corrupt it. Further examination of the file revealed that other models within the Rhino 4.0 file still retained S&S data still intact. Opening old data using S&S worked fine without crashing upon exit. I did not try to resolve new data yet, afraid of what might occur.
I will take special precautions before I attempt another S&S run, since I had not backed up the file prior to losing data and my knees are a bit weak now. In the mean time, thanks for your quick response. And perhaps it was other than your program that crashed the file. It did resolve stress information, but upon saving the file in Rhino, that was when the damage occured.
Regards, Ray
© 2025 Created by Michael Freytag.
Powered by