Forged Alliance (Not FAF launcher) CTD on start + possible solution
-
Hey,
Do excuse me if format/post location is not quite right.
I've just finished a pretty annoying debug session and thought I'd share, in case this helps anyone.
I've just done a clean installation of FA itself from Steam and installed FAF via the Linux script.
Installation went smoothly and FAF client launched correctly (albeit with a few graphical oddities).
Relevant libraries are present and updated to several months ago.
Upon attempting to start a CO-OP (alone, for testing purposes), I've encountered a crash-to-desktop due to access violation (surprisingly, not due to a null-dereference)
Starting directly via steam (With launch flags
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%) worked as expected.After some digging, I've narrowed the issue down as relating to the 'sounds' directory.
The was no sound specific error in the log, just a stacktrace (Is there anywhere I can get debug symbols from?) and an access violation exception.After going through the sounds one-by-one, I've narrows the problematic files to:
- UAAWeapon
- XES_Destroy
- XSA_Weapon
After removal (both xsb and xwb), game now launches correctly (though I've yet to actually start a round so may encounter more errors later on)
Casual system info:
OS: Manjaro 24 (Cinnamon DE V 6.2.6)
Kernel: 6.6.41-1-MANJARO LTS
CPU: Intel I9-10900K (Normal Tau, no OC aside normal boost clock)
GPU: Sapphire 7900XTX Nitro+
Mem: 32GiB DDR4 4GhZ (CAS... 17 if I recall, XMP, no manual OC)
Display server: X11 -
This is an interesting find. Perhaps @magge can add it to its how-to-fix-sound-crash guide as a possible solution.
-
@jip - Ack, glad to hear (and thanks for the response).
Please let me know if you require any further info, I'll try to keep an eye on this page.
