Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2022.2.0b3
2023.1.0a3
2023.2.0a1
Issue ID
UUM-11866
Regression
No
Render Pipeline Converter doesn't find all the Readonly materials when used right after installing the Universal RP package
Steps to reproduce:
1. Open the user’s attached project
2. Navigate to Window > Package Manager and install the Universal RP package
3. Navigate to Window > Rendering > Render Pipeline Converter
4. In the Render Pipeline Converter window make sure that the “Built-in to URP” option is selected
5. Enable the “Readonly Material Converter” option and click “Initialize Converters“
6. Observe the number of items found
7. Close the Render Pipeline Converter window and repeat 3-6 steps
Expected result: 250+ items are found the first time the converter is used
Actual result: First time 0 items are found and 250+ are found the second time the converter is used
Reproducible with: 14.0.2 (2022.2.0a12), 14.0.3 (2022.2.0b3), 15.0.0 (2023.1.0a3)
Not reproducible with: 12.1.7 (2021.3.8f1), 13.1.8 (2022.1.13f1), 14.0.2 (2022.2.0a11)
Couldn’t test with 10.9.0 (2020.3.37f1) (Render Pipeline Converter doesn’t exist)
Reproducible on: Windows 10
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
- [Linux] Cannot reorder GameObjects in the Hierarchy when the AI Assistant package is installed
- [iOS] Text Input field stops receiving changes when the "Cancel" button is used on the soft keyboard
- [WebGPU] URP RenderGraph RenderPass doesn't clear textures
- Query Builder items display raw code style names instead of human readable labels in search field
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.