Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.3.0b8
6000.4.0b9
6000.5.0a7
Issue ID
UUM-134455
Regression
Yes
Default Render Pipeline Asset is unassigned in Graphics Project Settings of the Universal 3D Template
Steps to reproduce:
- Upgrade Universal 3D Template in Hub to newest available (17.0.14)
- Create and Open a Universal 3D Template Project
- Navigate to Project Settings > Graphics
- Observe the "Default Render Pipeline" Object field
Actual results: "Default Render Pipeline" is unassigned
Expected results: "Default Render Pipeline" is assigned
Reproducible with versions: 6000.3.0b8, 6000.4.0b9, 6000.5.0a7 (Template 17.0.14) (Hub Shows 17.1.0)
Not reproducible with versions: 6000.0.68f1 (Template 17.0.12)
Tested on (OS): Windows 11, macOS 26.2
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.