GAME CRASHES!

When I freeze physics or game gets unstable and freezes physics and i change the map, when it is done loading it shows the map from the air and wont let me unfreeze physics.... A bug worth noting

 

Have you disabled mods and cleared cache?

 

Well it does that even when I have no mods, its the game's engine itself. That is the games bug... I just want them to fix it, it can be avoided.

 

Hmmm it happens when the game goes unstable and then i try to load another map when the physics are still frozen from being unstable....

 

I tried this.
Installed this mod: http://www.beamng.com/resources/bkl-claw-tractor.168/
When I spawned the tractor the game froze the physics because the mod is unstable.
If I change map I can still press J to unfroze the physics and the game runs fine.

 

Take a look at system memory usage when this happens. It may not be completely frozen, it may just be doing a lot of 'juggling'.
If you've been running the Tennessee USA map, sometimes it helps to restart the game before and after running it, just to be safe, as Beamng.drive sometimes does not free up all the memory between maps (it's not as bad as it was before 0.7.x and 0.6.x too, but it still does hang onto some assets in memory).
Sometimes, especially with anything but the absolute fastest-ghz-rated processor (and RAM) out there, it may take up to a minute for it to become un-stuck. Fiddle with the browser for two-to-three minutes in the mean-time and see if it un-sticks. I get this 'stuck app while unpausing physics' a lot when I exit the editor after editing my map (it's a lot better in 0.7.x), which happens especially if I've used up 80~90% of my 16gb of system RAM. Usually in a few seconds, sometimes 10~20 seconds, it gets unstuck just fine. Once or twice, it's CRASHED to desktop... but a restart of the app and it's back to business.
Also, using lots of AI (especially on LARGE maps) can really eat up memory, too. Be watchful.

I should know, I've managed to get this system up to 40GB of combined memory usage, 16gb of system ram, 24gb of page file - all at once.

 

Wow, I guess it was Just me then

 

"showing the map from the air" is because the camera attaching to the car's location doesn't happen until you unfreeze physics.
Try clicking anywhere on the screen (so that input isn't directed to the UI by mistake), then pressing J and waiting a while - like a good minute (especially if it's been paused a while). It may have to do a lot of thinking or juggling for some oblivious reason. It may not be totally locked up.
I've never had it refuse to unfreeze*, though a bad or outdated vehicle or prop could consistently re-freeze things.
If you think its frozen see if its using one core of the cpu & memory use is going up or down in task manager (CTRL+SHIFT+ESC).

* it has crashed to desktop after map-editing with physics paused for hours!

 

Okay, thank you!