Search Issue Tracker
Fixed in 2020.3.X
Votes
0
Found in
2020.3
2020.3.18f1
Issue ID
1416248
Regression
No
'Should not get here' and 'Assertion failed' errors appear when entering Game Menu in Play mode
Reproduction steps:
1. Open the attached user's project
2. Open the 'Level2' Scene
3. Enter Play mode
4. In the Game View press the Escape key
Expected result: No errors are in the Console
Actual result: 'Should not get here' and 'Assertion failed' errors are in the Console
Reproducible with: 2020.3.23f1
Not reproducible with: 2020.3.24f1, 2020.3.32f1, 2021.2.18f1, 2022.1.0b14, 2022.2.0a9
Could not test with: 2019.4.37f1 (due to compile errors)
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 2020.3):
Fixed in 2020.3.24f1