Search Issue Tracker
Fixed in 5.2.0
Votes
0
Found in
5.1.0b3
Issue ID
690612
Regression
No
[PointerHandlers] Pointer enter/exit detection order is not working correctly with sorting layers
Steps to reproduce:
1. Open the attached project
2. Open 'EventSystemBug' scene
3. Notice that three sprites are rendered corretcly according to the 'Sorting Layer' properties set
4. Play the scene
5. Hover the mouse on these sprites
Expected behavior: OnPointerEnter and OnPointerExit should be called with the same order the sprites are rendered.
Actual behavior: OnPointerEnter and OnPointerExit functions gets called without taking sorting layer into account.
Workaround: Place all the sprites in the same Sorting Layer and change their 'Order in Layer' values to match the wanted rendering result. Notice that now the mentioned functions get called as expected.
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
Add comment