If the parent_type is set to ARMATURE (instead of using the modifier). The deformations are not shown in the viewport anymore. #69326

New Issue

Michael Nischt · 2019-08-30T13:37:57+02:00

Michael Nischt commented

2019-08-30 13:37:57 +02:00

System Information
Operating system: Ubuntu 19.10 (also Windows 10)
Graphics card: NVIDIA GeForce GTX 765M

Blender Version
Broken: 2.80
Worked: 2.79a

Short description of error
If the parent_type is set to ARMATURE (instead of using the modifier). The deformations are not shown in the viewport anymore. In rendered frames the deformation according to the pose still works.
(Changing to an Armature modifier works. However, we use a custom exporter which relies on models using the parent_type instead of the modifier.)

Exact steps for others to reproduce the error

Take any rigged model (simple auto weighted is fine).
Remove the Armature modifier and set the mesh object's parent_type to armature instead.
Notice that in pose mode the mesh doesn't get deformed in the viewport anymore. (it does rendering a frame.)

**System Information** Operating system: Ubuntu 19.10 (also Windows 10) Graphics card: NVIDIA GeForce GTX 765M **Blender Version** Broken: 2.80 Worked: 2.79a **Short description of error** If the `parent_type` is set to `ARMATURE` (instead of using the modifier). The deformations are not shown in the viewport anymore. In rendered frames the deformation according to the pose still works. (Changing to an Armature modifier works. However, we use a custom exporter which relies on models using the parent_type instead of the modifier.) **Exact steps for others to reproduce the error** 1. Take any rigged model (simple auto weighted is fine). 2. Remove the Armature modifier and set the mesh object's `parent_type` to `armature` instead. 3. Notice that in pose mode the mesh doesn't get deformed in the viewport anymore. (it does rendering a frame.)

Michael Nischt commented

2019-08-30 13:37:57 +02:00

Added subscriber: @michael_nischt

Bastien Montagne commented

2019-08-30 15:43:18 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2019-08-30 15:43:18 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2019-08-30 15:43:18 +02:00

Bastien Montagne self-assigned this 2019-08-30 15:43:18 +02:00

Bastien Montagne commented

2019-08-30 15:43:18 +02:00

We do not handle user support on this tracker, only bug reports. User forums like blenderartists.org or blender.stackexchange.com and our devtalk should be used for that matter.

Parenting to armature with ARMATURE type is used to parent objects to bones, not to perform skined deformation. You need the modifier for that.

We do not handle user support on this tracker, only bug reports. User forums like [blenderartists.org](http:*blenderartists.org/) or [blender.stackexchange.com](http:*blender.stackexchange.com/) and our [devtalk](https://devtalk.blender.org) should be used for that matter. Parenting to armature with `ARMATURE` type is used to parent objects to bones, not to perform skined deformation. You need the modifier for that.

Michael Nischt commented

2019-08-30 15:49:22 +02:00

Hi Bastien,

I'm sorry but I think you are wrong. It is a bug report.

I think you are confusing it with the parent_type set to BONE where you also specify the armature in addition to a bone. That one still works just fine in the viewport.

At least in 2.79 you don't need a Armature modifier and according to the UI it's still the same in 2.8.
Further ARMATURE still part of the 2.8 API ( https://docs.blender.org/api/current/bpy.types.Object.html#bpy.types.Object.parent_type ).

I know most people use the modifier instead of the parent_type. However, the parent_type is much easier to export and since it still works in all places except the viewport I also wouldn't expect the functionality to be planned for removal and other parts like rendering had been missed.

Best,
Michael

Hi Bastien, I'm sorry but I think you are wrong. It is a bug report. I think you are confusing it with the `parent_type` set to `BONE` where you also specify the armature in addition to a bone. That one still works just fine in the viewport. At least in 2.79 you don't need a Armature modifier and according to the UI it's still the same in 2.8. Further `ARMATURE` still part of the 2.8 API ( https://docs.blender.org/api/current/bpy.types.Object.html#bpy.types.Object.parent_type ). I know most people use the modifier instead of the parent_type. However, the parent_type is much easier to export and since it still works in all places except the viewport I also wouldn't expect the functionality to be planned for removal and other parts like rendering had been missed. Best, Michael

Michael Nischt commented

2019-08-30 15:49:35 +02:00

Changed status from 'Archived' to: 'Open'

Michael Nischt reopened this issue

2019-08-30 15:49:35 +02:00

Bastien Montagne removed their assignment 2019-08-30 17:01:28 +02:00

Bastien Montagne commented

2019-08-30 17:01:28 +02:00

Added subscriber: @Sergey

Bastien Montagne commented

2019-08-30 17:01:28 +02:00

bug_update_virtual_armature_modifier.blend

OK, my bad. Think that is an update/DEG issue, since this implicitly generates a 'virtual' armature modifier, am pretty sure the necessary links are not made in DEG then, hence update is not done when editing the pose. You can see that by posing the bone, then selecting the cube and switching in/out of Edit mode, then the cube takes the current bone's pose.

I will try to check on that, but maybe @Sergey also have some clues here?

[bug_update_virtual_armature_modifier.blend](https://archive.blender.org/developer/F7710924/bug_update_virtual_armature_modifier.blend) OK, my bad. Think that is an update/DEG issue, since this implicitly generates a 'virtual' armature modifier, am pretty sure the necessary links are not made in DEG then, hence update is not done when editing the pose. You can see that by posing the bone, then selecting the cube and switching in/out of Edit mode, then the cube takes the current bone's pose. I will try to check on that, but maybe @Sergey also have some clues here?

Michael Nischt commented

2019-09-02 21:53:56 +02:00

Probably already clear to you guys since your looking for the missing dependency trigger but just in case: it seems obj.data.update() forces an update of the viewport.

Probably already clear to you guys since your looking for the missing dependency trigger but just in case: it seems [obj.data.update() ](https://blender.stackexchange.com/questions/150303/blener-2-8-using-parent-type-armature-instead-of-the-modifier-seems-to?noredirect=1#comment256966_150303) forces an update of the viewport.

blender-admin commented

2019-09-03 10:48:29 +02:00

This issue was referenced by 8a7a7af627

This issue was referenced by 8a7a7af627b89e67b12f9bc4ae9e175c397961ba

Sergey Sharybin commented

2019-09-03 10:49:21 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2019-09-03 10:49:21 +02:00

Sergey Sharybin self-assigned this 2019-09-03 10:49:21 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

If the parent_type is set to ARMATURE (instead of using the modifier). The deformations are not shown in the viewport anymore. #69326

If the `parent_type` is set to `ARMATURE` (instead of using the modifier). The deformations are not shown in the viewport anymore. #69326