Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
1
Found in
6000.3.0a4
6000.4.0a1
6000.5.0a1
Issue ID
UUM-113779
Regression
No
Scene is marked dirty when creating a scene with "Indoors (URP)" template
How to reproduce:
1. Create and open a new project, with “Universal 3D” template
2. In the toolbar, navigate to File > New Scene
3. Select the “Indoors (URP)” template
4. Click “Create” button
5. Observe the Hierarchy
Expected result: The newly created scene is not marked dirty
Actual result: The scene is marked dirty
Reproducible with: 6000.3.0a1, 6000.3.0a4
Couldn’t test with: 6000.0.55f1, 6000.1.15f1, 6000.2.0f1 (template is not included)
Reproducible on: Windows 11
Not reproducible on: No other environments
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
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
- Typing numbers in Matrix node’s numeric fields stretches Node
- Streaming is misspelled as "Steaming" in "Enable GPU Streaming" and "Enable Disk Streaming" tooltpis
- "IndexOutOfRangeException" thrown when moving caret left at start of TMP Input Field with rich text
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.
Resolution Note (6000.5.X):
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.