It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
mrT987: The Linux 2.0 version is actually there, but its hidden in the windows installer.
(...)
$ innoextract --output-dir "ion_fury_extracted" "setup_ion_fury_2.0_(51180).exe"
Thank you for this! I waited like a year ;)

(dnf install innoextract on Fedora, couldn't have been easier)

I've copied 3 files (fury.grp, fury.grpinfo and fury_nodrm.bin) into my ION Fury/game/ and yep, it's a Linux 2.0.0 version alright!

Thanks again, why has no one mentioned this before?! :)
avatar
mrT987: The Linux 2.0 version is actually there, but its hidden in the windows installer.
Either install it with wine and copy the required files over or extract it directly:

On Arch-based distros:
1. install innoextract
$ yay -S innoextract

2. decompress installer
$ innoextract --output-dir "ion_fury_extracted" "setup_ion_fury_2.0_(51180).exe"

3. make .bin file executable
$ cd ion_fury_extracted/
$ chmod +x fury_nodrm.bin

Thats it.
Thanks for that! - nice find!!
But frankly speaking, it's not exactly obvious. How am I supposed to know?
avatar
Lamieur: I've copied 3 files (fury.grp, fury.grpinfo and fury_nodrm.bin) into my ION Fury/game/ and yep, it's a Linux 2.0.0 version alright!

Thanks again, why has no one mentioned this before?! :)
I found the Linux .bin a few weeks ago by accident. I just wanted to extract the .grp file and try to run it with eduke32.
Its a bit strange, we waited for the Linux release for half a year and it was there all the time.
avatar
Bertelchen: Thanks for that! - nice find!!
But frankly speaking, it's not exactly obvious. How am I supposed to know?
I guess someone screwed something up with the release upload. The Developer, the Publisher or GOG; who knows :-)

Sadly this "Trick" does not work with the Turok 2 Remaster :-(
Post edited August 22, 2022 by mrT987
avatar
mrT987: The Linux 2.0 version is actually there, but its hidden in the windows installer.
(...)
$ innoextract --output-dir "ion_fury_extracted" "setup_ion_fury_2.0_(51180).exe"
avatar
Lamieur: Thank you for this! I waited like a year ;)

(dnf install innoextract on Fedora, couldn't have been easier)

I've copied 3 files (fury.grp, fury.grpinfo and fury_nodrm.bin) into my ION Fury/game/ and yep, it's a Linux 2.0.0 version alright!

Thanks again, why has no one mentioned this before?! :)
This does not appear to work for me on Linux Mint. I'm able to extract the files from the exe installer just fine, and set the bin to executable. But when running the game I get this cryptic error:

./fury_nodrm.bin: symbol lookup error: ./fury_nodrm.bin: undefined symbol: SDL_GameControllerGetSerial
avatar
ArkhamCraft: This does not appear to work for me on Linux Mint. I'm able to extract the files from the exe installer just fine, and set the bin to executable. But when running the game I get this cryptic error:

