Search Issue Tracker
By Design
Votes
0
Found in
5.5.0f3
Issue ID
878066
Regression
No
Possible caching problem with Texture2D's and stored prefabs loaded with Resources.Load
When the game is started for the first time Texture2D's together with prefabs are loaded. However, when the game is loaded for the second time, only the walls are loaded. If the scene is built after starting the game in the editor for the second time, the bug is carried to the built game.
The problem is fixed when the current map is edited or Unity is restarted until the scene is replayed.
Steps to reproduce:
1. Open attached project
2. Play "testing" scene
3. Press any key
5. Stop the game
4. Replay "testing" scene
5. Press any key
6. Observe the various blocks that disappeared
Expected result: the whole level with doors and other prefabs should be displayed from the read image
Actual result: Only the black walls are displayed from the read image
Reproduced in: 2017.1.0a4, 2017.1.0a1, 5.6.0f1, 5.5.0f3
Can't run the game because of compiler errors in 5.2.2f3, 5.4.1p1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Add comment