Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2017.2.0p1
Issue ID
1047148
Regression
No
Editing a "Sprite Atlas" dirties the scene, but doesn't "Check Out" the Scene in VCS
Reproduction steps:
1. Open "MinimalRepro.zip" project
2. Set-up the project to use Perforce VCS
3. Check Out the "Townfolk-Adult-F-002.png"
4. Open it in the Sprite Editor
5. Slice out a new image
6. See that in the Hierarchy window, the scene is marked as dirty
7. See that in the Project window, the scene is not marked for Check Out
Expected Result: If the scene is dirtied by some action it should be Checked Out
Actual Result: The scene gets dirtied by editing a Sprite Atlas, but doesn't get Checked Out
Fixed in: 2019.1.0a10
Reproduced with: 2019.1.0a5, 2018.3.0b6, 2018.2.13f1, 2018.1.9f2, 2017.4.13f1,
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Add comment