I am a college student using Rhino 6 for architecture projects. Late December/early January I purchased Rhino 6 with student pricing because my trial expired. Prior to this, I have never had issues with Rhino whatsoever. All the sudden though, I will be modeling in Rhino and it will crash. It has two different crash behaviors, and I am not sure how to reproduce these behaviors since they do not occur when any one specific task is being performed. They are listed below:
Crash behavior 1:
- While I can still move the mouse, whatever line or reference line connected to the thing I have selected stops moving and then deselects. Mouse clicks stop working (cannot exit, click the windows button, etc) and orbiting around whatever I am looking at still changes the mouse pointer but does not actually move anything. Esc does not work to exit out of the command being performed
- I quickly ctrl+s before the computer freezes completely (saves successfully everytime from what I have observed)
- Keyboard keys stop working (also notice that the seconds on the clock on my taskbar stop ticking around this point)
- Computer completely freezes; screen shows the point when Rhino crashed
- I have no way of using the mouse to exit, I have no way of using the keyboard to alt+F4 or ctrl+alt+del to force out of the freeze
- I am left with no option but to do a hard shutdown of my computer and restart
Crash behavior 2:
- Rhino begins to slow down all the sudden
- Graphics become slow/choppy
- Quickly ctrl+s fearing a total freeze will occur
- Save is successful, but Rhino continues to run super slow/choppy
- Unlike behavior 1, the keyboard and mouse seem to stay working a bit longer so I am able to exit Rhino properly
- If I reenter the file, Rhino becomes even slower and choppier, and I am forced to close the program
- At this point, I do a normal restart (do not need to force it) and the file will open normally after that and then one of the two crash behaviors will appear again randomly, starting the process over again
*This behavior happens far less than behavior 1, but nonetheless still requires a restart to actually be able to use Rhino without issues persisting
I want to note that once I have restarted the computer, there is no crash report and no mention of there being a crash from Rhino. I can open the file like normal and then at some point later, after frequent saves and work that in my opinion is not demanding of the hardware nor Rhino, it decides to crash again and the process repeats. It does not matter what file size; both small and large files have this issue. It does not seem to matter what the display type looks like (shaded, rendered, ghosted, etc…). I work a lot in perspective view, but I remember it crashing even in 2D views as well. The tasks that cause it to crash seem to be simple, but usually involve drawing lines, moving objects, moving the camera and making simple 3D shapes like cubes. The tasks I would consider to be tougher on the computer such as boolean operations and merging of faces seem to be fine and have never been the cause of the crashes.
Again, I have only started having this problem since purchasing Rhino 6 with education pricing. I have the latest graphics driver installed and the latest Windows updates whenever they come out. I have also tried repairing it through the Windows control panel and it fixed nothing even though it said it repaired successfully. The only thing I have not tried that I can think of is reinstalling it, but I worry that I won’t be able to get it back if I uninstall. I also have Rhino on my laptop, but I doubt that would cause a conflict with Rhino and licensing if it is all on my same account. Also worth noting, sometimes after enough of these freeze/restart cycles, my Rhino settings such as object snaps, gumball being turned on, and other personalization settings are reset and it behaves as though I am opening Rhino for the first time, because the announcements/help tab is back open on the right side even though it is something I turn off manually. I had the same exact problem as crash behavior 1 when I was using Adobe Illustrator a few days ago, but using the repair tool seemed to fix that, while repairing Rhino seemed to do nothing, or was a temporary fix if nothing else.
I am really at a loss and the delays that this ridiculuous issue has caused are not good for my workflow and increases the time I spend working on stuff with constant crashes that come without warning. Luckily I am not losing work because I can quickly save before the computer freezes completely, but I would rather have a Rhino 6 software that works correctly 100% without this problem persisting. Are there any solutions?