Answer by Rocket Alien
For simulation, you probably want to look into putting your logic into Update() or FixedUpdate() functions and using Time.deltaTime or Time.fixedDeltaTime for computing incremental updates to your...
View ArticleAnswer by aldonaletto
Lists are .Net/Mono stuff, and have nothing to do with Update. A possible cause is the coroutine being started before its previous instance has finished: this lets two or more coroutines running in...
View ArticleAnswer by Tarlius
This may be a simple oversight in the pseudo code provided, but you do have a loop in your coroutine... right? Because otherwise you'll just run through the list once and then the coroutine will...
View ArticleAnswer by enviralDesigns
Problem fixed! Thanks for all the suggestions and help. Through a different route I came up with several days break from this I managed to troubleshoot the problem down to my own logic. There were no...
View ArticleAnswer by Rocket Alien
For simulation, you probably want to look into putting your logic into Update() or FixedUpdate() functions and using Time.deltaTime or Time.fixedDeltaTime for computing incremental updates to your...
View ArticleAnswer by aldonaletto
Lists are .Net/Mono stuff, and have nothing to do with Update. A possible cause is the coroutine being started before its previous instance has finished: this lets two or more coroutines running in...
View ArticleAnswer by Tarlius
This may be a simple oversight in the pseudo code provided, but you do have a loop in your coroutine... right? Because otherwise you'll just run through the list once and then the coroutine will...
View ArticleAnswer by enviralDesigns
Problem fixed! Thanks for all the suggestions and help. Through a different route I came up with several days break from this I managed to troubleshoot the problem down to my own logic. There were no...
View Article
