Search Issue Tracker
Won't Fix
Votes
3
Found in
2021.3.35f1
2022.2.20f1
2023.2.12f1
2023.3.0b9
6000.0.0b11
6000.1.0a7
6000.2.0a1
Issue ID
UUM-65056
Regression
No
"Assertion failed on expression" error is thrown when using a specific Prefab on HDRP and URP
How to reproduce:
1. Open the “assertion_failed“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Observe the Console
Expected result: No errors are thrown
Actual result: “Assertion failed on expression“ error is thrown
Reproducible with: 2021.3.35f1, 2022.2.20f1, 2023.2.12f1, 2023.3.0b9
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Error: Assertion failed on expression: 'fidA != fidB'
Comments (1)
-
Caiusarcher
Jun 05, 2024 08:56
omg has it solved yet?
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
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
Resolution Note:
There are no fixes planned for this Bug
Resolution Note:
There are no fixes planned for this Bug