Posted November 09, 2024

LinuxFire
Linux Mint RX6600
Registered: Aug 2018
From France

madame-rachelle
New User
Developer
Registered: Feb 2014
From United States

Der_Pit
New User
Registered: Mar 2015
From Spain
Posted November 12, 2024
Well, there's not much of a startup log anywhere. If I start it from a terminal, all I get is
speedy:game% ./handsofnecromancy
Hands of Necromancy hon1-v3.0-gz - 2024-07-04 15:37:49 -0400 - SDL version
Compiled on Jul 4 2024
OS: openSUSE Tumbleweed, Linux 6.11.6-2-default on x86_64
Hands of Necromancy version hon1-v3.0-gz
Then a dialog pops up with the abovementioned error about SkipBexStringsIfLanguage.
I did run strace on it, and there I can see
newfstatat(AT_FDCWD, "/usr/share/doom/game_support.pk3", {st_mode=S_IFREG|0644, st_size=2370619, ...}, 0) = 0
newfstatat(AT_FDCWD, "/usr/share/doom/game_support.pk3", {st_mode=S_IFREG|0644, st_size=2370619, ...}, 0) = 0
openat(AT_FDCWD, "/usr/share/doom/game_support.pk3", O_RDONLY) = 9
This pak file belongs to the install of gzdoom 4.13, and contains the demurred definition.
But as I said, handsofnecromancy should never (try to) read that file on first hand.
speedy:game% ./handsofnecromancy
Hands of Necromancy hon1-v3.0-gz - 2024-07-04 15:37:49 -0400 - SDL version
Compiled on Jul 4 2024
OS: openSUSE Tumbleweed, Linux 6.11.6-2-default on x86_64
Hands of Necromancy version hon1-v3.0-gz
I did run strace on it, and there I can see
newfstatat(AT_FDCWD, "/usr/share/doom/game_support.pk3", {st_mode=S_IFREG|0644, st_size=2370619, ...}, 0) = 0
newfstatat(AT_FDCWD, "/usr/share/doom/game_support.pk3", {st_mode=S_IFREG|0644, st_size=2370619, ...}, 0) = 0
openat(AT_FDCWD, "/usr/share/doom/game_support.pk3", O_RDONLY) = 9
But as I said, handsofnecromancy should never (try to) read that file on first hand.

madame-rachelle
New User
Developer
Registered: Feb 2014
From United States
Posted November 13, 2024
That is still helpful information. That means it needs to load not any of the optional files that come with GZDoom.
Will be addressed in the next update.
Will be addressed in the next update.
Post edited November 13, 2024 by madame-rachelle

LinuxFire
Linux Mint RX6600
Registered: Aug 2018
From France
Posted November 29, 2024


In addition my other Linux games on GOG work well for most of them, I'm still happy to see the Linux version and I keep the game waiting for your next maj, thank you for your work madame-rachelle.

t-elos
FBK
Registered: Jun 2011
From United States
Posted January 04, 2025
Sound is not working on Mint 22 for me, but I'm guessing it's probably because I've had general audio issues since upgrading from 21. I'm using pulseaudio because pipewire was completely broken for me.
EDIT: NVM. Was running through Heroic. Works fine if I run ./start.sh
EDIT: NVM. Was running through Heroic. Works fine if I run ./start.sh
Post edited January 04, 2025 by t-elos

Der_Pit
New User
Registered: Mar 2015
From Spain

madame-rachelle
New User
Developer
Registered: Feb 2014
From United States
Posted February 13, 2025
Unfortunately this bug snuck by and I forgot to fix it, I was dealing with a lot of other issues updating the engine due to security fixes upstream (GZDoom).
The next update will work with GZDoom's current game_support.pk3 without issues, but if changes the archive again then the problem will come up again, unfortunately.
The only thing I can suggest is after the next update, do a `cp /dev/null /path/to/hon/game_support.pk3` as a workaround - an empty archive should(?) block the loading of the OS's default archives. If that doesn't work, then you'll have to throw it into a docker container or move the system-wide game_support.pk3 into ~/.config/gzdoom (HON will not look here).
The next update will work with GZDoom's current game_support.pk3 without issues, but if changes the archive again then the problem will come up again, unfortunately.
The only thing I can suggest is after the next update, do a `cp /dev/null /path/to/hon/game_support.pk3` as a workaround - an empty archive should(?) block the loading of the OS's default archives. If that doesn't work, then you'll have to throw it into a docker container or move the system-wide game_support.pk3 into ~/.config/gzdoom (HON will not look here).
Post edited February 13, 2025 by madame-rachelle