Operating system: Linux-5.3.0-7625-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44
Broken: version: 2.83 (sub 1), branch: HEAD, commit date: 2020-01-29 14:09, hash: rB9cb7ecefceee
Worked: Maybe a month or two ago?
Short description of error
When a proxy armature's custom property drives an object's hide_viewport or hide_render property, the console spams this warning:
add_relation(Driver -> Driven Property) - Failed, but op_from (OperationKey(type: PARAMETERS, component name: '', operation code: DRIVER, 'hide_render')) was ok add_relation(Driver -> Driven Property) - Could not find op_to (RnaPathKey(id: OBCube, prop: 'hide_render'))
When the armature is not a proxy, the issue is still present, but the above warning is not.
In the case of a simple file, this doesn't seem to cause an issue, but as the file gets more complex, the driver ends up becoming unpredictable/unreliable, and can even result in it locking a mesh as visible or invisible until the driver is simply removed.
Exact steps for others to reproduce the error
- Download attached file
- Link "Collection" collection to a fresh file
- Make proxy->"Armature"
- Pose mode->change the bone's custom properties. "prop" drives object visibility, "prop1" drives a shape key.
- The console spams the warnings only regarding the former.
This functionality will become important for our current project fairly soon, and I don't know of any workarounds.