Search Issue Tracker
Won't Fix
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.