Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.42f1
2021.3.16f1
2022.1.24f1
2022.2.1f1
2023.1.0a23
Issue ID
UUM-21111
Regression
No
Platform settings are overriden by a different platform in texture settings when applying a preset
How to reproduce:
1. Open the attached “Project“ project
2. Select the “Assets/ChangeFiles/hasAndroidInMeta” asset
3. Select the “iOS” tab in the Inspector
4. Click the “Select preset” button (above the “Open” button at the top of the Inspector)
5. Select the “texture_iOSOverride” preset
6. Observe the “Max Size” property in the iOS settings tab
Expected result: The property’s value changes, the same property’s value stays the same in the Android settings
Actual result: The property’s value stays the same (128), the same property’s value is changed in the Android settings
Reproducible with: 2020.3.42f1, 2021.3.16f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a23
Reproducible on: Windows 10
Notes:
1. Android Support and iOS Support components are required to reproduce the issue
2. Issue doesn’t reproduce with the “Assets/ChangeFiles/noAndroidInMeta” asset
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
- "Objects are trying to be loaded during a domain backup." errors on entering Playmode
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
Resolution Note:
After careful consideration, we've decided to close this bug as "Won't Fix" because it currently cannot be fixed in a way that meets our quality requirements.
TextureImporter presets currently have a number of issues related to texture platform settings created by limitations in our serialisation systems that are unlikely to be addressed in the near future. However, once these limitations are addressed, we will be having another look at the known issues with TextureImporter presets as soon as possible.
Our recommendation (regarding texture platform settings specifically, since other properties of the TextureImporter can be safely manipulated with presets) for the time being is to create a AssetPostprocessor that, in the "OnPreprocessTexture" function, makes use of "TextureImporter.SetPlatformTextureSettings" to define the needed settings per platform.