SO, Update 0.36..

Since updating beamng to the latest update, I keep getting this error - with mods installed and strangely without any mods installed... is anyone else having this issue?

I have uninstalled, reinstalled, verified files, you name it.. and still have this problem... really pissing me off.
I did originally post in the official 'latest update thread' but was ignored?

IMO, it's clear the dev team have changed something with this update,, but it has an unfortunate chain affect which has made the game unstable. If this is anything like this, this update shouldn't have been released without some serious debug testing first.

Anyhow, any help with this is greatly appreciated.

 

I see this error the first time here. Perhaps you have a hardware issue or something else is strange on your machine.

 

Thanks for you reply.

These are my specs: https://www.3dmark.com/sn/2396480

Never had an issue before until this update? I also get the error 0xc0000000 sometimes..

 

I get the same error, too. It usually happens when I'm working on one of my maps and switch back from the World Editor to Game Mode.

We have almost identical hardware. Perhaps a problem with this configuration or the graphics card (RTX 4090).
Intel i9 13900KS, Asus ROG Strix 4090 OC.

 

Hmm, very strange!

I even put a bypass on my antivirus to ignore beamng (main and mods) folders just in case there was something going on there but sadly still same error.

Also updated GFX drivers in case it was this - with our rigs, we shouldn't be having this issue?

I've come to accept this update is some-what broken. I think the devs are silent on this issue because they don't know why this is happening - I'm sure they're working hard to figure this out.

Fingers Crossed!

 

I think it definitely has something to do with the last update. I didn't have this problem before.
At first, I also thought it was due to my mods - or that I had installed faulty LUA code...but even after removing all mods, the problem persisted.
Unfortunately, I can't reproduce the issue specifically.
Sometimes I work on my map for two hours - and the problem doesn't appear. And sometimes I get the error immediately after closing the World Editor after two minutes.
As a workaround, I simply respawn the vehicle.

 

Did you check if you have the degradation problem with the intel processor? I had it and it was completely weird. I got an exchange processor from intel. Make sure you always have the latest bios update installed. If you didn’t hear about it google intel degradation.

 

Wait, you said you respawn the vehicle.. and this refreshes the vehicle/map/world editor error and temporary fix the issue until it happens again?
For me it doesn't remove the error when refresh the vehicle and completely bricks the vehicle.. maybe map its different when working on map/world editor? The error is the same as the pic you posted above, and replace 'pick up' with any other vehicle I have spawned at the time.

What a pain in the ass aye?
Hopefully this problem will be fixed sooner than later, maybe a hotfix or at most fixed in the next future update

 

I don't think the problem is related to the Intel degradation issue.
All other applications run smoothly, without crashes, errors, or blue screens.
Furthermore, the problem only started occurring after the last update to version 0.36...I can narrow it down pretty precisely, since I've never had this error message before.

Just pressing the R key doesn't fix the problem for me. You have to use CTRL + R.

 

interesting.. I will try this when it happens - but honestly I might have to bite the bullet and wait for the next update.

 

We can try to narrow down the source of the error. When does the error occur for you? Randomly while playing? Or are you also using the World Editor? And how often does the error message appear? Can you reproduce it?

 

For me, I could get lucky and be able to drive around for 30secs to a minute ..sometimes the error shows straight away as soon as the level loads. But it is guaranteed this error will show every time.

How about for you?

Edit: I should add, I haven't used world editor since last build, also for how it seems for me is the issue will pop up randomly with what I said above.

 

I really don't play much.
Instead, I work a lot on my map(s).
The error has never occurred while playing.
Usually, it only occurs when I'm in the World Editor...and then switch back to test the map changes.
Sometimes the error occurs after a few minutes...and sometimes only after hours.