Search Issue Tracker
Fixed
Fixed in 2022.2.15f1, 2023.1.0b10, 2023.2.0a7
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
- Vertex data is displaced when building with Addressables with Optimize Mesh Data enabled
- [macOS] “Input.GetMouseButtonDown” gets set to true when pressing and when releasing the mouse button in the Device Simulator view if "targetFrameRate" is set in the script
- UWP Capabilities are not changed when rebuilding the project
- [Oculus] Lights causing artifacts when Forward+ Rendering is selected
- Game Window Icons are white when in light mode
Add comment