Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.33f1
2022.3.14f1
2023.2.2f1
2023.3.0a16
6000.0.0b11
7000.0.0a1
Issue ID
UUM-57876
Regression
No
[BiRP] GetScriptableCullingParameters() uses the wrong projection matrix when rendering two forward+ passes in XR
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. In Mock HMD Add Camera window, select the Rendering Mode as “Single Pass Instance” for the Mock Camera 0
4. Enter the Play Mode
5. Select the Active checkbox for Mock Camera 0
6. In the Render Texture Viewer window, scroll down to view the output of the newly enabled Mock HMD and observe the shadow on the bottom of the green cylinder
Expected result: Shadow is fully rendered
Actual result: Only half of the shadow is rendered
Reproducible with: 2021.3.33f1, 2022.3.14f1, 2023.2.2f1, 2023.3.0a16
Reproducible on: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- In 2023.2 and above the Mock HMD Add Camera window is called MockHMD.Editor.MultiCamera.Add and the Render Texture Viewer window is called MockHMD.Editor.MultiCamera.Ren
- In 2023.2 and above Scene appears darker
- Does not reproduce with Multi-Pass
- Does not reproduce with OpenXR or Vulkan
- Only reproduces in Play Mode
- Reproduces with All Graphics APIs
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
- WebGPU performance regression
- Addressables Report window UI is broken when opening via Build > New Build > Default Build Script
- Addressables Profiles window UI break when creating a new Variable with a long name
- No character limit when renaming Profile in Addressables Profile window, allowing excessively long names
- Blurry, low quality Active Profile icon used in Addressables Profiles window
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.