Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flying pathing: Too high above #40

Open
Jamayyy opened this issue Nov 5, 2024 · 1 comment
Open

Flying pathing: Too high above #40

Jamayyy opened this issue Nov 5, 2024 · 1 comment
Labels
Bug Something isn't working

Comments

@Jamayyy
Copy link

Jamayyy commented Nov 5, 2024

This bug occurs when the "automatically interact with quest NPCs" is enabled while using the flying vnav pathing to the next quest NPC.

The problem is that vnav always paths in a way where you first fly above the NPC's head, and then descend on their location afterwards. Meanwhile the automatic interaction attempts to interact the instant the NPC is in range, but at that point you're still flying above the NPC's head and you get the error message that the "target is too far below you".

Basically the flight path looks like the yellow line, but the interaction attempt already happens at the red point, which is too early because you're still too high above the target:
image

This could easily be fixed by waiting 500ms before interacting, while the flying navigation is active. At that point the descent will have started or finished. Or maybe better yet, let the navigation finish completely before starting the automatic interaction. Thanks!

@Limiana Limiana added the Bug Something isn't working label Nov 6, 2024
@Jamayyy
Copy link
Author

Jamayyy commented Nov 7, 2024

This could easily be fixed by waiting 500ms before interacting, while the flying navigation is active. At that point the descent will have started or finished. Or maybe better yet, let the navigation finish completely before starting the automatic interaction.

Actually, since you already have the target's and own coordinates, adding a height difference check to the distance check would probably be best

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants