Koro rig (Caminandes) wrong in master, worked in 270(a) #39806
Labels
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#39806
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Windows 7, Geforce 540M
Blender Version
Broken:
f77207b
Worked: 2.69, 2.70(a)
Short description of error
The Koro rig is wrong in latest revisions.
Exact steps for others to reproduce the error
Open 11a_comp.blend from the Caminandes files (http://temp.dingto.org/caminandes_files.7z , ~480MB), reload trusted and go to frame 500.
2.70a is fine, in master the arms are wrong.
2.70a:
Master:
I want to show this file during my Cycles FMX presentation next week, with the latest Cycles speedups, so I would really appreciate a fix until Wednesday latest.. This is a bad regression anyways, so marking as unbreak now!
I know it's a large file, sorry for that. :)
Changed status to: 'Open'
Added subscriber: @ThomasDinges
Added subscribers: @JoshuaLeung, @ideasman42
Added subscriber: @nudelZ
confirmed :/
current master, ubuntu 13.10
:/ Most likely another bone roll mess of my own… I’m starting to wonder if one should ever touche that ugly code.
Ok, as expected, issue is caused by commit 07f8c5c…
Now, I just cannot investigate such a complex rig! We ask for simple blend files for reports, there’s a good reason for it…
To be more specific, with such a complex rig, I can’t determine where (as in, at which bone) happens the issue, I can’t make useful traces/prints in code, I can’t even say whether this is a real bug, or whether the rig had to compensate somehow a wrong behavior in previous code, that got fixed with this patch…
Added subscriber: @tippisum
I understand, but I don't see this as incomplete..
Maybe @tippisum has an idea.
Again, I need a simpler file demonstrating the issue, as stated in bug report rules!
Ok, so issue was actually caused by recent changes to Transform constraint (usual degrees to radians issue).
Here is a patch that adds an
Update Animated Transform Constraints
operator, which uses (a slightly modified) animsys_refactor to scan all actions and drivers, change RNA paths when needed, and alter FCurves keyframes and/or generator modifiers to convert from degrees values to radians ones.Not sure we would like to extend this to all changes made in 2.70 release regarding deg2rad?
Grrr…
P46: (An Untitled Masterwork)
Also, as suggested by Ton, we should raise the minversion (to warn users when they re-open under previous versions).
P47: (An Untitled Masterwork)
This issue was referenced by blender/blender-addons-contrib@c089150426
This issue was referenced by
c089150426
Changed status from 'Open' to: 'Resolved'
Closed by commit
c089150426
.