GPUPicker: Fix multiPickAsync return unexpected results in different hardwareScalingLevel #16537
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
see https://forum.babylonjs.com/t/gpu-multi-picking-issues/58074/2 and https://forum.babylonjs.com/t/gpu-picker-multi-pick-adjust-to-dpr/58091
In
multiPickAsync
, when the length of the screen coordinate array passed in is greater than 1, it is not processed to adapt to the current DPR, resulting in unexpected results being returned.