[BUG] AddOnScreenDebugMessage() Produces FVector to Change

Same results proceeded.Whenever the debug messages are on, they are definitely changing, while off they’re fine.

However, I did modify my logic a little and that seems to of fixed the issue (at least as far as I can tell) in that I am no longer adding up an Array of FVector’s to act as all my imposing forces to produce acceleration. Instead, I’m using a single FVector and modifying it directly and then using that, and the artifacts ar no longer appearing at this moment. So whether it was just poorly executed programming, or an actual bug I have worked around it for now.

But I couldn’t find any logic as to why adding the debug call would produce different results in the first place.