3DE / Blender Tool - Export 2D Markers from Blender to 3DE Does Not Work

[david-cattermole]

Problem

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?

Expected behavior:
2D Markers should be able to export from any software that supports .uv files, and import into any importer that supports .uv.

Actual behavior:
The Blender 2D Tracks exporter does not support "undistorted" position data, and the (current) "Import Tracks (MM Solver)" tool in 3DEqualizer always loads undistorted 2D data - there is no option to choose the (in this case) correct "distorted" 2D data.

The undistorted data written to the .uv file is x=0.0, and y=0.0, so the 2D Tracks in 3DEqualizer are loaded at the lower-left of the image.

Steps to Reproduce

1. Open Motion Clip Editor in Blender.
2. Open an image sequence and set the start frame to the frame number in the image sequence.
3. Create 2D Trackers in Blender and track some features.
4. Select 2D Trackers and use "MM Solver > Export 2D Tracks..." button, set a file path and save the file.
5. Open 3DEqualizer, use the menu "3DE4 > File > Import > Import Tracks (MM Solver)", set the file path and click "Ok".

Software Versions

• mmSolver version: mmSolver v0.4.3
• Import 2D Tracks (MM Solver) v1.2
• 3DEqualizer (4r5)
• Blender v3.0 and v3.4 - All supported Blender versions will have this issue.
• Operating System (OS): All supported OSs

[david-cattermole]

The "Import Tracks (MM Solver)" tool for 3DEqualizer has been fixed in 069b508, allowing users to choose Distorted or Undistorted 2D data. By default Distorted is used, because it is assumed that 3DEqualizer will contain the lens distortion values (hence "Distortion" is correct).

Additionally a bug in the Blender "Export Tracks" tool was found that would cause frame misalignment of the 2D data because Blender's 2D Tracks are stored without consideration of the start frame of the loaded image sequence - but mmSolver importers/exporters do. This was fixed in 35271a1.

I have updated the documentation to indicate that setting the correct Start Frame in Blender is important:
https://david-cattermole.github.io/mayaMatchMoveSolver/tools_inputoutput.html#copy-2d-tracks-from-blender

I will post for testing and confirm these fixes work, then release in v0.4.4.