fivem icon indicating copy to clipboard operation
fivem copied to clipboard
verified publisher icon citizenfx

Persistent Crash (c0000005) when streaming ANY Custom Audio REL file (Dat 151 or Dat 150)

Open nohassi opened this issue 3 months ago • 3 comments

What happened?

I am experiencing a consistent fatal client crash (c0000005 at 0x7ff613c03f55, as shown in the screenshot) whenever I attempt to start a resource that streams a custom audio .rel file in FiveM. The crash occurs specifically in the data file mounter stage.

The crash happens regardless of the .rel file type used: Dat 151 (Ambient Zone) or Dat 150 (Ambient Emitter). The resource works fine when the script is stopped.

Crash Example:

Expected result

The custom audio data file should mount successfully without causing a client crash, allowing the audio to play when the player enters the defined area.

Reproduction steps

  1. Audio Creation: Created a custom .awc file (e.g., marshall_zone_01.awc) using OpenIV from a correctly formatted XML .oac file (confirmed working and clean).

  2. Dat 151 Test (Ambient Zone):

  • Used CodeWalker Editor v30_dev46.

  • Created a Dat 151 Ambient Zone.

  • Crucial Step: Set the essential Flags 0 value to 0x00000000 to prevent the known Access Violation.

  • Created a corresponding .nametable file to resolve the Name Hash for the new file name.

  • Configured fxmanifest.lua to stream the DAT151.rel, DAT151.nametable, and .awc using AUDIO_GAMEDATA and AUDIO_WAVEPACK.

  • Result: CRASH.

  1. Dat 150 Test (Ambient Emitter):

  • Created a new Dat 150 Ambient Emitter (the simpler file type).

  • Used safe Emitter settings (e.g., Flags 0: 0xAA001100).

  • Updated the fxmanifest.lua to stream the DAT150.rel using AUDIO_SOUNDDATA.

  • Result: CRASH.

  1. Final Attempt: Tried using a Mono-channel AWC (single .wav file) with the Dat 150 Emitter to rule out stereo encoding issues.
  • Result: CRASH.
Image

Importancy

Crash

Area(s)

FiveM

Specific version(s)

GTA V build: b3258 (from GTA5_b3258.exe) FiveM client build: 20139

Additional information

Since both the Dat 151 (Ambient Zone) and Dat 150 (Ambient Emitter) cause a crash despite implementing all known fixes (Flags 0: 0x00000000, unique naming, nametables, and AWC integrity), the problem appears to be related to FiveM's handling of the .rel file structure generated by CodeWalker. Any insight or solution from the development community is greatly appreciated.

nohassi avatar Sep 27 '25 03:09 nohassi

Can you attach the dat151 file? Also you should not be using dat150, both of them can go inside of 151. You should also be using the latest codewalker version as many changes to rel files were done (by me)

ook3D avatar Sep 27 '25 03:09 ook3D

Oh, I see the issue here, you're mounting 150 as a dat54 rel, 150 and 151 are the same

ook3D avatar Sep 27 '25 03:09 ook3D

Thank you ook3D, for the excellent suggestion. I agree that seeing the full resource structure is the only way to pinpoint this issue.

I have uploaded the complete resource structure to Google Drive for you to check.:

  • marshall_zone_01.dat151.rel
  • marshall_zone_01.dat151.nametable
  • manifest.ymf`
  • fxmanifest.lua
  • The corresponding .awc file.

Resource Download Link https://drive.google.com/drive/folders/1vplmKn9SA-O81SsudQ2oeUmAk3J0GkbH?usp=sharing

I have also updated my CodeWalker to the latest version as you advised and will re-test the Dat 151 file again after you review it.

I appreciate you taking the time to look into this persistent crash!

nohassi avatar Sep 27 '25 03:09 nohassi