Hey guys! I play on the beammp meo drag servers literally everyday and for the last couple days I’ve been getting the same error over and over again while trying to go into a 2fast meo server. Really annoying and upsetting. I love this game and I feel like I’ve done everything to try and make it work. Anybody have any ideas???
This is a bug that is known
opened 01:26PM - 24 Sep 22 UTC
bug
enhancement
**Fill out general information**
OS (windows, linux, ...): Windows (maybe Linux… )
BeamMP-**Launcher** Version: 2.0.77
**Describe the bug**
The launcher disconnects from the server during the download of mods from the server. This happens while the mod is downloaded not in between them. A wireshark capture and the server/client logs implie that the disconnect happens intentionally from the Launcher.
[23/9/2022 00:01:57] [INFO] Launcher version is up to date
[23/9/2022 00:01:57] [INFO] Game Version : 0.26.1.0
[23/9/2022 00:01:57] [WARN] Game is newer than recommended, multiplayer may not work as intended!
[23/9/2022 00:01:57] [INFO] Downloading mod please wait...
[23/9/2022 00:01:58] [INFO] Download Complete!
[23/9/2022 00:01:58] [INFO] Game Launched!
[23/9/2022 00:02:13] [INFO] Game Connected!
[23/9/2022 00:02:13] [WARN] Game Reconnecting...
[23/9/2022 00:02:14] [INFO] Game Connected!
[23/9/2022 00:02:29] [INFO] Attempting to authenticate...
[23/9/2022 00:02:29] [INFO] Attempting to authenticate...
[23/9/2022 00:02:29] [INFO] Authentication successful!
[23/9/2022 00:02:30] [INFO] Authentication successful!
[23/9/2022 00:02:33] [INFO] Connecting to server
[23/9/2022 00:02:33] [INFO] Connected!
[23/9/2022 00:02:33] [INFO] Checking Resources...
[23/9/2022 00:02:33] [INFO] Syncing...
[23/9/2022 00:03:54] [INFO] 0 <<<<<<<<------------------
[23/9/2022 00:03:54] [WARN] Failed to close socket!
The Zero in the launcher log comes from:
https://github.com/BeamMP/BeamMP-Launcher/blob/master/src/Network/Resources.cpp#L132
which is the return of recv().
"If the connection has been **gracefully** closed, the return value is zero."
https://learn.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-recv
This means that the connection has been intentionally closed and the capture point towards the launcher causing it.
**To Reproduce**
Steps to reproduce the behavior:
I personally could not reproduce the bug, but these seem to be the steps to reproduce the bug. The bug does not happen each time. And seems to occure more often when the connecting player is far away from the server location (e.g. USA <-> GER)
1. Setup a Server
2. Put a bunch of Mods into the Client resource folder (it appears that the larger the mod, the more likely it is that the bug occurs e.g. a 700mb mod)
3. Connect to the Server with the game until the bug appears during mod download (you might have to delete the mods from your launcher resources folder to trigger the download again)
= You will see "Socket Closed Code 1" in the Lua mod and the 0 in the launcher when the bug has been reproduced successfully.
**Logs**
The Discord user Oro#9824 was so friendly to help debugging the bug so far and also uploaded the logs and capture here
https://www.dropbox.com/s/r3h7uom20dc91p5/Crash.7z?dl=0
**Additional context**
A ton of players already reported this bug in the dc by now
Only thing you can do currently is to pre download the mods and have them already in your Resource folder
1 Like