Client crashes on connect when server uses data_file 'SCENARIO_POINTS_OVERRIDE_PSO_FILE' (FiveM for GTAV Enhanced, early access)

FiveM Discussion Bug Reports
1

Any server resource that registers a scenario point manifest override via data_file 'SCENARIO_POINTS_OVERRIDE_PSO_FILE' '<file>.ymt' in its fxmanifest.lua causes every connecting client to crash immediately (“The application has crashed!”) on FiveM for GTAV Enhanced (early access). The same resource works fine on FiveM Legacy.

Environment

  • FXServer branch: early-access (custom branch, Enhanced)
  • txAdmin: v9.0.0-beta-646aba9a/b110-ea/Win
  • Client: FiveM for GTAV Enhanced, early access build (installed ~2026-08)
  • OS: Windows 10

Steps to reproduce

  1. Take any resource that ships a CScenarioPointManifest root file plus per-region CScenarioPointRegion .ymt files under stream/, registered via data_file 'SCENARIO_POINTS_OVERRIDE_PSO_FILE' 'sp_manifest.ymt'
  2. ensure the resource on an Enhanced server
  3. Connect with a FiveM Enhanced client
  4. Client crashes right after the last INIT_SESSION callback, no diagnostic info in the client log — just [critical] The application has crashed!

What we ruled out

  • Re-ran the resource’s binary stream assets through Alchemist — output was byte-identical, not a format issue
  • Used CodeWalker.Core to deserialize every CScenarioPointRegion file and found genuine corruption in 15/144 zone files (points sharing bogus Position.Z = -21588.934, ~21km below the map). Patched all to sane Z values and re-saved — crash persisted unchanged
  • Cross-checked the manifest’s 142-region list against physical files — no missing/mismatched references
  • Inspected EntityOverride entries — nothing out of range
  • Isolated the trigger precisely: with the exact same content-clean stream/ folder present, commenting out just the data_file 'SCENARIO_POINTS_OVERRIDE_PSO_FILE' 'sp_manifest.ymt' line makes the crash disappear completely. Re-adding that single line reproduces the crash reliably, every time.

This strongly suggests the SCENARIO_POINTS_OVERRIDE_PSO_FILE data-file mounter itself is broken in the current Enhanced early-access build, independent of the referenced file’s content.

Expected behavior
Server resources registering a SCENARIO_POINTS_OVERRIDE_PSO_FILE should load without crashing connecting clients, same as on Legacy.

2

Reports for enhanced should be in the RFC citizenfx/rfc · Discussions · GitHub

Please make sure your issue doesn’t already exist there too.

3

A similar issue was discussed on GitHub and addressed by today’s hotfix. However, that hotfix does not resolve the SCENARIO_POINTS_OVERRIDE_PSO_FILE crash reported here. I have opened a separate GitHub discussion with a minimal reproduction, so this forum thread can be closed. Further investigation will continue in Discussion #380.