Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2022.2.0a10
2022.2.6f1
2023.1.0b3
2023.2.0a1
Issue ID
UUM-26391
Regression
Yes
[HDRP] New project has unsaved changes when creating a project from HDRP templates
How to reproduce:
1. Create a new 3D (HDRP) or HDRP Sample Scene project
2. Observe the Scene name in top of hierarchy
Expected result: There is only scene name
Actual result: There is an asterix besides the name indicating unsaved changes
Reproducible with: 2022.2.0a10, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1
Not reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.2.0a9
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
There is an asterix due to the change in SampleScene.Unity. We will nt fix it as the template is currently working on multiple version and the asterix appear because the barinries change property in the scene when loading it. To fix it it mean we should produce a unique template version for all the release and always re-save the scene with the very latest binaries of each version, something we will not do. Still I have re-save the scene with latest binaries of most oldest version supported.
Resolution Note (2023.2.X):
There is an asterix due to the change in SampleScene.Unity. We will nt fix it as the template is currently working on multiple version and the asterix appear because the barinries change property in the scene when loading it. To fix it it mean we should produce a unique template version for all the release and always re-save the scene with the very latest binaries of each version, something we will not do. Still I have re-save the scene with latest binaries of most oldest version supported.