Search Issue Tracker
Fixed in 1.2.0
Votes
1
Found in [Package]
1.1.1
Issue ID
1367857
Regression
No
Animation Rigging throws exceptions when used with Sequences package (sometimes!)
When loading the project, and when jumping to different sequences when I use Animation Rigging in a timeline (specifically, when the RigBuilder component is enabled on a character), I get the following types of exceptions in the logs.
NullReferenceException: Object reference not set to an instance of an object
Repro:
- Open project, open sequences panel, go to Episodie 1 / Location 20 / Shot 50. Try to jump to Shot 60 and back to 50, watching the Console for exceptions such as the above.
notes:
- If you disable the RigBuilder component on "Ivy-v11-2 Prefab Variant" in the "Assets/_LOCAL/Episodes/Episode 1- Friendship Part 1/Episode 1 - Friendship Part 1.unity" scene (go into Ep1/Loc20/Shot50 - Ivy is in there). Re-enable the component the exceptions start coming again.
- I tried to create a new simple project using a small number of scripts etc, but it did not throw an exception. I deleted a lot of stuff from the project (it was 23GB!!!), so hopefully the uploaded files are sufficient to repeat the problem.
- If you jump around shots which do not have Rig Building enabled on characters, everything works well. As soon as you have a character with RigBuilder on, you get exceptions such as the above strack trace.
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
akent99
Feb 02, 2022 15:53
Tried again in 2022.1.b4 and still present (but I understand this fix has not been released yet).