Rhino 8 is creating many .tmp files in folder after failed save attempts

Hi McNeel Team,
I have noticed that over the past few months that Rhino8 has failed to save a file on the first attempt (see image), however it does save on the second attempt. After this Rhino saves a series of .tmp files in the files folder location (see image). Has anyone else experienced this recently? Is it a Rhino thing? or a server thing?


Hi Mark -

I don’t remember recent reports of such behavior.
Please run the Rhino SystemInfo command and copy-paste its output here.
-wim

Rhino 8 SR16 2025-2-11 (Rhino 8, 8.16.25042.13001, Git hash:master @ d0f731de6fe2c5fdcad78ad80faf154307815f18)
License type: Commercial, build 2025-02-11
License details: Cloud Zoo

Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 64GB)
.NET 7.0.20

Computer platform: LAPTOP - Plugged in [99% battery remaining]

Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA RTX 4000 Ada Generation Laptop GPU (NVidia) Memory: 12GB, Driver date: 8-31-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 538.92
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA RTX 4000 Ada Generation Laptop GPU (NVidia) Memory: 12GB, Driver date: 8-31-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 538.92
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port

Secondary graphics devices.
Intel(R) UHD Graphics (Intel) Memory: 2GB, Driver date: 11-26-2024 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- Secondary monitor is laptop’s integrated screen or built-in port

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
GPU Tessellation is: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 8-31-2024
Driver Version: 31.0.15.3892
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 12282 MB

Rhino plugins that do not ship with Rhino
C:\Users\MHOC\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\HLA_RhinoPlugin\0.0.17+40dca1d758669bcd8e1b0c0f661709687c1354a0\HLA_RhinoPlugin.rhp “HLA_RhinoPlugin” 0.0.17.0
C:\Program Files\Enscape\Enscape.Rhino.Plugin-net48\Enscape.Rhino8.Plugin.dll “Enscape.Rhino8.Plugin” 4.3.0.1179
C:\ProgramData\Autodesk\forma-rhino\Rhino8\FormaRhino.rhp “FormaRhino” 0.7.15.0
C:\Users\MHOC\AppData\Roaming\McNeel\Rhinoceros\8.0\Plug-ins\D5LiveSync (e0d5e210-02f6-4ee9-a2b0-1675e225d958)\D5Conv.rhp “D5 Live Sync for Rhino”
C:\Program Files\Chaos Group\V-Ray\V-Ray for Rhinoceros\V7\VRayForRhino.rhp “V-Ray for Rhino”

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.16.25042.13001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.16.25042.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.16.25042.13001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.16.25042.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.16.25042.13001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.16.25042.13001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\BlockEdit.rhp “BlockEdit” 8.16.25042.13001
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

Hi Mark -
Does the behavior persist when you disable all 3rd party plug-ins and restart Rhino?

-wim

Hi Wim,

Yes the behaviour persists when the plug-ins have been disabled, and rhino restarted. The problem also occurs whether I save locally on the C:drive or on the cloud server.
Further to that I received a different error message this time.


Hi Mark -

Does this also happen when you start a new document from a factory-default template, create a simple box, and save? Or is this file-specific?

Did that pop up while saving?
-wim

Hi Wim,

  1. This issue with the .tmp being created is office wide. We use a template file in the office which has various layers in it for practical and workflow reasons, but not all of these projects use that template, so I cannot be sure. I created a file and made a box and saved, and there was no issue. It is difficult to pinpoint exactly when and why it happens because it doesn’t happen on every ‘save’.

  2. Yes, that popped up whilst saving, but only from time to time. When that ‘improper argument’ message pops up it also deletes the original file, and only leaves a .tmp file behind. (whilst one can rename with .3dm and open it as if it were a backup) I have seen the same comments on the forum in the past with no resolution.

Hej Mark -
Note that the creation of a tmp file is a normal step in the process of saving files. It’s a problem when the entire process doesn’t complete as it should. Leaving behind a tmp file and deleting the original are consequences of the process failing somewhere.

Could you toggle the state of these two advanced settings to see if that makes a difference?
→ Rhino.Options.Advanced.UseCompressionWhenSaving
→ Rhino.Options.FileSettings.WriteLocalTempFileWhenSaving

-wim

Hi again, I tested out 'WriteLocalTempFileWhenSaving during this week and it increased save times to around a minute for large files which would normally save in a matter of seconds, but no .tmp files were made as I can see. So success I guess, though not optimal.

I have now turned off ‘UseCompressionWhenSaving’ and i’ll get back to you if I can see any results.

‘Note that the creation of a tmp file is a normal step in the process of saving files’ Do you suspect the problem is outside of Rhino, and perhaps with saving on the server?

Hej Mark -

Yes, otherwise we’d hear from lots of users about this issue.
-wim