Hi Robert - are you running V-Ray?
If not, please run the Rhino SystemInfo command and copy-paste the result here.
-wim
I’m not running V-Ray but I did recently install my first plug-in… Xnurbs.
Rhino 6 SR27 2020-6-24 (Rhino 6, 6.27.20176.05001, Git hash:master @
ba2c30de00be5a8b210bc297715204e941911799)
License type: Commercial, build 2020-06-24
License details: LAN Zoo Network NodeWindows 10.0 SR0.0 or greater (Physical RAM: 32Gb)
Machine name: ROBERT-Z97Non-hybrid graphics.
Primary display and OpenGL: NVIDIA GeForce GTX 1080 (NVidia) Memory: 8GB, Driver date: 11-12-2019 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 441.28OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: OnAnti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: HeightVendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 11-12-2019
Driver Version: 26.21.14.4128
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GBRhino plugins
C:\Program Files\Rhino 6\Plug-ins\Commands.rhp “Commands” 6.27.20176.5001
C:\Program Files\Rhino 6\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 6\Plug-ins\RhinoRender.rhp “Rhino Render”
C:\Program Files\Rhino 6\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 6.27.20176.5001
C:\Program Files\Rhino 6\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 6\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\XNurbs (80be33b0-13b2-4ac4-9c77-03829214f9e9)\4.0.0.0\XNurbsRhino.rhp “XNurbs”
C:\Program Files\Rhino 6\Plug-ins\RhinoCycles.rhp “RhinoCycles” 6.27.20176.5001
C:\Program Files\Rhino 6\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 6.27.20176.5001
C:\Program Files\Rhino 6\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 6\Plug-ins\Displacement.rhp “Displacement”
So, ok, if plugins are the culprit, that may very well be it. Can anything be done on the Rhino side, or is it up to each individual plugin maker to issue a “fix”?
Robert -
My uneducated guess would be that it’s up to the plug-in developer to make sure that they leave an unchanged document unchanged as there can be multitudes of ways to make a change and it would be impossible for Rhino to know what’s important and not.
For an educated reply, we should ask @brian for input.
-wim
I’m actually also now noticing Rhino asking me to save a document on quit, when I just manually saved it the moment before.
I’m going to have to look into how to uninstall this plug-in and see if things go back to normal…
Disabling the plug-in without uninstalling should be sufficient for testing.
Thank you!
Yes, I can now confirm that the trial of @XNurbs was what caused my “save change” popups to happen!
1 Like
Since 2 weeks or so I have that problem too in V6 and the WIP. Not each time but often enough. And yesterday I deleted the content of a file somehow by confirming the Save-Dialog with “Yes”. But I could not repeat that “bug”. P.S.: I never had V-Ray, XNurbs or any Evolute Tools installed.
Edit: I could repeat it. Probably I’m too focused on the command line and not reading what the pop-up dialogs are telling me. Anyways a serious bug I think.
It happens pretty reliable after starting the computer and opening Rhino for the first time. So today I tried Rhino V6 in Safe Mode et voila:
Looks like this ball is back in McNeel’s court.
Jess, I just added a bug to our list that this occurs when the BoxEdit panel is shown. Is that a panel you have visible?
1 Like
Hi Steve,
No BoxEdit is not open and I have not used it for months.
This bug looks hard to trap. Let me know if I can help somehow…
Jess
FYI-- Occurs when these Panels are open
in Version 6 SR30 (6.30.20238.13311, 8/25/2020)
Like @Jess, I “…never had V-Ray, XNurbs or any Evolute Tools installed.”
Hmm, got it with just Properties and Layers open.
Tomorrow I’ll start without any panels…
Edit: Happens also without any panels open.
1 Like
@stevebaer I’ve given up hope for a fix, so I have a request for a workaround. Could you add an advanced setting where we can add minimum amounts of changes before the file is marked changed? I hope that this way I can finally forget about this dialog box. 
Edit: maybe combine it with the time a file is open. It’s obvious that a file just opened isn’t changed
That’s more work than fixing the issue. Tim fixed the box edit bug this morning in V7 that we discovered over the weekend. I think I can wire up a test command to signal when the document is initially marked as modified so we can figure out exactly when this happens
Well this is a bug that I have been suffering from for years. So I prefer to have more options to circumvent this dialog. I can’t disable my plugins that’s not a solution. And if those plugins would change something when the file opens, Rhino should be intelligent enough that this happens on opening. A file that is open for 3 seconds is obviously not a changed file.
1 Like
More options is fine for the future. I want to figure out how to identify the current issues first so we can fix them.
Yes please if you could add a diagnosis tool that would be a great first step. Hope this tool can pinpoint exactly which plugin caused what change to the doc. Just to make sure: I get this dialog for years on empty new files as well as when I open an existing file (making no changes) and then trying to open another or starting a new.
Oh man, someone already wrote a diagnostics tool but it just doesn’t print information to the right spot… I’ll get this tuned up today.
1 Like
I don’t think the initial implementation will pinpoint the exact plug-in, but I can get something in that will be a good start down this path to help figure things out.
The next available build will include a test command named TestDocModified. This test command already exists, but doesn’t really do anything due to the way it was coded up. With the changes I made, after running this command Rhino will report when the document’s modified flag is set on the command line. This can be used to start tacking down the cause of this bug.
2 Likes