Search Issue Tracker
Fixed
Fixed in 6000.0.41f1, 6000.1.0b11, 6000.2.0a4
Votes
0
Found in
2021.3.44f1
2022.3.50f1
6000.0.23f1
6000.1.0a2
6000.2.0a1
Issue ID
UUM-84061
Regression
No
Artifact appears when generating a Mipmap on Normal map texture and Android platform is selected
Reproduction steps:
1. Open the attached “SpeedTreeNormal.zip” project
2. Open the “SampleScene”
- ensure Android is selected as build platform
- ensure Contents/MahoganyTree01_Normal preview shows "512x512 RGB Compressed ETC UNorm 170.7 KB"
-3. Move the Main Camera position up and down on the Y axis-
-4. Observe the Game view-
- or even easier: in SceneView, move towards/away from the top of the tree
Expected result: No red point is showing on the tree
Actual result: Red point is showing on the tree in certain Camera positions
Reproducible with: 2023.3.0a18, 6000.0.23f1
Not reproducible with: 2021.3.44f1, 2022.3.50f1, 2023.3.0a17
Reproducible on: macOS 14.6.1 (M1 Max), Windows 11
Not reproducible on: no other environment tested
Notes:
- -Does not reproduce when “Generate Mipmap” is unchecked on the "MahoganyTree01_Normal" texture- (untrue, but it becomes extremely hard to trigger)
- -Only reproduces when the Android platform is selected- (untrue, but the effects are much worse when compression format ETC is selected, which is the default selection for Android since 2022.3.0a18)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment