Delay in triggering first on_step call when realtime=True

[LostLucidity]

Hello. As in the title, on_step does get trigger for me until the 11th second in game time. This does not happen when realtime=False. I've emptied out the on_step method with just a print statement to remove any potential computer lag with the same result.

[alexander-kazakov]

Yes, I have the same, but the interval is random. Sometimes a few seconds, sometimes even a whole minute...

[h3nnn4n]

Same here. It takes a few seconds before it runs if realtime=True

[LostLucidity]

This seems to be caused by VSCode. A couple of users on discord have seen this issue cleared when running on the console outside of VSCode.

[alexander-kazakov]

What is VSCode? I'm running via command line.

…

On Wed, Aug 8, 2018, 13:10 Daniel Muñoz ***@***.***> wrote: This seems to be caused by VSCode. A couple of users on discord have seen this issue cleared when running on the console outside of VSCode. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#85 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIqAll7mA2krrBwXRy8mEeu02gp11kl1ks5uOscsgaJpZM4VSI-M> .

[LostLucidity]

Visual Studio Code is a popular IDE. You can run from their embedded command line. It seems a subset of this ticket's issue involves this IDE and using their terminal.

[pelletier2017]

I have the same issue and its from running the program in pycharm.