Draconicrose
Published
If playing native you need -screen-fullscreen 0 in the launch options. I recommend forcing proton because the native version stuttered a lot (even though it was high fps)
I used the Steam game-specific proton folder as the WINEPREFIX and ran mf-install as normal.
Once the game launches it only gets a black screen for a while before it turns white and errors with "failed to initialize Direct 3D".
PROTON_NO_D3D11=1 %command%
Manually set the resolution in the game's settings.xml
"Fake Fullscreen" acts exactly like fullscreen.
Significant performance issues turn the game sluggish and, while it's playable due to this being a city builder, it's not enjoyable.
The game drops to 15 fps randomly at the start (requires full pc restart to fix) and stays at this level of performance at around 200 population (New Home scenario)
Sometimes during choice events the camera will run all the way to the bottom of the map and glitch, but panning back to the city fixes it.
Depending on the proton version you will probably have issues with the cursor bounds.
Plays well, smoother than the Lutris version. Has an issue with long play sessions that can be mitigated by restarting the game.
gamemoderun %command% WINE_FULLSCREEN_FSR=1 DXVK_ASYNC=1 RADV_PERFTEST=gpl -provider Portal -autologin
After an hour+ of playing the FPS will tank until game restart.
It had severe graphical issues on any Proton higher than 8.0-5. It also froze my window manager and forced me to go into TTY to kill GW2 or restart to recover access to my computer.
Fullscreen sends the game window to the side of the screen, with most of it out of view.
Controller support is fubar'd.
The game stutters even at a constant 60 FPS and experiences significant frame drops more often than once a minute. This seems to have started with the latest patch.
Works extremely well, feels almost native.
Windowed fullscreen captures the mouse, even with the option disabled in the in-game settings.
Overall, during the demo, it seemed perfectly playable, especially after the first night.
Low fps during the first night
Crash with Steam overlay
After messing with settings it runs perfectly fine. Might be better with a controller.
Fixed by turning vsync off and fps to 60
In some in-game interactables, the bounds were incorrect. Sometimes UI arrows don't respond and I had to use the arrow keys.
At first the game detected my settings as way lower than my system can handle but that's just in-game stuff. Played about an hour from the start, going through the tutorial and a gwent game.
Proton-5.4-GE-3 GloriousEggroll
