raven
Published
Worked fine for me (2.6 hours in). Ran a bit hot for such a simple game, but I doubt that's Proton-specific.
Seems mostly playable, and I gather it suffers from similar surprising sluggishness issues on Windows.
Strange grey rectangles, I think it's a misrendering of smoke particles. One place where it says something like "missingfont3" instead of 3 in a special font, I guess.
Keyboard input would 'stick' and lag for several seconds - turning off key-repeat in Gnome settings fixed this.
Feels like 20-30fps - I would expect better from a 3060 on a game of this age.
It seems like the amount of artifacts gradually increases and then at some point the whole game freezes and requires a hard reboot to exit. Can play for about 20-30 minutes 'safely'.
One very minor bug, during startup animations Ubuntu says the game has stopped responding. Just waiting a few seconds makes the popup go away. (Clicking "wait" is worse than waiting, the popup comes back a few seconds later!)
Couldn't start with any Proton version
Tried GE, experimental, and a couple of 8 and 9 versions that had apparently worked for other people. Experimental did an "epic games thing has crashed do you want to send a bug report" and with every other version it just spun for a while then didn't even open a window.
"No suitable D3D12 adapter found"
Couldn't get the game to start up at all. I tried various combinations of the launch options suggested by others, and I tried proton experimental and proton 9.0-2. Every try resulted in the "No suitable D3D12 adapter found" error. I'm guessing having a 3060 and integrated graphics in the weird "hybrid mode" setup is the problem. (Or rather, the game having stupid requirements is the problem, but the hybrid mode is probably triggering it.)
eval $(echo "gamemoderun %command%" | sed "s|2KLauncher/LauncherPatcher\.exe|MidnightSuns/Binaries/Win64/MidnightSuns-Win64-Shipping.exe|")
On my machine it will only start up if GameUserSettings.ini is deleted. If it's there (even with the default values) then startup plays the Unreal Engine logo, half a second of some circle-sun-thing, then crashes. With the file deleted, it plays the Unreal Engine logo, half a second of some circle-thing, then the nvidia logo, and goes on to launch the game. (I'm guessing what's happening is something wrong with that video and the error behavior differs if there's no config file.)
Configuring to DX11/DX12, windowed/fullscreen/different resolutions all make no difference to this crash, the only thing that seems to work is deleting that ini file.
With the default settings (low everything, 1920x1200) it's about 10fps. When I turn it to 1600x900 it becomes reasonably smooth.
Crashes every couple of battles, takes Steam down with it. This sort of thing is pretty common with this NVidia/Intel chipset/drivers combination unfortunately.
Seems like it thought it was fullscreen but was only 3/4 screen. I was playing via steam link anyway so I didn't bother trying to fix it, because it was fullscreen on the receiving device.
With the default proton version (9.0.3 right now) the first time I tried to start it it got to the frozenbyte logo then froze (lol), and further attempts to restart didn't start at all. After switching to GE it worked.
Wouldn't start for me
gamemoderun %command%
Tried GE9-15, GE8-25, Experimental and regular 9, with or without gamemoderun %command%, all to no avail. It spent ages doing the vulcan shaders the first time, but then just flickered black for a moment and exited. Every subsequent try just did nothing for 4-5 seconds, flickered black, then exited.
Worked fine, no problems at all (except that it uses shift and tab as controls, triggering the Steam menu, which isn't Proton-related.)
Without setting an explicit Proton version it apparently tried to run a Linux-native version which resulted in it couldn't find its own binary. Manually setting a Proton version made it do some additional downloading then it worked fine.
Ran fine, no problems.
I even accidentally left it running all day, due to the long time it took on first run preparing the shaders - it got backgrounded when my lock screen came on, and came right back up still working when I unlocked the screen hours later.
Running with my defaults (proton experimental) the game crashed and froze frequently. After setting it to force using Proton 7.0-6, it runs smoothly.
