Your cart is empty.
Browse VehiclesFiveM Cars Disappearing at Distance?
The Vehicle LOD Problem, Explained & Fixed
Cars that vanish 30 meters away, pop in at the last second, or melt FPS across the whole block - three symptoms, one root cause: custom vehicles shipping with a single LOD level where GTA expects four.
How Vehicle LODs Work in GTA V / FiveM
LOD means Level of Detail: the engine swaps a vehicle’s mesh for progressively simpler versions as it gets farther from the camera. A native GTA V vehicle carries a chain of meshes - high → med → low → vlow - and a matching <lodDistances> line in vehicles.meta that says at how many meters each swap happens (a typical native line: 15.0 30.0 60.0 120.0 500.0).
Two files carry the meshes: carname.yft holds the med/low LODs and carname_hi.yft holds the full-detail model you see up close. That _hi suffix system is why a car with a missing _hi.yft looks low-poly even point-blank - and why a car with only a high mesh has nothing to draw at distance.
What we found auditing real mods
Running our fleet-audit tooling across customer-reported “FPS killer” vehicles, the pattern was always the same: lodLevels: 1 - a single 290–450k-polygon showroom mesh and no med/low LODs at all. Collision was fine (~760 polys); the cost was pure visual geometry. With one LOD, the engine has two bad options: render the full mesh from absurd distances (FPS hit for everyone) or draw nothing (the car “disappears”).
Match Your Symptom to the Cause
Car vanishes 20–40 m away
The mod has no med/low LOD meshes and its lodDistances end early - past the last distance, there is nothing to render. Classic single-LOD mod behavior.
Car pops in at the last second
Oversized assets streaming late: a 40–60 MB YTD or a heavy YFT cannot load in time as you approach. Often paired with texture loss elsewhere - same streaming budget being blown.
FPS drops when many customs are parked
Single-LOD, 300k+ poly meshes rendering at full detail from across the street, multiplied by every car at the meet. Resmon shows nothing - this lag is GPU-side, not script-side.
Car looks low-poly up close
The _hi.yft is missing from the resource (or was not uploaded), so you are looking at the base mesh. Check the stream folder for carname_hi.yft.
The Fixes, From Quick Patch to Real Cure
1. Tune lodDistances (quick patch)
For a disappearing car, raising the values in the vehicle’s <lodDistances> line keeps it visible farther out. Understand the trade: on a single-LOD mod you are telling the engine to render the full mesh farther - visibility fixed, FPS cost increased. Use moderate values (e.g. 25.0 45.0 90.0 180.0 500.0) rather than maxing everything.
2. Client-side LOD multiplier (per-server script)
SetVehicleLodMultiplier(vehicle, 1.5) on spawned vehicles extends LOD switch distances proportionally - a gentler global lever than editing every meta. Same trade-off as above: more distance = more rendered polys.
3. Cut the polygon cost (the real lever)
If the mesh is 400k polys, every distance trick just spreads the pain. The Optimizer’s model decimation reduces visual geometry (planar dissolve + smart collapse that protects body lines) with no visible change at gameplay distance - and its texture pass fixes the late-streaming pop-in at the same time.
4. Buy cars built right (the cure)
The only complete fix for missing LODs is a model authored with them. Every vehicle in the FiveMRides catalog is screened by the same audit tooling that found these defects - poly budgets, streaming size and meta validity checked before a car ships.
Honest note on “LOD generators”
Decimation reduces the polygons of the meshes a mod already has - it does not author the missing med/low LOD chain. Tools claiming one-click LOD generation for RAGE vehicles produce mixed results at best; treat “adds LODs automatically” claims with skepticism. Reducing base-mesh weight and fixing streaming size solves the practical symptom for the vast majority of servers.
Vehicle LODs - Frequently Asked Questions
Why do my FiveM cars disappear at a distance?
The mod ships only a high-detail mesh with no med/low LOD levels, and its lodDistances stop early - beyond the last distance the engine has nothing to draw. Raise the lodDistances values in vehicles.meta as a patch, or use vehicles authored with a full LOD chain.
What are good lodDistances values for FiveM vehicles?
Native GTA vehicles use lines like 15.0 30.0 60.0 120.0 500.0. For single-LOD mods that disappear, moderate raises such as 25.0 45.0 90.0 180.0 500.0 keep the car visible without forcing the full mesh to render from extreme range. Avoid maxing values across a whole pack - that multiplies GPU load.
What is the _hi.yft file for?
carname_hi.yft holds the full-detail mesh shown up close; carname.yft carries the lower LOD levels. Both must be streamed for the car to look right at all ranges - a missing _hi.yft makes the car look low-poly even point-blank.
Does raising LOD distances cause lag?
It raises GPU load: you are rendering more geometry from farther away. On well-built cars the cost is small because distant LODs are cheap. On single-LOD 300k+ poly mods the cost is the full mesh - which is why reducing polygon weight matters more than distance tweaks.
Why is my FPS low near car meets even though resmon is clean?
Resmon measures script CPU, not rendering. Twenty parked single-LOD vehicles at 300-450k polygons each is millions of triangles every frame - pure GPU load that resmon cannot show. Optimizing the vehicles (polygon decimation + texture compression) is the fix.
My car does not appear at all - is that a LOD problem?
If the car never spawns (rather than disappearing at range), it is a packaging problem - manifest, naming, or an oversized YTD. That is a different diagnosis with nine distinct causes, covered in the car-not-spawning guide.
Stop Rendering 400k Polygons Per Parked Car
Decimate the geometry, compress the textures, keep the look. The Optimizer handles both passes in one upload.
Web-based • Protects body lines • Zero visible quality loss