Fatal error when i spawn a car and i press TAB

So i joined a official Beamng server i spawn a car (the car does not appear)

  1. update your game. latest version is 0.36.4
  2. update your MP launcher. latest version is v2.5.1
  3. this is a known issue. “fatal error” could be due to reasons above. as a regular user, you should ignore this notification, it usually does not disrupt gameplay. but in this case, your vehicle was removed! this can be easily fixed by many ways, easiest being is to spawn your character in by pressing F and then in the vehicle menu click on SPAWN NEW car, then you can switch back to your character and get in the car (assuming you know the basic controls). afterwards, the TAB key should not continue this behaviour. another solution is to REMOVE ALL in vehicle configuration > debug, however, you will have to requeue and spawn everyone back in on the server manually (OR from the playerlist). as a last resort, try spamming C and TAB to change cameras and snap out of this floating bug. most of the time this happens the first time you spawn a vehicle on a server, in my personal experience…

hopefully this will be fixed soon, @WiserTixx

Thank you i see it but i have cracked beamng so … yes xd

no problem. im glad it works on a cracked client =)

and how to update my beammp?

I’ll try and see if I can reproduce this and look at the code in that function.
But quickly judging the error, it looks like a BeamNG issue/corrupted user folder.

err, it hapened with a fresh install (both userfolder and base game folders are deleted) on linux, like a few months ago. so this is still relevant. it is STILL happening, but i cant test atm. had the EXACT same issue, with the error being that the vehicle tried to spawn a ‘nil’ value or something. it made 0 sense. i remember it spawned a car and immediately removed it, and kept spamming the console with the same error UNTIL i deleted every player and i could finally spawn my own car

on the contrary, this is more of a matter of a LACK of cache, rather than the presence of it in the userfolder. so, with consequent spawns and joins, the error went away. i was able to spawn anywhere and anytime without this floating bug

but assuming people play a lot of beamng, they have accumulated a lot of cache and just simply dont get this kind of error. once again, this is just a guess

maybe its some sort of an incompatible setting set in multiplayer options about queues or camera and it was deprecated with the new code? that’d sound like a lot of work…

how to update my beammp guys?

BeamMP should automatically update itself to be compatible with the latest BeamNG.drive version. However because you have a pirated and outdated copy I cannot assist you with any incompatibilities.