square
Published
I was unable to do online play. Also, offline match works fine.
Restarting the game seemed to fix this.
I was unable to do online play. It said I wasn't logged into Steam and wasn't able to contact the servers when my internet connection works fine. I retried connecting to a server multiple times with the same message.
Mostly smooth performance and doesn't crash at all. I say mostly, because when the cinematic view of each kill happens, the fps drops temporarily until the games goes back to normal fps when the cinematic view ends. This tended to be the worst when the slow motion kill happened in first person. Also, sometimes, depending on the direction the camera is pointing in first person, it seems like the shaders break and the game ui, hand and weapon models, and the yellow hue disappears and a blue tint can be seen (may be the base color before the shaders are applied). This disappearance is usually corrected by moving the camera to another direction, typically opposite or 45 degrees left or right of the aforementioned direction. Also, if the game is set to full screen and alt + tab is performed, it seems impossible to get the window back into focus, no matter how many times the window is put into the foreground. This requires the game to be forcefully closed and launched again to be able to interact with it again. Overall, better experience than on Windows unmodded due to lack of crashes.
Opening the options menu either in the main menu or in the exit menu in a loaded level immediately crashes the game. This occurs when no command line options are supplied to the game. This was also tested with the -novid -windowed launch options.
Crashes with unable to read memory error starting a new game.
When I first started the game, I got an error message that my computer/gpu didn't support DX11. So then I launched the game with the following command: PROTON_USE_WINED3D=1 %command% When I then start a new game and select a character, the loading screen occurs and then stops and then a menu noise occurs and the mouse cursor comes up and then a window comes up with the following title without quotes: "Prey.exe has stopped working" with the following contents without outside quotes: "Attempt to read from address 0x0000000000000000 The memory could be "read"" The game persists in a black screen with a movable cursor after the error window is closed and the process has to be killed (i.e. quit and let the dialog show up that says its unresponsive) to close it.
I tried changing every setting to the lowest, reducing resolution to the smallest sized, running in bordered and windowed, turning off vsync and adaptive resolution, and the crash still occurs. I tried running with this launch option: PROTON_USE_WINED3D=1 %command% PROTON_NO_ESYNC=1 DefaultLimitNOFILE=1048576 %command% and it still crashes.
I tested with Proton 5.0-9 and then Proton 4.11-13 with same results.
