-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Cannot spawn more than one thread #10
Comments
Looks like the error has something to do with Maybe this helps: Automattic/node-canvas#1718 |
Thanks for looking into this, turns out that the causing issue is indeed Closing this, though of course a canvas independent implementation would be amazing - maybe with Phaser 4. |
👍🏻 Btw, I was experimenting with a Standalone Arcade Physics lib. |
Yes! Appreciate this so much since there seems to be no great standalone Node.JS physics engine out there (P2 and Matter.js seem abandoned) others are really small and barely used 🤔 |
No, matter.js is not abandoned. It's my favorite 2d physics engine. |
Okay, glad to hear that too! I had read that somewhere (cannot have been a credible source though) and the open issues/ PRs did not directly contradict it. But we are way off topic here now anyway 😉 |
Description
I am using
phaser-on-nodejs
for implementing an authoritative server instance of a multiplayer online game. There might be multiple games in parallel, which is why I need multiple instances of the server and I was hoping to solve this with multithreading.How to reproduce
Assuing I have a working
phaser-on-nodejs
game working with an entry script calledgame.js
, I spawn the server side code using something like:With the first thread this works fine, however on spawning a second thread I get:
The text was updated successfully, but these errors were encountered: