well then I'm pretty sure what the problem is. I suppose you didn't reset scales values before exporting. Try Ctrl-a on your objects, select "Scale and Rotation to ObData". Then, ctrl-n again if needed. Exports. Should work :)CarRepairer wrote:I only convert to triangles now when I export to obj. Even working with quads, when I mirror piece A to piece B, piece B's faces will now have CW vertex winding order while still having outward facing normals. This happens whether I scale -1 or if I use the mirror action. Flipping the normals for the piece does fix the problem in Spring but now it looks bad in Blender. I want it to look correct in both Spring and Blender. Obviously this just a minor problem and I can live with an inside-out arm and leg in Blender without any sleep lost, just hoping for a better solution one day.
I just redownloaded it, works fine now.. ^^Kloot wrote:No, I didn't. The link correctly points to version 1.1 for me, so maybe your browser cache is just stale?
Ho yes it works this way, offsets are local in the exported metadata lua script.Kloot wrote:To solve this I need a favor:
1. Create a model consisting of three unit-sized cube objects (call them A, B, and C)
2. Make B a child of A, and make C a child of B (A <-- B <-- C)
3. Move A to <1, 0, 0>, move B to <2, 0, 0> wrt A*, move C to <3, 0, 0> wrt B**
4. Use v1.1 of the exporter, then pastebin the .obj, .lua, and the .log
* meaning to <3, 0, 0> in global space
** meaning to <6, 0, 0> in global space
So the critical key process is to move piece after parenting them which is really not my workflow and I guess not most of people's workflow.
I mean, when you do a model, you generally do one big single piece. Then you split your model into different pieces and move piece's origins (because the pieces are already in the right place !).
But if you want to parent pieces before moving them, you have to separate pieces, move piece's origins, reset pieces pos to 0,0,0, parent pieces, move pieces and find the right local offset to move pieces where they were before... wow, it's faster to write the metadata script by hand and manually calculate the local offset via subtracting child global pos to parent global pos, isn'it ?
Maybe it can be done in the exporter ?
I mean, a solution could be to export local offset in two ways :
- if you have parented pieces before moving them, keep the way it actually do
- if you have parented pieces after moving them, calculate local offsets by subtracting X, Y, Z child values to parent values
PS : but after all it might be me who have an odd workflow