Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2022.2.0a12
2022.2.3f1
2023.2.0a7
2023.3.0a3
Issue ID
UUM-30912
Regression
Yes
[URP] Render Pipeline Converter "Convert Assets" button is active and does nothing, because no assets are initialized yet
Steps to reproduce:
1) Download attached project and open in Unity
2) Open Render Pipeline Converter: Window >> Rendering >> Render Pipeline Converter
Note: Convert Assets button will be active and does nothing
Expected result: Convert Assets button should be inactive(greyed out), because assets are not initialized yet
Actual result: Convert Assets button is active and does nothing
Reproduced with:
2022.2.0a12; 2022.2.0b1; 2022.2.3f1
Not reproduced with:
2022.2.0a11
Regression since:
2022.2.0a12
Device under testing:
MacBook Pro (16-inch, 2021), CPU: Apple M1 Max, Memory: 64 GB, macOS: Monterey 12.6 (21G115)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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 (2023.3.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.