Repository navigation
Fix distant pickup - #891
Conversation
|
As far as I can see, the code is the same, and the part that says Nevertheless, I checked out your branch, and couldn't find any difference. Which demo are you testing? |
|
I've updated my addon version in my project and this change broke the distant grab. Indeed when reading again my commit, it should be better, I will rework it, because it just reversed the problem but with the variable instead. The new code with typings introduced that if the pickable doesn't have the function, it will return (even if it has the variable) |
|
I see what it is now. Because of the line This should just be changed to |
|
Oh nice catch for the snap zone. Should I update the PR with your code proposal or I met you handle this and I close this PR ? |
|
Updating the PR you have here is fine. |
|
There is a problem with the new changes: we are now rejecting ranged grabs for objects that explicitly enable them. Instead of: |
|
damned I copy pasted what you wrote without reading 🥲 |
|
Can you squash your commits? |
|
Sorry for the delay |
The PR #804 introduced a bug in the function pickup
_on_ranged_entered()by rejecting every Node without acan_ranged_grabfunction.I think most of the scenes, like the basketball, relies on a var
can_ranged_grab, and they are rejected.Can you confirm @mubinulhaque ?
(btw thank you for all these typings everywhere 😍)