It means that so far, you’re the only one that has had a negative impact, at least that I’m aware of. It could be that not very many people use step export or it could be that it’s working ok for others. I guarantee if it was a large scale problem I’d be hearing about it. Is this happening for all of your exports to step or only with particular models? For instance, if you make a very simple model, like a box, and export to step, does it still have the problem?
@tim this is the same technique that I wrote for saving 3dm files to network locations and couldn’t turn the feature on by default because of unknown failures for systems like Gianpietro’s.
We should probably key your file writing technique off of the same advanced setting as I am using.
1 Like
Hi @tim
thank you, first of all. To answer to your questions:
YES, it happens also with VERY simple geometries (i.e. a single BOX)
and
NO, it doesn’t happens with other formats I export frequently, like STL or OBJ (I didn’t test many other formats aside STP, STL and OBJ though)
OK. This is the YT issue to track this. I’ll start in on it today. https://mcneel.myjetbrains.com/youtrack/issue/RH-66270
1 Like
Thank you @stevebaer , this would be a great help, again! These saving issues are a big big hassle, I reckon!
And @tim , I think I was not the only one with these kind of problems in saving 3dm files…and now I suppose not to be the only one facing the same problem in exporting STPs, sincerely.
The problem started with one of the last updates, by the way, so maybe (maybe!) there’s other people, experiencing the same behaviour, which did not reported it yet.
Hi everybody
I installed the RC 7.14 as suggested by @KelvinC in which WriteLocalTempFileWhenSaving is set to “false” by default. Now the error doesn’t appear anymore: the STP file is correctly saved to network drive position. Great work.
One (ok: two) last question(s): nobody of you guys (@KelvinC , @stevebaer, @pascal, etc) has an idea of why this two saving errors happen? And do they happen to some other people, or am I the only lucky one? In this last case I owe you much more beers…
Thank you again and have a good day to everybody.
Gianpietro
1 Like
You are the only user we know of that has this issue. I’m assuming there are many other users out there that this could effect that we don’t hear from.
1 Like
Hi @stevebaer , thanks for the new SR. I will test it this month (I was away from the office for 2 weeks).
*Since 17 October, I tracked my errors more precisely: with writeLocalTempFileWhenSaving=true, I would sometimes fail to save on my local auxiliary drive. With writeLocalTempFileWhenSaving=false, I would sometimes fail to save on my server.
**During my support calls with less experienced staff, I saw the same ‘temporary file could not be renamed’ error pop up, thus confirming that it is happening on other workstations in our office (on the sister server). But settings were not changed on these workstations.
–Regarding the other save errors recently mentioned: I do not experience problems exporting to other formats.
Thanks again and I will report back in 30 days.
@stevebaer
Today I had a save failure on the server, F:\Drive.
Version 7 SR12
(7.12.21313.6341, 2021-11-09)
Commercial
Results of your Debug command TestLocalTempWriteDebug gave me:
Error found: MoveFileExW returned false (err code = 32)
SystemInfo:
Rhino 7 SR12 2021-11-9 (Rhino 7, 7.12.21313.06341, Git hash:master @ 5590153808223b57a9f41516a969fd949aa81bff)
License type: Commercial, build 2021-11-09
License details: LAN Zoo Network Node
Windows 10.0.19041 SR0.0 or greater (Physical RAM: 32Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro RTX 4000 (NVidia) Memory: 8GB, Driver date: 4-8-2021 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 462.31
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1
Secondary graphics devices.
Intel(R) UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 10-28-2020 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- There are no monitors attached to this device!
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: 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: 4-8-2021
Driver Version: 27.21.14.6231
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB
Rhino plugins that do not ship with Rhino
H:\Tools & Libraries\34 - Rhino\04_GH_SETUP\01_PLUGINS\Elefront (GH)\elefront421\ElefrontProperties.rhp “ElefrontProperties” 1.0.0.0
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino7.rhp “Datasmith Exporter” 4.27.0.0
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 7\Plug-ins\RPC.rhp “RPC”
C:\Program Files\Rhino 7\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Users\K.Hinz\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\PanelingTools (6caed836-bc06-4ebc-b1fd-e10886a0dc94)\2018.12.17.906\PanelingTools.rhp “PanelingTools”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\Alerter.rhp “Alerter”
C:\Program Files\Rhino 7\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\Walkabout.rhp “Walkabout”
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\BlockEdit.rhp “BlockEdit” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”
C:\Users\K.Hinz\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\SectionTools\2019.7.29+584\SectionTools.rhp “SectionTools”
That error code resolves to
ERROR_SHARING_VIOLATION
32 (0x20)
The process cannot access the file because it is being used by another process.
Was there some other program using the file you were trying to write to?
Yea, I saw that a few hours later.
The file was open on another workstation when I thought it had been closed; totally my mistake.
I’ll keep looking to isolate the occurrence.
Today I had another temp file cannot be renamed error. And TestLocalTempWriteDebug also returned err code = 32.
This time, I did not have my file opened on a second workstation.
I will keep looking and report again.
Hi @stevebaer
Today another save error, this time to my local auxiliary drive.
I can confidently say that I did not have another instance of this file open.
My resolve is to saveAs, then rename the file after closing down for the day.
Details are below
Results of your Debug command TestLocalTempWriteDebug gave me the same:
Error found: MoveFileExW returned false (err code = 32)
Rhino 7 SR12 2021-11-9 (Rhino 7, 7.12.21313.06341, Git hash:master @ 5590153808223b57a9f41516a969fd949aa81bff)
License type: Commercial, build 2021-11-09
License details: LAN Zoo Network Node
Windows 10.0.19041 SR0.0 or greater (Physical RAM: 32Gb)
Computer platform: DESKTOP (Hosting Remote Desktop session)
Standard graphics configuration.
Primary display: Microsoft Remote Display Adapter (Microsoft) Memory: 0MB, Driver date: 6-21-2006 (M-D-Y).
> Remote Desktop display device with 16 connection(s)
- Windows Main Display using connection #0
- Secondary monitor using connection #1
Primary OpenGL: NVIDIA Quadro RTX 4000 (NVidia) Memory: 8GB, Driver date: 4-8-2021 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 462.31
> Accelerated graphics device with 0 adapter port(s)
- There are no monitors attached to this device!
Secondary graphics devices.
Intel(R) UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 6-1-2021 (M-D-Y).
> Integrated graphics device with 0 adapter port(s)
- There are no monitors attached to this device!
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: 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: 4-8-2021
Driver Version: 27.21.14.6231
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB
Rhino plugins that do not ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo”
H:\Tools & Libraries\34 - Rhino\04_GH_SETUP\01_PLUGINS\Elefront (GH)\elefront421\ElefrontProperties.rhp “ElefrontProperties” 1.0.0.0
C:\Program Files\Rhino 7\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino7.rhp “Datasmith Exporter” 4.27.0.0
C:\Users\K.Hinz\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\PanelingToolsScripts\0.2.2\PanelingToolsScripts.rhp “PanelingToolsScripts” 0.2.7432.20919
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 7\Plug-ins\RPC.rhp “RPC”
C:\Program Files\Rhino 7\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino 7\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Users\K.Hinz\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\PanelingTools (6caed836-bc06-4ebc-b1fd-e10886a0dc94)\2018.12.17.906\PanelingTools.rhp “PanelingTools”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\Alerter.rhp “Alerter”
C:\Program Files\Rhino 7\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\BlockEdit.rhp “BlockEdit” 7.12.21313.6341
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”
C:\Users\K.Hinz\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\SectionTools\2019.7.29+584\SectionTools.rhp “SectionTools”
I wonder if you can tell what process has the destination file open using process explorer
@stevebaer
Does it make sense if I “reactivate” the “fast saving function” and do the same check you suggested to Kevin3 ? The alert that used to appear to me was the same…
Process Explorer gives me the name of the original problem file: 211029_E9_Block.3dm
(I right-click>properties>Rhino.exe to see this window)
However, the file I have open and running at the time of this screenshot is my _saveAs file: 211029_E9_Block_2.3dm
To me, it looks like compute.geometry.exe is blocking my file.
I have seen compute.geometry.exe block files before in the Task Manager.
What version of Hops do you have installed? This was an issue several versions ago that was fixed (or at least I thought I fixed it).
Looks like you have 0.4.1 installed. @will and @Trav the UI for the package manager is not very clear on this subject. It is easy enough to think that 0.10.1 is installed based on the above screenshot.
@kevin3 I believe this old version of Hops may have been the problematic one that you need to either remove or install a newer version over.