Closed Melech closed 4 years ago
Still happening in 3.1.1 got socket error: 10054
I can't reproduce this on commit https://github.com/godotengine/godot/commit/6b30f284a0544972f761be3e92ad8d1b176c9f9f on Linux. Playing the Multiplayer Bomber demo for about 5 minutes results in no errors (and nothing printed to the console). Perhaps this is OS-specific?
After test again on new project with only Node2D the crash is unrelated to Multiplayer Bomber Demo. Crash will always happen to demo that run after the first one.
Found the work around for my problem.
Wait until second demo stop responding and click X button then
Try to restore the program
After that join localhost client no longer crash. And on windows 10 everything work fine without this issue.
Edit: Found another method. Run first demo and second demo stop the first and run its again also work.
Can anyone confirm if this still happens in Godot 3.2 with the current version of the demo project?
Don't crash anymore for me, Godot 3.2 with new bomber demo.
I'm closing this then, but feel free to comment if anyone is experiencing crashes still.
When I run this demo, it works fine for exactly 90 seconds, then the non-host client crashes with no error printed in output, or the cmd prompt running in the background.
The host sees the client disconnect after about 5 seconds seconds and ends the game, but never crashes. Only the clients connecting to the host crash (every time after exactly 90 seconds)
The client thread locks up and becomes unresponsive. Even after I close the non-responsive window, godot still shows the game as running and I have to click stop.
The client crashes even if I do not start the game. It happens 90 seconds after the UDP(?) connection is established with the server.
I am running this on Godot 3.0.2, windows x64