Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2018.4
2018.4.26f1
Issue ID
1285072
Regression
No
[Editor][Android] Dynamic Textures made at runtime that use DXT5 compression are forced to use Point filtering
How to reproduce:
1. Open the attached "FilterModeTest.zip" project
2. Make sure Android Target is selected in Build Settings
3. Make sure to make Texture2D property public in CreateTexture.cs line 8
4. Enter Play Mode
5. Select Cube GameObject in the Scene Hierarchy
6. Double click the Created Texture2D in the Inspector
7. Try to change "FIlter Mode" on the Texture
Expected Behavior: "Filter Mode" is changed
Actual Behavior: "Filter Mode" is always "Point"
Reproducible with: 2018.4.28f1
Not reproducible in: 2019.1.0a1, 2019.4, 2020.1, 2020.2, 2021.1
Note: Seems to only be reproducible in 2018.4 and only on Android Build target
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment