Mets/CloudRig
8
12
Fork 6
Code Issues 7 Pull Requests 1 Projects Releases 5 Wiki Activity

Action slot with duplicate action #118

New Issue
Closed
opened 2023-09-02 00:52:30 +02:00 by jerffson.mm · 3 comments
jerffson.mm commented 2023-09-02 00:52:30 +02:00 (Migrated from gitlab.com)
Copy Link

System Information Operating system: Windows-10-10.0.19041-SP0 64 Bits

Blender Version 3.6.0, branch: blender-v3.6-release, commit: 2023-06-27

CloudRig Version: (0, 0, 9) (2023-09-02 18:00)

Description of the problem: Attached .blend file to reproduce the problem:

blender.png

In actions created in version 0.0.8 it was not causing these "duplicate" issues. But with the 0.0.9 update this warning appeared on my character. I saw that it also happens in the Rig of the SNOW character

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits **Blender Version** 3\.6.0, branch: blender-v3.6-release, commit: [2023-06-27](https://developer.blender.org/rBc7fc78b81ecb) **CloudRig Version**: (0, 0, 9) (2023-09-02 18:00) --- Description of the problem: Attached .blend file to reproduce the problem: ![blender.png](/uploads/8fe6bc9bca98ee89fc019dc405a0f2fd/blender.png) In actions created in version 0.0.8 it was not causing these "duplicate" issues. But with the 0.0.9 update this warning appeared on my character. I saw that it also happens in the Rig of the SNOW character
jerffson.mm commented 2023-09-02 00:55:21 +02:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
jerffson.mm commented 2023-09-02 21:12:16 +02:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
bloopert commented 2023-11-09 02:05:42 +01:00 (Migrated from gitlab.com)
Copy Link

This is causing a failed rig to generate from a metarig that successfully generated in the previous release. Is this intentional, and if I want to update I need to break up my finger action?

This is causing a failed rig to generate from a metarig that successfully generated in the previous release. Is this intentional, and if I want to update I need to break up my finger action?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
blender

Needs to be addressed in core Blender. A report should be created on projects.blender.org.

  
bug

   
documentation

Could be addressed by improving tooltips, home page, or the wiki.

  
duplicate

   
feature

A suggestion for a new feature.

  
improvement

A suggestion for how an existing feature could be improved.

  
incident

Denotes a disruption to IT services and the associated issues require immediate attention

  
invalid

Nothing in this report is addressable on development side.

  
need-info

Report is waiting for more info from user

  
question

Question about how to use CloudRig. Also used for issues that are solved by existing features.

  
rigify

Needs to be addressed on Rigify's end. A report can be created on projects.blender.org, or Rigify maintainers notified via chat.

  
wontfix

Admittedly weird behavior, but working as intended.

No Label
blender
bug
documentation
duplicate
feature
improvement
incident
invalid
need-info
question
rigify
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 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: Mets/CloudRig#118
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?