Search Issue Tracker
Duplicate
Votes
0
Found in
Issue ID
1017476
Regression
No
[MSE] "Bake paused in play mode" incorrectly appears in progress bar after entering into play mode
When entering into play mode with additively loaded scenes in the Hierarchy, "Bake paused in play mode" text incorrectly appears in progress bar. This behaviour is only expected when user enters play mode while the scene is still baking with Auto mode enabled. However, this is not the case with the project attached to the case. Auto mode is disabled, lighting is generated manually (lighting data asset exists locally inside the project) but the status of progress bar still changes. This is unexpected.
Steps for reproduction:
1) Download the project from the link below
2) Generate lighting
3) Enter into play mode
4) Observe the behaviour in progress bar.
Notes:
- Not a regression
- The behaviour of the issue is indeterministic, presumably due to threading problem. Thus, it's not possible to consistently reproduce the problem
- An image is attached below to show the problem
Comments (2)
-
GuardHei
Jan 07, 2019 13:40
Exactly the same problem! And the frame rate dropped significantly! Is anyone working on this right now?
-
GuardHei
Jan 07, 2019 13:40
Exactly the same problem! And the frame rate dropped significantly! Is anyone working on this right now?
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
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
This is a duplicate of issue #1022871