As of October 23, 2026, with BeamNG.drive on version 0.40 (October 19), most mod problems come from old mods that haven’t been updated, a corrupted cache, or loose files in the user folder that override the game’s own. The official documentation lays out a clear order: launch in Safe Mode to find out whether your mods are to blame, use Clear Cache, and if a mod is the problem, re-enable your mods in small groups until you find it. The beamng.log file in your user folder helps you confirm it.
Shortcut: load your beamng.log into Holyfix for BeamNG, our free analyzer: it tells you which mods the game loaded, which one is throwing errors (scripts, missing parts, corrupted or duplicate files) and what to check first. The file is analyzed in your browser and never uploaded.
Quick diagnosis
| Symptom | Likely cause | What to do |
|---|---|---|
| Black screen with «UI Loading» at the bottom | According to BeamNG, it can be caused by mods | Back up and empty the user folder, remove third-party mods and verify the game files |
| The Repository is stuck on «Loading..» | Connection, VPN or proxy; in rare cases, badly packed mods | Disable all mods and re-enable them one at a time |
| Missing textures or official levels that won’t load | Old or corrupted cache | Clear Cache in the launcher |
| Everything breaks after an update | Mods made for the previous version | Update them from the Repository or disable them |
| A mod is still active even though you deleted it | An unpacked copy in the unpacked folder | Delete that copy |
Crash with VK_ERROR_DEVICE_LOST |
A graphics card problem, not the mod | Update your drivers and remove any overclock |
Step 1: Safe Mode, to see if it’s your mods
In the BeamNG.drive launcher, open Support Tools and choose Safe Mode. The game starts with a temporary, empty user folder: no mods, no settings and none of your files, and anything you change during that session is discarded when you quit. The official documentation sums it up like this: if the game fails normally but works in Safe Mode, something in your user folder (a mod or a cache file) is broken. If the problem persists in Safe Mode, the cause is on your PC: drivers, minimum requirements or a known game bug.
Step 2: Clear Cache
This is also in Support Tools. Clear Cache moves certain cache files to a backup folder inside your user folder so the game doesn’t load them, and afterwards you can decide whether to delete them. BeamNG recommends it for broken textures or materials in official content, official levels that don’t load properly, and mod problems. The first load afterwards takes longer than usual.
Step 3: find the bad mod
BeamNG suggests this method, which works no matter how many mods you have:
- Close the game and rename your user folder (for example, add _backup to the end). When you launch the game, it creates a new one.
- Check whether the problem is still there. If it’s gone, the cause was in your files.
- Move your files back in small groups, one folder at a time, testing after each group.
- For mods, move them into the new mods folder in halves until the problem comes back: the last group contains the culprit.
If you move everything at once, you won’t know which file it was. For simpler cases, the game’s Mod Manager lets you disable them all and enable them a few at a time without touching any folders.
Where to find beamng.log
You can open the user folder from the launcher with Manage User Folder. By default, on Windows it’s in %LOCALAPPDATA%\BeamNG\BeamNG.drive\current, and on Linux in ~/.local/share/BeamNG/BeamNG.drive/current. That’s where beamng.log lives, the log for the current session; numbered files, like beamng.1.log, are from previous sessions. Open it after the crash and look for the names of mods or vehicles that show up near the errors. It’s also the file BeamNG’s official support asks for if you open a ticket.
Updates and versions
In a major update (when the second number changes, like from 0.39 to 0.40), the game cleans the user folder automatically and moves any files it doesn’t recognize into a backup folder next to current, with the date and version in its name. Old mods may stop working until their authors update them. After updating, go to the Repository, update anything that has a new version and re-enable the rest a few at a time. If a mod hasn’t been updated in a long time, suspect it first.
Other common errors
- Loose files in the user folder. BeamNG explains that a file with the same relative path in the user folder replaces the game’s file. An old file can break official content.
- User folder inside the game folder. This isn’t recommended: Steam may delete unknown files when it updates or verifies the game.
- Too many mods. BeamNG doesn’t recommend having more than 20 or 30 active at once.
- Mods that aren’t .zip files. Be wary of a mod that comes as an .exe: that’s not the game’s format.
More BeamNG.drive guides: how to install mods, the best mods, the best maps and the PC requirements.
Frequently asked questions
Why is BeamNG stuck on «UI Loading»?
BeamNG says it can be caused by mods. Its fix: copy your user folder somewhere safe, empty it, uninstall third-party mods and verify the integrity of the game files on Steam.
Does Safe Mode delete my mods?
No. It uses a temporary, empty user folder; your mods and settings stay in yours and come back when you launch normally.
What does Clear Cache do?
It moves cache files to a backup folder inside your user folder so they don’t load, without touching your personal files. You can delete them afterwards.
Do 0.39 mods work in 0.40?
Some do and some don’t. With major updates, it’s best to update from the Repository and re-enable your mods in groups to spot the ones that fail.
Where are BeamNG mods stored?
In the mods folder inside your user folder: on Windows, %LOCALAPPDATA%\BeamNG\BeamNG.drive\current\mods. Open it from the launcher so you don’t get it wrong.