Search Issue Tracker
Fixed in 2022.2.0f1
Fixed in 2022.2.X, 2023.1.X, 2023.1.0a19
Votes
1
Found in
2022.2.0b13
2023.1.0a9
Issue ID
UUM-12644
Regression
No
Custom Full Screen Render Pass does not work on XR
Error assigning 2DArray texture to 2D texture property '_BlitTexture': Dimensions must match
is thrown when trying to run on XR
Steps to reproduce
1. Create new URP project
2. Add "Full Screen Pass" renderer feature (it should have default material assigned)
3. Add XR to the project
4. Probably works with other XR SDKs but I tested only with MockHMD
5. Play the scene.
You should get an error and default full screen effect is not rendered.
Project that reproduces the issue is also attached
Comments (2)
-
moritz_jaeger
Nov 05, 2022 21:17
It does not occur when I switch the Stereo Rendering Mode to "Multi Pass"
-
moritz_jaeger
Nov 05, 2022 21:09
Having the same problem with 2022.2.0b13.
Using the Oculus XR Plug-in with a Quest 2 connected via Quest Link.
Stereo Rendering Mode is set to "Single Pass Instanced".Only occurs if I set "Color" as requirement on the Full Screen Pass Renderer Feature.
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
- Entering “NaN” or “Infinity” values in Game Object Brush Orientation value fields spams Quaternion-related errors in the Console and persists unless value is undone in Tile Palette window
- An InvalidOperationException is thrown in the Editor when using On-Tile Rendering with the Mock HMD plug-in
- Unity UI does not trigger "OnFocusLost" and doesn't refresh when focusing on other Windows in the Editor
- Project Auditor's settings cannot be searched in the Preferences window
- Crash on SerializableManagedRef::CallMethod when performing various Unity operations
Resolution Note (fix version 2022.2.0f1):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/SGB-278
Resolution Note (fix version 2023.1.0a19):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/SGB-278
Resolution Note (fix version 2023.1):
Fixed in 2023.1.0a19