Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2020.3.38f1
2021.3.8f1
2022.1.13f1
2022.2.0b4
2023.1.0a6
2023.2.0a1
2023.3.0a3
Issue ID
UUM-13821
Regression
No
QOI file mode does not change when multiple files are selected
To reproduce:
1. Open the project “QOIF”
2. Select two .qoi files in the Assets folder (“dragon-nest” and “ravens_in_field”)
3. Change the Wrap Mode or the Filter Mode in the Inspector
Expected result: The new mode is applied to both .qoi files
Actual result: The mode was changed only for a one file
Reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.13f1, 2022.2.0b4, 2023.1.0a6
Reproduced on: macOS Monterey 12.5.1 (Intel)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.
Resolution Note (2023.3.X):
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.