EngineGears
Published
Excellent in VR but REQUIRES GE-Proton6-26
VR REQUIRES GE 6-26 See: https://github.com/GloriousEggroll/proton-ge-custom/pull/106
They include a native Linux binary in the windows install which works well and might work well for VR soon.. but for the time being running via GE-Proton8-26 is "110%". It even had no issues supporting my Logitech Speed Force Wireless for Wii wheel - first time I've experienced good force feedback!
Some recent changes I made which have vastly imrpoved performance:
See: https://forums.developer.nvidia.com/t/enabling-gsp-makes-steamvr-unplayable-on-rtx-3090ti/298694 for performance.
Using tmpfs for Steam's log dir ( https://github.com/ValveSoftware/SteamVR-for-Linux/issues/631#issuecomment-2114253901)
Note: I'm now running a 3090 and 64GB RAM
Works out of the box.
Make sure you go back in time... also look into the settings for other locomotion options like hand swing to move around.
PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 %command% #Note: due to dual GPUs - want to use my dedicated Nvidia GPU
Protontricks uses winetricks. An older version of winetricks will install older DLL versions!
UPGRADE WINETRICKS:
sudo winetricks --self-update
Install d3dcompiler_47 DLL:
protontricks 307960 d3dcompiler_47
If you've already installed an old dll it may be easiest to install the new dll in another game and copy it over. Dll's are found in:
~/.steam/debian-installation/steamapps/compatdata/307960/pfx/drive_c/windows/system32/
I'm shocked I havent' come across the need to use a newer winetricks! My upgraded version is dated 20220411 whereas the one that didn't work was a year or two older. The new d3dcompiler_47.dll file is much bigger at 4.2MB. see https://github.com/ValveSoftware/Proton/issues/3106
Launch options:
taskset -c 10-11 %command%
#will only use the last core on AMD 6 core 12 processor cpu
from Linux shell:
sudo winetricks --self-update
protontricks 307960 d3dcompiler_47
- if you did the protontricks command with an old winetricks then delete the old compat folder for the game, start the game to regenerate a new 307960 folder then run the protontricks command again. Compat folder is at ~/.steam/debian-installation/steamapps/compatdata/307960
- Turn OFF reprojection to avoid crashing steamvr during heavy smoke effects ( fire tank while zooming, crash plane etc ). To do this run SteamVR and go to settings->video->perApplication video settings. Choose IL2 Sturmovik and then set Use Legacy Reprojection Mode to ON
- I use taskset -c 4-7 %command% for SteamVR's Launch Options.
More performance:
- You can also turn off compositing on your desktop ( for KDE use Alt-Shift-F12 )
- pkill vrwebhelper
@kylemontanaro - installing the d3dcompiler should solve your exact error!
add
"enableLinuxVulkanAsync" : false,
to the "steamvr" section of ~/.steam/debian-installation/config/steamvr.vrsettings
as well as (or instead of) turning off reprojection as I mentioned in my previous report.
don't forget to protontricks 307960 d3dcompiler_47 at the very least as well.
Works
I did most of my testing with forced Proton experimental and just did a quick test with no tinkering.
in local files dir ( next to the game exe ) added dxvk.conf file containing: 'dxgi.nvapiHack = False' to ignore my CPU's built in graphics and use my dedicated GPU.
On startup it requires a EA account login which wasn't straightforward to enter. You may get a black screen with only the word "close" in the top right with no easy way to do so. It also failed to toggle back to VR ( SteamVR failed which also required a restart of the game )
Moving the mouse around would highlight menus but no mouse pointer was visible. Sometimes it listed controller buttons which didn't exist ( no button 11 ?) so forced to use keyboard.
Recognized my flight stick without issue.. was easy to configure within the game.
Works perfectly out of the box. I've been using an older Proton version by default. It could work fine with a newer version as well.
My AMD CPU graphics were interfereing with my dedicated GPU. Browse local files ( where WW1.exe etc are located ) and added a dxvk.conf file containing the line:
dxgi.nvapiHack = False
Hints: In the WW1_dxgi.log file I was seeing "DXGI: NvAPI workaround enabled, reporting AMD GPU" Alternative solution: run steam via:
export DXVK_FILTER_DEVICE_NAME="NVIDIA"; steam
Where "NVIDIA" (or "3060ti" etc) is unique to a single card as found via command: vulkaninfo
Without my fix an invisible window would take over my desktop. I could switch away using alt-tab. Additional resources: https://github.com/doitsujin/dxvk/wiki/Driver-support