./fury_nodrm.bin: symbol lookup error: ./fury_nodrm.bin: undefined symbol: SDL_GameControllerGetSerial
It points to an error with SDL library. Check with your package manager if you have 'libsdl2' packages installed.
avatar
mrT987: It points to an error with SDL library. Check with your package manager if you have 'libsdl2' packages installed.
Here's what I found when I searched my package manager for libsdl2. Looks like most are installed except for the three with the white boxes next to them. None of the uninstalled ones seem like they'd be relevant.
Attachments:
libsdl2.png (91 Kb)
avatar
mrT987: It points to an error with SDL library. Check with your package manager if you have 'libsdl2' packages installed.
avatar
ArkhamCraft: Here's what I found when I searched my package manager for libsdl2. Looks like most are installed except for the three with the white boxes next to them. None of the uninstalled ones seem like they'd be relevant.
'SDL_GameControllerGetSerial' is available since SDL 2.0.14 : https://wiki.libsdl.org/SDL_GameControllerGetSerial .
Your installed version 2.0.10 is too old. So either try to install a newer SDL version or upgrade your distribution to a newer release. Im not very familiar with Mint or Ubuntu based distros, I use Manjaro Linux.
Good luck :-)
Post edited September 08, 2022 by mrT987
avatar
ArkhamCraft: Here's what I found when I searched my package manager for libsdl2. Looks like most are installed except for the three with the white boxes next to them. None of the uninstalled ones seem like they'd be relevant.
avatar
mrT987: 'SDL_GameControllerGetSerial' is available since SDL 2.0.14 : https://wiki.libsdl.org/SDL_GameControllerGetSerial .
Your installed version 2.0.10 is too old. So either try to install a newer SDL version or upgrade your distribution to a newer release. Im not very familiar with Mint or Ubuntu based distros, I use Manjaro Linux.
Good luck :-)
Correct, SDL 2.0.10 doesn't meet the minimum requirements for the current version of the game. However, the next patch will provide a binary that uses static linking for SDL so that the game will run on older distros. The work to get the game running acceptably with SDL linked in statically on Linux has been done for several months, but the game goes through a full QA pass for every patch released to make sure that the entire campaign can be completed with 100% kills and 100% secrets. Understandably, we aren't going to do that again until it's time for whatever version number we slap on the next update.

To play the game on Linux sooner than whenever the next patch is dropped, I second the suggestion to upgrade the distro to something more current... SDL 2.0.14 itself is almost 2 years old at this point, but beyond that I'd be concerned about the number of CVEs an older distro used as a desktop might be vulnerable to. Alternatively, one could also possibly just install Steam and add the fury.bin inadvertently shipped with the Windows version of 2.0 to their library as a non-Steam game. Steam ships current versions of stuff like SDL and runs game binaries with their PATH set so they pick up the Steam-provided libs before looking at those directly installed on the system. I think whether or not this will work here depends on if Steam runs stuff added to the local library as a non-Steam game with the Steam runtime added to the PATH like it does with regular game installations. I'm not on a Linux desktop at the moment and can't check.
avatar
mrT987: 'SDL_GameControllerGetSerial' is available since SDL 2.0.14 : https://wiki.libsdl.org/SDL_GameControllerGetSerial .
Your installed version 2.0.10 is too old. So either try to install a newer SDL version or upgrade your distribution to a newer release. Im not very familiar with Mint or Ubuntu based distros, I use Manjaro Linux.
Good luck :-)
avatar
TerminX: Correct, SDL 2.0.10 doesn't meet the minimum requirements for the current version of the game. However, the next patch will provide a binary that uses static linking for SDL so that the game will run on older distros. The work to get the game running acceptably with SDL linked in statically on Linux has been done for several months, but the game goes through a full QA pass for every patch released to make sure that the entire campaign can be completed with 100% kills and 100% secrets. Understandably, we aren't going to do that again until it's time for whatever version number we slap on the next update.

To play the game on Linux sooner than whenever the next patch is dropped, I second the suggestion to upgrade the distro to something more current... SDL 2.0.14 itself is almost 2 years old at this point, but beyond that I'd be concerned about the number of CVEs an older distro used as a desktop might be vulnerable to. Alternatively, one could also possibly just install Steam and add the fury.bin inadvertently shipped with the Windows version of 2.0 to their library as a non-Steam game. Steam ships current versions of stuff like SDL and runs game binaries with their PATH set so they pick up the Steam-provided libs before looking at those directly installed on the system. I think whether or not this will work here depends on if Steam runs stuff added to the local library as a non-Steam game with the Steam runtime added to the PATH like it does with regular game installations. I'm not on a Linux desktop at the moment and can't check.
Good to know! I have seen complaints about things in the Mint software manager being out of date when using official repositories, so I'm not surprised that's the case here.

I usually don't mess with replacing official repositories for stability's sake, but I'll look at what I can do about getting a newer version of SDL. Thanks to both of you!