Search Issue Tracker
Fixed
Fixed in 6000.3.0a6
Votes
0
Found in
2022.3.64f1
6000.0.54f1
6000.1.13f1
6000.2.0b11
6000.3.0a3
Issue ID
UUM-112328
Regression
No
“Default Renderer is missing” error is thrown when converting Rendering Settings with the Render Pipeline Converter even though the Default Renderer is set and not missing
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Open the Render Pipeline Converter window (Window > Rendering > Render Pipeline Converter)
- Check the Rendering Settings checkbox
- Click the "Initialize And Convert" button
- Click on the Rendering Settings
- Select All
- Click the "Back" button
- Repeat step 4
- Close the Render Pipeline Converter window
- Repeat the 2, 3, 4, 5, 6, 7, 8 steps
- Observe the Console window
Actual results: "Default Renderer is missing, make sure there is a Renderer assigned as the default on the current Universal RP asset:PC_PipelineAsset" error is thrown
Expected results: No errors are thrown
Reproducible with versions: 2022.3.64f1, 6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a3
Tested on (OS): Ubuntu 24.04, macOS Silicon Sequoia 15.5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
Add comment