Currently it just uses the “render mesh quality” selected which is very annoying if you want to export a certain way, but preview it in another way. (.obj allows you to select)
Also a bug: if you get to this window
then tab out, or open another window it can’t get reopened and rhino is now stuck, so you have to close it with ctrl+alt+delete.
RH-97659 is fixed in Rhino 8 Service Release 35 Release Candidate
Wow you guys are so fast! Any idea about the mesh export options on .glb, or basically on non .obj exports?
Hej Viktor -
I’ve reported this as RH-97724 File IO: glTF: Mesh Settings
The mesh formats that I tried show that dialog. Which one(s) did I miss?
-wim
ye gltf/gltb both show “gLTF Export options” so i assume your fix would cover both cases.
two examples, then the rest below.
.ob
.fbxwhich are very common. (.gltb, .fbx are probably the most common)
but if we look at all of them then:
these DONT have it
.3ds, .3mf, .dae, .fbx, .glb, .gltf, .obj, .ply(also doesnt have dark mode), .stl, .wrl, .x3dv, .xaml,
but these DO have it:
.amf, .x, .gts, .lwo, .raw, .usd, .xgl.
So a lot of them have their own little flow/window which is a bit funny (it spreads out features).
I guess they could all get the same unified mesh settings one? (which would make automation from a set configuration easier and not reliant on whichever file you export to have an effect).
edit: and i guess these could include meshes, but i havent checked them
.skp, .kmz, .cd, .rib, .udo, .gf, .slc
Hej Viktor -
Exporting to a format such as .amf goes straight to the mesh settings dialog.
Exporting to a format such as .obj has a lot of other options that appear in a first dialog. When those options are set, the mesh setting dialog opens.
The glTF format has a lot of options, but the mesh settings dialog does not appear when those are set. That is a bug.
That settings are separated into two different dialogs is by design.
-wim
fair enough, ye i also see it on the fbx after that! so ye i guess i was unlucky with .glb not having it haha.
but then what purpose does the “mesh” settings even have on the specific ones that do change to the mesh window like obj/fbx. does thes subd level just carry over to the actual menu, or why is it there? then couldnt it overwrite the “preset” or whatever you might expect to be there? (then why have 2 conflicting menus)
I see a comment on the issue from @Joshua_Kennedy who says (in https://mcneel.myjetbrains.com/youtrack/issue/RH-97724):
“”"
OBJ is another mesh format. If you select render meshes it skips that dialog too. For glTF we went with always deciding to use the render meshes. glTF is a visualization format so I think that makes sense.
“”"
which i think is unfair, and i think it would be great to atleast have an option like the .obj one
the obj mark he’s talking about:
“Is a visualization format” would surely mean you would want control over exactly how it should get exported, especially if you have workflows/export setups for games/other software, there you more than in most cases want very precise control over exactly how the mesh gets generated.
why should how the model is meshed in rhino (for our preview while working/editing) have anything to do with how its exported?
and another thing is its just a file format, it could be used for anything. for example an app i use only accepts .gltf/glb files as import and recently removed the .obj support, and i feel like .glb is a more modern ‘open’ standard for meshes anyway.
I think a large number of users want the exported model to appear in a glTF viewer as close as possible to the way the model looks in Rhino. That’s why it uses the render meshes. That being said I am going to add the render meshes option and mesh options dialog to the glTF exporter to support your use case.
