Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4.12f1
2020.1
Issue ID
1289310
Regression
No
Loading another Scene when the Editor/Player is out of focus results in the current Scene freezing when using Physics
How to reproduce:
1. Download and open the project "1289310.zip" from the attached link (or alternatively use the provided TeamViewer machine)
2. Load the Scene "_primaryUI_Main"
3. Wait ~5 minutes for the initial Scene to begin
4. Click on the topmost "CAMPAIGN" button
5. In this "SELECT DIFFICULTY" menu press "Ok" (make sure "Tutorial" option is ticked off)
6. Go through the story options selecting random character traits
7. Skip the cutscene by clicking the left mouse button
8. Once in this new loading Screen put the Editor out of focus (for ex. open another application on top of the Editor)
Expected result: The new Scene loads without any issues
Actual result: The current Scene freezes and no longer loads the new Scene
Reproducible with: 2020.1.14f1, 2020.1.17f1
Could not test with: 2018.4.30f1, 2019.4.17f1, 2020.2.1f1, 2021.1.0b1 (project is complicated, takes too long to upgrade/downgrade to test)
Notes:
- Does not fail to load the other Scene when the Editor/Player is in focus (might take ~5 mins to load)
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Complex reproduction steps and project, isolated issue, not enough team bandwidth to further investigate and deconstruct this issue. Until new circumstances come up, we won't be working on this bug