Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
1
Found in
2021.3.18f1
2022.2.8f1
2023.1.0b5
2023.2.0a4
2023.3.0a3
Issue ID
UUM-28265
Regression
No
OnPointerEnter/OnPointerExit is called when the mouse is not moving
Reproduction steps:
1. Open the attached project “UI_Bug“
2. Open the “Offline3D“ Scene
3. Enter Play Mode
4. Click the “Singleplayer“ button
5. Press the “I“ key to open the inventory
6. Hover your mouse over the sword icon
7. Without moving the mouse, move the character around using the “A“ and “D“ keys
Expected result: The sword UI is always visible
Actual result: The sword UI flickers when moving
Reproducible with: 2021.3.18f1, 2022.2.8f1, 2023.1.0b5, 2023.2.0a4
Not reproducible with: 2020.3.45f1 (Invalid dependencies)
Reproduced on: macOS 13.0.1, Windows 10 64bit (User reported)
Note - Tested the Build
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Hello again, the project provided with this bug case is unfortunately too complex and heavy to be effectively used for debugging the issue you found. If you could share a simpler example project that allowed us to do so effectively there would be a higher chance to get this sorted out officially within the Unity code. If that's not possible, one of our colleagues has shared some alternatives that can help overcoming this issue, like not attaching the canvases to the moving objects themselves. There are ways you can organize your hierarchy that would provide you the same outcome without running into the issues you're currently experiencing.
Best regards,
Julia Perdigueiro
Manager, Software Engineering
Resolution Note (2023.3.X):
Hello again, the project provided with this bug case is unfortunately too complex and heavy to be effectively used for debugging the issue you found. If you could share a simpler example project that allowed us to do so effectively there would be a higher chance to get this sorted out officially within the Unity code. If that's not possible, one of our colleagues has shared some alternatives that can help overcoming this issue, like not attaching the canvases to the moving objects themselves. There are ways you can organize your hierarchy that would provide you the same outcome without running into the issues you're currently experiencing.
Best regards,
Julia Perdigueiro
Manager, Software Engineering