[exia]

@Arbiter @Cloud
I'm calling Interactable#getInteractionPoint() and it is occasionally returning terribly incorrect Points. For example: InteractablePoint[30909,-21685]

I'm guessing it happens when the object is off screen, or something of that sort, but it would be better functionality for the method to return null in that case.

This is also the root issue of that StackOverflow Error that happens when you move the mouse to an object every now and then.

 

[cloud]

Nice job on finding the source of that issue, but you should be doing visibility checks before hand.

 

[exia]

Nice job on finding the source of that issue, but you should be doing visibility checks before hand.

Yeah, I noticed that too, it seems that my code was checking if the mouse was inside the object before doing this (if the mouse is on it already then it will be visible), but I had notted the contains by accident.