BeamNG shuts down after a while without an Error [v0.3.2]

I dont know why but BeamNG likes to turn off itself after a while (15-30min)

I get no Error or something like that, no laggs... it just turns off.
I had this issue 4 Times now, only on Small Island.

I hope this get fixed.

 

Same here. Very frustrating when you're editing a map and don't save :/

 

I get the same thing, so here's the T3D log file. Looks like it's the main.lua file that crashes but I'll leave that to the devs

 

Driving the Bolide around and it closed randomly. This was at the end of torque3d.log file

Code:

937.506090|BEAMNG| ERR | *** FATAL LUA ERROR: "lua/system/main.lua"]
937.506613|BEAMNG| ERR | [string "lua/system/main.lua"]:93: stack overflow
937.526537|BEAMNG| ERR | *** FATAL LUA ERROR: [string "line"]:1: stack overflow

937.526570|BEAMNG| ERR | Stack Traceback
937.526598|BEAMNG| ERR | ===============
937.526624|BEAMNG| ERR | (2) main chunk of [string "line"] at line 1

 

Exact same thing for me. I hope devs will take a look into the lua file and fix this for the next update

Code:

1263.975564|BEAMNG| ERR | *** FATAL LUA ERROR: "lua/system/main.lua"]
1263.976149|BEAMNG| ERR | [string "lua/system/main.lua"]:93: stack overflow
1263.993519|BEAMNG| ERR | *** FATAL LUA ERROR: [string "line"]:1: stack overflow


1263.993598|BEAMNG| ERR | Stack Traceback
1263.993648|BEAMNG| ERR | ===============
1263.993697|BEAMNG| ERR | (2) main chunk of [string "line"] at line 1

 

And it's not exactly the code at the line it's sayiing, removing this code causes a stack overflow with a liner further down the LUA file

 

I only get this crash when I have used slow motion. If I dont use slow motion at all then the game will run all day without a crash. The game will crash within 10 minutes of using slow motion.

here is my log

Code:

339.901769| *** loading input map DONE *** 
339.901808| *** done intializing vehicle (T3D side) *** 
340.463027|BEAMNG| bullettime.onDeserialized: 100
494.284108|DInputDevice::processAsync -- joystick0 input device's event buffer overflowed!
505.266834|DInputDevice::processAsync -- joystick0 input device's event buffer overflowed!
647.472639|BEAMNG| ERR | lua/system/waypoints.lua:487: stack overflow
647.568569|BEAMNG| ERR | *** FATAL LUA ERROR: "lua/system/main.lua"]
647.568832|BEAMNG| ERR | [string "lua/system/main.lua"]:94: stack overflow
647.594437|BEAMNG| ERR | *** FATAL LUA ERROR: [string "line"]:1: stack overflow

647.594491|BEAMNG| ERR | Stack Traceback
647.594521|BEAMNG| ERR | ===============
647.594550|BEAMNG| ERR | (2) main chunk of [string "line"] at line 1

It would be interesting if everyone could try playing with the slow motion for the first 10-15 mins to see if it crashes. Then play again without using slow motion and see if it crashes. It seems very predictable from my testing.

 

i had a crash to desktop, too. i used 4 cars and slow motion. happens after a couple of minutes.
my log:

Code:

508.809408| *** loading input map DONE *** 
508.809434| *** done intializing vehicle (T3D side) *** 
509.164331|BEAMNG| bullettime.onDeserialized: 100
550.952049|*** Control Object Changed
551.879266|*** Control Object Changed
552.255066|*** Control Object Changed
577.551122|*** Control Object Changed
578.847799|*** Control Object Changed
600.348661|*** Control Object Changed
613.382881|*** Control Object Changed
614.218407|*** Control Object Changed
617.030528|*** Control Object Changed
618.915879|*** Control Object Changed
619.844899|*** Control Object Changed
641.770364|*** Control Object Changed
642.595454|*** Control Object Changed
670.759314|*** Control Object Changed
698.788887|*** Control Object Changed
699.482340|*** Control Object Changed
716.321094|BEAMNG| ERR | *** FATAL LUA ERROR: "lua/system/main.lua"]
716.321450|BEAMNG| ERR | [string "lua/system/main.lua"]:93: stack overflow
716.342544|BEAMNG| ERR | *** FATAL LUA ERROR: [string "line"]:1: stack overflow

716.342575|BEAMNG| ERR | Stack Traceback
716.342594|BEAMNG| ERR | ===============
716.342610|BEAMNG| ERR | (2) main chunk of [string "line"] at line 1

 

Happend now to me on Gridmap.

 

Off-roading a Ibishu Pigeon and BeamNG randomly exited to desktop 2 days ago.

 

I had several crashes in several maps with several vehicles. I suppose it's not determined by what map or what vehicle are you playing with.

 

Got the same crash.

730.894592|BEAMNG| ERR | *** FATAL LUA ERROR: "lua/system/main.lua"]
730.894936|BEAMNG| ERR | [string "lua/system/main.lua"]:93: stack overflow
730.908052|BEAMNG| ERR | *** FATAL LUA ERROR: [string "line"]:1: stack overflow


730.908080|BEAMNG| ERR | Stack Traceback
730.908103|BEAMNG| ERR | ===============
730.908126|BEAMNG| ERR | (2) main chunk of [string "line"] at line 1

Please make this #1 priority because its a gamebreaker.

 

Same error here

 

Same Problem for me, same Lua Line Stack Overflow for me.. Slowmo seems indeed to trigger the failure

Had this in the unpatched pre race update already ( http://www.beamng.com/threads/8602-Random-Crashes-without-BeamNG-recognizing-it )

 

i have not had this problem yes ive used slowmotion and multiple cars

 

Are you playing with a gamepad or something like that, or do you use keyboard? I start getting the feeling that the crash happens when I am pressing some key on the gamepad..