Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Duplicate in 2019.2.X
Votes
0
Found in
2017.4.0f1
2018.3.9f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1164347
Regression
No
[VCS] Sprite Atlas asset is checked out in Perforce after entering Play Mode and exiting Editor
How to reproduce:
1. Add the attached project ("SpriteAtlasPerforceIssue.zip") to your correct workspace folder and open it
2. Connect it to your Perforce server and submit the initial Assets/Project Settings folders
3. Open the "SampleScene", enter and leave the Play Mode
4. Close the Editor
5. Refresh the Perforce's pending file list (Observe that the sprite atlas asset is now checked out/modified)
Expected result: the sprite atlas is not modified/checked out when closing the editor
Actual result: the sprite atlas is modified/checked out each time the project is closed after entering Play Mode
Reproduced in: 2019.3.0a7, 2019.2.0b7, 2019.1.8f1, 2018.4.3f1, 2017.4.28f1
Note: The Editor does not need to be closed while the Play Mode is running but it does not reproduce if the project is re-opened without ever going into Play Mode at all
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- 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
Add comment