Skip to content

Fix translucent objects are pickable when skybox is disabled#9688

Open
show50726 wants to merge 1 commit intogoogle:mainfrom
show50726:fix/transparent-picking
Open

Fix translucent objects are pickable when skybox is disabled#9688
show50726 wants to merge 1 commit intogoogle:mainfrom
show50726:fix/transparent-picking

Conversation

@show50726
Copy link
Contributor

Fix #9687

Previously, we only cancel the depth write of translucent objects in structure pass, the commands still happened, so the ID of translucent objects were still written to the picking buffer (but without updating the depth buffer).

It didn't cause problem when the skybox is enabled because the depth of skybox is always drawn at last, so the translucent objects' ID will eventually be overriden with the skybox one and hence becomes unpickable.

However, when the skybox is disabled, the translucent objects' ID remains on the buffer so we would be able to pick it.

We solve this problem by cancelling the translucent objects' commands completely when they are filtered out.

@show50726 show50726 added the internal Issue/PR does not affect clients label Feb 6, 2026
Copy link
Member

@bejado bejado left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but Mathias should definitely review

@bejado bejado requested a review from pixelflinger February 6, 2026 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Issue/PR does not affect clients

Projects

None yet

Development

Successfully merging this pull request may close these issues.

setTransparentPickingEnabled(false) does not disable transparent picking unless a skybox is present

2 participants