Juniorissimo
Published
Game runs fine out of the box
Some frame drops during gameplay - IIRC Windows has/had the same problem
If you are running on a Ultra Widescreen resolution you'll need to change the executable with an HeX editor or download an already patched version. (https://steamcommunity.com/app/752590/discussions/0/3264459260612219759/)
I also disabled fringe and MotionBlur in the "ENGINESETTINGS" to get rid of blurring effect on the sides. (you can find this file in ".steam/steam/steamapps/compatdata/752590/pfx/drive_c/users/steamuser/Documents/My Games/A Plague Tale Innocence/"
Download and play
Stable 100FPS (sync on) with everything maxxed out on 3440x1440
A fun little co-op experience.
Trees have graphical artifacts (leaves on trees flicker)
While loading scenes the frames can drop quite a bit / game stutters
Except for the occasional stutter/frame drop and weird tree graphical glitches/artifacts the game plays fine.
Game will not get past splash screen
No version I tried:
- Proton 8.0-5
- Proton 7.0-6
- Proton Experimental
- Proton 9.0-2
- GE-Proton 9-11
- GE-Proton 9-13
- GE-Proton 7-49
gets pasted the splash screen. If I switch between versions (eg. experimental, game closes en then choose 8.0-5 it will get past it but the game will crash). Installed VCRedist seperatly as suggested on "https://aom.arkanosis.net/linux/" but nothing will get past. Tried it on x11 where it booted once on the main menu. Closed the game and restarted it and it was back to 0, nothing would bring it back to the main menu. Saddly unplayable in its current state.
Running on the latest mesa-git did not work. Needed to remove and install the default mesa drivers. After refreshing steam (steam --reset) and reinstalling all proton versions it started to work.. played a couple of hours now without any major problems.
Engine changes
Location: $USERNAME/.local/share/Steam/steamapps/compatdata/19680/pfx/drive_c/users/steamuser/My Documents/My Games/Alice Madness Returns/AliceGame/Config/AliceEngine.ini
PhysXGpuHeapSize=1024
PhysxMeshCacheSize=16
bSmoothFrameRate=True
MinSmoothedFrameRate=62
MaxSmoothedFrameRate=122
PoolSize=140
Location: $USERNAME/.local/share/Steam/steamapps/compatdata/19680/pfx/drive_c/users/steamuser/My Documents/My Games/Alice Madness Returns/AliceGame/Config/AliceInput.ini
bEnableMouseSmoothing=False
Mouse Sensitivity need to be on lowest + disblae bEnableMouseSmoothing in AliceInput.ini
depending on hardware set Physx on lower settings
Native wont start - used proton 7+ and experimental with no problems
Games work better with Proton, Native crashes after couple minutes of playtime
When changing from native to proton saved games are gone (in my case at least). During usage of proton I had 0 troubles.
Texture streaming slow, fixed with "-DisableTexturePool" launch option
Microstutters during gameplay with texture streaming, fixed with "-DisableTexturePool" launch option
Without disabling Esync and Fsync the game has blurry textures
-nostartupmovies
Edit paramter 'bForceNoMovies=False' to 'bForceNoMovies=True' in both StormPCCookedEngine.ini and StormEngine.ini.
Files are located in your steamfolder > compatdata/501590/pfx/drive_c/users/steamuser/My Documents/My Games/Bulletstorm Full Clip Edition/StormGame/Config/
after loading save audio is gone until a reload
Plays out of the box
Occasional stutter during cutscenes / loading areas
when using an ultra-widescreen monitor you might want to change the executable with an HeX editor:
- Search for F6 41 2C 01 4C, and replace with F6 41 2C 00 4C to remove pillarboxes
- Search for 35 FA 0E 3C A4, and replace with 35 FA 3E 3C A4 for ultra-widescreen
Great little cosmic horror adventure
In larger areas frames can drop significant. Also whilst loading areas it can drop. Majority of game plays well over 100FPS
Around Chapter 12 of the game some cutscenes were not able to play. I got an "Test image" for testing screens. But then again the cutscenes of the final did play again properly again. (Have the MF git)
Except for the last couple of cutscenes and some FPS drops in certain areas. The game is perfectly playable out of the box.
RADV_PERFTEST=rt mangohud %command%
Even with RT enabled on max settings the game still ran pretty well (given no Nvidia Physx/RT card) 60+ FPS
PROTON_NO_ESYNC=1 RADV_PERFTEST=rt mangohud %command% +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1
Unable to play with current MESA / RADV drivers. no matter what settings I use (Low + no RT or Ultra Nightmare + RT) the frames are stuck on 10-30FPS from loading screen to game
unplayable due to low frame rate
RADV_PERFTEST=rt VKD3D_CONFIG=dxr11 %command%
This could be due to bad mesa drivers where GPU not fully supported yet
Raytracing works but isn't stable. When starting the game one day it will load with RTAO enabled and the other day it won't be able to load the game. Removing the "RADV_PERFTEST=rt VKD3D_CONFIG=dxr11" form launching runs the game only with AO and runs with 180ish FPS
Works out of the box, no major issues
Stutters / framedrops. Vsyncs helps
No problem with the DirectInput dll which caused low FPS on a Windows installation. Great game, great experience!
When loading new area when game makes auto save taskbar gets shown for a second. Nothing major.
Installs unable to start game
Game installs without problems. Opening up the game shows a "loading screen" for a second before closing.
When removing all movies from the game (renamed extension to .bak) ".local/share/Steam/steamapps/common/Halo Infinite/videos/". The game is able to boot (after a while) to the main screen.
When the main screen loads the driver/display manager crashes. You can still hear background music. Need to restart X or restart your machine to resume anything in your session.
error messages in log file (proton):
- ole:CoUninitialize Mismatched CoUninitialize
- seh:dispatch_exception Fatal EXCEPTION_WINE_CXX_EXCEPTION exception (code=e06d7363) raised
- winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
- ntdll:RtlpWaitForCriticalSection section 000000002CD30078 "?" wait timed out in thread 0184, blocked by 0134, retrying (60 sec)
- d3d12_command_queue_bind_sparse: Failed to submit signal, vr -4.
- d3d12_command_queue_bind_sparse: Failed to perform sparse binding, vr 4.
Finally, after a long wait Halo Infinite is playable
After playing a couple of MP games I did not experience any major problems
It still has some issues but is playable for the SP
textures are of lower resolution (texture streaming?) then i have seen on Windows running the same settings
Loading Co-oP campaign maps in the "overworld" loading times can take up minutes. We found out that when playing a Youtube "AV1" video in the background we got it reliably down to 44-55 seconds
In the overworld during Co-oP everyting on Ultra we sometimes got a crash during a transition point / checkpoint.
Multiplayer itself plays fine, no real issues to report there Co-op has some troubles that are also linked to the SP campaign
Multiplayer ran fine already. Recently completed the campaign in Co-op mode where had some crashes but nothing major. Some instances one of us was unable to spend upgrade points for the mjolnir armor and the tacmap loading can take a while. For the rest the gameplay felt fluid were able to complete the game.
Taskbar visible when boot. Need to disable/re-enable fullscreen in settings menu.
Perfect OOB experience!
Played on new patch (enhanced). Ran everything on "Very High" with RayTracing on "High" no AMD FSR. Game ran nicely between 80-100 (100 capped vsync)
Game plays as intended.
If possible play with a controller, keyboard and mouse aren't the "easiest" to play the game with.
Works great out of the box
On Ultrawide screens you might need to edit the executable with an HeX editor.
For Multiplayer you need to use the following protontricks command: protontricks 2310 win7
When Alt-Tabbing out of the game taskbar keeps visible. Reboot of game required or re-initiate fullscreen in settings menu
To be able to join a Multiplayer Lobby you will need to use winetricks. If not installed on system yet first install winetricks. After that (with the game closed) run "protontricks 2310 win7".
When the command finishes you can start the game and you will be able to join MultiPlayer Lobbies
WINEDLLOVERRIDES="dinput8=n,b" RADV_PERFTEST=rt VKD3D_CONFIG="dxr,dxr11" VKD3D_FEATURE_LEVEL="12_2" mangohud %command%
To enable Raytracing you need to go to the game folder locatoin (eg. /home//.local/share/Steam/steamapps/common/RESIDENT EVIL 4 BIOHAZARD RE4/) and edit the local_config.ini file.
AppRayTraceOnOff=2 (1 for default, 2 for high ray tracing settings)
AppRayTraceResolution=0
Game plays without any problems at a steady 100FPS (vsync on 100) without any problems with all settings maxed out including Raytracing on max settings with 3440x1440 resolution.
I added the WINEDLLOVERRIDES="dinput8=n,b" to load RE framework mod to fix/change FOV which also worked without a hitch.
Exiting the game crashes it
Using GE-Proton fixes the cutscenes. RT functionality did not work (unable to set the graphics setting)
Unable to play the game on any version of Proton or GE
Tried all different Proton versions (Experimental, 7-x, GE, etc.) but was unable to get past the loading screens. Tried to force dx11 and dx12 but nothing helped to get past starting the game
Plays perfectly out of the box
Performance is stable - some FPS stutters when loading in new areas, nothing major.
RADV_PERFTEST=rt mangohud %command%
On AMD 7000 series cards mesa-git drivers are necessary but after usingn those I got 100+FPS throughout with everyting on Ultra + RT on 3440x1440 - Ingame benchmark gave an average of 120fps
Unable to get past intro movies (PROTON_USE_WINED3D=1 %command% -dx11) without launch command game won't start at all
Tried to change launch options to run it in DX11 mode but keeps giving errors. When game starts it craches when the intro movies start playing.
-dx11
After a complete Distro change (Arch to Debian) and adding the dx11 launch option the game is able to start. Ran multiple benchmarks FPS is noticably lower (10-25FPS) then Windows on same settings with more random lag spikes.
