...in particular, I do not think that an error message is a good solution for a problem. I would better disable that button (or hide it) in case Cycles is not used. What is still missing, I think, is a button that simply put the solver constraint on the camera (without anything else related to adding objects to the scene I mean).

I do not think it can be considered "resolved": the commit considered as the Fix, as far as I understand, works only with Cycles, and I (and I think a lot of people like me) do not understand how to switch the Motion Tracker to Cycles (switching it in the render tab does not work).

@Dalai Felinto (dfelinto) I am wondering if it even makes sense to have an EEVEE setup at this point. As far as I can see EEVEE does not have something like a shadow catcher, nor can collections ins view_layers be set to holdout, which is both kind of important for a working setup. So I would first make it use Cycles.

I have managed to make the Setup_Tracking_Scene operator work without errors by disabling the old BI and layer stuff, now I am trying to make the renderlayer setup work again.
However, it seems as if there are some python bindings missing still.
To make the setup work I am planning to have 2 Viewlayers, Background and Foreground (as was already implemented in the new script), with two collections, "background" and "foreground". In the Foreground viewlayer, the background collection will be set to "holdout", in the Background view_layer the foreground collection will be set to indirect only.
I can make the setup work with the outliner View_Layer menu, however I could not find a way to do that via python. Something like bpy.context.scene.view_layers["Background"].collections["foreground"].holdout = True
That or at least something similar does not seem to exist yet.
Or if it does, maybe someone can give me a hint?

I will have a look

I will have a look. Maybe first just kick out all the old stuff so that at least the basic setup of constraints and background images work. Speaking of which, the whole camera background image stuff doesnt seem to work all that great yet. Footage is always drawn in front of objects, no matter the front/back setting in camera background images. Also the colors are completely off in solid mode.

how about an option to make a simple setup using a shadow catcher plane and just one render layer..? that is often enough to have a working scene

@Sebastian Koenig (sebastian_k) maybe this is something you could help with?

Committed as:

• 7907dfc400182b408e558d9fef1240d9929f8661
• 5d15e68743fc92b41a85ef4180628427ab3b86da
• 5a89dfe06baa2ab96947bb6b5f6c63c4b864fab2

Apart from theming issues we're talking in IRC at this moment don't see stoppers or anything. Good job!

Address issues raised on review.

Final fix for object trackers and regular trackers (they were working for the initial frame only)

Final fix for object trackers and regular trackers (they were working for the initial frame only)

@Campbell Barton (campbellbarton) think this falls in your area?

I think it should lock the reload button and if pressed highlight the ongoing prefetch job percentage with an appropriate message in the bottom panel{F4031466}

ASAN report of the crash btw:

Confirmed (though a bit difficult to reproduce with default settings, since prefetch is nearly immediate with simple video files…).

note atm. only crashes in 2.8 are accepted in the tracker, but had a quick glimpse and D3542 fixes the operator (not the viewport drawing)

In recent versions of Blender we've changed logic in a way that only selected tracks are converted to mesh. This way it's more useful to do partial reconstructions, or to ignore some "helper" tracks from the object.

Full backtrace:

@Philipp Oeser (lichtwerk) Here's the file, all pared down from the original, but has the motion tracking data, and the working constraints.

with the old dependency graph objectsolver_evaluate() is called on file load but not on playback
@Sergey Sharybin (sergey): could you have a look? If its an easy fix, give me a hint, I'll do then

not happening with the new dependency graph btw. ( when you start blender with blender --enable-new-depsgraph )

I can confirm its not working in the provided file.
First findings: if you add another bone constraint in the constraint stack [e.g. copy location] the object solver constraint on the bone will start to work.
(It doesnt really matter what kind of properties you set in the 'other' constraint -- could be inactive/hidden even...)