Motion Paths not working with BlenRig armatures #73686

New Issue

Stephen Hamacek · 2020-02-09T03:30:24+01:00

Stephen Hamacek commented

2020-02-09 03:30:24 +01:00

System Information
Operating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits
Graphics card: NVIDIA GeForce GTX TITAN X OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.133

Blender Version
Broken: version: 2.83 (sub 2), branch: master, commit date: 2020-02-07 22:49, hash: a010d97204
Worked: 2.80 but not since

Short description of error
Armature motion paths not working on BlenRig armatures

Exact steps for others to reproduce the error
Load attached .blend in 2.80--Motion paths work, can be updated etc.
Load in 2.81 or above, Motion trails are visible from saving in 2.80, but create or update them on this rig (or other BlenRig armatures that I'm using), and the trails and keyframe numbers just seem to stack on top of each other at the current bone location. I've tried with simple armatures and non BlenRig character rigs and they seem fine, but Motion Paths seem broken with BlenRig, or Blenrig is broken with Motion paths I guess.

BlenRigMotionTrail.blend

**System Information** Operating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits Graphics card: NVIDIA GeForce GTX TITAN X OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.133 **Blender Version** Broken: version: 2.83 (sub 2), branch: master, commit date: 2020-02-07 22:49, hash: `a010d97204` Worked: 2.80 but not since **Short description of error** Armature motion paths not working on BlenRig armatures **Exact steps for others to reproduce the error** Load attached .blend in 2.80--Motion paths work, can be updated etc. Load in 2.81 or above, Motion trails are visible from saving in 2.80, but create or update them on this rig (or other BlenRig armatures that I'm using), and the trails and keyframe numbers just seem to stack on top of each other at the current bone location. I've tried with simple armatures and non BlenRig character rigs and they seem fine, but Motion Paths seem broken with BlenRig, or Blenrig is broken with Motion paths I guess. [BlenRigMotionTrail.blend](https://archive.blender.org/developer/F8330583/BlenRigMotionTrail.blend)

Stephen Hamacek commented

2020-02-09 03:30:24 +01:00

Added subscriber: @StephenHamacek

Richard Antalik commented

2020-02-11 23:49:00 +01:00

Added subscriber: @iss

Richard Antalik commented

2020-02-11 23:49:00 +01:00

Changed status from 'Needs Triage' to: 'Archived'

Richard Antalik closed this issue

2020-02-11 23:49:00 +01:00

Richard Antalik self-assigned this 2020-02-11 23:49:00 +01:00

Richard Antalik commented

2020-02-11 23:49:00 +01:00

I can confirm this, though this isn't officially supported addon.

I see that you file bugreport in addon repo, so you need wait until it's developers can fix problem or find problem on "our side" so we can fix it.

I can confirm this, though this isn't officially supported addon. I see that you file bugreport in addon repo, so you need wait until it's developers can fix problem or find problem on "our side" so we can fix it.

Philipp Oeser commented

2020-04-16 14:00:07 +02:00

Added subscribers: @jpbouza-4, @lichtwerk

Philipp Oeser commented

2020-04-16 14:00:07 +02:00

@jpbouza-4: Is this something that needs fixing on the blender side?

Philipp Oeser commented

2020-04-16 14:15:13 +02:00

Added subscriber: @Alex_Rom

Juan Pablo Bouza commented

2020-04-16 17:13:44 +02:00

@lichtwerk BlenRig doesn't use coding in the armature, it's a simple armature, so if there anything that is not working with it and blender tools, I guess it should be fixed in Blender.

@StephenHamacek maybe you could provide a test file with just one bone? Like erase all but one bone and see if it keeps happening? Also, have you tried this with the addon turned off?

@lichtwerk BlenRig doesn't use coding in the armature, it's a simple armature, so if there anything that is not working with it and blender tools, I guess it should be fixed in Blender. @StephenHamacek maybe you could provide a test file with just one bone? Like erase all but one bone and see if it keeps happening? Also, have you tried this with the addon turned off?

Philipp Oeser commented

2020-04-17 15:03:04 +02:00

Changed status from 'Archived' to: 'Needs User Info'

Philipp Oeser reopened this issue

2020-04-17 15:03:04 +02:00

Philipp Oeser commented

2020-04-17 15:03:04 +02:00

@jpbouza-4 : thx getting back
@StephenHamacek: will reopen, but please try to find a way to reproduce this in a simpler rig (this would be a great help in tracking this issue down...)

@jpbouza-4 : thx getting back @StephenHamacek: will reopen, but please try to find a way to reproduce this in a simpler rig (this would be a great help in tracking this issue down...)

ALEKSANDR_Romanets commented

2020-04-17 16:49:56 +02:00

In #73686#911396, @jpbouza-4 wrote:
@lichtwerk BlenRig doesn't use coding in the armature, it's a simple armature, so if there anything that is not working with it and blender tools, I guess it should be fixed in Blender.

@StephenHamacek maybe you could provide a test file with just one bone? Like erase all but one bone and see if it keeps happening? Also, have you tried this with the addon turned off?

This also does not work with the addon disabled.

> In #73686#911396, @jpbouza-4 wrote: > @lichtwerk BlenRig doesn't use coding in the armature, it's a simple armature, so if there anything that is not working with it and blender tools, I guess it should be fixed in Blender. > > @StephenHamacek maybe you could provide a test file with just one bone? Like erase all but one bone and see if it keeps happening? Also, have you tried this with the addon turned off? This also does not work with the addon disabled.

Stanislav Ovcharov commented

2020-04-17 17:35:52 +02:00

Added subscriber: @StanislavOvcharov

Stanislav Ovcharov commented

2020-04-17 21:51:05 +02:00

@jpbouza-4 Quick test: Motion path works fine and fast on rigify meta-rig but on blenrig 5 add from armature menu it doesn't work, looks like whole bone's path is on first calculated frame and it calculates much longer than rigify. And there is no difference with blenrig 5 addon on or off. Blender 2.83 Win 8.1

Juan Pablo Bouza commented

2020-04-18 00:50:56 +02:00

Guys, ok, I know what it is, but I don't know why the behavior of blender changed with it.

So, the property is 'Bone Auto Hide' if you disable it as I show in this picture, the motion paths will work again.

https://pasteall.org/pic/2b5915501ca847f7b722064ccafd6776

This is an option that I won't be using in the new BlenRig version I'm working on, to tell you the truth I haven't used it in a while, not even in Spring or the Agent projects. Basically, this option hides the bones depending on the FK / IK state you are in. I really don't know what the motion paths update does behind the scenes, but apparently it doesn't like this auto hide feature.

If you want to fix this permanently, you could press the "expanded" option in that layer tab and you will have a different layer scheme that doesn't use this option.

@lichtwerk in the picture I'm sharing, you can see the function that is causing the problem. I don't know if it is the function itself, the handlers, I don't know and it's not something I'm too familiar with, this is really basic code I managed to put together, but I'm definitely not a coding guy. The file that was first attached in this task contains a py with the function.

So my guess is that something changed in the motion path update code, or in the handlers, I don't know... I suspect that for some reason bones might be getting hidden by the function with the motion path update? Therefore the path is not calculated.

Guys, ok, I know what it is, but I don't know why the behavior of blender changed with it. So, the property is 'Bone Auto Hide' if you disable it as I show in this picture, the motion paths will work again. https://pasteall.org/pic/2b5915501ca847f7b722064ccafd6776 This is an option that I won't be using in the new BlenRig version I'm working on, to tell you the truth I haven't used it in a while, not even in Spring or the Agent projects. Basically, this option hides the bones depending on the FK / IK state you are in. I really don't know what the motion paths update does behind the scenes, but apparently it doesn't like this auto hide feature. If you want to fix this permanently, you could press the "expanded" option in that layer tab and you will have a different layer scheme that doesn't use this option. @lichtwerk in the picture I'm sharing, you can see the function that is causing the problem. I don't know if it is the function itself, the handlers, I don't know and it's not something I'm too familiar with, this is really basic code I managed to put together, but I'm definitely not a coding guy. The file that was first attached in this task contains a py with the function. So my guess is that something changed in the motion path update code, or in the handlers, I don't know... I suspect that for some reason bones might be getting hidden by the function with the motion path update? Therefore the path is not calculated.

Stanislav Ovcharov commented

2020-04-18 06:41:23 +02:00

It did the trick for IK only. Motion path still doesn't work with FK with autohide disabled