Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.63f1
6000.2.15f1
6000.3.0f1
6000.4.0a5
6000.5.0a2
Issue ID
UUM-129204
Regression
No
Nested Canvases' CanvasGroup.blocksRaycasts parameter ignores inheritance from parent Canvases' CanvasGroup when Override Sorting is enabled
How to reproduce:
1. Open the attached “My project” project
2. Enter Play mode
3. Try to click the Button through the Image
4. Observe the Game view
Actual result: Image GameObject blocks Raycasts
Expected result: Image GameObject will not block Raycasts
Reproducible with: 2023.1.0a1, 6000.0.63f1, 6000.2.15f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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 reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
While the CanvasGroup respects its parent CanvasGroup's blockRaycast value, the GraphicRaycaster on the Child Canvas is behaving as expected. When a Canvas has a GrahicRaycaster, Raycasts go down from the Canvas to all of its elements, not up to other Canvases. The Raycasts can pass through transparent elements of child Canvases. CanvasGroups may be used to ignore those Raycasts, but the Canvas with the GraphicRaycaster still receives them. Therefore, parent and Child Canvases which both have GraphicsRaycasters will behave as follows. The child Canvas will handle Raycasts on all if its children, and CanvasGroups can be used to ignore those Raycasts. The parent Canvas handle all the Raycasts on it's children, but not the children of the Child Canvas.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
While the CanvasGroup respects its parent CanvasGroup's blockRaycast value, the GraphicRaycaster on the Child Canvas is behaving as expected. When a Canvas has a GrahicRaycaster, Raycasts go down from the Canvas to all of its elements, not up to other Canvases. The Raycasts can pass through transparent elements of child Canvases. CanvasGroups may be used to ignore those Raycasts, but the Canvas with the GraphicRaycaster still receives them. Therefore, parent and Child Canvases which both have GraphicsRaycasters will behave as follows. The child Canvas will handle Raycasts on all if its children, and CanvasGroups can be used to ignore those Raycasts. The parent Canvas handle all the Raycasts on it's children, but not the children of the Child Canvas.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.