Hi Wim, I think it has to do with date and or time.
My sequence of mouseclicks are exactly the same, I open Rhino with a shortcut, making sure the cursor is not on the popup window but somewere else on a Rhino viewport. After the popup vanish, moving the cursor to menu item “Help”, selecting “About Rhinoceros…” and the popup appears with tab “Recent” active. Clicking the most recent file. Exit without saving or doing anything in Rhino.
When opening exactly the same within minutes Rhino do not ask to save.
When wating 24 hours without using Rhino and doing exactly the same, Rhino ask me to save the blank.
For me, with Rhino 6 it DOES happen all the time, whereas with Rhino 7 it does not happen at all.
(both latest releases)
Don’t know if this information is of any help.
It seems to me it has not to do with autosave. Why? I do not use Rhino for professional purpose and the last days I only did open rhino to determine when the problem occurs
This also happens on my Rhino 7 quite often, despite the fact that no changes were made to the scene. Kind of annoying, because the Undo stack is empty anyway.
I was told by McNeel staff “hmmmm, not happening here” and that was the end of it.
This is STILL happening with my files on multiple computers… This is a problem IF you are not paying close attention. Once, (not sure how) I saved the empty file over a file I wanted to open.
@tay.othman from your video it looks like you have some commands that run at start. If so, could you let me know what these commands are? The same question applies for @schultzeworks
Hadn’t reported this because if I go slowly during app startup it doesn’t interfere with my workflow, but:
Sorry for the wordiness… just throwing it all out since this has been hard for you guys to track down.
I see this problem regularly too: perhaps a low single digit percentage of Rhino starts when I pick a file from the (splash screen?)'s recent file tiles. I think it started happening more often on my downgraded laptop than it did before (then current i7 → several gens ago i3).
No UI customization or run on start type scripts. Simple, small models.
There’s a single non-stock plugin installed; all it does it watch object type events (add, select, delete, etc.) without altering the model. It does call calculation commands like area+volume+centroid though.
Between this and some other occasional UI oddities during startup if I do a few things quickly before Rhino has stabilized*, my suspicion would be that there may be at least one race condition during app startup combined with file load that would be hard to deliberately reproduce.
The issue doesn’t show up for me on subsequent file loads or app exits once you’ve gotten past whatever file(s) including the blank one got loaded at startup.
*whether Rhino ‘remembers’ a command line command to open my plugin (one letter and enter with autocomplete, so I can do it extremely quickly during/upon startup), menu clicks, and window drags before it’s completely settled down after file load- also, sometimes it visually seems almost as if I’ve triggered a recent file load after Rhino had decided to open a blank template.
When you see this again, try running the TestDocModified command. This is a test command I wrote a while ago that attempts to record the command the placed the document in a modified state (which is why you get asked to save). The cause very well may not be a command, but this tool could help us track things down.
Oh, Good Catch @stevebaer
Here are my startup commands, the setdimensionlayer modifies the file, so it is expected that I need to save the file before opening my recent file
I opened Rhino 7, did nothing, i.e. got an empty file.
I then did File > Open and was asked if I wanted to save the new/empty/unchanged file.
I hit cancel and then ran your command ‘TestDocModified’
(It was not possible to run the command with the dialog open.)
This is what showed up in my command line:
The reference to Rhino 4 is interesting. This laptop is only three years old, so it never ran Rhino 4.
Anyways, I hope this clue is helpful in tracking down the issue. ALSO > There is no D:\BuildAgent directory on my laptop! (no files were hidden by the OS)
That path is to the low level C++ source code file on a McNeel computer the Rhino 7 was built on. It has nothing to do with Rhino 4 or any file on your own computer.
Why is paste in the command history above? That would be a command that would modify the document.
Dude! I copy and pasted your command, ‘TestDocModified,’ so that’s why you see a paste.
To avoid that issue, I committed it to memory … and it happened again. Same results. Here is the command line readout:
Command: TestDocModified
The current document is marked as modified
– D:\BuildAgent\work\commercial\src4\rhino4\Plug-ins\RDK\RDK\RhRdkDocumentImpl.cpp (line 1726)
At the top of my command line, there are two plug-ins loading.
Loading Bongo 2.0 for Rhino 6.0 version Feb 12 2019 10:00:39
Loading V-Ray for Rhino, version 6.10.03 ( Oct 13 2023 )
Try disabling Bongo and V-Ray from the plug-in manager UI and restart Rhino. Do your test again to see if you are still asked to save. This will eliminate the possibility that those plug-ins are possibly at fault.
Ok, I saw it again. It’s Rhino 8, 8.0.23304.09001.
When starting up, I generally have my hand on the mouse (standard MS three button with scroll, no macros or such mapped), so I’m not sure where “Command: _SaveAs” came from in the command history. It’s interesting that it came before the load, which I got by clicking the icon for that file on the splash screen.
