Ashes is definitely my favorite doom TC of all time.
Really liked the enriched edition of the first two releases – but after beating the new versions of OG Ashes and DMW I had to realize I don't get to enjoy the main course.
I run gzdoom 4.1.1 on FreeBSD and it just falls flat on its ass when trying to start up Ashes Afterglow – is this version of gzdoom just too old?
I start gzdoom manually from the terminal:
Code: Select all
~ $ gzdoom -iwad ~/WAD/official/doom2.wad -file ~/WAD/ashesafterglow/ashesafterglow/AshesAfterglow1_02.pk3
This works fine with the .pk3 of Ashes Enriched, but in the case of Afterglow only leads to this:
Code: Select all
GZDoom <unknown version> - - SDL version
Compiled on Sep 6 2021
M_LoadDefaults: Load system defaults.
W_Init: Init WADfiles.
adding /usr/local/share/doom/gzdoom/gzdoom.pk3, 621 lumps
adding /home/phryk/WAD/official/doom2.wad, 2919 lumps
adding /home/phryk/WAD/ashesafterglow/ashesafterglow/AshesAfterglow1_02.pk3, 7571 lumps
I_Init: Setting up machine state.
CPU Vendor ID: GenuineIntel
Name: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
Family 6, Model 61, Stepping 4
Features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 HyperThreading
I_InitSound: Initializing OpenAL
Opened device OSS Default
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
V_Init: allocate screen.
S_Init: Setting up sound.
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
AshesAfterglow1_02.pk3:zactors/enemy/manslayer.zsc, line 370: A_StartSound: action function not found in RJBullshitHack
AshesAfterglow1_02.pk3:zactors/object/flametrap.zsc, line 21: A_StartSound: action function not found in RJFlameTrap
fish: Job 1, 'gzdoom -iwad ~/WAD/official/doo…' terminated by signal SIGABRT (Abort)
I already tried just commenting the offending lines in the .zsc files out and rezip it to pk3 – that makes the two error messages go away, but doesn't fix the SIGABRT…