Snow_V2 Rig Incompatible with Blender 3.3.1 #102040

Closed
opened 2022-10-24 23:10:56 +02:00 by Maxfield Bishop · 8 comments

(I really wish you all had a way to report bugs for specific rigs without having to pay 10 dollars a month, but it's better that someone tells you now than one of the paying customers!)

The Snow_V2 Rig, as well as possibly the entire CloudRig project. seem to be heavily incompatible with the latest version of Blender.

When using any combination of FK and IK bones in the sample "Snow" rig provided by Blender Studio, the mesh will quickly distort after the keyframe is placed and the frame is moved. This includes going back to that keyframe after moving in the timeline, it's a simple matter of giving the darn thing some coordinates to process so it can break.

Testing with prior versions of Blender (3.2.2, 3.2, 3.1) indicate that this issue is only prevalent in the most recent builds of Blender 3.3. I have yet to try this with Blender 3.3.2, but I'd wager I will likely have the same issue (I am currently downloading it, however the connection is quite slow.)

There's no real need for me to attach the Blend file, it's the stock one given by downloading on the website, but here's 3 images of the entire process.

Before.png

key applied.png

After.png

(I really wish you all had a way to report bugs for specific rigs without having to pay 10 dollars a month, but it's better that someone tells you now than one of the paying customers!) The Snow_V2 Rig, as well as possibly the entire CloudRig project. seem to be heavily incompatible with the latest version of Blender. When using any combination of FK and IK bones in the sample "Snow" rig provided by Blender Studio, the mesh will quickly distort after the keyframe is placed and the frame is moved. This includes going back to that keyframe after moving in the timeline, it's a simple matter of giving the darn thing some coordinates to process so it can break. Testing with prior versions of Blender (3.2.2, 3.2, 3.1) indicate that this issue is only prevalent in the most recent builds of Blender 3.3. I have yet to try this with Blender 3.3.2, but I'd wager I will likely have the same issue (I am currently downloading it, however the connection is quite slow.) There's no real need for me to attach the Blend file, it's the stock one given by downloading on the website, but here's 3 images of the entire process. ![Before.png](https://archive.blender.org/developer/F13759331/Before.png) ![key applied.png](https://archive.blender.org/developer/F13759333/key_applied.png) ![After.png](https://archive.blender.org/developer/F13759336/After.png)

Added subscriber: @mbishop3d

Added subscriber: @mbishop3d

Update: Tested with current release candidate 3.3.2, issue persisting even with fresh version of Snow V2.

Update: Tested with current release candidate 3.3.2, issue persisting even with fresh version of Snow V2.

Added subscriber: @ChrisLend

Added subscriber: @ChrisLend

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

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

Sorry but I cannot reproduce this.
my steps:

  • download latest snow character
  • link file into scene
  • add library override
  • key chest controller
  • go to next frame

one thing to check is if you have the rigify addon enabled. There can be conflicts with cloud rig

Sorry but I cannot reproduce this. my steps: * download latest snow character * link file into scene * add library override * key chest controller * go to next frame one thing to check is if you have the rigify addon enabled. There can be conflicts with cloud rig

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

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

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

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 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: studio/blender-studio#102040
No description provided.