-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NodeJS: scene started before plugins loaded #6893
Comments
Hi @hubertgrzeskowiak. Thanks for submitting this issue. We have fixed this and pushed it to the |
Thanks heaps, @zekeatchan! That's some awesome news. And who would have thought that the fix is literally a single line (I spent a few hours trying to debug this). I will try to test it next time I've got some time, but that may take a few weeks. |
Cheers @hubertgrzeskowiak, glad to be of help and hope it works as expected. Feel free to add a comment or reopen this issue if this is still a problem. |
Just tested this and it still doesn't seem to work for me... Here's a sample for reproducing:
Remove the nodeJS import and switch render type to AUTO and it work in a browser, but on NodeJS, this gives me:
|
Description
This is a duplicate of geckosio/phaser-on-nodejs#13, but I'm hoping that somebody on this project might have some hints on the problem.
In short, when running on NodeJS, Phaser starts the system scene and the first scene set in global config before initialising any of the plugins specified in the game config. This seems to be caused by the texture manager finishing unexpectedly early and starting the main game loop, before the game's boot event is even fired - the plugin manager is listening on that for booting.
Any idea how to debug this? I find Phaser's boot sequence events rather confusing.
The text was updated successfully, but these errors were encountered: