hey,
i get the error message above (or in the screenshort) when i try to open a 3dm file ive been working on. the error seemed to appear out of nowhere while exporting views with viewcpaturetofile. rhino crashes instantly on startup - its unusable now.
it does start in safe mode though.
cheers flo
Huh never seen that before…like literally you’re the first person to post an error like that…has there been some sort of crash dump file put on your desktop?
Does Rhino crash if you open without an existing file?
Does Rhino crash if you open a different file?
whoops it just fixed itself… but no, no crash dump file
You’re running Rhino in Safe Mode…so “appear out of nowhere” isn’t really accurate… you switched to Safe Mode, and started getting this error.
Safe Mode disables all OpenGL usage, and the error gets issued when an OpenGL call gets made and Rhino is running in Safe Mode…it’s not supposed to happen, but sometimes paths through the code take unforeseen turns and this message is just indicating that situation.
You cannot get any real work done in Safe Mode… all kinds of things will not work… and certainly none of the Shaded, Rendered, or Technical modes are going to work, since they all require OpenGL.
So let’s address the real issue here… Why isn’t Rhino loading on startup?
When did this start happening?
What version of Rhino are you running?
Did earlier versions work?
What is your hardware configuration?
-J
okay i think i remember this error popping up with rino not in safe mode… it was only after this that i tried recovering the file in safe mode. I might be mistaken though. I know that safe mode is unusable, thats why i posted it on the forum instantly so i could continue working.
when did it start? -rhino crashed during viewcapturetofile
im running rhino8 (latest update i think)
didnt test
an acer aspire 3 on win10 and a i7 16gb
i also had bongo installed which i thought might be the cause, so i uninstalled that and restarted everything. shortly after rhino started normally again. might be correlation not causation though.
as i said it seems to have fixed itself…
cheers flo
Well if you can get into Rhino right now, run “SystemInfo” and post the results…
