Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.27f1
2022.3.1f1
2023.1.0b20
2023.2.0a18
Issue ID
UUM-37784
Regression
No
Physics2DRaycaster does not trigger input when the Overlay Camera depth is lower than its Base Camera
How to reproduce:
1. Open the “T1571378_OverlayCam.zip“ project
2. Open the “OverlayTest“ Scene
3. Hover the mouse over the “Sphere“ GameObject in the Scene view
4. Observe the GameObject
Expected result: The sphere turns green when the mouse is over it
Actual result: The sphere does not change color
Reproducible with: 2021.3.27f1, 2022.3.1f1, 2023.1.0b20, 2023.2.0a18
Reproducible on: Windows 10
Note: Reproducible in Player
Workaround: Change the Overlay Camera depth to match the Base Camera (In the project press A)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, please contact your account manager or PRM if you’d like to discuss this specific case in more detail, or if you would like to provide additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, please contact your account manager or PRM if you’d like to discuss this specific case in more detail, or if you would like to provide additional information relating to the severity of this bug.