In the WIP 9.0.25315.12306, Exporting .Obj is blocked .
both my regular Macro and manually exporting do not work.
a very strange “you do not have permission” massage popup when manually trying to export.
Exporting is fine in R8
Hi Akash -
Is that also the case when you are exporting a simple box from a new file?
Can you post the settings that you are using when exporting?
-wim
Hi @wim
thanks.
yes it fails also with just a box in a new file.
here is the command history [ this is for my button that runs that export as a macro and works fine in R8]
Command: Box
1 closed extrusion added to selection.
Command: -Export
Command: “/Users/akashlotan/Library/CloudStorage/Dropbox/Mac (2)/Documents/ZbrushWork/From-Rhino.obj”
Failed to save as /Users/akashlotan/Library/CloudStorage/Dropbox/Mac (2)/Documents/ZbrushWork/From-Rhino.obj.
Now I tried manually to export with a different name and a different location and it worked But I didn’t change any of the export settings…. so something perhaps with the auto overwrite in the Macro is not working [just guessing ]. the Macro overwrite the file so I can quickly send to Zbrush [where I have a button with a macro to import it in one click too.
Any idea ? [I use this all the time for fast moving mesh parts between rhino and ZB so it’s really important here]
I’m trying to open this Macro to see how it is structured… but can’t seems to find how to do this in the WIP?
How about the file path. Do the parens in the folder path cause the problem?
it works fine in R8 so as far as I can tell it is something in the Wip that’s makes it fail.
I’d like to open that macro to check if it’s the same as in 8 [perhaps it got messed up when copied from R8] But I can’t [remember how to ] open it. ?
I am getting errors also. We are taking a closer look.
1 Like
In my testing new Rhino WIP out on Tuesday seems to fix this. Get and update and see if it works for you also?
thanks @scottd
I just tested and it’s failing here with my export Macro. Manually it is also failing [same as before]
I’m on 9.0.25343.14056, 2025-12-09
Can we try other things:
- Can another file format be written to the same spot. Something like STL?
- Can the OBJ be written to a local file. The current folder is a Dropbox folder.
- Can Rhino write a 3DM file be written?
We need to remove the variable until it works, then add steps back to see where the problem is.
yes
it’s not a dropbox folder it’s a local folder on my computer! I never save files directly to DB. it is doing it’s sync after the files are saved locally
what you see as the strange path [perhaps it looks like this for PC users..?]. is simply the way DB is integrated within the MacOS file system.
for example a path like this
is just my local Download folder. [with a DB backup and sync in the background
Yes. It’s only failing with OBJ
And to say again. In R8 the OBJ is saving in that location without an issue with the same Macro. or manually via the Export command
I understand DB does sync. Although in some cases if we are not careful, the sync happens in the middle of the process and it confuses Rhino. For instance the OBJ might get written, but then the MTL file also needs to be written. But if DB Sync gets active in the middle of that it can get confused.
One thing OBJ does is write multiple files, I wonder if that is the problem?
The challenge here is we are not seeing the problem. Trying to change the variables on your side to determine what part of the setup you have.
Since Rhino 8 has no issue. this can’t be a DB related problem I would imagine.
But I can test this since DB in not syncing all the computer. only certain folders….
I’ll try and report back
So I was able to save that OBJ box on a part of the computer that does not have a DB Path.
So it seems the 9WIP OBJ does not like DB integration . But Rhino 8 is totally happy to work with it. So what is the difference in the way the WIP is saving the OBJ compare to R8 ?
