"file format not supported in file" error when opening Rain Character Rig v2.3 in Blender #95625
Labels
No Label
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Content
Type
Design
Type
Report
Type
To Do
Type
Web Development
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/blender-studio#95625
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?
This Blend file will not open in multiple versions of Blender, including 2.80, 2.83 and 2.92, nor can anything within the file be appended. The download page specifies that it is for Blender 2.80. I tried downloading the file again just in case it somehow got corrupted on my computer, but there was no change.
Was this file edited in Blender 3.0? Can anyone confirm this version is working?
Sorry if this is the wrong place to report.
Added subscriber: @DoNotCare
"file format not supported in file" error when opening Rain Character Rig v2.3to "file format not supported in file" error when opening Rain Character Rig v2.3 in BlenderAdded subscribers: @Mets, @lichtwerk
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Think v2.3 from https://studio.blender.org/characters/5f1ed640e9115ed35ea4b3fb/v2/ was saved with compression (this is why it wont open in 2.93 or below).
It does state though that
But agree, that page also says
@Mets : was this saved with compression intentionally?
Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
Even if it were to open in 2.9, the rig now uses a new option on its Action constraints that's only available in 3.0. ("Before Original" mixing mode) so it won't behave as expected. So I updated the version info, it should now say 3.0 instead of 2.80. That was an oversight when updating the rig, so thanks for the report!