Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.1.0b1
2022.1.24f1
2022.2.0a1
2022.2.12f1
2023.1.0b5
2023.2.0a7
2023.3.0a3
Issue ID
UUM-30962
Regression
Yes
[URP] Render Pipeline Converter: Built-in Transparent material is not converted properly to URP
Steps to reproduce:
1) Download attached project and open in Unity
2) Open ReproScene
3) Install "Universal RP" package using the Package Manager
4) Go to Render Pipeline Converter: Window >> Rendering >> Render Pipeline Converter
5) Make sure converting is selected to "Built-in to URP"
6) Eanble all converters
7) Click on "Initialize Converters" button
8) Click on "Convert Assets" button
9) Go back to the Scene view and notice transparency is gone
Expected: Transparent parts should be transparent after the conversion
Actual: Transparent parts are visible in the scene
Reproduced with:
2022.1.0b1; 2022.1.24f1; 2022.2.0a1; 2022.2.12f1; 2023.1.0b5; 2023.2.0a7
Not reproduced with:
2021.3.20f1
Converter freezes the Editor using 2022.1.0a10; a13; a15 once Convert Assets button is pressed
Regression is somewhere in 2022.1 alpha, but due to Render Pipeline Converter bugs I'm not able to find the exact version
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
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
- [Settings Search] Search results not always matching search term correctly
- Crash on memcpy when opening a project that loads TSS files
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.