Rigify UI throws an error ('thigh_fk' cannot be found) #89910
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#89910
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
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11
Blender Version
Broken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash:
blender/blender@1b8d33b18c
Worked: 2.92
Behavior changed in blender/blender@afa5da9ce0
Short description of error
Rigify UI throws an error ('thigh_fk' cannot be found)
Exact steps for others to reproduce the error
fm 001.blend
N
panelAdded subscriber: @Rolinga
Added subscriber: @PratikPB2123
Can please add a simple test file with steps to reproduce ? Issue is possibly related to rigify addon so changing the tag
Changed status from 'Needs Triage' to: 'Needs User Info'
Hi there, this is the same file that I've using when the problems appears.
fm 001.blend
Thanks and sorry my english, I'm from Chile... but I try hard to make me understand!
Insert keyframe for all bones selected doesn't work with the "n" panel shown... I hace to close it to go on.to Insert keyframe for all bones selected doesn't work with the "n" panel shown... I have to close it to go on.Added subscriber: @lichtwerk
Think the keyframes are actually inserted correctly.
Rigify has a problem though [which was still possible in 2.92, only 2.93 onwards has this problem]:
Added subscribers: @Mets, @angavrilov
Behavior changed in blender/blender@afa5da9ce0
@Mets , @angavrilov : does this ring a bell?
Insert keyframe for all bones selected doesn't work with the "n" panel shown... I have to close it to go on.to Rigify UI throws an error ('thigh_fk' cannot be found)Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Changed status from 'Needs Developer To Reproduce' to: 'Archived'
In the attached file, the properties in rig_ui.py are defined using the old
=
assignment, but looking at the git blame of the code that generates that code, it has been kept up to date immediately with Blender 2.8, and changed to the new:
annotation syntax.So this means your rig was generated with a version of Rigify and Blender that are more than 3 years old, and that's why it's no longer compatible with current Blender.
The ideal solution here is to find the metarig that generated this rig, and re-generate it with the current Rigify. If that's not available because the rig's author has made the huge mistake of discarding the metarig (which should never ever be done) then your best bet is to simply go into rig_ui.py and replace the
=
signs in the operator class definitions with:
signs, as per Blender 2.80 Python API requirements.Thanks for the report, but there's no bug here, so closing. Hope the above info will help with the problem though.
thx looking at this @Mets !
Thanks a lots, and sorry for reporting a non bug issue!
Cheers... and also thanks for all your work!!