EDIT: This problem seems to be fixed for me. I can't get it to do anything anymore without crashing. In general it is this error, but I get others often enough too. I think it related to memory availability. So my question is really whether there is a way to increase the amount of memory available to the game, as it doesn't seem to use all of my computer power? Otherwise, any other hints? I've deleted all mods, reinstalled the game, cleared caches, etc. To be honest, I am now giving up on making any more maps. I finally learned how to do it with my Somerset map at the end of last year, but I can't even replicate something like that anymore. Kudos to those who continue the battle. I look forward to enjoying the fruits of your labours.
I've had a similar problem, except my error was about a "STATUS_STACK_BUFFER_OVERRUN". With your problem, you may want to check that there isn't any unimportant tasks/programs running in the background. That could possibly cause the issue. When in the game, try removing your vehicle so that you're only in freecam mode, and try pausing physics to minimize things that BeamNG needs to run. As always, if the problem persists, the best thing to do is to contact their support, however these are suggestions I have that might help.
Thanks. I will try. I'm trying hard not to give up, but it is disappointing to spend hours trying different approaches and have them not work. Appreciate the suggestions.
This annoying thing keeps happening out of the blue, usually when resizing editor scene/asset/material windows. I'll try to copy and send the error next time.
Support ID 121838 created, Ticket: 56868 Divide by zero -crash happens when moving (WSAD) and resizing the scene/asset/material window at the same time. - update, new ID 122011 Clean install, no mods, default settings, editor in safe mode. Crashed with the same error when flying in Italy map at 100% speed, accelerated with L-Shift, while decreasing a window that had scene tree and inspector in it. I was deliberately trying to get the crash and it took a while fooling around like that. Maybe too many buttons were pressed at once or something. It's still annoying when it happens accidentally and all work is lost if auto save feature is not on.
New ID 124096 Now it can happen just by resizing a window that holds scene+asset+material+inspector while not even moving the camera. Just before the Divide. Editor freezes for a second, then crashes to desktop. Tried this on a few maps, both in normal and in safe mode. There is another, maybe related issue: Locked flight/movement, that I think shouldn't happen. Press and hold W to move, click and hold Left Mouse Button on window or toolbar, release W, release LMB. Movement can be stopped only by clicking W. Works with all WSAD combos.
