Search Issue Tracker
By Design
Votes
0
Found in [Package]
14.0.0
Issue ID
1391696
Regression
No
Camera uses Viewport Rect for mouse position when the Camera's Render Type is set to Overlay
How to reproduce:
1. Open the attached project "ViewportRectBug.zip"
2. Open "SampleScene" Scene
3. Select the "OverlayCam" GameObject in the Hierarchy window
4. Change the Render Type to Base in the Inspector window
5. Change the Viewport Rect values to X: 0.4, Y: 0.4, W: 0.4, H: 0.4
6. Change the Render Type to Overlay
7. Enter Play mode
8. Hover the mouse over the cubes
Expected result: The mouse is not offset, the cube that the mouse is hovering over turns red
Actual result: The mouse is offset, the cube that the mouse is not hovering over turns red
Reproducible with: 7.3.1, 7.7.1 (2019.4.36f1), 10.8.1 (2020.3.30f1), 12.1.5 (2021.2.13f1), 13.1.5 (2022.1.0b9), 14.0.0 (2022.2.0a5)
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
- Shader warnings are being thrown after building Mixed Reality Template
- Error is thrown when entering play mode with build profiles docked and standalone profiler open
- The Player hangs when activating another maximized application
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
- Crash on RtlLookupFunctionEntry when using 10 or more GameObjects with Articulation Body component in the scene
Resolution Note:
By design. If the user selects the base camera again and look at the stack. There should/will be an error that says it is out of sync.