Gerarderloper
Published
Proton-5.9-GE-8-ST
Battleye version does not work.
Proton-TKG builds do not work for me, only ProtonGE.
Does not launch, many solutions attempted. (AMDGPU)
For NVIDIA users that want to get this to load, I suggest using proton5.0-10 and nothing above as wmp11 and xact will not install their dll's correctly otherwise.
As for AMD users, even when doing this the issue remains, I've tried several proton versions and ge to no avail, proton logs are not particularly helpful for this game.
Works however as people have pointed out you need -noLauncher to start the game, and when joining a MP server for first time it will prompt to install anticheat software which installs fine, you then need to relaunch game and join server again. However it will crash after 15minutes, hopefully that can be fixed at some point.
Also this works fine with esync from my testing, and to resolve the mouse panning to right lock issue if you get that, is set display to fullscreen window (only happens on fullscreen).
Typical gamer needs to know howto rename files since launcher does not work.
The launcher will not work, must renamed arma_64.exe and replace launcher exe!
Basically can't work.
I tried dotnet48 to get launcher working but it still seems to have issues, maybe something else is needed on top to get it to spin up!
Fixed the crackling with = PULSE_LATENCY_MSEC=90 %COMMAND%
Launcher does not work atm, even with dotnet48.
Use this line in Properties > Set Launch options = PULSE_LATENCY_MSEC=90 %COMMAND% -nolauncher -nosplash - world=empty -skipintro
MP Performance is likely poor compared to Win10 on large MP-BE games!
If I fiddle with Audio options it can cause crackling or persistent helicopter noises. Also my microphone appeared to only work sometimes (had often had a disabled mic icon on screen).
I had to execute winecfg on the prefix and tick Automatic Capture Mouse otherwise the cursor would go onto my Display-2 and cause issues.
Multiplayer showed significant performance hit as more people joined the BattlEye 20+ player coop server I was on. I tried fresh prefix and several work around, but I was seeing up to %50 less performance directly compared to Windows10! Not sure of the problem, may only occur on large COOP/Player Servers+Maps...
Sometimes on joining a server I would get these hangups but they went away after a couple tries. Re-creating prefix may help.
BattlEye while works; BUT may be causing significant performance loss when directly compared to Win10. (Dual-booted to compare; the difference is ~%50+ performance loss when run under Linux)
If you directly compare large scale multiplayer gameplay to win10 then you will likely see the alarming issues I've been getting with performance.
Works great NOW: Read my comments on the proton arma3 github issue report about performance issue & possible solutions.
If you switch the audio device in-game, you'll likely need to restart the client or suffer distortions.
protontricks --no-bwrap 107410 winecfg; set fullscreen mouse capture.
Originally I had 24-55fps with frame stutter issue; but switching to kwin-lowlatency and a new arch install with a few other tweaks, I now get 55-90fps. I can't put my finger on the exact fix, but it solved my problem at least.
I had to recreate my prefix and fell back to Proton Experimental because Proton-GE kept freezing up once in-game.
I can't be 100% sure; but I may now be getting better then win10 performance!
echo "%command%" | sed 's/ArmaReforger_BE.exe/ArmaReforgerSteam.exe/' | sh
No Fullscreen options in-game.
Touch and go performance hickups, could be shader caching or alpha nature of game.
Sometimes fidgiting with graphic settings in-game results in a crash.
You need to bypass BattlEye; I used a launch command workaround using sed tool.
LAUNCH OPTIONS used:= echo "%command%" | sed 's/ArmaReforger_BE.exe/ArmaReforgerSteam.exe/' | sh
echo "%command%" | sed 's/ArmaReforger_BE.exe/ArmaReforgerSteam.exe/' | sh
Any other proton version seems to cause foliage and rock flicker/displacement!
Major foliage flicker with any OTHER proton version.
I do not know what other proton versions work but latest versions don't. This foliage object flicker needs to be addressed!
This game will actually run the windows version with proton and perform significantly better then native (also looking slightly better). You need to install DotNet45 or above, and possibly set proton to win7 configuration. Without doing this the game will fail to launch. I found this to be a better option then running Native. Also it may help to install protonfixes into your proton version (refer to github instructions).
Didn't need to disable e/fsync, used DX12 option but DX11 may run better? didn't experience any real issues. I did use latest proton-tkg.
DirectX12 has performance issues. Use DX11
Provided you use DX11, it should run quite well. DX12 had some bad framerate fluctuations.
Just use default Proton6.3-7 atm until Origin-Launcher problems with current Exp/TKG/GE can be figured out.
Only Proton6.3-7 was able to install Origin and execute bfv.exe correctly. Experimental, TKG, GE all had issues with Origin launcher. Perhaps if you wait ultra long period of time they eventually sort themselves out as the origin process was doing work, but I feel that is unacceptable.
It's possible some people are having no issues with Origin-Launcher and Proton Exp/TKG/GE; however I was unable to get them to launch BFV.
Default proton versions gave terrible performance.
TKG or other proton versions other then ProtonGE will result in very low frame rates!
The game has a CTD issue which is aggrevated with higher gfx settings. However it still will very often CTD.
Sometimes the creation of the proton prefix can cause the game to get low 1-3fps.
Deleting the prefix entirely and re-creating it often fixes this issue, or try a different proton version.
Unfortunately this doesn't fix the random CTD issues which is IMO the MAIN issue atm with this game. The CTD produces no error output or log!
May also happen on windows. Could be related to specific graphic settings as lowing them to minimal reduces mid-game CTD but often crashes at match end.
It may be possible to get it to work fine on older proton versions or with specific setting configurations or proton flags. There doesn't appear to be any exact fix for everyones ctd at this time. The LOW FRAMERATE issue however can be fixed by deleting the prefix and trying again, maybe with different proton version. Not sure what triggers it originally.
Proton9 may cause issues. Use a fresh PREFIX folder! DO NOT turn up car reflection quality above Medium or CTD will happen.
PROTON_ENABLE_NVAPI=1 %command%
CTD can happen at times, usually after match.
DO NOT turn up Car Reflection Quality beyond Medium as it will trigger instant CTD within 10 seconds of playing.
Proton8 seems fine when NVAPI is enabled. PROTON_ENABLE_NVAPI=1 Avoid turning up Car Reflection Quality beyond Medium or CTD. AMDGPU users may have a different set of issues. I have everything turned up max except DOF (looks bad) and CarReflections (crashtodesktop) and I get well above 60fps, but you'd expect that with a 4090!
Game no longer works with most recent update, dotnet472 does not fix, running empyrion.exe directly does not work either.
USE Proton Experimental or normal Proton. I could not get GE to work without major performance slow downs and stutters.
Needs FAUDIO
USE Proton Experimental or normal Proton. I could not get GE to work without major performance slow downs and stutters.
Game tries to load but quits out with a runtime error, tested with DXVK 1.5.2 and WineD3D9 AND D9VK enabled, both produce the same result.
Game works fine after I uninstalled and reinstalled it, seems proton forgot to install critical dependencies the first time around.
There is a community patch 1.74 that people may find useful, community patch 1.75+update MAY or MAY NOT work.
Just tested the start of game with default proton DX9 support and it renders everything fine except performance is not very good and gamma cannot be changed. I also tested D9VK but it just renders black screen for the most part, and might even crash your desktop. The game is Dx9.0c so I dunno why D9VK doesn't work (works in Risen 3 btw)
I have tried using dxvk.conf to spoof to AMD but I think this is the way it is by default, also tried nvidia id's and no luck. ATM with this proton version I get 5-6fps and is generally pretty unplayable, something is seriously going wrong for NVIDIA owners with this game. Apparently it works fine with AMD users, however I can't test this as I have no AMD card. There is a github issue report for this game, but no progress there either. Going to label this as borked!
If you work around the club launcher install issue, and use llvm compiler for AMD cards, then you should be fine.
ACO compiler caused white surfaces for Navi2 card. RADV_DEBUG=llvm fixed it.
Outside of proton, (wine) the keyboard inputs would cause game to freeze up.
When looking close to objects my fps halved, disabling winedbg.exe probably solved the issue. You can also try disabling esync.
Rockstar Club Launcher will not install (infinite wait) with newer proton, so you may need to revert back to proton4.11 or 5.0-GE-1, then install the club app, then switch back to newer proton. 'MAY' be related to winedbg.exe which you can disable, or some other wine component.
GTA5 runs fine with e/f-sync for me, however winedbg.exe did need to be disabled and the club launcher was refusing to install correctly on newer proton builds.
Additionally graphical config settings in game will not save until you either start the story, or run the benchmark mode under Graphics setting.
Attempting to save settings prior to doing that resulted in them defaulting, which was frustrating because the game must restart each time.
Also when you run benchmark or save settings, DO NOT interrupt the games reboot process or you risk reverting all your graphics settings etc..
Other then the initial startup delay, it should work with Proton. There may be issues starting with normal Wine however.
PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 %command%
The initial startup took 30seconds or so to happen.
I tested this game with the GOG version and protonGE.
Just avoid excessive mod packs; tweak vanilla setup to run 60+ fps first! Maybe avoid vsync and use DXVK_FRAME_RATE instead.
With VSYNC enabled the mainmenu was frozen(failed to update). Rather odd, not a crash, just failing to updating the display.
Needed to turn on Fullscreen-mouse-capture in winecfg via protontricks! (Valve why is this not default?)
Shadows can cause issues; and be careful of some resource hungry mods. Avoid AIO packs, install mods independently and test or fps drops can be nasty!
DXVK_FRAME_RATE=120 MANGOHUD=1 ENABLE_VKBASALT=1 gamemoderun %command% +exec user.cfg
Using last good release of Optimized_Graphic_Presets (updated version) which is no longer available.
The game is running at 4k with medium+ settings and gets around 10-20fps lower then Windows10 with high+ settings.
At 2160p (4k) my 6800XT does struggle to get above 60fps with medium settings. I could probably squeeze another 10fps if I removed a few things but then it look considerably worse. Compared to Windows10 this game gets around %30 less FPS under Linux, which is quite alright for most people but if you want 4k 80-120fps performance then you need a RTX3090 or above!! That %30 performance loss is felt very hard at 4k, and FSR1.0 on a 4k panel in this game just looks really terrible IMO! It is a shame game never got any engine updates or additions like DLSS2 etc..
Game seems to work well at 4k on my 1080TI (50fps at high settings). HOWEVER you need to enable proton-fixes or run proton-GE which has them enabled. Other then that it seems fine. Maybe we can get proton-fixes mainlined someday but until then you need them.
This game will only load with LOW AND MEDIUM quality setting for NVIDIA 4090 (probably others).
HIGH and EXTREME cause lockup upon loading menu. Possible NVIDIA driver bug or VKD3D bug that.
VKD3D_FEATURE_LEVEL=12_2 VKD3D_CONFIG=dxr11 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 gamemoderun mangohud %command%
user.cfg had to change resolution manually due to 4k detection issue.
Would only detect resolutions on SECOND lower res monitor.
Crashing will occur with Hairworks is enabled.
You need to have correct launch options and also disable hairworks, then you should be for the most part in the green.
This now works flawlessly more or less, I had DX11 mode enabled in my testing. To get this working you need wine6.6+ so I used proton-tkg-6.7 which allowed dotnet452 to be installed. Dotnet452 IS the missing part to get this to work, but it had been broken in pre6.6 wine/proton for whatever reason. After this you can launch game once, if may fail but try again and go into the launchers options screen and enable dx11 mode and whatever else you want (controls here may be finicky, try TAB and arrow keys etc).
This appears to no longer work since recent update.
Tried most tricks including GE. Game just sits at a blank screen for 10seconds then ctd.
EAC appears to work ATM!
I had a issue where Steam Verify failed to detect corrupt files so deleting the game and re-installing fixed the issue.
This works with my current setup and the recent beyond patch however the performance is pretty bad, expect 10-30fps most the time, so a considerable downgrade from OpenGL unfortunately (it now uses Vulkan). Not sure what the issue is, reducing resolution/settings doesn't really help much.
Game crashes when trying to bring up the main menu. It seems to not render correctly. APITRACE was not possible.
You will need to bypass GamesForWindowsLive by using a local account xlive.dll+ini files. This needs to be done even under Windows so isn't Linux specific. GFWL died a long time ago, taking many games with it (especially their Multiplayer features), its a huge tragedy!
If people want the mouse spinning issue fixed then turn off mouse warp in lutris or go into winecfg and untick capture full screen mouse.
This resolves that issue for me except inside crafting you can move mouse to second screen, but that is not a issue since normal playing it stays to primary.
The issue I have atm is the action shortcut keys are not shown just empty circles, probably a fix around for that.
Updated Report:
The game runs reasonably well but needs mouse-warp/full-screen capture turned off or mouse movement issues occur after 20mins, you can do this easily using steamplayprefix scripts (gitlab) and running winecfg -> graphics tab. (note game still has minor mouse issues sometimes, this is a game-bug and not proton)
Second of all, if you try to run this game via Lutris (using the proton prefix etc..) you'll have missing fonts, such as those for quick access bar, so launch from steam!
Requires GOG Risen.exe (rename to Risen2.exe)
https://drive.google.com/file/d/1WVjTqhqoOTrNAVMFxOytV-96kJ7_f5PZ Don't launch via steam, it will auto-delete the exe, use lutris or sppfx protontricks 40390 -q corefonts d3dx9 d3dcompiler_43 binkw32 gdiplus physx tahoma
This works OK'ish default proton dx9 support but if you want the best performance then try (PROTON_USE_D9VK=1 %command%), just keep in mind D9VK can be a bit finicky at start because it needs to cache everything (somewhere) and sometimes that cache can get corrupted. With D9VK you will experience initial stutters in new areas due to caching but once that passes it will run great, even works with reshade tools.
The game crashes with proton after about 15minutes but I did not experience the crashes with lutris wine install. The crashing is appears to be related to proton in specific.
VSYNC will cause fps issues, use dxvk 1.9 fps limiter.
Crashes after 15mins on the dot basically, if proton is used.
Use WineGE with Lutris, no issues after 2hrs of play. But if I use steam+proton it crashes after 15mins all the time.
If you have RADV/MESA and a newer AMD GPU, then your experiences will likely be constant random freezes.
With MESA/RADV ICD Loader I got graphical glitches, but AMDVLK 64 icd loader was fine.
Sometimes autosave can trigger a freeze-up event.
Crashes with Proton often, and also with Wine unfortunately. Originally I thought Wine was ok, but it eventually goes into freeze up mode also.
Game is prone to constant freezing on my 6800XT setup; I've heard that NVIDIA users and SOME other AMD users didn't get freezing; but you REALLY need to put in time to play the game to know if that is a issue, not just load up for 5mins in the tutorial level!
The game runs solid 6+ hrs under Win10 with only 1 crash/freeze.
If you don't have the gamescope HDR crash issue that I've been experiencing, then you should be 100% fine.
Just some mods to improve performance. (not related to CTD)
Exclusive fullscreen needed for HDR
Gamescope needs --force-grab-cursor
I managed to fix most the stutters or latency using some mods.
Unfortunately gamescope with HDR enabled for me causes this very random silence CrashToDesktop issue that I've been completely unable to find a fix. Tried a few different versions of gamescope and env flags without luck.
I think this is working for most people but performance will vary, its a VERY demanding game and if you can't use Frame Gen then you may be stuck at lower graphical settings and resolution. Also I noticed some mods can improve input latency by a large margin when frame-gen is enabled, also reduce stutters for many.
Lots of people can't tell difference between SKSE and SKSE64, SKSE may work but SKSE64 does not because getskseversion does not work in console (simple test). SKSE64 needs a special patch which from what I can tell isn't applied to proton. Possibly because its not mainlined yet... this problem has existed since 64 bit script extenders existed.
DLSS Frame Generation for whatever reason is greyed out and cannot be enabled.
Game has performance issues atm, so I can't really recommend it. DLSS Framegen not working is a bit annoying.
As mentioned by others, this works fine with 4.2-4 however you will notice only specialfx sounds work, music and voice does not work until you install faudio via sppfx OR protontricks scripts. I had an additional issue after this wity crackling and popping which was resolved by using PULSE_LATENCY_MSEC=60 %command% in the launch options section.
Keep in mind if you want to use SKSE64 it will generate a random APPID folder in your $HOME/.steam/steam/steamapps/compatdata directory which means you need to install faudio to that new appid folder (and copy/move ini's also).
This appears to run fine now, however I did once get a false crash in background. There is one cavete' which might affect a select few people, and that is RESHADE does not work under steamplay, it causes the aces.exe to freeze. This is related with DXGI.DLL injector which allows you to run better fsaa and sharpening effects in game since War Thunder has pretty bad options for this.
