How to read the BeamNG.drive log to find the mod that crashes your game

24 Oct 2026 · 3 min read · ModsDrop

Pictured: Mercedes-Benz G-Class 2027, from the ModsDrop library.

When BeamNG.drive crashes, freezes on a loading screen or spawns a car without a body, the game has usually written down why. The log is a plain text file, it names the mod responsible more often than not, and reading it takes less time than reinstalling. Here is where it is, what to search for, and how to turn what you find into a useful report.

Where the log is

In the user folder of the current game version, which the launcher’s Manage User Folder button opens: the main file is beamng.log. The previous session’s log is kept alongside it (with a number or “previous” in the name), so if the game crashed and you restarted it to get to this point, the crash is in the previous one. The launcher also has a Support Tools section that can collect the logs into a single archive for a bug report.

What is in it

One line per event, each with a time, a level and a source. The levels that matter:

E (error): something failed. These are what you search for.
W (warning): something was wrong but the game carried on; a missing texture, a deprecated setting.
I and D: information and debug; thousands of lines you can ignore.

The source column often names the system (vehicle loading, Lua, the UI, the renderer) and the file path involved, and that path usually includes the mod’s folder name.

Finding the mod in five searches

Search for “|E|” (or just the word Error). Read the first few errors after the game started, not the last ones; the first failure is the cause, the later ones are consequences.
Search for “mods/”. Every mounted zip is listed as it mounts; a zip that appears with an error right after it is damaged or incompatible.
Search for the vehicle’s folder name (the one under vehicles/ in the mod zip). Errors mentioning it point at that mod’s JBeam or materials.
Search for “lua” and “stack traceback”. A Lua error with a path inside a mod zip is a script mod failing; the path names the mod.
Search for “ui” and “vue” after the 0.40 update. Errors there are HUD app mods built for the old interface.

What common entries mean

“Failed to load” / “could not open” a file inside a zip: the zip is incomplete or corrupted. Re-download; compare the size with the file page.
“Material not found” or “texture missing”: the mod references a texture it does not contain, or one the game renamed. Cosmetic if it is one part; a whole invisible car if it is the body.
“duplicate” with two paths: two zips provide the same file. Keep one.
“JBeam parse error” with a file and line number: a syntax error in a mod’s JBeam; the mod author’s problem, and it tells them exactly where.
“Out of memory” or “VRAM”: too many high-resolution textures loaded at once. Lower texture quality or run fewer heavy mods together.
“unsupported” together with a version number: the mod declares a game version the game no longer accepts; usually old script mods.

From the log to a fix

If the log names a zip: deactivate that zip in the Mod Manager and start again. If the error is gone, you have your culprit; check the mod’s page for an update or a 0.40 note before reporting it. If the log names a game file rather than a mod, try Clear Cache and then Verify Game Files in Steam. If the log ends abruptly with no error, the game was killed from outside (a driver crash, the system running out of memory); check Windows’ Event Viewer for the same minute.

Writing a report an author can use

Three things, in this order: the game version (0.40.3, say), the exact lines from the log that mention the mod (copy five to ten lines around the first error, not the whole file), and what you did right before (spawned the car, loaded the map, opened the parts menu). Add which other mods were active if there were few; if there were many, say whether the problem survives with everything else deactivated. A report with those three things gets fixed; “it crashes” does not.

What not to post

The whole log. It can be tens of megabytes and contains your user name in the paths. Copy the relevant lines, and if you must share the file, trim the paths. Nobody reads 40,000 lines, and the ten that matter are the ones you found with the searches above.