Search Issue Tracker
In Progress
Fix In Review for 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
- Multiple errors occur when setting the Render Object Event to AfterRenderingPostProcessing while using STP for Upscaling
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
Add comment