I was getting the same error.
There is workaround:
- Use a port that is not included in the default dynamic port range (so select port from
49152to65535range ), and do not specify the port as an excluded port by running thenetshcommand.
The bigger issue is that after you change the port for the launcher, you’re unable to change the port in the multiplayer mod in the game itself - it remains set to 4444 because the zip file with the mod is getting replaced with every launch of the launcher.
Then "Game is not connected to the launcher" error appears even the launcher (by observing the console) is obviously controlling the game instance, even the game is showing correct launcher version (but the ports mismatched - launcher is set e.g. to 50150 to prevent the issue from this subject, game mod remains set to 4444).
But I’m not sure if the port matching settings will solve all issues and I’ll be finally able to connect to my localhost server. I tried to change the port settings in the mod zip file and lock it by setting Windows file permission to readonly so the launcher was unable to replace it, however the "Game is not connected to the launcher" error remains…
The beamng.log file contains this:
12.08414|E|GELua.MPCoreNetwork.send| Socket error: Socket is not connected
13.46937|E|GELua.MPCoreNetwork.send| Socket error: Socket is not connected
15.40501|W|GELua.MPCoreNetwork.connectToLauncher| connectToLauncher called! Current connection status: false