Search Issue Tracker
Fixed
Fixed in 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a2
Votes
1
Found in
6000.0.51f1
6000.1.8f1
6000.2.0b7
Issue ID
UUM-109748
Regression
Yes
"Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
How to reproduce:
1. Open the attached “IN-105270” project
2. Open the “SampleScene” Scene
3. Enter Play mode
4. Click the buttons in the sequence, “Spawn PrefabA” → “Change Character Culling Type” → “Spawn PrefabB”
5. Observe the result in the Console
Expected result: No errors appear in the Console window
Actual result: “Assertion failed on expression: 'renderer->GetRequiresAnimationVisibility()'“
Reproducible with: 2023.3.0a8, 6000.0.51f1, 6000.1.8f1, 6000.2.0b7
Not reproducible with: 2021.3.51f1, 2022.3.63f1, 2023.3.0a7
Reproduced on: Windows 11
Not reproduced on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
- FrameTimingManager.GetLatestTimings adds background time to the next focused frame when the Player is unfocused
- PropertyDrawer gets disposed while still being active when adding a secondary component
Add comment