Skip to content

FXServer artifact 38435 - client crash when loading certain ipls #4387

Closed

Description

@Rakii23

What happened?

When loading ipls "prologue_DistantLights" and "prologue_LODLights" on new artifact 38435 fivem client crashes. Loading same ipls on artifact 35945 works fine.

Expected result

Not to crash

Reproduction steps

/

Importancy

Unknown

Area(s)

FXServer

Specific version(s)

artifact 38435

Additional information

Windows server

Activity

  1. added
    triageNeeds a preliminary assessment to determine the urgency and required action
    on Nov 8, 2026
  2. redxtv commented on Nov 9, 2026

    @redxtv

    I am also having the same issue :(

  3. OneEarJoe5 commented on Nov 11, 2026

    @OneEarJoe5

    Tried to reproduce this locally with artifact 38435 and the current client: requested prologue_DistantLights and prologue_LODLights at resource start (during loading) and after spawning, also together with the full North Yankton IPL set, at night and flying around there. No crash for me.

    One thing that might explain "35945 works, 38435 crashes": since b5b3cb5 the default game build went from 3258 to 3889, so servers without sv_enforceGameBuild in their cfg switched builds with the artifact update. Could you check if setting sv_enforceGameBuild 3258 on 38435 makes the crash go away? That would at least narrow it down to the game build.

    It would also help if you could post the crash signature/ID from the crash dialog and which other map or IPL resources are running, since the two IPLs on their own don't seem to be enough to trigger it.

  4. Rakii23 commented on Nov 12, 2026

    @Rakii23
    Author

    Im on a game build 3751, but even after downgrading it to 3258 same problem occur.

    Crash dialog: https://prnt.sc/EQV-oPpqVwLt

    As regards to other loaded ipl-s, there are numerous loaded parts of los santos map (yacht, mansions, etc.)

  5. OneEarJoe5 commented on Nov 13, 2026

    @OneEarJoe5

    Thanks for the screenshot. One thing stands out: the crash is in GTA5_b3889.exe, so that client was running build 3889, not 3751 or 3258. Looks like the downgrade didn't actually apply. sv_enforceGameBuild has to be in server.cfg and the server fully restarted (a resource restart isn't enough), then the crash dialog should say b3258. Could you try that once more and check the build in the dialog?

    I also tried it again closer to your setup: 38435 with build 3889, bob74_ipl (yachts, mansions etc.) plus prologue_DistantLights and prologue_LODLights, requested during loading and after spawning, flying around LS and North Yankton at night. Still no crash here, so it's probably something more specific in your map setup.

    If it still crashes, could you click "Save information" in the crash dialog and upload the zip here? The log in there shows what was loading right before the crash, that would help the most. Maybe check it for IPs/identifiers first. The crash ID from the dialog would also be good for the Cfx team.

    A list of the map/IPL/MLO resources you run would help too, and turning those off one by one until it stops would narrow it down a lot.

  6. radium-cfx commented on Nov 13, 2026

    @radium-cfx
    Contributor

    A fix for this has been deployed to Canary, could you please verify if this resolves your issue?

  7. Rakii23 commented on Nov 13, 2026

    @Rakii23
    Author

    Fixed, works good in canary, thanks.

  8. removed
    triageNeeds a preliminary assessment to determine the urgency and required action
    on Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions