raylinth
Published
Absolutely could not get this to start
Nothing worked - I saw the other comments, GE Proton, older versions, run it and wait. I waited upwards of half an hour, never launched. Did get errors once.
I gave up. I'm not going to bother when other racing games in proton with racing wheels no issue: wreckfest, dirt rally 2.0, project cars 3. Sorry Assetto Corsa, but I don't have the time to bother with you not launching after an hour of trying multiple things. I refunded the game.
Great, cozy game
DISABLED STEAM INPUT. Using an 8bitdo pro controller, button presses were hitting twice. Select down would open a menu but letting up would close it (like two button taps).
With Steam Input disabled, the controller area reads "Suports your xbox controller". With it enabled (bad), it read "Mostly Playable with your controller".
Unsure if this is just this controller or this game, but this was a really necessary tweak for me.
Mic push to talk was crackling, had to leave it on.
Game used to run at 80fps, now struggles to keep 30, running at 23-50. This was because of the latest update. Hopefully devs address performance.
gamemoderun %command%
Fun time, great experience on linux and with force feedback racing wheel.
gamemoderun %command%
XBOX-one controller stopped working, had to right click Properties > Controller > "Disable Steam Input" then it began working again. (Does not require big picture mode)
gamemoderun %command%
Steam overlay only working in EXPERIMENTAL, did not show in proton 9.0-2
Occasional freezing after cutscens.
35-40 fps consistency
In-game: D3D11. Set windowed: 1066x666. Anti-Aliasing: High. All settings: Low. FSR v2.1.1
Deck: FSR at 5. 40Hz limit.
4 watt TDP for improved battery life
Perfect
As stated by bolby atmos, screen tearing was occurring at fullscreen but was resolved by adding a dxvk.conf in the base folder (next to FINAL FANTASY.exe) with the following contents:
dxgi.maxFrameRate = 60
dxgi.tearFree = True
fullscreen starts windowed, but can alt+enter into fullscreen
Wayland is great
Did switch distros from X11 to wayland and screen tearing is a thing of the past for the Final Fantasy Pixel Remaster games.
Wayland is great
Did switch distros from X11 to wayland and screen tearing is a thing of the past for the Final Fantasy Pixel Remaster games.
Wayland is great
Did switch distros from X11 to wayland and screen tearing is a thing of the past for the Final Fantasy Pixel Remaster games.
Lower resolution + FSR can make a difference on battery while looking just as good.
FFX worked with any version of proton but X-2 only worked with 6.3-8 and no launch options. Before that change X-2 would crash on boot. It's fully playable at this version.
DXVK_ASYNC=1 gamemoderun %command%
Using the lutris XIVLauncher - https://lutris.net/games/final-fantasy-xiv-online/
DXVK_ASYNC=1
required to avoid dropping frames <40 and running consistently >100 fps. Can run on desktop high graphics.
I did one action to get this game to work with easy-anti-cheat: I used protonup-qt
to install GE-Proton7-20 and switch the game to it. Do not run any scripts or modify a fresh install if you use this version.
Audio missing from starting cutscene but fine in game.
Only supports 16:9 aspect ratio, which looks fine with black bars.
gamemoderun %command%
Hard crash of entire machine, wayland
Instability with servers (as with all players)
Good when servers are not overloaded
a pathway to use directx-12 and AMD
I'm making this report cause I'm not a fan of the influx of reports saying to just use-d3d11
. I tried that and the game was noticably worse. It looked worse (lighting and environmental fidelity is noticably worse), the performance was significantly more choppy - and it became unplayable with choppy/stuttering inconsistent frame-rate.
After tinkering around with graphics options for my AMD 5700 XT
- I found a happy medium.
What didn't work:
At medium-ish graphics and 1440p, the game defaults to ai-upscaler of "ULTRA QUALITY" and the game runs about 45fps and 100% GPU high usage. I suspect the hovering at 100% to be why the game crashes. The crashing made it not-playable, but the performance was "ok" when it ran.
What worked better:
Simply lowering the resolution. I found QUALITY to be very blurry and not worth it. However, I found that changing to 1080p, setting it to NATIVE, and locking it at 60fps to be absolutely excellent. I understand this is a bit subjective, but I feel it's worth saying I found a native lower-resolution to be better than the upscaling options that looked smeary. A little bit of aliasing going on. Most importantly, the game ran locked and the GPU stayed around 80% usage and my crashing went away.
This was pre-PATCH 1.000.11, I'm mostly going to trust that the devs address the crashing issues seen with AMD, but my goal was 60fps at this card anyway, so I'm satisfied. I played a few hours no issue (low peak servers).
Doesn't run
Black screen, loading logo, crash. proton-experimental and GE-7-28. Bleh.
Demo ran by default
Demo version, Feburary nextfest 2024. I didn't have to tweak a single thing.
PROTON_USE_WINED3D=1 %command%
Played fine once unity launched
Must do a custom mf install to run the game. Runs fine with proton 6.3-5.
How to install.. git clone https://github.com/z0z0z/mf-install && cd mf-install && WINEPREFIX=~/.steam/steam/steamapps/compatdata/837610/pfx/ ./mf-install.sh && cp system32/*.dll ~/.steam/steam/steamapps/common/Mary\ Skelter\ Nightmares
PROTON_LOG=1 %command%
By disabling upscaling, I was able to see and play the game instead of a black screen.
My GPU isn't handling this well. But it's kinda old. I would think the best I can handle here is 30fps in gameplay.
Great with FidelityFX ON
Recommended in-game FidelityFX ON for boost from 60 to 80 FPS with card 5700xt. Other than that, nothing specific to proton vs windows10 - equivalent experience.
gamemoderun %command%
Fun time, great experience on linux and with force feedback racing wheel.
AMD_VULKAN_ICD=RADV gamemoderun %command%
STUTTER: Best to avoid NTFS/NTFS-3G. I typically use an ntfs-3G windows shared drive for numerous games without issue (Resident Evil 3, Monster Hunter World), but this game it was the primary cause of a stutter during gameplay every few seconds. Especially if going to the menu causes a "program not responding" lag response.
FIXED: I moved the game over to my OS nvme ssd and the problem went away. Simply put EXT4 and your fastest drive is recommended for this game loading assets.
ADDITIONAL: Also recommended, FidelityFX Super Resolution 1.0 at Quality. Terrain Tesselation at Enhanced (everything else High). Milage may vary.
flatpak run com.github.Matoking.protontricks 2549740 vcrun2019
Had to toggle alt-tab, but then fullscreen worked
MEDIUM settings for 60 FPS
flatpak run com.github.Matoking.protontricks 2549740 vcrun2019
The demo appid is 2549740 I'm running steam and protontricks in flatpak. Protontricks --gui should detect it, but I had issue with it showing up hence the command. This command installs the missing vcrun2019 dependancy for this demo. You have to click YES/OK on a bunch of dialog because the vcrun2019 version is slightly updated so the MD5 doesn't match - just ignore and continue. You install 2 things, the x86 version and the x64 version. Then the game should run
For my GPU, I needed to go to MEDIUM settings to get 60 fps (probably just demo jank).
just no luck
despite other notes of 'protontricks 1113000 wmp9 quartz devenum' - no luck here. displays black window and immediately crashes at 5.0-10. 6.3-5 says sorry.
World loading tunnel drops to 1-5 FPS and never loads, eventually freezes entirely.
DXVK_ASYNC=1 gamemoderun %command%
At least Final Fantasy XIV plays fine instead....
Runs well on steam deck, worth tweaking for performance and battery
Had issues with push to talk not alwasy registering with L1, so made that always on for a better experience. Radio was fine, also mapped it to L4. I found opening doors difficult, made better by mapping A to R4. (so thumb can stay on right-stick as you "swing" the door open holding button)
Since menus are mouse-centric, that was made better by making R5 left click and using both trackpads as mousepads.
Darkness of gameplay basically requires full screen brightness, changing resolution for battery life and performance, detailed below..
Windowed mode was required for proper FSR.
Mic push to talk was inconsitent (might be the game itself) - always on mic was better experience. Weirdly, push-to-talk radio (which is required) has no issues.
While the game in most houses ran at stable 60FPS, the campsite caused the deck to struggle sub 30fps.
For 3+ hours of battery life, visually comparable, set graphics to..
- 960x600 @60hz
- Fullscreen Mode (windowed) (required to enable FSR properly)
- Shadow Resolution: Medium
With the steam menu..
- Lock refresh rate 50
- FSR (scaling factor)
Do NOT change "half rate shading", makes text on boards and devices less readable due to aliasing
Game appears to freeze when loading, this is on all platforms. Playing online with someone on a steam deck, a computer, and VR is a trip and works... as well as this janky game already works, which is quite good.
Extremely fun to play on steamdeck (recommend headphones) and linux desktop environment.
gamemoderun %command%
8.0-4 had no issue. Proton experimental had black boxes and no UI graphics.
Fun time, great experience on linux and with force feedback racing wheel.
-force -dx11
DirectX-11 provided massive performance improvements in <100 fps at 1440p.
decky - powertools governor powersave, or the game runs at 100% throttle when it's unnecessary
To fix red lines on train after second character is introduced, GE-Proton7-49.
BE PATIENT - had to wait 5 minutes on first launch (spinning steam logo) to boot this version of proton-GE. It's likely silently doing a 2GB shader cache download.
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=1 %command%
Switched from 2022 default (ray-tracing) to BETA "dx11_non-rt".
Swithced to DirectX-11. MASSIVE performance improvement. DirectX-12 was tanking below 30 while DirectX-11 is consistently running over 100 FPS at 1440p. Recommended High settings and FidelityFX ON.
gamescope -w 2560 -h 1440 -f gamemoderun %command%
Had issue with demo keeping in window and unable to select options in the graphics menu UNTIL I added gamescope. Also added feral gamemode for safe measure. Ran with some FSR upscaling, ran as well as RE2
RE4 DEMO using proton experimental.
OOB works great
For this graphics card 5700xt, probably want to tweak into medium to get 60fps at 1440p, still looks excellent.
gamemoderun %command%
First time had issue running, but removed mods and epic games updated. Then launched, no issue.
1440p
80-90fps - Ray Tracing Shadows/Reflections high. FSR set to quality. Settings at Epic. or 90-110fps - No ray tracing, native (no screen optimizations). Settings on Epic.
For earlier missions which are guns only, gyro is helpful
Luxtorpeda is an alternative to proton when a game has a linux engine replacement. Luxtorpeda is installable from protonup-qt. When Jedi Outcast 2 or Acdemy is set to Luxtorpeda (via force compatability), it will download OpenJK which is a native linux game engine for these games (it does not support multiplayer unforunately). OpenJK works perfectly well on steam deck. This is honestly a pretty cool compatability option I just learned about and played about 2 hours into the game.
See more games supported by luxtorpeda - https://github.com/dreamer/luxtorpeda
Would freeze entire OS forcing hard reboot
Would freeze entire OS at menu forcing a hard reboot. Any version is proton including GE.
Lutris+GOG was playable but no music and having lib32-openal installed broke YouTube of all things (any browser).
I was left wondering if this was a pipewire audio or Wayland issue but this is a problem I don't have with any other game. Journal logs showed kernel panic - I just don't want to deal with that.
This game messed with my overall system in such weird ways it really wasn't worth it. It was super weird.
DXVK_ASYNC=1 RADV_PERFTEST=nggc AMD_VULKAN_ICD=RADV gamemoderun %command%
1080p, medium graphics, FSR 3. 60-80 fps.
One crash
Demo version
gamemoderun %command%
Crashing between 1-5 minutes. After testing various launch options, switching from wayland to X11 removed crashing. This is pretty uncommon (I play all games just fine with wayland) and I assume this is just a day 1 issue.
RADV_DEBUG=nodcc %command%
UE5 is demanding on 5700xt and I got crashes at first due to my GPU running hot. Monitor with watch -n 2 sensors
and radeontop
. Once I fixed my airflow issue, the problem went away.
Launch option RADV_DEBUG=nodcc %command%
is because there is a potential MESA bug causing GPU hang in UE5 engine games. Though I did not experience this with Thaumaturge, I did with Talos Principle 2.. though I now suspect that was my airflow issue. See - https://gitlab.freedesktop.org/mesa/mesa/-/issues/10021
Don't expect to push outside of low. That said locking in 30fps/30hz is good - some occasional dips. Some indoor areas may reach 40 but most of this game is vast and open, so I would just lock at 30. ((As a side note, streaming with steamlink or moonlight/sunshine is how I actually play at high/60fps/800p - HOWEVER this is a report for native steam deck play. ))
Missing end of speech
Menu was flickering
Crashing after 10 minutes
This game has a miriad of issues. Here's how you can make it playable:
1 - run it in a window, to fix mouse interactions
The game does not scale to fullscreen, running at 800x600 by default in the top left of a black void at our resolution. Worse, the touch interactions are offset to the right of the visuals. Running in a window will fix the mouse interactions. Use winecfg and use Emulate a virtual desktop. Doesn't matter if you give a bigger resolution, it always seems to force 800x600. I switched to wine and winecfg to play the game. If you want to try proton, I think you can set the prefix to the directory in steam. So for me using a flatpak version of steam that is..
Navigate to the game's prefix directory
cd /home/chris/.var/app/com.valvesoftware.Steam/.steam/steam/steamapps/compatdata/785480/pfx/
Start winecfg in this directoryenv WINEPREFIX=$PWD winecfg
2 - use a magnifier :(
Unfortunately this is why I didn't play on the steam deck. You can set the magnifier toggle to a button, but the mouse will now pan the entire window.
Instead I used my DE (gnome) to use a magnifier to 2.5 (at 1080p) and have the cursor push the content around. This lets me use the mouse while keeping the screen in the center.
3 - run it one cpu, to fix crashing
taskset -c 1 wine TI.EXE
I had trouble with the proton version and this taking affect, however you may set this after launch with pidof TI.EXE and taskset -cp 1 #####.
4 - run it on one cpu, to fix dialogue cutting off at the end of setences
Again, I had issue with this taking affect launching through steam, but taskset does fix audio cutoff.
5 - disable window decoration to fix flickering/crashing save dialog box
winecfg and disable Allow the window manager to decorate the windows and disable Allow the window manager to control the windows
gamemoderun %command%
Fun time, great experience on linux and with racing wheel.