Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2020.3.23f1
2021.3
2022.1
2022.2
Issue ID
1414665
Regression
No
OnMouseXXX events are not triggered when "Far Clipping Plane" of camera is set higher than 1e+09
Reproduction steps:
1. Open user attached project
2. Open the "SampleScene" scene
3. Press Play
4. In the Game view click on the white box
Expected result: Names of executed OnMouse functions are printed in the console
Actual result: Nothing is printed in the console
Reproducible with: 2022.2.0a14, 2022.1.0f1, 2021.3.2f1, 2020.3.34f1, 2019.4.39f1
Reproducible on: Windows 10 (tested only on Windows 10)
Note: Issue only reproduces if Projection of camera is set to Orthographic. A workaround to this issue would be setting the tested gameObject Z-axis position to any value greater than 0.5
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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Resolution Note:
This issue is caused by floating-point imprecision. When the object is close to the Vector3.zero position and the Far Clipping Plane is very far (1e+09) + camera is Orthographic, this causes imprecise distance calculations.