Custom property of armature object not up-date visual value with pose bone transorm value #86562

Open
opened 2021-03-14 07:37:58 +01:00 by takeshi funahashi · 8 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40

Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: 02948a2cab
Worked: (newest version of Blender that worked as expected)

Short description of error
Armature object custom property which driven by the armature bone transform value,not change value as visual untill select the property in properties objcet panel
visualupdate.JPG

When I move mouse curser on the property area, it suddenly change value. but when I rotate bone along with X , it not up-date value.
ipdate.JPG

Though value seems up-date correctly (internal) , but when use bone driver to control many property,
like driven propA drive other propB, propB drive shape keys ,, etc,,current behavor make really difficult to check pose bone driver working or not.

Exact steps for others to reproduce the error

  • Open attched file
  • In the 3D View Sidebar, change the bone rotation X value. (This value drive the custom property float value label as "prop". The driver expression only use one variable var = transform channel bone X rotation value).
    it not up-date visual value in object property panell >>custom properties prop value. , until select the prop value area.
    But In driver editor view prop value actually up-date (change with bone X rotation value)

bonedriver.zip

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40 **Blender Version** Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: `02948a2cab` Worked: (newest version of Blender that worked as expected) **Short description of error** Armature object custom property which driven by the armature bone transform value,not change value as visual untill select the property in properties objcet panel ![visualupdate.JPG](https://archive.blender.org/developer/F9890328/visualupdate.JPG) When I move mouse curser on the property area, it suddenly change value. but when I rotate bone along with X , it not up-date value. ![ipdate.JPG](https://archive.blender.org/developer/F9890332/ipdate.JPG) Though value seems up-date correctly (internal) , but when use bone driver to control many property, like driven propA drive other propB, propB drive shape keys ,, etc,,current behavor make really difficult to check pose bone driver working or not. **Exact steps for others to reproduce the error** - Open attched file - In the 3D View Sidebar, change the bone rotation X value. (This value drive the custom property float value label as "prop". The driver expression only use one variable var = transform channel bone X rotation value). it not up-date visual value in object property panell >>custom properties prop value. , until select the prop value area. But In driver editor view prop value actually up-date (change with bone X rotation value) [bonedriver.zip](https://archive.blender.org/developer/F9890338/bonedriver.zip)

Added subscriber: @TakeshiFunahashi

Added subscriber: @TakeshiFunahashi

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

Changed status from 'Needs Triage' to: 'Resolved'
Germano Cavalcante self-assigned this 2021-03-16 17:45:06 +01:00

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

Changed status from 'Resolved' to: 'Needs Triage'
Germano Cavalcante removed their assignment 2021-03-16 17:58:19 +01:00

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Oops, it is not resolved

Oops, it is not resolved

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

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

I will confirm for now, but it is possible that it is a limitation.

I will confirm for now, but it is possible that it is a limitation.

This UI issue can avoid, if I make driven custom prop as Armature.data, I can see the prop change iwth keep Object and Pose mode.
At same time I hope to ask developer, is there any demerit, if I attach custom prop for Armature.data , (not attach custom prop for Armature object)?

I can not see any problem for such simple case, but I need to attach many custom prop for complex rig . (which use many shape key, and custom prop to import character rig)
Then when we set porp slider and prop which driven by other props,, (l pose bone transform, or shape key value will be driven, and sometimes it drive other prop)
Then hope to ask developer, Is there any suggestion when I attach custom prop for Armature(object) or Armature.data ?

After I see this issue, I am thinking, if it is better to atach all custom prop of rig for rig.data,, , like rig.data["prop"] (armature) not rig["prop"] (object). If developers know which is better for peformance,, I really apreciate.. (or there is no difference, as peforrmance? to drive pose bone, ,to drive shape keys)

This UI issue can avoid, if I make driven custom prop as Armature.data, I can see the prop change iwth keep Object and Pose mode. At same time I hope to ask developer, is there any demerit, if I attach custom prop for Armature.data , (not attach custom prop for Armature object)? I can not see any problem for such simple case, but I need to attach many custom prop for complex rig . (which use many shape key, and custom prop to import character rig) Then when we set porp slider and prop which driven by other props,, (l pose bone transform, or shape key value will be driven, and sometimes it drive other prop) Then hope to ask developer, Is there any suggestion when I attach custom prop for Armature(object) or Armature.data ? After I see this issue, I am thinking, if it is better to atach all custom prop of rig for rig.data,, , like rig.data["prop"] (armature) not rig["prop"] (object). If developers know which is better for peformance,, I really apreciate.. (or there is no difference, as peforrmance? to drive pose bone, ,to drive shape keys)
Philipp Oeser removed the
Interest
Animation & Rigging
label 2023-02-09 14:35:51 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#86562
No description provided.