InnerSpace
Published
Stability issues maybe due to my current setup. Noticed it with other game client using default proton. (Kingdom Come: Deliverance.)
1 hangup needing to send kill signal to steam, 1 CTD of game client causing steam to freeze needing to send a kill signal to steam.
Warning: Uses EasyAntiCheat!
Enabling MTU probing via terminal:
create and and append the file with the configuration line
$ sudo cat > /etc/sysctl.d/mtu.conf
net.ipv4.tcp_mtu_probing = 1
cancel the operation ctrl+c
load the config file $ sudo sysctl --load=mtu.con
net.ipv4.tcp_mtu_probing = 1 entails enabling the detection of the MTU for a network connection when a black hole connection is detected so its off by default with an exception. This poses a minor security issue to me.
Runs wthout issues
- Proton 9.0-1.
- Controller eSwapX Pro (AUR: xone-dkms-git), buttons/sticks/rumble work as intended.
Runs flawleslly on my setup. This is a great hidden, albeit difficult, gem
As of 27/04/23 it doesn't have options to rebind keys but does come with alternate bindings predefined, e.g.: super powre on Middle mouse + Shift.
used a 8Bitdo Ultimate in BT mode which has a Nintendo layout to rebind the controlls in game. I did so succesfully.
UI scaling is slightly small for the screen size of the Deck.
After >1h of prolonged play minor framedrops.
Framedrops are less worse than around june 2022. The performance has improved over 1 year of patches.
Requires above average tinkering but I hope this will help others as well. Therefore: YES!
Downloaded large aware adress patch (4GB patch)
P.S.: my steamlibrary resides in different location. Note that the proton wineprefixes still reside in ~./steam
WINEPREFIX="/data/SteamLibrary/steamapps/compatdata/2100/pfx" /home/**user**/.steam/steam/steamapps/common/Proton\ 8.0/dist/bin/wine /home/**user**/Downloads/Large\ Address\ Aware.exe
Installed the unlimited patch with minimods. This requires you to symlink the media folder in mm to mm_root
ln -s /data/SteamLibrary/steamapps/common/Dark\ Messiah\ Might\ and\ Magic\ Single\ Player/mm/media/ /data/SteamLibrary/steamapps/common/Dark\ Messiah\ Might\ and\ Magic\ Single\ Player/mm_root
Will create na imprint of partial game client on the black bar right side. Fixed by switching to appropriate aspect ratio: 4:3 to 16:9
Amazing this runs with proton and how flexible the wineprefixes are. :) Childhood favorite game.
It is recommended to get about knowledge wineprefixes. In theory you could use my terminal commands, but i encourage understanding what it does. I use the games pfx for consistency. This never let me down. Can be used in other games as well. I have used this method to mod games like STALKER SoC, CS, CoP extensively.
Runs flawlessly on highest graphical settings with my setup with current recommended default Proton version: 8.0.4
One of the very few games I haven't tinkered with. Kuddo's to the dev. As of this report game version 0.9 is released. Game is EA, but at the price point well worth the spend compared to amount of content.
Single Player works flawless out of the box.
Haven't tried Multiplayer yet, will update once played.
Cannot recommend due to full system lockups playing under Dx12 since you can only get out by hard resetting the PC.
%command% --use-d3d11
Dx12 is the default API. Switching to Dx11 lowers graphical quality.
The camera wouldn't move in game in Dx12. The symptoms are best describe as the cursor sticking to the center of the screen. You can move out of the center but it snaps back. Also, the sensitivity settings are ridiculously high. Have to put it all the way down to 0.07 out 20.
Full system lockups within 10 to 90 minutes of client uptime. These lockups didnt leave any trace in journalctl. Forced to Dx11 gave me a stable 120 minute play session. I have tried many workarounds: GE-Proton, attempting troubleshooting fixes on ArchWiki and using a couple kernel parameters from random thread (which i wont list because they don't work and are irrelevant.) Did not try the upstream AMD drivers. These cause FPS losses from 120 to 40 in Monster Hunter World.
I experience the same issue with Monster Hunter: World. I believe this to be a general issue with the cominbation of Dx12 API + Proton + an AMD GPU. I have had an RTX2080Ti in place of the 7800XT. I didn't have any issues except performance loss with the RTX2080Ti compared to the 7800XT
Models can stretch out, rapidly switching weapons causes the animations to glitch out. Sometimes keyboard inputs seem not to be registered.
DXVK_HDR=1 gamescope -w 2560 -h 1440 -r 160 -f --hdr-enabled --force-grab-cursor --adaptive-sync %command%
Using gamescope on a multihead setup to prevent the hardware cursor staying in image and leaving the screen --force-grab-cursor argument is required.
Quoted from hero's contribution prior: "Occasionally the framerate will get into a bad state where every few frames are long (visible via mango) and flickery." I have the same issue.
Without HDR support it runs as described above. Flickering image issue is annoying and doesn't seem tied to HDR being abled. Haven't found a solution yet. Framerate is usually at least 60 FPS. The image flickering can be a dealbreaker for playing this game for prolonged time. Marked this report as not recommended for non-tinkering users to warn for the flickering image issue.
Performs better than my last contribution. Runs very well on my setup. Beautiful graphics and good framerate (>60)
See my earlier contribution about tinker steps used.
In my earlier contribution i spoke about screen flickering. In my case with and AMD Card the solution was to Turn off "Dynamic Resolution Scaling" and only use AMD FSR3 upscaling. This also improved general percieved FPS and frame stabilty.
I also noticed that the Dynamic resolution scaling settings back from 60 to 20 would make the flickering less intense but not remove it.
See earlier report. In gamescope with multihead setup capturing mouse argument is required.
Dynamic Resolution and upscaling settings used:
Dynamic Resolution Scaling: Off
Anti Aliasing: greyed out unavailable
Upscale Method: AMD FSR 3
Upscale Quality: Quality
Frame Generation: AMD FSR 3 Frame Generation
Artifacting causes degredation in gameplay value. The game is playable. But the artifacting is enough to put me off.
Will have heavy artifacting on UI icons and stretched twitching textures.
I looked at a modified dinput8.dll. This slightly helps / does not help. I am not so sure since the acceleration is janky/random and seems to appear the most when streaming textures and having slight stutter, or appears at random turning a corner.
ME1/ME2: Developers of this remaster weren't bothered to remove the ridiculous mouse acceleration behavior of the original. This is not a Proton issue.
ME1 stutters occasionally when streaming in textures.
Forced Proton 8.0.4. In reports before this 4 months 7.0.6 was recommended. This didn't work. EA-link messed up and the game wouldn't boot.
At the moment 8.0.4 is the default version as of this report. Due to issues with EA-link I have deliberately forced this version to account for future updates, and when this report is no longer relevant.
I looked at the ME3Tweaks Mod Manger. There are mods for ME1/ME2 that remove the mouse acceleration. But of course, it must be some specific weird mod manager. This will unpack within the wineprefix of Mass Effect. But it threw me an error wanting to make a directory. I couldn't be bothered to solve this, given the issue is relatively benign. If you'd like to try yourself the syntax of doing this is:
WINEPREFIX="steam-proton-gamepfx-directory" steam-proton-directory location-ME3Tweaks.exe
WINEPREFIX="~/.steam/steam/steamapps/compatdata/1328670/pfx" ~/.steam/steam/steamapps/common/Proton\ 8.0/dist/wine /Downloads/ME3Tweaks\ Mod\ Manager
Autofill the last line to match the build.
ME3 not thoroughly tested. They run out of the box with Proton 8.0.4
Works great without tinkering, nothing should stop you from playing this game right away.
As of now this game particular has issues syncing to steam cloud. It will fail to upload the save file right after closing the game. This can be worked around by waiting >10 minutes and retrying sync.
After 3h session some framedrops. They were minor and didn't impair gameplay in my opinion.
Game supports ful in-game key-rebinding <3
Runs flawless without any tinkering.
Amazing job of the dev putting out such a high quality solid running game.
No battery life review. Majority of playtime connected to a wall outlet.
Amazing job of the dev putting out such a high quality and great running game.
Heavy artifacting on icons in menu's. Also causing textures to stretch and glitch during gameplay.
Minor framedrops after loading in, will resolve within a minute.
This game's a throwback to Shadowgrounds with roguelite twist. It's a nice satisfying shmup and has a reasonable difficulty curve.
Developer has reacted to bug report in steam forums. See post for details
gamemoderun %command% -d3d12
I had one instance where the whole audio stream would fade out and in repeatably, not reproducable and was fixed with restarting the game.
With FSR3.1. on I have stable > 60 FPS but in dark areas specles of white pixels come and go. Doesn't affect gameplay and doesn't bother me too much.
The input is very laggy and floaty out of the box. When i set the launch commands with FSR on balanced the framerate number and stability improved and the lag was bought way down but still slightly present.
I've modded the game. I tweaked the aforementioned file as well as Engine.ini in the same folder. This caused my game to break and crash with a UE5 error report. Thereafter the mod "Project Itemization" broke and uninstalling the game made the game load again but my save file was corrupt.
I mean to say: be veeeeeeery careful editing config files and installing mods. It can break the game and saves.
This game doesn't run well out of the box. Forcing Dx12 is required, gamemoderun helped. I am able to play on the graphics settings profile 'high' With FSR 3.1 on balanced and FSR3.1 checkbox marked enabled
The game will freeze up and needs to be forced closed at every shader warm up attempt on boot.
It will toggle a line in /steam/steamapps/compatdata/1643320/pfx/drive_c/users/steamuser/AppData/Local/Stalker2/Saved/Config/Windows/Game.ini to false.
[/Script/Stalker2.OptimizationSettings]bPSOWarmupStarted=False
Then the game loads with a warning it will skip the shader warm up which can be clicked ok where as the game loads to the main menu.
When you close the game this time the line above will turn to True again. At this time I don't attempt to revoke write rights to this file as messing with these files caused my game to irrepairibly crash and corrupt my save file because mods can't be used anymore before the shader warm up. So try this at your own risk.
I've had a main quest trigger break and had to reload before the last quest trigger to fix it. This caused me to lose 3 hours of gameplay due to me raiding stashes and doing side quests.
Main quest step: "Visit the old mill" (Garbage main quest step). This doesn't spoil anything and can't really direct you in the game except when you go googling this.
Use graphical improvement mods at your own risk. They can modify configuration files in the proton prefix that could theorethically irrepairibly break your game.
Runs very smooth, but strains my GPU for it.
summary:
No tweaking done, it wasn't needed. Didn't notice any issues regarding proton.
unrelated issues:
- Rebinding Move Forward will cause an issue with the boat. Accelerated does not adhere the rebound move forward key.
- Hard locked the game once when I opened the menu and moved my mouse from top to bottom over the first 8 tutorial listings.
According to developer the game is released earlier in Early Acces because of the fanbase requesting for it. It runs as expected compared to people with a Windows system. (for example SplattercatGaming's review on this game). This means in quiet area's >100 FPS but when it gets busy it can go < 60 FPS but not lower than 30 FPS. This is most likely due to lack of optimization and is not a Proton issue.
In this specific case I find it acceptable that it runs < 60 FPS in intense situations due to the state of this Early Access. The game is playable without other issues with Proton for my setup. Not recommended because of the state of the game at the moment.
Does not launch with proton 8.03.
Switching to Proton-Expirmental or GE-Proton-8.11 fix this issue.
Runs very well on my hardware without adjustment.
Menu music cackles occasionally. the audio during gameplay is flawless.
in 4h of playtime saw some texture pop in during the first tutorial mission.
It artifacts when booting flashing a two thirds high and full screen wide window that eventually full screens.
I prefer rebinding WASD to ESDF. There is a hidden keybind for default bind F (melee). Pressing RMB + F = swap weapon. Therefore when in aim mode and move left you will swap weapon with every time F is pressed.
Seen a lot of reports about frequent crashes every 2 hours due to uncapped framerate. I have not experienced those. I didn't modify configuration and the the time Proton is version 8.0.4
I would not recommend copy pasting any of the modifications (Proton-GE, Mangohud) in earlier reports when you are on a full AMD CPU + GPU only if you have to due to performance.
First try out playing on an unmodified game client. Proton versions are on a rolling release and these issues might be solved in these versions.
At most this game loads into the menu. But crashes on hitting new game/continue.
Switched various proton versions.
1. 20240917 Proton Experimental
- Crashes with steam overlay on, turn it off.
- Switched to Proton Experimental. Now getting past the Seizure warning.
- Still crashes on loading after pressing continue on main menu.
2. Hotfix 2.1 @ Proton 9.0.2.
- After patch gets stuck on Warning: Risk of seizure screen. needing to stop the game.
- Restart of steam fixed it
- Issues as described under point 6.
3. Any Proton version
- Instantly crashes on epilepsy warning with steam overlay turned on.
4. Proton 9.0.2
- Crashes with steam overlay on, turn it off.
- Popup crash sender utility during opening cinematic. If you dont click it the opening cinematic keeps running to the end. End of cinematic shows "Failed to connect to game, Enter to continue" error. When hitting enter shows a black screen SIGNED IN AS USER and will freeze there indefinitely
- This behavior repeats
5. Proton GE 9-13
- Crashes with steam overlay turned off
- Hangs on running. Game doesn't start.
- Game starts after system reboot
- Hangs on warming: risk of seizure force close needed, no crash handler is shown.
6. 20240910 Proton Experimental
- Crashes with steam overlay on, turn it off.
- Popup crash sender utility during opening cinematic. If you dont click it the opening cinematic keeps running to the end. End of cinematic shows "Failed to connect to game, Enter to continue" error. When hitting enter shows a black screen SIGNED IN AS USER and will freeze there indefinitely
- This behavior repeats
7. Switched back to Proton 9.0.2
- Turned off Crossplay after reading on steam community forum FAQ that PS5 players have a lot of connectivity issues.
- Crashes persist
8. Switched back to Proton 8.0.5
- Crashes with steam overlay on, turn it off.
- Crossplay still turned off
- Steam crashes on the install script "launching"
9. Switched back to Proton 9.0.2
- Crashes with steam overlay on, turn it off.
- Crossplay still turned off
- Pressing continue reveals the "loading" screen and starts the crash handler unable to proceed and force close the game.
- Restart steam, game finished install script but hangs and crashes on Epilepsy warning.
10. Windows comparison
- I am in the unfortunate but fortunate position to dualboot Win10
- Game launches and plays flawlessy. Hardware issue ruled out.
- Rerolled to Arch and launched the game on Proton 9.0.2.
- Hit continue (played 60 minutes on Windows).
- Game instantly crashes when "Loading resources" appear.
Concluding:
The game for me might have issues with connecting to EAC and/or EPIC game services and translates this into crashes. I noticed that my system doesn't spin up and seems to go under load at all when loading as it does in Windows supporting the theory. It might fail right away at a EAC/EPIC handshake and not even begin loading resources when you hit continue. This might also explain why on New Game playing the cinematic it does do this in reverse and brings the system under load, meaning it loads recources first but then fails connecting and starts the crash handl
Runs flawlessly on my setup with Proton 9.0.3
Didn't need to tinker, runs > 100 FPS right out of the box. Very stable, no issues found.
