「 C h i f i l l y 」
Published
I would very infrequently have my view randomly jerk to another location, but unsure whether that's a Proton issue, or a game issue.
Just wanted to note, this was in the play test I got access to today, and and only had access to a limited amount of the game, and the game will come out into early access.
PROTON_ENABLE_NVAPI=1 WINEDLLOVERRIDES="winmm,version=n,b" gamemoderun %command% -modded --intro-skip --launcher-skip
Very occasionally audio would drop for a split second.
If tabbed out for too long, it seems to make the game incredibly choppy when moving the mouse.
After a lot of searching and configuring, I found that only Proton 7-37 works for me. Any version above that causes the game to completely freeze when starting to play the CDPR logo (or the loading screen with the Night City background if modded to remove launch videos).
The launcher in this Proton version doesn't work and just loads a black screen, hence the --launcher-skip flag. If you want to log in first or enable RedMOD mods, you will need to use a different version of Proton first, log in and enable mods, then close it and change Proton version.
PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr %command% -dx12
Without using the mentioned launch options, I would crash just after leaving the incinerator where you encounter BT's for the first time
gamemoderun %command%
It was only in the very final cutscene of the game, the video was delayed by a few seconds.
Infrequent crashes, freezes and slow downs.
gamemoderun %command%
When in an airlock and it was pressurising, the particles seemed to drastically drop FPS, however it's only for a few seconds and you can't do anything else in an airlock anyway.
Occasionally, when some voice lines attempted to play, the game would completely freeze for a few seconds, but would recover and continue as normal.
Outside of the occasional few issues, which gets fixed by restarting the game, I think it plays pretty much as expected.
Occasionally I would get hitches, and after a few hours of play FPS will drop to a point where it's noticably lower, but a game restart fixes it.
I would very rarely (ie. about once a week, playing for a few hours a day) have the game just freeze, and I needed to force-kill the game and restart (doesn't seem to be a pattern), and also occasionally when quitting the game it would freeze and had to be force-killed.
You will need to install protontricks and run protontricks 275850 win10 to get multiplayer to work, but it works fine after that.
I also play with mods (about 60 mods), and the game still works as you'd expect.
Slight choppiness and crackling, but this is the first game I tried after installing Linux so I may need to do a bit of tinkering with my audio setup since I changed to PipeWire.
gamemoderun %command%
While in the garage, my FPS was significantly lower than when on a drive, and having shadows on anything above medium would significantly tank performance.
Although I had the performance issues, I could just keep shadows on medium and push through stuff in the garage with the lower frame rate, and I was able to complete the game with no other issues.
Bear in mind that with my hardware and settings, I only get 40-50 FPS, but for me in a game like this, that's playable.
gamemoderun %command%
The game would open with a black screen in fullscreen or borderless window, but audio would play so the game hadn't crashed, and I could see what should have been visible in the task manager preview.
Switching to windowed would not work (Alt+Enter), as it would just become a black square in the middle of the screen, but killing the game and restarting would launch the game in windowed and it would work.
In the settings, keeping it set to windowed but setting the game to the native resolution essentially made the game behave as if it was in borderless window, without actually being in borderless window or fullscreen.
Every now and then, the game would freeze for a couple of seconds, come back for a second, freeze for a second, then go back to normal. I'm not sure if it's server lag, but other people seem to be unaffected, so it could be a Proton/Linux issue or my PC. It doesn't happen very often (every could of hours or so), there doesn't seem to be a pattern, and it's not super obnoxious.
With my hardware, I have most everything set to medium (with stuff like AA and shaders higher for pretification and view distance for gameplay) and using XeSS set to performance (XeSS looked the best for me in this game, with the least artifacting, but YMMV).
Terrible performance, even on low with a lower resolution (like 40 FPS with frequent drops terrible).
DXVK_ASYNC=1 gamemoderun %command%
I played the original fine, but this version's performance is terrible.
Switched to the public-beta - Pulic Beta beta branch for the native Linux version
- Enabling fullscreen didn't actually make it fullscreen until the game was restarted
- If you enable fullscreen, it still starts up windowed, then goes into fullscreen once loaded. The issue for me is that the window always opened on the wrong monitor, so I either had to move the window to the correct monitor before it finished loading, or use a global shortcut to move the current window to a different monitor
Without the Public Beta branch (or potentially force-enabling Proton which Steam didn't do for me, although untested by me) you receive a Fail to find launcher.sh error
