Search Issue Tracker
Fixed in 2023.1.0b10
Fixed in 2022.2.X, 2022.2.15f1, 2023.1.X, 2023.2.X
Votes
0
Found in
2022.2.3f1
Issue ID
UUM-25186
Regression
Yes
Custom renderer feature doesn’t work and errors are thrown when using the official imported URP samples
Reproduction steps:
1. Open project “IN - 26766”
2. Open scene “KeepFrame”
3. Enter Play Mode
Expected result: no errors are thrown and the particles in the scene have a smudged trail effect
Actual result: errors are thrown in the console and particles have no effect - the custom renderer feature doesn’t work
Reproducible with: 2022.1.0b1, 2022.2.3f1
Not reproducible with: 2021.3.16f1, 2022.1.0a16
Couldn’t test with: 2020.3.44f1 (no samples available), 2023.1.0a26 (due to compiler errors trying to import samples)
Reproducible on: macOS Catalina 10.15.7 (Intel)
Notes:
- The attached project uses official URP samples imported through Package Manager
- The “TrailEffect” sample scene also doesn’t work as expected (errors are thrown in the console and the trail effect isn’t visible) due to the same custom renderer feature from “KeepFrame” being used
- Couldn’t build player due to compiler errors
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment