Page MenuHome

Driven bone's visibility in the outliner has no color(purple) indication of their status.
Closed, ResolvedPublic

Description

System Information
Windows 10 64 Bits.
Graphics card GeForce GTX 1080 Ti.

Blender Version
Broken: version: 2.90 hash: a1c2441390e6

Short description of error
When you add a driver to bone's 'restrict visibility' there is no purple color indication that it's driven in the outliner.

Exact steps for others to reproduce the error

  • Open the demo file.
  • Scrub through the timeline to see the custom property changing its value, and the visibility changing because there is a driver on it.
  • The driven visiblity Icon in the outliner has no purple color for indicating that it has a driver.

Event Timeline

CobraA (CobraA) renamed this task from Driven bones visibility in the outliner has no color(purple) indication of their status. to Driven bone's visibility in the outliner has no color(purple) indication of their status..Sat, May 9, 5:22 AM
CobraA (CobraA) updated the task description. (Show Details)

@CobraA (CobraA) please don't ask questions and report a bug in the same report. I'll try and answer your questions here, and then remove them from the report to make sure it's clear what it means when the report is closed.

why bones don't have 'eye' Icons as a secondary visibility toggle?

I'm not 100% sure, but I suspect this is due to the way the eye icon works. It is not a property of the object, but of its base (that's the thing that links an object to a scene, and what allows it to be visible in one scene but not the other). Since bones don't have such a base, there is no place to store that eye icon's value.

if you drive the bone's 'restrict visibility' then you can't hide it manually per viewport

Correct.

and if it's hidden and you hit 'Alt+H' then unhide again then it gets selected for some reason.

That's just how Blender works. It always selects unhidden bones/objects.

Sybren A. Stüvel (sybren) changed the task status from Needs Triage to Confirmed.Mon, May 11, 11:54 AM

In the 2.83 branch (rB0461727553135f4dee29) and master (rBde53c039adb4b7efe3a) the outliner also doesn't show the puple colour, but the properties panel does show it:

I now realise that the attached demo video is misleading, as the active bone is not the one with the driver on it.

I did some digging in the outliner code, and it seems to be simply not implemented.

@Nathan Craddock (Zachman) @Campbell Barton (campbellbarton) you seem to have worked in the bone-related areas of the outliner. Is this something that's doable? Or shall I file this as a known issue for now?

In the 2.83 branch (rB0461727553135f4dee29) and master (rBde53c039adb4b7efe3a) the outliner also doesn't show the puple colour, but the properties panel does show it:

I now realise that the attached demo video is misleading, as the active bone is not the one with the driver on it.

My bad, the video is from the project while the demo file is the simplified version.

I asked those questions because i didn't know if you guys considere them expected behaviors or bugs/limitations but from your answer it seem impossible to "lift them" due to how Blender works.

@Sybren A. Stüvel (sybren) Yes this is doable, the restriction buttons just need to be connected to the RNA properties.

Partially related question: In fixing this, I noticed a few other visibility toggles would also fail to show keyframes and drivers, is it fine to fix all in a single commit?