@Ezzett the way I understood it, 3run is already using calculations that are framerate independent but very low framerates still produce results that are "off"

I'm pretty certain it's due to the lower accuracy when running at a low framerate

@3run I don't really get it? from what I can see, the code is correct and it behaves the way it should?