now is working thanks

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).

Thanks king

@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.

I've posted about tweaks needed to get this to work for Termina at https://sp.zhabite.com/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!

@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]

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]

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

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

@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