When using the Roblox Studio explorer’s “right click” → “Export Selection…” .obj exporter, if objects aren’t positioned close to 0, 0, 0 (the world origin) the resultant .obj file seems to suffer from floating-point precision issues.
Despite this mug (composed of a single meshpart) only being 2,000 studs away from the origin and looking fine in studio, if you export it out into an .obj and look at it in blender, it’s vertices seem to suffer characteristic “blocky” floating-point precision errors that objects in roblox usually only suffer from when they’re placed well over 2,000 studs away from the origin.
This makes interoperability unnecessarily frustrating when working with especially meshes in studio - I have to bring every mesh I export to the origin point before export to be able to work on it, and then I have to position it back in the spot it was in before.
Expected behavior
If the mesh looks fine in studio, then I would expect the exported mesh to look fine when I bring it into other 3d software.
This has been an ongoing issue for many, many years to my knowledge. It’s something I’ve encountered before, but I didn’t realize how much of an inconvenience it was until working more extensively with Roblox Studio, can get frustrating sometimes when you just wanna make a quick export on the spot.
Exporting to obj also sets the world-origin (0,0,0) as the .obj file’s center; making it quite annoying to edit in software such as Blender (since the default pivot is at 0,0,0, far away from the actual object). Meaning there is probably going to be some level of precision issues since the objects are actually offset by that amount (or maybe it is just the pivot, please do correct me if I’m wrong here )
Albeit the issue is much more obvious in your exported file rather than in Studio, so there is certainly something else happening, too.
Hi @144hertz and @Abcreator , thanks for the reports. Apologies for all the frustration this has caused you.
If we could kindly ask for a litttttle patience here – we’re currently working on getting out the public glTF exporter which should help alleviate these issues!
Expect the public glTF exporter around H1 2025.
We’re also currently contemplating a rewrite of the OBJ exporter to follow suit if people still find value in the OBJ exporter.
I’m closing this issue for the moment, please come bug us about this if the glTF exporter falls short of your expectations.
)