Rigify: CloudRig featureset fails to register #97622

Closed
opened 2022-04-26 12:55:47 +02:00 by Stephen Kinuthia · 26 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: AMD Radeon R6 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6

Blender Version
Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: blender/blender@c77597cd0e
Worked: (newest version of Blender that worked as expected)

Addon Information
Name: Rigify (0, 6, 5)
Author: Nathan Vegdahl, Lucio Rossi, Ivan Cappiello, Alexander Gavrilov

Exact steps for others to reproduce the error
opened the rigify addon and added the cloud rig via the new feature sets
Video taken from blender/blender#103541
20221229_rigify_generate_python_scrip_error.mp4

Traceback (most recent call last):
File "/Applications/Blender.app/Contents/Resources/3.5/scripts/modules/addon_utils.py", line 369, in enable
  mod.register()
File "/Applications/Blender.app/Contents/Resources/3.5/scripts/addons/rigify/__init__.py", line 511, in register
  ui.register()
File "/Applications/Blender.app/Contents/Resources/3.5/scripts/addons/rigify/ui.py", line 1508, in register
  animation_register()
File "/Applications/Blender.app/Contents/Resources/3.5/scripts/addons/rigify/utils/animation.py", line 994, in register
  register_class(RIGIFY_OT_get_frame_range)
ValueError: register_class(...): already registered as a subclass 'RIGIFY_OT_get_frame_range'
**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: AMD Radeon R6 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6 **Blender Version** Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `blender/blender@c77597cd0e` Worked: (newest version of Blender that worked as expected) **Addon Information** Name: Rigify (0, 6, 5) Author: Nathan Vegdahl, Lucio Rossi, Ivan Cappiello, Alexander Gavrilov **Exact steps for others to reproduce the error** opened the rigify addon and added the cloud rig via the new feature sets Video taken from blender/blender#103541 [20221229_rigify_generate_python_scrip_error.mp4](https://archive.blender.org/developer/F14099138/20221229_rigify_generate_python_scrip_error.mp4) ``` Traceback (most recent call last): File "/Applications/Blender.app/Contents/Resources/3.5/scripts/modules/addon_utils.py", line 369, in enable mod.register() File "/Applications/Blender.app/Contents/Resources/3.5/scripts/addons/rigify/__init__.py", line 511, in register ui.register() File "/Applications/Blender.app/Contents/Resources/3.5/scripts/addons/rigify/ui.py", line 1508, in register animation_register() File "/Applications/Blender.app/Contents/Resources/3.5/scripts/addons/rigify/utils/animation.py", line 994, in register register_class(RIGIFY_OT_get_frame_range) ValueError: register_class(...): already registered as a subclass 'RIGIFY_OT_get_frame_range' ```

Added subscriber: @njuguna01

Added subscriber: @njuguna01

blender/blender#103541 was marked as duplicate of this issue

blender/blender#103541 was marked as duplicate of this issue

#103331 was marked as duplicate of this issue

#103331 was marked as duplicate of this issue

#103233 was marked as duplicate of this issue

#103233 was marked as duplicate of this issue

#102821 was marked as duplicate of this issue

#102821 was marked as duplicate of this issue

#98409 was marked as duplicate of this issue

#98409 was marked as duplicate of this issue

#98787 was marked as duplicate of this issue

#98787 was marked as duplicate of this issue

#97646 was marked as duplicate of this issue

#97646 was marked as duplicate of this issue

#96989 was marked as duplicate of this issue

#96989 was marked as duplicate of this issue
Demeter Dzadik changed title from rigify addon to Rigify: CloudRig featureset fails to register 2022-04-26 15:13:39 +02:00
Member

Added subscriber: @Mets

Added subscriber: @Mets
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Demeter Dzadik self-assigned this 2022-04-26 15:14:33 +02:00
Member

Can you check if this is happening with the version of CloudRig for Blender 3.0-3.1?

