Search Issue Tracker
Fixed
Fixed in 8.0.0-pre.3, 2021.3.0, 2022.1.0, 2022.2.0, 2023.1.0
Votes
0
Found in [Package]
2021.3.0
2022.1.0
2022.2.0
Issue ID
DANB-19
Regression
Yes
Upgrading PSDs authored in Krita from 20.3 to 21.3 causes lost Sprite reference
If a project contains Krita authored .psd files and the project is upgraded from Unity 2020.3 to Unity 2021.3, the Sprites in the .psd file gets new Sprite Ids and consumers of these sprites loses their references.
*How to reproduce:*
# Create a .psd file in Krita, save it to disk and rename the file ending from .psd -> .psb
# Create a new project in Unity 2020.3 and add the .psb file into the project
# Drag a Sprite out from the .psb file into a scene and save the scene
# Relaunch the project in Unity 2021.3 and view the scene with the Sprite in it
*Expected:*
Sprite is visible in the scene
*Actual:*
The SpriteRenderer has a missing reference in the Sprite property.
*Tested with:* 2020.3.33f1 & 2021.3.0f1
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2022.1.0):
https://github.cds.internal.unity3d.com/unity/2d/pull/1761