Steam Community :: Guide :: [Unofficial] Linux Native Game Launch

Fear & Hunger

This Community Hub is marked as 'Adult Only'. You are seeing this hub because you have set your preferences to allow this content.

All Discussions Screenshots Artwork Broadcasts Videos News Guides Reviews

Fear & Hunger > Guides > Tostaday's Guides

Not enough ratings

[Unofficial] Linux Native Game Launch

By Tostaday

Run the game natively on Linux, with the help of NW.js executable without Steamplay (Proton), use it at your own risk.

Award

Created by

Tostaday
Offline

Category: Modding or Configuration

Languages: English

Posted

Updated

16 May, 2023 @ 9:27am

18 Sep, 2024 @ 2:46pm

1,603	Unique Visitors
31	Current Favorites

Guide Index

Overview

Info

Fear & Hunger - Termina by Monsieur Elephant

1a - Download NW.js (Direct Link)

1b - Navigate their site (Alternative way)

2 - Extract and overwrite the existing files

3 - Give executable run permissions

4 - Run the game

Tweaks

NW.js additional info

Comments

Info

I tested this with NW.js version 0.57.1, others might or might not work.

NW.js versions who were built with node 14 or 16 in mind are more likely to be compatible as per my testing, node 18+ focused versions break some images and sprites in-game.

This was not tested in Steamdeck, i have no idea if it works there.

I advise you to backup your save data located in the sub-folder "www / save" in your steam game install dir

Fear & Hunger - Termina by Monsieur Elephant

For Fear & Hunger - Termina, check out Monsieur Elephant's guide. Link below.

Link 1

1a - Download NW.js (Direct Link)

Direct Link(s)

64 bits executable[dl.nwjs.io]
or
32 bits executable (Not tested)[dl.nwjs.io]

Below is the expected file structure inside the archive, if you follow 1b), you need to download the Linux compatible archive

1b - Navigate their site (Alternative way)

Go to this page to download NW.js https://nwjs.io/.

After entering the homepage and click "Downloads" on the navbar

Click "Previous Releases"

Choose version 0.57.1 from the list

Download the linux executable, paste it in the steam dir folder and extract it

2 - Extract and overwrite the existing files

Warning: If you intend to run the game with Steamplay (Proton) at a later date after doing the step below, you might need to delete the game folder or reinstall the game, don't forget to backup your saves beforehand

Extract the archive inside the game dir and overwrite any existing files.

3 - Give executable run permissions

Right click and go to "Properties" in your file manager

Go to the "Permissions" tab and enable the "is executable" checkbox

4 - Run the game

Click "nw" to run the game and you're done

Tweaks

If you want to use the steam to start the game, you can also set steam launch options:

./nw %command%

/'InstalledGameLocationPathHere'/nw %command%

NW.js additional info

The method shown works for most RPGMaker games by my experience, but you need to figure out the right version of NW.js for each game and even then it might still not work, for those who like to tweak things, this below might help.

This is based on my experience with this and other RPGMaker games, therefore some of my assumptions below might be wrong, in any case it can serve as a starting point for more experienced users.

Locally installed Node.js version or game code based on it:

10 -> NW,js v0.33.4
12 -> NW,js v0.41.3
14 -> NW,js v0.49.1
16 -> NW,js v0.57.1
18 -> NW,js v0.69.1

21 Comments

< >

gumball riggy 25 May @ 10:44pm

hi, thanks for the guide. just wanted to let anyone interested know that this works perfectly for me with NW.js v0.100.0 (just upgraded from v0.99.1, which also worked without a hitch)

if you're really crazy (as i am), run ./nw using gamescope for extra performance (in the same dir as nw):

>sudo setcap 'CAP_SYS_NICE=eip' $(which gamescope) && gamescope -f --expose-wayland --backend drm --immediate-flips --rt -- ./nw

use drm backend if running straight from tty for best performance, otherwise use the default if running on top of DE (or for me, needing sdl backend currently as there is some bug with unsupported windows scRGB profiles - very interesting).

Fishamus 4 Jan @ 6:51pm

Thanks king

Tostaday [author] 18 Sep, 2024 @ 2:49pm

@Monsieur_Elephant

Added a link to your guide at the top, hope you don't mind. Good job on figuring out what the problem with NWjs/Linux was.

Monsieur Elephant 18 Aug, 2024 @ 3:27pm

I've posted about tweaks needed to get this to work for Termina at https://steamproxy.net/sharedfiles/filedetails/?id=3311914110

I wanted to post it as a comment, but there were formatting/character restrictions for a comment :(. Thanks again @Tostaday for this guide!

Tostaday [author] 7 Mar, 2024 @ 5:37pm

@Keliryn

Short answer: yes but with no success.

Long answer: I experimented running it with NW.js 0.69.1 or earlier sometime before i made the guide (~ 1 year ago), i remember you were able to leave the train but performance was really bad and random crashes happened 5 to 15 min into the game so i gave up on making a Termina guide also. I gave it another shot today and tried NW.js versions (0.41.3 ; 0.49.2 ; 0.69.1 ; 0.77.0 ; 0.85.0), versions earlier than 0.69.1 run but get stuck in the train's loading screen, versions after that show a new error pop-up on the screen that can be solved by adding text to the "name" key inside the "package.json" file located in the root folder ("name": "FH2" for example), that makes the game boot normaly but it still gets stuck at the train's loading screen as before.

[Part 1/2]

Tostaday [author] 7 Mar, 2024 @ 5:34pm

My suspicion is that since file paths work differently between Windows and Linux a special character ($, &, /, \) or a hardcoded path (C:\%gamedir%\img\1;2;;3.png) in the game code makes the game unable to find one or more of the game assets which leads to it staying stuck looping forever trying to load them, but i didn't do any in depth testing so it's just speculation on my part. I might give it another go later if i have some free time to spare, but for now Proton or a native version released by the dev is probably your best bet.

Part [2/2]

Keliryn 6 Mar, 2024 @ 2:11pm

Hi, first of all thanks for the guide.

Tell me, have you tried running Termina with this method?
The first game launches without problems, but Termina goes into an infinite loading screen when exiting the train at the beginning.

Arch, nw.js 0.57.1

Deathstruck 30 Nov, 2023 @ 7:12am

Ah, I tried that as well with the .exe renaming and command. Unfortunately stil no good results. Only difference is that now there is no sound in the background at all during the spinning logo, haha.

At this point I think it's really up to the developer himself to fix this then. Nothing that can be really done about the Deck. Until then, I am fine with just using the "nw" file as a non-steam game in the library.

But thank you so much for trying to help me and giving me a bunch of methods to try! It's really appreciated

Tostaday [author] 29 Nov, 2023 @ 2:38pm

@Deathstruck you can try renaming Game.exe to Game.exe.old and nw to Game.exe and using "./Game.exe %command%" in the steam launch options to see if steam "catches it", other than that, you can try newer NW.js versions, they might work better with steam overlay (See NW.js section and try some of the versions there), if even that fails, there's not much else to do but wait for steam to support the game better or the developer releasing a patch for that deck specific problem

Deathstruck 28 Nov, 2023 @ 10:31pm

Gave it a try too, and the "switch window" is not present at all in the steam button menu. :(
(I also made sure to turn off the startup movie on wake)

I know that some people with similar issues with other games (spinning logo over the screen) - when they pressed the steam or settings button, they could briefly see the game in the bg, but here all I see is a black screen instead.
Which leads me to believe the game does indeed run but Steam gets kinda confused because it seems to be expecting a connection to Game.exe instead of "nw"? Even despite the command?

< >