Search Issue Tracker
Won't Fix
Votes
1
Found in
2019.4.40f1
2021.3.33f1
2022.3.14f1
2023.2.3f1
2023.3.0a17
6000.0.0b11
Issue ID
UUM-57805
Regression
Yes
The Texture Shape of an Image changes from 2D to a Cube when the project is upgraded to 2019 and above
Reproduction steps:
1. Create a new project with Unity 2018.3.X
2. Import the “Blend” Image and its .meta file from “TextureProject” into the project
3. Observe the Texture Shape of the “Blend” Image
4. Upgrade the Project to 2019.4.X or above
5. Observe the Texture Shape of the “Blend” Image
Expected result: The Texture shape remains configured as 2D
Actual result: The Texture Shape is changed to Cube
Reproducible with: 2019.4.40f1, 2021.3.33f1, 2022.3.14f1, 2023.2.3f1, 2023.3.0a17
Not Reproducible: 2018.4.36f1
Reproducible on: macOS(Intel) 14.0
Not reproducible on: No other environment tested
Note:
1. The Blend.png and its .meta file must be imported to reproduce
2. The Blend image and its meta file can be found in “TextureProject”
-
yangjm2015
Dec 01, 2023 02:44
This issue because the .meta file uses /r/r/n, but it is difficult to fix the issue on the user side during import. Hope it can be fixed in unity.
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.