[Bug] strange network error that doesn't seem to have any helpful context

[Aristhain]

Have you read our FAQ/Wiki/#before-you-ask ?
Yes

Describe the bug
a weird network hiccup has started happening on my BeamMP client today. it prevents me from staying connected to BeamMP servers shortly after joining them.

To Reproduce
Steps to reproduce the behavior:

1. install beamng to proton7 on steam using SteamTinkerLaunch (makes it easiest to do the following steps).
2. put beammp installer binary in its compatdata and choose it as SteamTinkerLaunch's custom command. enable "only custom command," too. save and run.
3. once installed, put beammp-launcher binary as custom command. check "only custom command," too. run to use beammp like normal.
4. See 404 socket error shortly after joining into a BeamMP server.

Expected behavior
N/A

Screenshots

Desktop (please complete the following information):

• OS + Version: Linux (kernel 6.6-LTS)

Additional context
potential interference by stuff such as DNS or router is ruled out already.

[O1LER]

Whats the reason for you to not use either linux native BeamNG and/or BeamMP?

Theres a linux build in the BeamNG game folder and the BeamMP launcher can be built for linux, so you dont need to use Proton for either.

Alternatively, you can use Proton for BeamNG, for example if you have issues with your window manager (i think wayland does not like running native BeamNG). Just use the compatibility option in steam without steam tinker launch and use the native launcher. A guide is here

To your issue: Are you able to reproduce it? Has it worked previously, so is it an error introduced by a recent update? Which versions did you use of BeamNG, BeamMP launcher and mod? Which server did you try to connect to, an official one?

[Aristhain]

Whats the reason for you to not use either linux native BeamNG and/or BeamMP?

as far as i can tell, vulkan deprecated their support for my gtx 660ti, so all i'm gonna get from the native beamng binary, and anything else natively using Vulkan, is "a suitable vulkan device was not found."

Alternatively, you can use Proton for BeamNG, for example if you have issues with your window manager (i think wayland does not like running native BeamNG). Just use the compatibility option in steam without steam tinker launch and use the native launcher.

I don't fully understand what you're saying there. needs rephrasing.

To your issue: Are you able to reproduce it? Has it worked previously, so is it an error introduced by a recent update? Which versions did you use of BeamNG, BeamMP launcher and mod? Which server did you try to connect to, an official one?

yes, it is reproduced on every launch of beammp. since it started happening just today, i only assume it was the last beammp update pushed to my beammp client.

i am using the latest version of all three, and i tried connecting to both official and community beammp servers.

[O1LER]

Alternatively, you can use Proton for BeamNG, for example if you have issues with your window manager (i think wayland does not like running native BeamNG). Just use the compatibility option in steam without steam tinker launch and use the native launcher.

I meant to say with this, that you can run windows beamNG trough Proton but run the native linux beamMP launcher, so you dont need to add the windows launcher to the proton folder of windows beamNG. Follow the link to the guide, there i may have described things better.

Can you give us version numbers please? Since we issue newer versions to early access first.
Latest launcher release is v2.3.2 but the prerelease v.2.4.0 was pushed to EA members yesterday.
Same for the mod, v4.13.11 is latest, but EA gets v4.13.12, however this one is two weeks old, so i guess the issue is with the launcher

[Aristhain]

I meant to say with this, that you can run windows beamNG trough Proton but run the native linux beamMP launcher, so you dont need to add the windows launcher to the proton folder of windows beamNG. Follow the link to the guide, there i may have described things better.

huh... that honestly seems like it'd be jankier to me, but i'll try it.

Can you give us version numbers please? Since we issue newer versions to early access first.
Latest launcher release is v2.3.2 but the prerelease v.2.4.0 was pushed to EA members yesterday.
Same for the mod, v4.13.11 is latest, but EA gets v4.13.12, however this one is two weeks old, so i guess the issue is with the launcher

launcher version does indeed show as v2.4.0. not sure why, as i have not gone out of my way to do whatever i would do to be an early-access member. if the launcher has separated stable upstream and pre-release upstream, i did not do anything to have it use the pre-release upstream, either.