Inconsistent behavior with armature deformation of objects disabled by driver #80977

New Issue

Jonathan Albert · 2020-09-20T01:09:15+02:00

Jonathan Albert commented

2020-09-20 01:09:15 +02:00

System Information
Operating system: Linux-5.4.0-47-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100

system-info.txt

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-18 22:24, hash: 7b9e47a35e (tested with factory settings)

(Current 2.83 LTS is also broken.)

Short description of error
A mesh object deformed by an armature modifier does not appear to be disabled correctly if disabled by a driver, even if the driver is a trivial driver with no dependencies (eg. a scripted expression of "True" or "1" with no variables). While the mesh object will be made invisible in the viewport, Blender seems to calculate the object's deformation anyway when the armature is posed or transformed, resulting in massive viewport performance degradation if the hidden mesh is complex.

This seems like a bug to me, because disabling the object manually works as expected: as soon as the mesh vanishes, I can pose the armature without framerate issues.

Disabling the armature modifier on the complex object does not resolve performance issues (although this appears to be the case regardless of visibility). Deleting the armature modifier does, however. I assume there's something funky with the depsgraph, but I'm not familiar enough to know how to approach this.

(My use case here is being able to hide elements of a linked/proxied character without those elements incurring heavy performance penalties; as of now I'm unable to feasibly use complex characters without having to append them, resulting in massive file bloat. EDIT: I did manage to find a workaround. If processing the modifier stack is unavoidable, then a Mask modifier can be placed at the top of the stack so that the Armature, etc. modifiers have no work to do as an alternative. This does require creation of another vertex group containing all vertices, though, which is a little messy.)

Exact steps for others to reproduce the error

Open attached .blend

{F8900847}

Either perform some transformation on the armature object or attempt to transform the bone in pose mode. Notice viewport performance tanks, despite ComplexObject being hidden via driver with constant value 1 (i.e. no obvious dependencies on ANY datablock), seemingly implying deformation is still being computed while the mesh's object is disabled. (Subdiv level on the complex object is tuned for my underpowered computer, so may need more subdivision levels to be apparent on a modern workstation).

{F8900863, size=full}

Delete the driver on ComplexObject's visibility.

{F8900865, size=full}

Perform another transformation of armature object or pose bone; notice viewport performance is back to normal despite no changes in visibility.
Set ComplexObject's visibility back to True. The object is now visible, but viewport performance is now identical to what it was when hidden via driver.
{F8900867, size=full}

**System Information** Operating system: Linux-5.4.0-47-generic-x86_64-with-debian-bullseye-sid 64 Bits Graphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100 [system-info.txt](https://archive.blender.org/developer/F8900908/system-info.txt) **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-18 22:24, hash: `7b9e47a35e` (tested with factory settings) (Current 2.83 LTS is also broken.) **Short description of error** A mesh object deformed by an armature modifier does not appear to be disabled correctly if disabled by a driver, even if the driver is a trivial driver with no dependencies (eg. a scripted expression of "True" or "1" with no variables). While the mesh object will be made invisible in the viewport, Blender seems to calculate the object's deformation anyway when the armature is posed or transformed, resulting in massive viewport performance degradation if the hidden mesh is complex. This seems like a bug to me, because disabling the object manually works as expected: as soon as the mesh vanishes, I can pose the armature without framerate issues. Disabling the armature modifier on the complex object does not resolve performance issues (although this appears to be the case regardless of visibility). *Deleting* the armature modifier does, however. I assume there's something funky with the depsgraph, but I'm not familiar enough to know how to approach this. (My use case here is being able to hide elements of a linked/proxied character without those elements incurring heavy performance penalties; as of now I'm unable to feasibly use complex characters without having to append them, resulting in massive file bloat. EDIT: I did manage to find a workaround. If processing the modifier stack is unavoidable, then a Mask modifier can be placed at the top of the stack so that the Armature, etc. modifiers have no work to do as an alternative. This does require creation of another vertex group containing all vertices, though, which is a little messy.) **Exact steps for others to reproduce the error** # Open attached .blend ``` {F8900847} ``` # Either perform some transformation on the armature object or attempt to transform the bone in pose mode. Notice viewport performance tanks, despite ComplexObject being hidden via driver with constant value 1 (i.e. no obvious dependencies on ANY datablock), seemingly implying deformation is still being computed while the mesh's object is disabled. (Subdiv level on the complex object is tuned for my underpowered computer, so may need more subdivision levels to be apparent on a modern workstation). {[F8900863](https://archive.blender.org/developer/F8900863/image.png), size=full} # Delete the driver on ComplexObject's visibility. {[F8900865](https://archive.blender.org/developer/F8900865/image.png), size=full} - Perform another transformation of armature object or pose bone; notice viewport performance is back to normal despite no changes in visibility. - Set ComplexObject's visibility back to True. The object is now visible, but viewport performance is now identical to what it was when hidden via driver. {[F8900867](https://archive.blender.org/developer/F8900867/image.png), size=full}

Jonathan Albert commented

2020-09-20 01:09:15 +02:00

Added subscriber: @jabblerty

Stephen Swaney commented

2020-09-20 03:16:33 +02:00

Added subscriber: @StephenSwaney

Germano Cavalcante commented

2020-09-23 22:19:24 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-09-23 22:19:24 +02:00

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

Germano Cavalcante commented

2020-09-23 22:19:24 +02:00

There are some known issues with modifiers updating even though they are disabled by driver.
I don't know if it is related since in this case it is the visibility of the object with a modifier that is disabled.
So I am confirming it as a different bug for now.

There are some `known issues` with modifiers updating even though they are disabled by driver. I don't know if it is related since in this case it is the visibility of the object with a modifier that is disabled. So I am confirming it as a different bug for now.

Sybren A. Stüvel commented

2020-09-24 16:23:57 +02:00

Closed as duplicate of #76257

Sybren A. Stüvel closed this issue

2020-09-24 16:23:57 +02:00

Sybren A. Stüvel commented

2020-09-24 16:24:34 +02:00

Added subscriber: @dr.sybren

Sybren A. Stüvel commented

2020-09-24 16:24:34 +02:00

From what I can see, this describes the same issue as #76257 (Disabled objects still get evaluated if there is a driver on their hide_viewport property.).

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

Inconsistent behavior with armature deformation of objects disabled by driver #80977

Open attached .blend

Delete the driver on ComplexObject's visibility.