Krzd
Published
Crashes after Launcher
Installs the game and launcher, but does not launch the game itself.
Runs fine without any major issues right out of the box.
Fullscreen switches monitors when using Alt+Tab, and can (with very limited testing) only be moved back by returning to the title screen
Using a German keyboard, Y and Z were not automatically switched.
I cannot confirm the other report of being unable to aim and move at the same time, that worked flawlessly for me.
Extreme performance issues (<10fps)
Very strong lag, not accepting multiple keypresses if made in quick succession. This might be caused by the performance issues however.
Very extreme performance issues ( <10fps), irrelevant of graphics settings (tried both lowest and on highest settings)
Crashed once in a 3 hour session, restarted without any issues.
Works almost perfect OOTB, and definitively good enough for a satisfactory experience
Atrocious Resource Usage.
|Where? |DEFAULT |LOW |
|--- |--- |--- |
|Main Menu | 5 FPS | 157 FPS |
|Cut scenes | 5-6 FPS | 6-8 FPS |
|Viewing KSC | 3 FPS | 7-8 FPS |
|Empty VAB | 3-4 FPS | 6 FPS |
|K1 in VAB | 3 FPS | 6 FPS |
|K1 on launchpad | 3 FPS | 5 FPS |
|K1 during launch | 2-4 FPS | 3-6 FPS |
|K1 in Orbit | 5-6 FPS | 6-7 FPS |
|Map View | 26 FPS | ~48 FPS |
Constantly minimizes, unable to keep on screen.
I've tried multiple lauch options, including but not limited to:
"PROTON_ENABLE_NVAPI=1 %command%"
Combined with GE and experimental this resulted in multiple successful launches (and origin crashes), but constant minimizing when in focus. GE seems to have a tiny bit higher chance of success."PROTON_NO_ESYNC=1 %command%"
Combined with GE and experimental this resulted in a few successful launches, less than using the command above, but no origin crashes. Still constantly minimizes on focus."PROTON_USE_WINED3D11=1 %command%"
Using experimental this resulted in a single successful launch, but caused a fatal directX error.
Using GE it launched multiple times, all of which failed due to a fatal directX error."gamemoderun %command%"
Combined with GE and experimental this resulted in NO successful launches, with NO successful origin launches.
--disable-gpu
When you launch it it might not detect the display correctly, just switching windows twice fixes it every time for me.
Rare crashes, about once every few hours of continuous gameplay. If involved in large fights.
Client-side feels a bit less laggy compared to windows, the server-hamsters to have some strokes occasionally.
Apart from the "--disable-gpu" launchflag directly in steam it works perfectly OOTB
This is purely a functionality report..
