It is strange, Other objects export as obj without a problem.
but this gem polysrf fails to export.
I have exported that same object [round diamond polysrf] numerous times in the past…
and i’m having a hard time figuring out why it is failing now. [ on latest SRC here]
Any ideas?
obj_fails.3dm (2.5 MB)
SysIno15:03:25.txt (5.8 KB)
How does this fail for your? Any messages on the command-line? Over at my place this export just fine from Rhino, and imports into Blender:
thanks Nathan
it is strange…
i get this
Again, it is only for this object other stuff export as usual!
I tried also to export the same object from a new empty file and it fails , even when i explode it and just try to export one face, it fails…
I tested with 8.19, and an 8.18 build that is 4 days newer than yours.
Perhaps share screenshots of the different tabs of the export options.
Does the export work if you export to your desktop instead of to dropbox?
I’m not exporting to DropBox, the destination is a folder on my HD.
[also other object export fine]
Note: on Mac because i have dropbox active, it has this files path looking like this, but the files are save to my computer , and only then they are [automatically ] backed up to DropBox
like so
I understand, my point is that Dropbox could be doing something at the same time Rhino is trying to save - or doing something to the file. At least if you have it enabled and syncing.
The question really is: does the export fail also when exporting this as OBJ to your desktop - a folder that is not being synced to a cloud storage ?
Desktop is also backup to DB
only System isn’t. i can try to save to library app support macneel . but i can’t seems to navigate there from the save window.
and again DB only synic to cloud after the file is saved locally not before. and there is no problem with other objects it only this diamond. so it so strange.
From your responses I am unable to determine if you have tried saving to a location that is not being backed up.
The settings look good to me, and I’m able to export here without problems from the 3dm you shared.
yes i tried.
but the save window only let me save in a backed up locations. so i don’t know how to save to a non backup place?
Not sure what you mean. This is the export dialog I see. The green rectangles are where I can change the location
Clicking the drop-down on the right gives
If your save windows looks like
Then click on the arrow head highlighted in the green rectangle.
Doubtful, I was able to export your gem just fine.
thanks
i really do know how to use and navigate in the save window.
the only place i can go to that is not backup in DB is application. [since exposing the other location via Options is not working in the save window.
So here i tried in to save to Application. and it fails too.
I suppose I don’t understand why you wouldn’t be able to browse to other locations. That does not make any sense to me. I have a hard time believing you are not able to select any folder you want, like Desktop, Documents, Downloads and you home folder.
You should not save to /Applications. That is for… applications to be installed to.
there is no problem what so ever to select any of these locations!
I have added above screen shots of the paths.
please see that when one has dropbox active in Mac. [the change happened a few OS ago]
it create a path that has Dropbox in it. but the save is local [and later sync to DB]. this is same for all the non system folders including desktop, download …
But the question here why this one object fails while every other object export without an issue…? [paths are the same]
Yes, or rather: why does it fail for your, as the 3dm you shared exports just fine here. And you have tested with the very same build as I have. FWIW, I am also on a M2 Max. The only difference I can see is that you are on MacOS 15.3.2, I am still on 15.3.1.
edit: have you tried with dropbox syncing turned off/paused?
Guess i’ll just rebuild the standard round brilliant from a chart.
was trying to find it in either .gcs .gem or .asc [so it will auto build in GemCutStudio] with no luck.
all other gemstone in my gem library export fine here.
This strange anomaly has been bypassed by making a new [standard round brilliant cut] object
The problem is still unknown, but i’ll just work with the new gem.
Hi Akash -
FWIW, I found an older thread on this subject and a user reported that using the “Mac OS X” option in the formatting settings solved this on their end…
-wim
