Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
7.1.8
Issue ID
1264734
Regression
No
[HDRP] QualitySettings.lodBias value is wrong when using HDRP
Steps to reproduce:
1. Open a new HDRP project
2. Create a cube
3. Create a sphere as the cube's child object
4. Add an LOD Group Component to the cube
5. Set the cube mesh as the mesh for LOD0
6. Set the sphere mesh as the mesh for LOD1
7. Set the LOD Bias Mode to Override and the LOD Bias to some value other than 1 in Edit>Project Settings>HDRP Default Settings
8. Try to use the camera slider in the LOD inspector to see that the displayed LOD levels (correct) do not match what is shown in the UI because it is using the wrong lodBias value. (See attached video)
This is caused by the HDRP code always setting the value here https://github.com/Unity-Technologies/ScriptableRenderPipeline/blob/2bdf0eb2a88ae6085b18979cb427b01c9bf862c8/com.unity.render-pipelines.high-definition/Runtime/RenderPipeline/HDRenderPipeline.cs#L2834
Actual result: the LOD Group UI behaves in the wrong way because the QualitySettings.lodBias value is wrong
Expected result: we either use the QualitySettings.lodBias to represent the actual bias value that is currently used, or offer the means for users to get the value from the SRP in some obvious, documented way.
Versions affected: 2020.2.0a11. Note that this issue probably affects every version prior to that because that's how it's always been made to work.
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
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
This is a duplicate of issue #1211957