Man, this thing really couldn’t be more frustrating. I’m not talking about the tracking, I was able to get a solve of less than 1, so I’m happy with that. In Blender, a small cube I placed at the origin, when I scroll through the timeline, looks absolutely perfect, doesn’t slide, doesn’t move at all, in relation to the ground of course.
Then I export an FBX so I can work with it in Modo. Turns out, like I put in a post above, that unless I set the scale to 100, it doesn’t work. Scale 100 is the only way that the virtual camera travels roughly the same distance I traveled when walking with the camera, about 24 meters.
The main problem is that there seems to be some other bug or something in the Blender FBX exporter, because the FBX export looks terrible in Modo, and also in Lightwave. Simply put, the cube at the origin appears out of place, and as I move the timeline cursor ahead, at one point it kinda reaches the origin, after a lot of sliding, and then it keeps sliding to where it’s not at the origin anymore. Like I said, in Blender the cube sticks to the origin perfectly. Some of you may be thinking it’s a frame offset, but no, there was a one frame offset and I already corrected for that. If I don’t compensate it looks even worse, and it still slides. Also, both Blender and Modo are at 24 fps, not 23.98, but 24, and the footage was originally exported from After Effects at 24, and read by Blender as 24 fps.
I also tried exporting Collada, which has given me better results than FBX for certain things, and even though it doesn’t compensate for Blender’s swapped Y and Z axes, I compensated for that in Modo by setting the X axis to -90°. Still the same weird effect.
The fact that Lightwave also shows the same weird behavior makes me think that this is a problem in how Blender exports the file. Do you guys know anything about this, or should I maybe post in another section of the forum that deals with exports?