Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.57f1
6000.1.16f1
6000.2.3f1
6000.3.0b1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-116556
Regression
No
Pressing “Open” button in Inspector > “High Quality Lines” Override throws “Item m_RenderPipelineSettings.supportHighQualityLineRendering not found” warning
Steps to reproduce:
1. Create new Unity project using empty HDRP Template
2. Select “Sky and Fog Volume” GO in Hierarchy window
3. In Inspector > Volume Component add “High Quality Lines” Override
4. In Warning help box press “Open” button
5. Observe the Console window
Actual results: Warning is thrown in the Console window “Item m_RenderPipelineSettings.supportHighQualityLineRendering not found in window Project Settings.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) (at /Users/bokken/build/output/unity/unity/Modules/IMGUI/GUIUtility.cs:224)”
Expected results: No warnings should be thrown in the Console
Reproducible with versions: 6000.0.57f1, 6000.1.16f1, 6000.2.3f1, 6000.3.0b1
Tested on (OS): macOS Silicon, Sequoia 15.6 (M1)
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
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.