Can you check if this is happening with the [version of CloudRig for Blender 3.0-3.1](https://gitlab.com/blender/CloudRig/-/releases/3_0-3_1)?
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev

Added subscriber: @Harvester

Added subscriber: @Harvester

It does happen with version 3.1 too but, please, note that in the init.py file of the CloudRig feature set it states clearly that the minimum compatible version of Blender is 3.2, so I wouldn't expect it to work with 3.1 version. Anyway, the error messages are the same.

It does happen with version 3.1 too but, please, note that in the __init__.py file of the CloudRig feature set it states clearly that the minimum compatible version of Blender is 3.2, so I wouldn't expect it to work with 3.1 version. Anyway, the error messages are the same.

Added subscribers: @lukai, @mano-wii

Added subscribers: @lukai, @mano-wii
Member

Added subscribers: @Densle, @TodorNikolov

Added subscribers: @Densle, @TodorNikolov
Member
Added subscribers: @mernaz_ze, @PratikPB2123, @Kali-4, @sorciere007
Member

Changed status from 'Needs User Info' to: 'Needs Triage'

Changed status from 'Needs User Info' to: 'Needs Triage'
Member

Added subscriber: @abbuntt

Added subscriber: @abbuntt
Member

Added subscriber: @Dturtle

Added subscriber: @Dturtle

Added subscriber: @kaicovieira

Added subscriber: @kaicovieira
Member

Added subscriber: @hoanguk

Added subscriber: @hoanguk
Member

In #97622#1347311, @Harvester wrote:
It does happen with version 3.1 too but, please, note that in the init.py file of the CloudRig feature set it states clearly that the minimum compatible version of Blender is 3.2, so I wouldn't expect it to work with 3.1 version. Anyway, the error messages are the same.

AFAICT, the version of CloudRig I linked has the minimum Blender version in __init__.py as 3.0, which is correct.
I tested each of the tagged CloudRig releases in their corresponding Blender versions, and they all seem to work. But to try to remedy the situation, I've made the Releases page a bit clearer.

> In #97622#1347311, @Harvester wrote: > It does happen with version 3.1 too but, please, note that in the __init__.py file of the CloudRig feature set it states clearly that the minimum compatible version of Blender is 3.2, so I wouldn't expect it to work with 3.1 version. Anyway, the error messages are the same. AFAICT, the version of CloudRig I linked has the minimum Blender version in `__init__.py` as 3.0, which is correct. I tested each of the tagged CloudRig releases in their corresponding Blender versions, and they all seem to work. But to try to remedy the situation, I've made the [Releases](https://gitlab.com/blender/CloudRig/-/releases) page a bit clearer.

Thank you @Mets for that update to the Releases page of CloudRig, very clear and detailed.

Thank you @Mets for that update to the Releases page of CloudRig, very clear and detailed.
Member

Just to reiterate, at the time I write this comment, I'm pretty sure all the reports being merged into this thread are a result of users trying to match incompatible versions of CloudRig and Blender.

Most of the time, these compatibility breaks come from features from CloudRig being merged into core Rigify, which means it's not just compatibility breaks for the sake of it, but it's something that cannot be avoided, and is a symptom of positive progress.

I don't know what else to do about the constant influx of people who are plainly installing wrong versions of CloudRig. I added warnings, updated ReadMe's, gave people buttons in Blender with links that lead to the correct page, I do all I can to help users find the correct version before having to resort to feeling like they need to make a bug report.

If anyone has any more suggestions, please let me know. But, considering I've recently tested all the releases and they're working fine, I will close this task for now.

Just to reiterate, at the time I write this comment, I'm pretty sure all the reports being merged into this thread are a result of users trying to match incompatible versions of CloudRig and Blender. Most of the time, these compatibility breaks come from features from CloudRig being merged into core Rigify, which means it's not just compatibility breaks for the sake of it, but it's something that cannot be avoided, and is a symptom of positive progress. I don't know what else to do about the constant influx of people who are plainly installing wrong versions of CloudRig. I added warnings, updated ReadMe's, gave people buttons in Blender with links that lead to the correct page, I do all I can to help users find the correct version before having to resort to feeling like they need to make a bug report. If anyone has any more suggestions, please let me know. But, considering I've recently tested all the releases and they're working fine, I will close this task for now.
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-05-23 17:01:57 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
7 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-addons#97622
No description provided.