Skip to content

Conversation

nishchalchandna
Copy link

We compare absolute values, but then store the plain value as the current max. This breaks in the case where the closest off is a negative dot product, but is overridden by a subsequent, smaller positive dot product.

How did I find this? Well it apparently happened enough times in game for me to notice that the arrow was often pointing in the wrong direction.

(I've not tested this, but if you want me to let me know how)

We compare absolute values, but then store the plain value as the current max. This breaks in the case where the closest off is a negative dot product, but is overridden by a subsequent, smaller positive dot product.

How did I find this? Well it apparently happened enough times in game for me to notice that the arrow was often pointing in the wrong direction.
@nishchalchandna
Copy link
Author

@qqrz997 to take a look.

FWIW I have been using this patch for the last couple of days in my own game. So it nominally works (and removes the randomly pointing arrows).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant