Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.31f1
2022.3.12f1
Issue ID
UUM-54442
Regression
No
Assets Migration configuration option remains unfixed when selecting 'Fix' in HDRP Wizard
Reproduction steps:
1. Open the attached “repro-project“
2. In the HDRP Wizard window select the “Fix“ button under the “Assets Migration“ configuration option
3. Note the warning logged in the Console saying the asset is migrated and the project should be saved to save the changes
4. Observe the issue remaining unfixed after saving
Reproducible with: 2021.3.31f1, 2022.3.12f1, 2023.1.0a24
Not reproducible with: 2023.1.18f1, 2023.2.0b15, 2023.3.0a11
Fixed in: 2023.1.0a25
Reproduced on: Windows 10 Pro, Windows 11 (by reporter)
Not reproducible on: No other environment tested
Notes:
1. The full warning logged in the Console:
“Migrated asset Assets/HDRPDefaultResources/HDRenderPipelineGlobalSettings.asset. You should save your project to save changes.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)“
2. Trying to build the project fails with the following error:
”Error building Player: BuildFailedException: Current HDRenderPipelineGlobalSettings Assets/HDRPDefaultResources/HDRenderPipelineGlobalSettings.asset is a non updated asset. Please use HDRP wizard to fix it.”
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
When debugging the asset to migrate (HDRenderPipelineGlobalSettings), it has the version 8 on it. So obviously, it cannot be migrated to 2023.1.0a24 or less, since version 8 or + doesn't exist in the Version enum (HDRenderPipelineGlobalSettings.Migration.cs). Starting 2023.1.0a25, the Version 8 does exist (it's EnableAmethystFeaturesByDefault) which explains why the migration now works for this version and next versions.
The only reason a user could have the version 8 on it's asset before 2023.1.0a25 is by upgrading the project and downgrading it. HDRP doesn't really support downgrading, so it's expected in a way.
Unfortunately, there's no plan to support that for now. The best workaround to fix this problem are:
- Open the Global Settings / HDRP Asset in Debug mode
- Set the Version dropdown to an existing value.
- The issue should be gone.