David Cattermole

Hello @ldmoser, My fear with changing the definition of a Marker is conceptual for users (I have always insisted Markers are "2D"), but also pragmatic for the code. Inside mmSolver...

Hello @ldmoser, Sorry for the late response, I've been thinking about this for a few days. Before I continue I should say that I'm unable to implement this feature myself...

The 3DE "Classic" lens distortion model has been added to the node `mmLensModel3deClassic`, with rudimentary support. This is working in the `develop` branch and can be tested.

A custom Marker transform node has been created as part of #106 and is currently in the `develop` branch, ready for release in v0.4.0.

Hey @ktonegawa, Thanks for this! It looks like a good start - first new code of 2022 :) > Should we be taking the entire length of a given scene's...

This feature can be extended to a more general use of "in-memory" calculations, rather than using Maya's DAG network. We should not limit ourselves to only world space attributes and...

Here is the current state of this issue... Lower-level core library: - [x] Construct a flat Scene Graph matching Maya's DAG. - [x] Construct a Scene Graph with hierarchy matching...

Hello @ktonegawa, I think the rig that generated the original error was [this one](https://www.highend3d.com/maya/downloads/character-rigs/c/mr-suruj-for-maya) from the #183 issue. I have tried to re-created the issue with mmSolver v0.3.14 on Maya...

@ktonegawa that makes sense. Perhaps a special check that is run each time the user runs a solve to check if the attributes are connected to a Character Set and...

Current development of this tool has been happening in the `vp_renderer`. https://github.com/david-cattermole/mayaMatchMoveSolver/tree/vp_renderer