Search Issue Tracker
Fixed in 6000.0.0b11
Fixed in 2023.3.X
Votes
1
Found in
2021.3.33f1
2022.3.17f1
2023.2.5f1
2023.3.0b1
Issue ID
UUM-60093
Regression
No
Adding URP to a project does not respect Camera's Target Eye value
Steps to reproduce:
1. Open the attached user's project "VR Spectator.zip"
2. In the Hierarchy, select the "VR Spectator Camera" GameObject
3. In the Inspector, under Camera -> Output (if it's available), observe the "Target Eye" property being set to "None"
4. Open Project Settings -> Graphics and add a URP Render Pipeline Asset
5. Repeat step 3 and observe that the "Target Eye" property is now set to "Both"
Expected Result: Camera's Target Eye value remains the same no matter if URP is added or not
Actual Result: Adding URP to a project does not respect Camera's Target Eye value
Reproducible with: 2021.3.33f1, 2022.3.17f1, 2023.2.5f1, 2023.3.0b1
Testing Environment: Windows 11
Not reproducible on: No other environment tested
Comments (1)
-
DevDunk
Jan 31, 2024 12:50
Not exactly the same. This one it automatic, the other is manual code
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note (fix version 6000.0.0b11):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-60381
Resolution Note (fix version 2023.3):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-60381