Rawrior
Published
Controller would not detect if Steam Overlay was turned off. No clue why that affects it.
I had performance and stability issues with Proton 7.0.3 and Experimental. GE worked perfectly and had performance much more in line with what I expected.
Cutscenes and closeup dialogue seem to be locked to a much lower framerate, however, even if the framerate counter reports FPS in the 70-80 range.
Slight stutter and framerate drops in loading corridors when moving between areas. Doesn't affect gameplay.
Very slight stutters on camera cuts in cutscenes, just like 0.05 seconds of stutter
I experienced a lot of crashing during character creation, every 10-15 minutes. Otherwise, nothing.
Apart from the character creation crashes, I have had no problems for ~4 hours gameplay. Played with an Xbox X controller, and everything worked fine.
Tried proton experimental, GE proton, a mix of launch options found in other reports here.
Roads were completely borked. Something about the level of detail setting made it so that the geometry would blow up to fill pretty much the entire screen/skybox, which made the game completely unplayable. Turning it down would make the glitch "go away", as in it didn't occur when the camera was far away enough.
Will have to come back to it later, but for now, nothing worked.
Works perfectly fine out-of-the-box. DSFix only needed WINEDLLOVERRIDES="dinput8=n,b" %command% added to launch options in Steam to work.
DSFix keyboard shortcuts (cap/uncap FPS for example) do not work.
A few long loads, but works great out the box.
The very first load when booting for the very first time took a very long time to load. Initial loads for subsequent boots of the game still take some time, but not nearly as long. Some load screens also feel somewhat long, but that may just be because the game actually has a lot to load, not quite sure.
Controller would not detect when Steam Input was enabled, but detected fine with it disabled, weirdly enough.
I got maybe 10 FPS, which is unplayable as game speed seems to be tied to framerate
I tried Proton Experimental, 7.0-1, and GE 7.4, and none remedied the FPS problem. I also tried some launch options mentioned in here, but none made any difference.
I'd hazard a guess that non-GE proton also works fine, I just hadn't noticed until now that I'd selected a GE version.
Native popped up with a window for a tenth of a second, then closed immediately.
--use-d3d11
There is a 1-pixel white border when in borderless window mode, but that mode seems to be required
Game would not fully launch when fullscreen
Fullscreen made the game not launch fully, but the game uses borderless window as its default. Multiplayer works great, haven't had any problems during my playtime. Not sure if the launch option is actually required.
Runs perfectly out the box.
Replugging a controller made my system hang for a significant amount of time (10-15 seconds), but it worked fine afterwards.
Ran perfectly out the box
I had some intermittent half-second (or less) stutters during some sessions, but not during others. I suspect they were due to some bottlenecked loading, but they were not significant enough to affect gameplay all that much.
PROTON_USE_WINED3D11=1 %command%
Without the launch option, I got the following error: "Failed to initialize graphics. Make sure you have DirectX 11 installed, have up to date drivers for your graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphics failed."
Does not run
Tried both GE 9.4, experimental, and default. None would launch the game. It would pop up with a black screen for a tenth of a second, then close immediately.
There was a long "shadow" on the main character, extending to the right. After some playtime, I stopped really noticing it. Buttons and some sprites in situations also seemed to be shifted or stretched too far to the right, cutting them off.
Game seems to be windowed only. The graphical glitches don't impact playability.
PROTON_USE_WINED3D11=1 %command%
Very minor artifacts or odd rendering, mostly when alt-tabbing in and out.
After alt-tabbing out and back in, mouse would sometimes not be constrained to the game screen. This was fixed by tabbing out and back in again
Once I got it running, everything worked great. The other tinker options of forcing D3D9 didn't work for me, so try a a few different thngs.
