Thank you! Yes, it is likely a moving issue. I used a nested for loop to create the trajectory display, which really isn't the most optimal route to draw it. I do plan on fixing that in a future update though!
