I opened an existing file, saved it under a new name (ClampHead.3dm), then spent several hours editing it.
There was a display freeze, then recovery, with the message that the display driver have failed to respond in the required time and Windows had reset it - something that seems to happen far to often with the latest NVIDIA drivers.
Other applications continued on, but Rhino reported it had a problem and had to close.
Latest release of Rhino 5 64-bit:
Version 5 SR6 64-bit
Event log application error details:
Faulting application name: Rhino.exe, version: 5.6.31028.18305, time stamp: 0x526ebf38
Faulting module name: opennurbsx64.dll, version: 5.6.31028.18305, time stamp: 0x526ebbc8
Exception code: 0xc0000005
Fault offset: 0x00000000003378e0
Faulting process id: 0x1398
Faulting application start time: 0x01cee1aaeb1b2749
Faulting application path: C:\Program Files\Rhinoceros 5.0 (64-bit)\System\Rhino.exe
Faulting module path: C:\Program Files\Rhinoceros 5.0 (64-bit)\System\opennurbsx64.dll
Report Id: fbfb1857-4e65-11e3-9c6b-0015830cbfeb
Anyway, I reopened Rhino, and there was no prompt about AutoSaved files, and when I opened the file I had been working on, it was back at the original that I had copied from, with none of my edits.
I then looked at the Help info for AutoSave, and found the AutoSave directory. It contained three files, two of which were:
RhinoAutosave.3dm and the other file had modified dates over three months old, but ClampHead_RhinoAutosave(11688).3dm was current, and when I opened it directly with Rhino, it had all my edits in it. I then saved it over the top of ClampHead.3dm, and was able to continue.
The AutoSave files are on the local C:\ drive, while the others are on a network share.
I’ve tried closing and opening Rhino several times, and it doesn’t prompt about AutoSaved files at all, although the files remain in the directory, whether Rhino is open or closed.
Does anyone know what is happening here?