Wiggity
Published
Game started up and played great on the first try. I actually didn’t expect it to work because of the “Borked” status here (which is generally the case, and almost always due to EAC or something similar). I noticed that almost every single person who hadn’t been able to play it was running a Nvidia GPU. The one guy said he was able to play it on Arch, but with lower frames. I didn’t actually check my frame rate, but it was at least 30-40 because there was no noticeable hitching or anything - the game played relatively smooth. A buddy I was playing with was on Windows and was getting 30-40 frames. Single/multiplayer worked great for a good 20 hours or so this weekend.
Game started up and played great on the first try. I actually didn't expect it to work because of the "Borked" status here (which is generally the case, and almost always due to EAC or something similar). I noticed that almost every single person who hadn't been able to play it was running a Nvidia GPU. The one guy said he was able to play it on Arch, but with lower frames. I didn't actually check my frame rate, but it was at least 30-40 because there was no noticeable hitching or anything - the game played relatively smooth. A buddy I was playing with was on Windows and was getting 30-40 frames. Single/multiplayer worked great for a good 20 hours or so this weekend.
Same freeze as others, tried -windowed and -windowed w 1024
-windowed / -windowed w 1024
Tried starting the game under Proton 7.0-1 and GE-Proton7-14. The -windowed settings took effect while using GE, but didn't seem to work under normal Proton. For instance, when using normal Proton and the -windowed flag (and later the w 1024 flags), my game still started fullscreen @ 1080p.
In all cases, the game would freeze after clicking the first button for character selection (something like "GOT IT"). I'm using the Pop!_OS tiling as well, so I tried this with tiling on and off. Game is currently unplayable for me.
