Motion Tracking Object Solver Constraint doesn't work as Bone Constraint #53691

New Issue

Matt Hoecker · 2018-01-03T20:50:16+01:00

Matt Hoecker commented

2018-01-03 20:50:16 +01:00

Windows 10
GTX970
16GB RAM

Bottom Line: Applying an object solver as a bone constraint does not change the bone's location/rotation/scale during animation (it doesn't seem to affect it).

NOTE:Sorry for all the edits, I'm just continuing to add details and clarifying as I felt was needed. Hopefully nobody takes issue to the long list!

(<-This was accidentally linking to a different post, that has no relevance to this one, so I put it in code tags, however the link to that unrelated post still exists at the bottom of this page.)

It doesn't work in 2.78 or 2.77 official builds.
~~It may work in Blender 2.78 (I'm downloading a 2.78 and 2.77 build now to test) as~~ I have an older file where I have a working object track constraint on a bone. See below.

It is entirely possible I'm missing a step, but I was able to set this up (I don't remember how long ago) and it worked, and following the steps below in 2.79-2.77, it does not. I'm not 100% sure if it's a bug or I'm making an error. Hopefully it's just me making an error!

When the object solver constraint is added to the bone, it causes the location of that bone to initially change indicating to me that the solver is applied and is having an affect on the bone, however no motion happens on the bone as animation is played (it doesn't continue to follow the tracked object). The same solver applied to a cube is working perfectly. I have attached a file that I hope will still work without the footage attached. If not, I'll render a proxy of the footage.

I have a project from an earlier version (I don't remember when) that has a working object solver constraint on a bone, and when loaded into 2.79 the constraint works. If I delete that constraint and then add it again, even in 2.79, once set to the proper tracker, it still works and affects the bone justas it should.

Also, as a weird side note that may help diagnose the problem, when I use this older file in which the constraint works, and I try to bake that constraint to an F-Curve I get an

Motion Tracking constraint to be converted not found

error. So maybe some mix up or regression in syntax between ~~2.78~~ an older version and 2.79? ~~I cannot say for 100% sure that it works in 2.78. I'll try to download 2.78 and test this there as well.~~

Based on a (as simple as possible) attached .blend file with minimum amount of steps

{F1682547}

In this file, all the tracking is already set up. It shows that the constraint works on the cube, but doesn't on the bone as a bone constraint.

To do it from a fresh file:

Load footage into motion tracker.
Add an object track and place points and track and solve.
Add camera solver constraint to camera (required for object track constraint to work)
Add an armature with at least one bone. Number of bones doesn't matter (I tried one or multiple).

Add an object solver as a bone constraint.

Bone jumps to new location.

Play animation

Bone doesn't move with motion tracker.
Add a cube.
Apply object solver
Cube moves with object solver as it should.

Hopefully this all makes sense, let me know if you need any clarification!

Windows 10 GTX970 16GB RAM Bottom Line: Applying an object solver as a bone constraint does not change the bone's location/rotation/scale during animation (it doesn't seem to affect it). NOTE:Sorry for all the edits, I'm just continuing to add details and clarifying as I felt was needed. Hopefully nobody takes issue to the long list! ```Doesn't work in Blender 2.79 (5bd8ac9) or 2.79.1 Build 2018-01-01 14:02 (e59cf13) or 2.78, 2.77 but did work at some point as I have a file that has a object solver constraint as a bone constraint. ``` (<-This was accidentally linking to a different post, that has no relevance to this one, so I put it in code tags, however the link to that unrelated post still exists at the bottom of this page.) It doesn't work in 2.78 or 2.77 official builds. ~~It may work in Blender 2.78 (I'm downloading a 2.78 and 2.77 build now to test) as~~ I have an older file where I have a working object track constraint on a bone. See below. It is entirely possible I'm missing a step, but I was able to set this up (I don't remember how long ago) and it worked, and following the steps below in 2.79-2.77, it does not. I'm not 100% sure if it's a bug or I'm making an error. Hopefully it's just me making an error! When the object solver constraint is added to the bone, it causes the location of that bone to initially change indicating to me that the solver *is* applied and *is* having an affect on the bone, however no motion happens on the bone as animation is played (it doesn't continue to follow the tracked object). The same solver applied to a cube is working perfectly. I have attached a file that I hope will still work without the footage attached. If not, I'll render a proxy of the footage. I have a project from an earlier version (I don't remember when) that has a working object solver constraint on a bone, and when loaded into 2.79 the constraint works. If I delete that constraint and then add it again, even in 2.79, once set to the proper tracker, it still works and affects the bone justas it should. Also, as a weird side note that may help diagnose the problem, when I use this older file in which the constraint works, and I try to bake that constraint to an F-Curve I get an ``` Motion Tracking constraint to be converted not found ``` error. So maybe some mix up or regression in syntax between ~~2.78~~ an older version and 2.79? ~~I cannot say for 100% sure that it works in 2.78. I'll try to download 2.78 and test this there as well.~~ **Based on a (as simple as possible) attached .blend file with minimum amount of steps** {F1682547} In this file, all the tracking is already set up. It shows that the constraint works on the cube, but doesn't on the bone as a bone constraint. To do it from a fresh file: - Load footage into motion tracker. - Add an object track and place points and track and solve. - Add camera solver constraint to camera (required for object track constraint to work) - Add an armature with at least one bone. Number of bones doesn't matter (I tried one or multiple). # Add an object solver as a bone constraint. - Bone jumps to new location. # Play animation - Bone doesn't move with motion tracker. - Add a cube. - Apply object solver - Cube moves with object solver as it should. Hopefully this all makes sense, let me know if you need any clarification!

Matt Hoecker commented

2018-01-03 20:50:16 +01:00

Added subscriber: @MatthewHoecker

Matt Hoecker changed title from ~~Motion Tracking Object Solver constraint doesn't work as bones~~ to Motion Tracking Object Solver Constraint doesn't work as Bone Constraint

2018-01-03 20:51:12 +01:00

Philipp Oeser commented

2018-01-05 18:25:06 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2018-01-05 18:25:06 +01:00

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...)

@MatthewHoecker: could also be helpful if you could share the other .blend you mentioned (the one where the object solver constraint on the bone was actually working). Could you post this here?

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...) @MatthewHoecker: could also be helpful if you could share the other .blend you mentioned (the one where the object solver constraint on the bone was actually working). Could you post this here?

Philipp Oeser commented

2018-01-05 18:45:31 +01:00

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

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

Sergey Sharybin was assigned by Philipp Oeser

2018-01-05 19:12:07 +01:00

Philipp Oeser commented

2018-01-05 19:12:07 +01:00

Added subscriber: @Sergey

Philipp Oeser commented

2018-01-05 19:12:07 +01:00

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

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

Matt Hoecker commented

2018-01-05 23:37:55 +01:00

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

Object Constraint Working Test.blend

@lichtwerk Here's the file, all pared down from the original, but has the motion tracking data, and the working constraints. [Object Constraint Working Test.blend](https://archive.blender.org/developer/F1711767/Object_Constraint_Working_Test.blend)

blender-admin commented

2018-01-09 14:27:19 +01:00

This issue was referenced by f5d64b59f5

This issue was referenced by f5d64b59f5152114cfa25a2b7433ed25204cb149

Sergey Sharybin commented

2018-01-09 14:33:20 +01:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2018-01-09 14:33:20 +01:00

Sign in to join this conversation.

4 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#53691

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Motion Tracking Object Solver Constraint doesn't work as Bone Constraint #53691

Add an object solver as a bone constraint.

Play animation