2.8 auto/manual upgrade rig-ui for Rigify #63463
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#63463
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Rig UIs generated with Rigify in 2.7x won't work correctly in 2.8 and have to be updated.
This can be handled by the Rigify generate function, the whole rig would be overwrote tough.
We dealt with similar design issues moving from 0.4 to 0.5. In that case opening a blender file containing an old rigify rig/metarig would have displayed a warning giving the user the option to upgrade the rig/metarig to make it work in new version (displaying also a confirm pop-up disclaiming feature may change)
run rigify in legacy mode and ignore new features.
From an user point of view i think would be better if we could create a similar feature for 2.8 too.
So we have here 2 options in my opinion:
automatic: if rigify is enabled, and detects an old rig, re-generates the python scripts
manual: if rigify is enabled, and detects an old rig, displays the user a warning and the option to re-generate the python scripts
the interface can display a button like the one we did for legacy rigs just replacing "Upgrade metarig" string:
Added subscribers: @icappiello, @LucioRossi, @angavrilov
Added subscriber: @LucianoMunoz
Added subscriber: @rwman
Added subscriber: @TodorNikolov
Added subscriber: @rjg
@icappiello The triaging team is currently in the process of cleaning up ticket status and tags. Is this still a relevant ToDo or has this task been complete or abandoned?