When the direction does not change the error is zero. But when it starts to turn the estimate overshoots, I get the mechanics behind this.
What I want to know is, how does the algorithm work in order to get back on track quickly.
The estimated position where the entity is drawn must "catch up" with the next estimated position, does this mean the velocity increases beyond the real velocity?
Where exactly do we aim our new estimated velocity vector, if you would look at the image? Do we compensate by speeding up and overshooting the "real velocity vector" (last red line)? Or do we use a smooth cubic method of narrowing in? Or do we just point the corrected estimated velocity vector at the same point the real sample points? What is the vector math here?
What is it meant by "snap" and "aim" velocities/pos in the EPIC source?
Cheers!