Troubleshoot

For a wall that remains after the trailer fix, see common issues and the clean-test procedure. Back up affected resources before changing files.

Common issues and solutions for Aurum Motors

Collision Issue at Ramp / Trailer Spawning on Front

Why This Happens

Aurum Motors uses collision and map data that can conflict with other MLOs or IPL loaders on your server. When two resources try to load overlapping .ymap or .ybn files, GTA V applies the wrong collision data — causing vehicles to clip through the ground, float, or tilt at the dealership ramp area.

Symptoms

Vehicles tilt, float, or clip into the ground near the dealership ramp
A trailer or object spawns at the front of the dealership
Cars bounce or behave erratically when driving onto the lot

Vehicle collision issue - car tilting at dealership ramp

Vehicle tilting due to collision conflict at ramp

Dealership exterior view

⚠ DO THIS FIRST

Check the documented conflict

Step 1: Remove Garment Factory Collision Files

These files can cause the documented ramp/trailer conflict. Read it carefully before moving to Step 2.

Check for conflicting garment factory map files. If they are absent, continue with the isolation procedure rather than deleting unrelated files.

Search your entire server resources folder for these two files. Back up matching files before temporarily removing the documented conflicting copies and testing:


m24_2_garment_factory_1.ybn
m24_2_garment_factory.ymap

These files are commonly found inside the BOB74 IPL resource in your server root folder. Check there first.

Where to Look

Inside the Aurum Motors MLO folder itself
Inside BOB74_IPL or any IPL-loading resource in your server root
Inside any other MLO resource that loads garment factory data

After removing these files, restart your server and test before continuing. If the trailer disappears but a wall remains, investigate that remaining symptom separately in Step 2.

Fix — Step 2: Check for Conflicting MLOs

If the collision issue still exists after removing the garment factory files, another MLO on your server is likely the culprit.

How to Find It

Open each MLO resource folder in your server
Look for .ymap or .ybn files that share names with files inside Aurum Motors, such as:

★ MOST COMMON CONFLICT

Check this file first

Another documented filename to check is:

hei_id2_rd_long_0.ymap

Search other MLO/IPL resources for this file. Confirm which resource conflicts through an isolated test before changing it; keep a backup.

File Type	Common Conflicting Files
`.ymap`	`hei_id2_14_critical_0.ymap`, `hei_id2_14_long_0.ymap`, `hei_id2_14_strm_0.ymap`
`.ybn`	`hei_id2_14_0.ybn`, `hi@hei_id2_14_0.ybn`, `hi@hei_id2_14_2.ybn`, `id2_14_0.ybn`

Confirm the conflict on a development server, then use the appropriate product-specific patch or temporarily disable the conflicting resource there. A matching filename alone is not proof that it should be deleted.

Do not delete collision files from Aurum Motors itself. If the only copy is inside Aurum or the correct replacement is unclear, ask support before changing it. Do not remove an entire IPL loader as a general fix.

Removing Service Lift Props

If you want to remove the service lift props from the service/mechanic area, delete the following file from the stream folder:


dealerash_service_lift.ydr

Service lift prop models

Service lifts inside the mechanic area

After deleting the file, restart your server for the change to take effect. The service area will remain intact — only the lift props will be removed.

Summary

Step	Action	Fixes
1	Delete `m24_2_garment_factory_1.ybn` and `m24_2_garment_factory.ymap`	Documented ramp/trailer conflict
2	Isolate the conflicting resource; apply a verified fix	Remaining collision conflicts