Blender to 3DE 2D Tracks export issue

[Konstantin W]

Hey!
I'm trying to export Blender tracks using mmSolver_blender_addon (latest release from v0.4.3). It saves/copies tracks without any error into .uv file, but when I try to Import them with Import 2D Tracks (MM Solver) v1.2 .py script inside 3DE (4r5) they got imported without any position animation. All of them are located in the lower left corner without any placement animation even though on the timeline they're displayed as "tracked" markers. I've tried to use older blender version 3.0, but results are the same (as well as Blender 3.4). By the way exported from blender .uv file seems to have correct numbers inside it, but still this structure differs from what I get while exporting a nativly tracked point inside 3DE and reimporting it back with Import 2D Tracks (MM Solver) (this tracked point imports correctly).
Any ideas how to get it work?

[David Cattermole]

Hello,

That's an interesting use case, I haven't tested that yet.

I'll do some investigating and get back to you.

In the mean time, I have a possible (but slightly annoying) workflow to (maybe) workaround the issue.

I think you could copy from Blender, paste into Maya, and then copy from Maya and paste into 3DEqualizer?

That might work.

David

[David Cattermole]

Hello again,

After some initial investigation, I think I can see the issue.

The problem is that the MM Solver Blender Addon writes out zero positions in the .uv file for the "undistorted" 2D Tracking positions, because Blender doesn't support undistorting 2D tracks.

The "Import Tracks" tool in 3DE does not (currently) have the ability to load the "distorted" 2D Tracks from the .uv file, and so the importer is reading the zero positions (which is the lower-left side of the image in 3DE).

If all goes to plan I can release a new version of the "Import Tracks" tool which allows you to choose the "Distorted" or "Undistorted" position data from the .uv file.

I'll have a look tomorrow.

Thanks for reaching out and letting me know of the issue.

David

[David Cattermole]

Hello,

I have also discovered a bug in the Blender exporter, which I've also fixed. The details are here:

https://github.com/david-cattermole/mayaMatchMoveSolver/issues/246

One issue that I found was that when loading image sequences in Blender, the Start Frame starts at "1" by default, even if your image sequence starts at a different number (such as "1001"). That means I've needed to fix the Blender exporter too.

You can see the updated documentation here:

https://david-cattermole.github.io/mayaMatchMoveSolver/tools_inputoutput.html#copy-2d-tracks-from-blender

You can download the latest "Import Tracks (MM Solver) v1.3" tool for 3DE here:

https://raw.githubusercontent.com/david-cattermole/mayaMatchMoveSolver/master/share/3dequalizer/scriptdb/import_tracks_mmsolver.py

For the Blender Addon fix, I'll privately send you a file to test with.

If you're able to test and get back to me and confirm it's working for you, that would be great :D

These fixes will be included in the next release of mmSolver.

Thanks,

David

[David Cattermole]

Hello all,

Just tying up loose ends, the original poster has said that the issue is fixed and the ticket above has been closed.

The updated "Import Tracks (MM Solver) v1.3" is released in mmSolver v0.4.4.beta1 and will be on 3DEqualizer's ScriptDB in the coming days.

The updated Blender Addon can be found in the mmSolver v0.4.4.beta1 release if it's urgently needed

Both updated tools are needed to get a correctly working Blender to 3DEqualizer workflow.

Thanks,

David