Answer by Baste
The problem is that you're starting another instance of the coroutine on every frame. This means that you've got a bunch of updates of the newPos and oldPos variables all the time, which will cause a...
View ArticleAnswer by robertbu
As @Baste mentioned, there are significant problems with your current approach. But even if you get them fixed, there is a conceptual problem. Assuming you are checking each frame but are updating...
View ArticleAnswer by Baste
The problem is that you're starting another instance of the coroutine on every frame. This means that you've got a bunch of updates of the newPos and oldPos variables all the time, which will cause a...
View ArticleAnswer by robertbu
As @Baste mentioned, there are significant problems with your current approach. But even if you get them fixed, there is a conceptual problem. Assuming you are checking each frame but are updating...
View Article
