Search Issue Tracker
Fixed in 2022.3.14f1
Fixed in 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0a15
Votes
0
Found in
2021.3.31f1
2022.3.11f1
2023.1.17f1
2023.2.0b14
2023.3.0a10
Issue ID
UUM-53676
Regression
Yes
HDRP is missing a mipmap bias override for SAMPLE_TEXTURE2D_ARRAY_GRAD
Reproduction steps:
1. Open the attached "repro_IN-57283.zip" project
2. Open the "Assets/_Repro/TestScene" Scene
3. Enter the Play Mode
Expected result: Both "Texture2DArray" (upper right and lower right) textures match the "Texture2D" (upper left and lower left) textures (both look sharp)
Actual result: The "Texture2DArrayGrad" is blurry compared to "Texture2DGrad"
Reproduced with: 2022.2.0a8, 2022.3.11f1, 2023.1.17f1, 2023.2.0b14, 2023.3.0a10
Not reproduced with: 2021.3.31f1, 2022.2.0a7
Reproduced on: Windows 10 (22H2)
Not reproduced on: No other environments tested
Notes:
- Reproducible in Player
- If you embed the HDRP package and manually edit the "ShaderVariables.hlsl" file, remove the override for "SAMPLE_TEXTURE2D_GRAD", and enter the Play Mode, the "Texture2DGrad" will be just as blurry as the "Texture2DArrayGrad"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment