1 What a pink blob actually is
In BeamNG, when the game is told to draw a vehicle but can't find the mesh and textures for it, it falls back to a placeholder — a featureless pink/magenta shape. In BeamMP, this happens when your client is told another player is driving vehicle X, but your client doesn't have vehicle X's mod loaded.
The key thing to understand: BeamMP is peer-rendered. The server tells your game "player Brandon is in a Bruckell Bastion with these parts," and then your own machine renders it using your own copy of those mod files. If you don't have the exact files Brandon's car uses, your game can't draw it — so it shows a pink blob instead.
2 How mods are supposed to sync
BeamMP only syncs mods that live in the right place on the server. There are two folders that matter, and people mix them up constantly:
| Folder | What goes here | Synced to players? |
|---|---|---|
Resources/Client | Vehicle mods, maps, configs, skins — anything players need to see and drive | Yes — pushed to every client on join |
Resources/Server | Server-side Lua scripts only (admin tools, events) | No — never sent to clients |
So if your vehicle mods are sitting in Resources/Server, or installed only on individual players' PCs, they will not sync. They must be zipped and placed in Resources/Client for everyone to render them.
mods folder and uploads them, but the server is large (50+ mods) and one client's download fails or times out mid-sync. That single client then sees blobs while everyone else is fine.3 Reading the symptom pattern
The pattern of who-can-see-whom tells you exactly what's wrong. Here are the three you'll actually run into:
One player sees everyone as blobs
That player's client has almost no mods loaded. Their sync failed entirely, their mod cache is corrupt, or their files are in the wrong place. Fix that one client.
A player sees some people but not others
That viewer is missing the specific mod(s) the blobbed players are using, but has the ones the visible players use. A partial sync.
Same car — one driver shows, another blobs
The blobbed driver has a local-only part/config not on the server. The base car is fine; their custom version uses files nobody else has.
4 The tricky one: "same car, but only one of them blobs"
This is the case that confuses everyone, so it's worth spelling out. Say two players both hop into, on paper, the exact same car — and you can see one of them perfectly but the other is a pink blob.
If you can see the first player in that car, then you clearly have the car mod. So the problem isn't the base vehicle. It's something specific to the blobbed player's copy of it:
- They're running a custom config (a saved
.pcfile) that adds parts — wheels, a body kit, an engine swap, a skin — from mods that only exist in their local folder. - Those local-only parts never got uploaded to the server, so they never synced to anyone else.
- Your client tries to build their car, hits the missing parts, and falls back to a blob — even though the base vehicle is identical to the one you can see.
5 The 30-second diagnostic test
Before changing anything, confirm what you're dealing with:
- Have the blobbed player select their vehicle and reset it to the default/factory config (stock parts, no custom
.pc). - Have someone who saw the blob look again.
Then:
- Stock config now visible, custom config blobs → it's a local-only part. The custom config depends on mods that aren't on the server.
- Still a blob even on stock → the viewer is missing the base vehicle mod itself (a sync/cache problem on the viewer's side).
6 Fixes, in order
Fix 1 — Clear the client mod cache & re-sync
For any player seeing blobs, have them clear their BeamMP client mod cache (the synced-mods folder the launcher manages) and rejoin. This forces a clean re-download of everything from the server and resolves corrupt or partial syncs — the #1 cause of Pattern A and B.
Fix 2 — Make the server the single source of truth
Every mod the server needs should live in Resources/Client as a zip. If a player has mods that only exist locally (the cause of Pattern C), upload those zips to the server too so they sync to everyone. The goal: nobody relies on a manually-installed local mod.
Fix 3 — Remove conflicting local copies
If players manually installed the same mods locally that the server also sends, version mismatches between the two copies can cause blobs. Cleanest setup: players don't pre-install the server's mods — they let the server sync them.
Fix 4 — Match versions
Make sure all players are on the same BeamNG.drive and BeamMP client version. A version gap between clients can also produce missing/blob renders.
7 Quick reference
| You see… | Most likely cause | First fix to try |
|---|---|---|
| One player sees everyone as blobs | Total sync failure / corrupt cache on that client | Clear that client's mod cache, rejoin |
| Viewer sees some players, not others | Partial sync — missing specific mods | Clear cache + confirm mods are in Resources/Client |
| Same car, one driver blobs | Local-only part/config on the blobbed driver | Test stock config; upload the local mod to the server |
| Everyone blobs to everyone | Mods in wrong folder or not zipped correctly | Move mods to Resources/Client as zips |
Running BeamMP with Solace?
Our panel gives you direct file access to Resources/Client over SFTP, so syncing your whole mod pack to every player is a drag-and-drop.