Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.21f1
Issue ID
UUM-82848
Regression
No
The High Quality Line Renderer stops the hair from being affected by the Screen Space Ambient Occlusion
How to reproduce:
1. Open the “XRTestUnity6“ project
2. Open the “HairSample_HDRP“ scene
3. Open the “Global Volume“ GameObject in the Inspector
4. Enable the High Quality Line Rendering Volume Override
5. Enable the Screen Space Ambient Occlusion Volume Override
6. Move the Intensity of the Screen Space Ambient Occlusion from max to min
7. Observe the Game view
Expected result: “Hair“ change according to the Screen Space Ambient Occlusion intensity
Actual result: “Hair“ doesn’t change according to the Screen Space Ambient Occlusion intensity
Reproducible with: 6000.0.21f1
Could not test with: 2021.3.44f1, 2022.3.48f1 (High Quality Line Renderer not supported yet)
Reproducible on: Windows 10 Pro (22H2)
Not reproducible on: macOS 14.6.1 (Intel)
Notes:
- Changing the Composition Mode of the High Quality Line Renderer to non-depth related one does not fix the issue
- After disabling High Quality Line Renderer the SSAO on the “Hair“ GameObject works as expected
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.