"Launcher is up to date error" problem

[sekkej]

Bug: Launcher closes after checking version. My launcher version is v2.0.82, but if you go to the one of these links: https://beammp.com/builds/launcher?version=true from Startup.cpp -> line 77 https://backup1.beammp.com/builds/launcher?version=true from Startup.cpp -> line 80 You'll see that launcher checking current version with old versions (launcher==v2.0.82, version from link==v2.0.79 or v2.0.81). I'm not very good at cpp, but my launcher doesn't work, it crashes after message "Launcher is up to date" (Startup.cpp, line 111: else info("Launcher version is up to date");)...

Some screenshots: p.s. look at the my beammp launcher version after this message, my launcher crashes automatically downloaded old versions

[Anonymous-275]

Hey there, you could try updating the launcher manually from that link. This type of bug's fix is in V3 that hopefully will come eventually to public release.

[sekkej]

Hey there, you could try updating the launcher manually from that link. This type of bug's fix is in V3 that hopefully will come eventually to public release.

Thank you for the answer, but this fix method also doesn't work. I downloaded launcher from https://backup1.beammp.com/builds/launcher?download=true (Startup.cpp line 87). Launcher automatically starts download of new launcher version (v2.0.82).

[RealSourceOfficial]

+1, I cannot launch through BeamMP as of 2.0.82 Originally thought it was my portable copy of BeamNG causing weird issues, however after ejecting the disk, restarting Steam to make sure it wasn't using the portable copy, and relaunching, I still can't launch the game...

EDIT: Fixed - Verified game files, ran the game without BeamMP launcher and then started it with launcher again.

[Anonymous-275]

Please reopen if this persits in 2.1.0

[O1LER]

Since we cant use the new launcher, this is still an issue with 2.0.82

Please fix

[Protogen187]

@sekkej Did you buy BeamNG.Drive from Steam? Did you change your BeamNG.Drives Userfolder location?

[lionkor]

The issue IMO is not that it shows that, but the fact that it closes without properly explaining what went wrong, steps the user can take to fix that, etc.