Common issues and troubleshooting

Reviewed 4 November 2026. Start with the symptom below. A reported issue is not necessarily a confirmed product defect, and a fix for one server may not apply to another.

Before changing files

Back up the resource, configuration and saved business data. Note the exact asset name, installed version, game build and first server-console or F8 error. Download updates from Cfx Portal — Granted Assets using the account that owns the asset. Preserve custom settings when updating.

Test changes on a separate development server before applying them to a populated server. Do not delete every duplicate filename, remove an entire IPL loader, or edit escrow-protected code to try a general fix.

Invisible walls, unwanted props or disappearing interiors

These symptoms can involve overlapping map, collision or occlusion data. Roads, landscaping and IPL resources can conflict even if no other MLO is nearby.

Test the map on a clean development server with its required companion script and dependencies.
If the problem disappears, add other map/IPL/road resources back in controlled groups, restarting and testing between changes. Narrow the group until you identify the conflicting resource.
Compare the relevant files against the product-specific guide. Matching filenames are a clue, not permission to delete them indiscriminately.
If the issue remains in the clean test, stop repeating conflict fixes. Send support your coordinates, reproduction video, installed versions and test results. This needs investigation; it does not by itself establish the cause.

Aurum Motors: trailer gone, invisible wall remains

The trailer and remaining wall can have different causes. Follow the Aurum troubleshooting guide for the documented garment-factory files, then investigate the remaining collision separately.

Check other resources for hei_id2_rd_long_0.ymap and the guide’s listed overlapping files. One reviewed support case was resolved by identifying another MLO included with a separate script. That does not identify the culprit on your server.

Preserve Aurum’s required collision files. If the only matching file is inside Aurum and you are unsure whether the removal step applies, ask support before deleting it. Removing an entire BOB74_IPL resource is not the recommended fix.

FACTORY Club: stairs, seating, poles or occlusion

For disappearing geometry, use the clean-test procedure above. Reports of rooftop stair access, walk-through seats, poles and placement issues require the exact location and installed version. Some visibility problems improved after isolating other resources, but that does not establish a universal fix for the remaining geometry issues.

Do not apply an old ticket attachment or another product’s collision patch without confirmation. Encrypted geometry changes require the creator. Separate seating systems are not included in the product listing; distinguish missing scripted seating from a physical collision problem.

SkyDome: event overlap versus missing collision

For event overlap, keep only the selected event map active: mt_venue_dj.ymap or mt_venue_marriage.ymap. Follow event switching.

Falling through grass, railings or windows in a clean test is a different issue. Send coordinates and a video to support. Aurum’s collision-file instructions are not a SkyDome fix.

SeaDome: choose the right symptom

Water inside the venue

Follow the water troubleshooting guide and compatibility guide. Check map-data resources as well as individual MLO folders for water.xml and gta5.meta. If your combination is not covered, ask support to review it rather than copying a water file intended for another map combination.

Flickering or missing walls

Use the isolation procedure above. If you run SeaDome and Grand Meridian together, use the merged occlusion patch and instructions. Back up both maps, replace only the exact filenames supplied by that patch, and retain the merged copies in one stream folder. Restart and check both interiors.

Do not use that patch for unrelated map combinations. NPC vehicles parking on grass are a separate symptom; provide coordinates and a video rather than repeating the water fix.

Only one player cannot see the interior

Compare that player’s F8 errors and rendering result with another player at the same location. Test with a clean client setup and the isolated server. Record whether visual modifications are installed. Repeatedly clearing cache or reinstalling FiveM is not a diagnosis; if those steps already failed, tell support.

`/dome` still opens for an unauthorized user

/venue access does not prove that /dome and its menu actions enforce the same permission. Record your installed resource/version, permission-test result and which action remains accessible. Ask support to review the actual server-side checks. Do not grant everyone administrator access or assume an unverified ACE name fixes it.

Yacht Club: configuration errors or DJ music without sound

Yacht Club uses resources such as Script_Harbour and Harbour_restaurant; it is separate from Marina Deck Resort.

The 27 October changelog announced Yacht Club Restaurant v0.85, while the store description still lists v0.75. Check the version in your current granted download. A general “minor bugs” changelog does not confirm a particular error is fixed.

Config syntax error followed by nil Config: investigate the first syntax error. Compare that line with the original configuration from the same version, preserving your custom settings.
Invalid vector dimensions: a vector3 cannot take four coordinates. However, do not convert every vec3 to vec4; each setting must match the supplied configuration’s expected type.
ox_lib export error: check whether ox_lib itself starts successfully and whether it starts before the business script. Capture the first startup error, not only the later cascade.
DJ menu opens, but music remains silent with “unsupported operation on a vector value”: if the supplied configuration and isolated setup still reproduce it, send the version, relevant configuration and full error to support. No universal verified fix was established in the reviewed tickets. An escrow ?:-1 error does not identify an editable config line.

Do not copy Skyline or SkyDome coordinates into Yacht Club to resolve this error.

FACTORY Club: setup and supported music

The business script requires OneSync, ESX or QBCore, ox_lib, the included Map_file_Club resource and configured job grades/inventory items. Select the correct framework adapter and start its dependencies first. ox_inventory and ox_target are optional integrations.

The DJ supports configured local MP3/OGG files and native GTA radio. YouTube URLs and arbitrary streaming URLs are not included. The product’s YouTube showcase is a demonstration video, not an in-game playback feature.

Grand Meridian: black or incorrectly oriented theatre screen

Follow the complete theatre screen guide. The supported P-Television v1.2.5 setup uses a patch containing both config.lua and client/main.lua. Preserve the folder structure and back up existing TV settings before replacing files, especially if you use other screens.

Start ox_lib before ptelevision and perform a full server restart. Try /tv near the screen. For a black screen, check both patched files and console errors. For rotation or stretching, compare the TV-script version and patch. Keep theatre_los_screen.ydr and theatre_screen.ytd named as supplied. Playback-provider support depends on the TV script.

Missing documentation or installation links

For a missing NOIR README or a 404 link: extract the purchased package, place the actual resource folders in resources, retain their manifests and companion scripts, and add ensure entries using their exact installed names. Restart and inspect the console. Ask support for the current bundled instructions if dependencies or resource names are unclear. Do not guess a new documentation URL or rename folders to match another product’s example.

Lock & Glove: consumption or timer expectations

Use the installation guide and FAQ. Confirm the resource version, supported/adapted inventory and any bypass job before reproducing the issue. Config.GloveItemLimit is not evidence of an automatic timer setting. If one glove remains usable beyond the configured behavior, send reproduction steps and configuration to support; do not assume arbitrary inventory replacements are compatible.

What to send support

Exact purchased asset and installed resource/version.
The first error, plus relevant server/F8 output.
Coordinates and a short video for map problems.
Checks already completed and the clean-test result.
Relevant configuration with passwords, API keys, license keys and personal information removed.

Keep purchase receipts and account-transfer questions in a private support ticket. Missing grants or transfer restrictions need account-specific review; cancelling and buying again is not a guaranteed fix. Staff must confirm any refund, credit or replacement entitlement.