0
$\begingroup$

I copy and pasted a driver from a modifier's visibility buttons to an objects visibility buttons, but the resulting visibility is opposite for the object. As in, a driver value of 1 for the modifier results in visibility being true, and for the curve object the same driver value of 1 results in visibility being false. Is this intentional behavior, or is there something I am missing? It doesn't seem to be documented but maybe I missed it. The driver is working, moving the bone to get a driver value of 0 toggles both.

Modifier Driver Object Driver

$\endgroup$
2
  • 1
    $\begingroup$ "Component" here is a little vague-- looks like you mean a modifier, but there are a lot of potential things you could mean, and each could be something different. The driver properties for object visibility don't agree with object visibility text, however. Outputting "true" to object visibility hides objects. I always figured this was more of an interface issue, where the text/checkmark is backwards, too smart for its own good. $\endgroup$
    – Nathan
    Commented Sep 5, 2022 at 23:46
  • $\begingroup$ Fixed it, I meant modifier. $\endgroup$
    – Bloop
    Commented Sep 6, 2022 at 19:53

1 Answer 1

0
$\begingroup$

Seems like the underlying variable is inverted. For modifiers its .show_viewport and for objects its .hide_viewport. Weird.

.show_viewport .hide_viewport

$\endgroup$

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .