Search Issue Tracker
Fixed
Fixed in 2021.3.32f1, 2022.3.13f1, 2023.1.19f1, 2023.2.0b17, 2023.3.0a12
Votes
0
Found in
2021.3.4f1
2022.3.5f1
2023.1.4f1
2023.2.0a23
Issue ID
UUM-42695
Regression
No
.spriteatlasv2 file is not checked out to Version Control when Sprite Atlas is edited after hitting "Check Out Meta"
How to reproduce:
1. Open the “FC1565480.7z“ project
2. Connect to Perforce through Edit → Project Settings → Version Control
3. Select the “New Sprite Atlas“ asset in Assets → RPG_inventory_icons
4. In the Inspector window press “Check Out Meta“
5. In the “Objects for Packing“ section add any sprite to the Sprite Atlas and press “Pack Preview“
6. Press “Submit“ and observe the files in the Version Control Changeset
Expected result: .spriteatlasv2 file and .meta file are seen
Actual result: Only the .meta file is seen
Reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.1.4f1, 2023.2.a023
Reproducible on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Source Image property gets set to 'None' when using a specific Sprite and Play mode is entered
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
Add comment