Skip to content

Troubleshooting

Failed to verify protected resource nopixel-...

Section titled “Failed to verify protected resource nopixel-...”

The server’s license key does not belong to the Cfx.re account that owns the package. Check under Servers in the Cfx.re Portal which account the key was issued to, and under Assets which account holds the grant. Either register the server under the owning account or transfer the grant.

Other causes: the resource folder was renamed (the .fxap key file is tied to the resource name), or an encrypted file inside the resource was edited or replaced. Re-download the package from the portal.

Could not find the asset in your grants or the package is missing from the portal

Section titled “Could not find the asset in your grants or the package is missing from the portal”

The purchase was made with a different Cfx.re account, or the grant has not been processed yet. Sign in with the account used at checkout. If it is still missing after a few minutes, contact support with your order number.

Resource starts but is a few bytes or has no stream folder

Section titled “Resource starts but is a few bytes or has no stream folder”

The download was interrupted or the zip was extracted only partially. Delete the folder and download the package again.

The folder is not where FXServer looks. Resources must sit in resources/ or inside bracketed category folders under it, with fxmanifest.lua directly inside the resource folder. A common mistake is double nesting after extraction: resources/[nopixel]/nopixel-bennys/nopixel-bennys/fxmanifest.lua. Move the inner folder up one level.

A resource stays at “starting” or the server hangs on boot

Section titled “A resource stays at “starting” or the server hangs on boot”

Very large resources take a moment to register their stream files. Undercity, Maze Bank, the hospital and the courthouse are the biggest. If it never finishes, check disk space and that the antivirus is not scanning the stream folder on every read.

Interior is invisible or I fall through the floor

Section titled “Interior is invisible or I fall through the floor”
  • Confirm the resource is started (ensure in server.cfg, no error in the console).
  • Check that sv_enforceGameBuild is 3570 or newer. Interiors can fail to load their collision on older builds.
  • If you use a custom gta5.meta or replace_level_meta from another pack, it can drop the pack’s IPLs. Try with that resource stopped.

Fleeca banks, Mission Row PD and Otto’s disable the vanilla interior with a client script. If you see both:

  • Stop any other MLO for the same building.
  • For Fleeca, make sure the legacy nopixel-fleeca is not started alongside nopixel-fleeca-new.

nopixel-props-custom-shared (for the Interiors group) or nopixel-pdprops (for La Mesa PD, Pacific Bank, Townhall) is not running. See Configuration.

Lights float in the air at night, or shine through buildings

Section titled “Lights float in the air at night, or shine through buildings”

nopixel-lodlights is not running. It strips the vanilla distant LOD lights that the replaced buildings no longer match.

Black screen after joining, or the sea looks wrong underwater

Section titled “Black screen after joining, or the sea looks wrong underwater”

Caused by an older version of nopixel-visuals. Download the current version from the portal. If it persists, stop nopixel-visuals to confirm it is the cause, then check that no other visual pack is running.

Weather or time of day looks different from the screenshots

Section titled “Weather or time of day looks different from the screenshots”

The screenshots were taken with nopixel-visuals on. Interiors ship their own timecycle modifiers, but exterior lighting depends on the visual pack.

Ambient peds stand inside walls of a replaced building

Section titled “Ambient peds stand inside walls of a replaced building”

nopixel-scenarios overrides scenario points, but a few vanilla points may remain. Disable the resource to confirm, and report the location so the override can be extended.

First visits download a lot of data; later visits hit the client cache. If it stays slow for everyone, check your outbound bandwidth or move streamed files behind a CDN.