Search Issue Tracker
Fixed in 10.4.0
Votes
0
Found in [Package]
9.0.0-preview.35
Issue ID
1294683
Regression
Yes
VolumeComponentEditor.cs script changes the order of the parameters when the order is manually created in another script
Reproduction steps:
1. Open the user's attached project "VolumeComponentEditorTest.zip"
2. In the Project window go to the Assets folder and select the ScriptableObject "TestVolumeProfile.asset"
3. Expand "Test Volume Component" in the Inspector window
Expected result: "Test Volume Component" parameters are placed in the sections from the TestVolumeComponent.cs script
Actual result: "Test Volume Component" parameters are not placed in the sections from to the TestVolumeComponent.cs script
Reproducible with: 9.0.0-preview.35 (2020.1.17f1), 10.2.2 (2020.2.0b14, 2021.1.0a9)
Not reproducible with: 7.5.2 (2019.4.16f1), 9.0.0-preview.13 (2020.1.17f1)
Could not test with: 2018.4.30f1 (Associated scripts could not be loaded)
Note:
- When updating the package version to 9.0.0-preview.35 a new line "m_Parameters.Sort(new ParameterSorter());" appears in the VolumeComponentEditor.cs script, which causes the issue by making the parameters ignore the placement order which is written in the TestVolumeComponent.cs script. If the line is commented out, the issue disappears and the parameters are placed in the order which is written in the TestVolumeComponent.cs script
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
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Resolution Note (fix version 10.4.0):
Fixed in HDRP 10.4.0