Unknown
WINE_ALERT_SIMULATE_SCHED_QUANTUM=1 %command%
Disable Frame Limit, set to 60Hz | TDP: Auto (No Limit) = 2-3 Hours @ 60fps | TDP: 8-10 = 3 (maybe 4) hours @ 45fps
Using the following configurations will get the game running at a mostly stable 60fps, sometimes dipping into the low 50s and very rarely high 40s. Pause menu in-game is locked to 30fps. You will get around 2-3 hours of playtime. You can lower the TDP to around 8-10 to squeeze out more playtime while going down to a consistent 40-45 fps.
Some objects (including player character) may look blurry/unfocused the farther away they are. Unnoticeable if you're playing at a distance.
PROTON_USE_WINED3D=1 WINE_CPU_TOPOLOGY=1:0 %command%
For me it Boots and gets into Gameplay with Current Default Proton, Proton 9.0-4 adding the Luanch Options just gets rid of Lag Spikes and general Choppy Lag
taskset -c 0-1 %command%
Requires the same are the first game, personally I think the Taskset Command is better for the Deck... Actually any time I try the Typology command on my Deck it just refuses to Boot, but on PC the Typology Command Works and Taskset makes it insta Crash
PROTON_USE_WINED3D=1 WINE_CPU_TOPOLOGY=1:0 %command%
For my case, steps are similar to the first game, just with further CPU restrictions. I would have preferred to run in 6.3-8 as it is smoother (after using gamescope or disabling vsync in dxvk.conf to prevent crashes right after starting the game), but that had random mid-cutscene crashes no matter what I did, and I could not open the game in earlier proton versions at all. Therefore I made it work in 9.0-2 instead.
PROTON_USE_WINED3D=1eliminates a wine error that crashes the game soon after launching the game (line 39 of loader_thunks.c). For this case, using WineD3D over DXVK simply works.WINE_CPU_TOPOLOGY=1:0makes the game run smoothly; there's massive performance issues without it (you will notice immediately in 3D areas). There are some FPS reductions under this setting, but seems mostly fine.
Installed Windows DLL "xact_64" and added "xactengine3_7" as native,builtin to Libraries list in winecfg through protontricks
On my second playthrough in NG+, the game often crashed when I rushed through battles and events.
Launch protontricks with "protontricks --gui", select Death End re;Quest, select standard wineprefix, choose Windows-DLL and scroll down and mark "xact_x64", then click "Ok". Next select "Start winecfg", go to "Libraries" tab and add new override for library "xactengine3_7". Add and apply and close the windows.
esync fsync could cause crashes. Game only works on Proton version 5 or lower! After Proton 6 the game might start but it constantly crashes whatever you do. Sometimes when closing
When closing the game check if the wineserver and other wine related apps have closed with it. Sometimes it just hangs them behind and you wouldn't be able to run any other game anymore!
Newer Proton versions (6.3/Experimental/GE builds) do not work well with this game!
Same issue like the prequel. Game freezes then crashes on main menu.
Using Proton 5.0 sadly crashes right on start. Using Protontricks to install xact and adding the dll overrides from winecfg might do the trick!
Installing xact via either protontricks or winetricks, setting dll overrides for xaudio 2_7 and xactengine3_7 (native then builtin) on Proton-GE-5.9-ST via winecfg on the prefix makes the game work.
Needs child window rendering, that is why you need either Proton-GE or Proton-tkg compiled with child window patch
Requires installation of xact through winetricks, then applied xaudio2_7 and xactengine3_7 overrides on the prefix. Use Proton-5.9-GE-5-ST.
Requires installation of xact through winetricks, then applied xaudio2_7 and xactengine3_7 overrides to the prefix. Game should then run with the latest proton release from glorious eggroll Proton-5.9-GE-5-ST.
Proton causes a DX11 related crash in this game.
I attempted to use GloriousEggroll's fork of Proton, and while it shows the startup window, it crashes shortly after that.
Requires child windows patch so official Proton wont work.
Tried proton-ge, proton-tkg, xact+dll overrides. 100% borked and AFAIK, there is no workaround.
