UnsupportedShow Details
Unknown
Game reports issue with initializing graphics, I checked if I have everything up to date (including DXVK) but nothing seems to work.
Full error message: Failed to initialize graphics. Make sure you have DirectX 11 installed, have up to date drivers for your graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphics failed
gamemoderun %command%
Use Proton-8 variants to fix dx11 check.
Works perfectly out of the box. Using Meta Quest 3 via ALVR.
I've sent this report mainly because there was a report from someone saying "Make sure you have DirectX 11 installed", that does not make sense because Linux doesn't have DirectX11. What you have is dxvk (on proton) translating Direct3D 11 calls to Vulkan. I've tested the game thoroughly (via ALVR) and everything is working.
Fails with directx11 error if steam VR is running
Tried to use for Dx11 but didn't work if steam vr is running errors with Failed to initialize graphics. Make sure you have DirectX 11 installed, have up to date drivers for your graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphics failed
Other VR games are working fine but the whole ALVR to steam VR thing might be complicating matters.
Runs pretty great with ALVR to stream to a standalone VR headset.
Worked out of the box without any tinkering
I am using a Valve Index with the default SteamVR and the game worked without any issues so far. The only change in the game settings was enabling FSR to get smooth 90 fps.
After a few hours I managed to get it to work on 1.0.4 with the PROTON_USE_WINED3D=1 launch arg.
gamemoderun PROTON_USE_WINED3D=1 %command%
I totally misspelled the arg before my previous report, ignore that one. Runs a little slower, but otherwise works fine now. Previous versions on the game did not require this arg. Might be a nvidia bug.
After 1.0.4 update, game no longer starts. Trying different launch arguments and proton versions has yet to make a difference.
gamemoderun %command%
Attempting to boot the game with SteamVR open will display a window with the following error message: "Failed to initialize graphics. Make sure you have DirectX 11 installed, have up to date drivers for your graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphics failed" Starting the game without SteamVR does not display this error, but also does not display in headset.
No longer works, worked perfectly before 1.0.4
When I start the game, I get just this window, and the game does not proceed to start:
Failed to initialize graphics. Make sure you have DirectX 11 installed, have up to date drivers for your graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphics failed
It worked perfectly on the previous version. I play on Garuda Linux latest kernel via ALVR with steam VR, with my Meta Quest 3.
in SteamTinkerLaunch I have FSR(OpenVR) enabled and I am using vortex mod manager to load mods I am also loading an older version of the game in particular u11.3
just lag sometimes
I am using SteamTinkerLaunch to get Vortex Mod manger working and modding working on version U11.3 of the game so far using SteamTinkerLaunch to mod the game is the best way I've found so far and I recommend it to others who want to mod too. I also recommend you do research into SteamTinkerLaunch https://github.com/sonic2kk/steamtinkerlaunch
Works really well.
The audio was slightly crackling occansionally.
Played on a Valve Index.
I launched through ALVR I am using CoreCTRL to set my power profile as per their documentation. This must be backported if on bookworm
~/.steam/debian-installation/steamapps/common/SteamVR/bin/vrmonitor.sh %command%
Upon initial startup, the IPD settings were way off giving me severe doublevision.
Debian Trixie played much nicer than Bookworm, but everything I did should work on Bookworm if you backport CoreCTRL to make ALVR work properly.
The double-vision glitch could not be made to go away on Bookworm, but after experimenting on Debian Trixie (testing), I found that the supersampling setting in the Blade and Sorcery options was the main culprit. If supersampling is set above 2.0, then the double vision issues start again.
Other than these issues, the game runs very smooth. Highly recommend giving it a shot on Debian Trixie / Bookworm.
Started and played as expected. Experienced no graphical or audio issues, saves from different OS imported perfectly. Extra steps for mods.
gamemoderun %command%
Certain mods install with a .dll file, and will crash the game when loading. Using the launch argument [WINEDLLOVERRIDES="MOD_NAME.dll=n,b" %command%] will allow the specified .dll to load. Replace MOD_NAME with whatever the .dll is named. You can find the name in the mod folder. For multiple mods, just add a space between them, e.g. "MOD_NAME_1.dll=n,b MOD_NAME_2.dll=n,b"
На windows - 80 ФПС 85-90% времени без снижения разрешения и изменений настроек от стоковых
На Linux - 80 ФПС 90% времени только с FSR 1.0 на уровне производительности. Серьезный % от ФПС сжирает огонь
Играйте в ВР игры на windows, друзья. Без Декарда ВР нежизнеспособен на линуксе. Либо у вас должна быть видюха 4090 или 7900 ХТХ. И то даже она не позволит запускать игры, которые тупо не запускаются
Played on ALVR with Meta Quest 2
If you are crashing at 9%, please try the following to see if it helps. 1) Manually install 'openxr' from your package manager. I use pacman so for me I did "sudo pacman -S openxr". 2) Set Proton version to 6.3-8, you can use 5.13-6 however I had a weird issue where it rendered everything in a way that made it seem like I was looking at the game while cross-eyed. 3) Don't start the game by pressing the 'Play' button on Steam; load into SteamVR and open it through the interface there. 4) [optional] - If you still have issues, do everything here the same but run the "Update 10.2" version instead. You can do this by Right Clicking on Blade & Sourcery in your library -> Properties -> Betas -> Beta Participation and select the "previousversion_u10 - Update 10.2" in the drop down list. I have managed to get around the Unity crashes on the latest version, but some people do say this works if nothing else does.
Game works perfectly out of the box with no problems
Played the game using an Oculus Quest 2 with ALVR v19.1.0 (streamed)
Played on Quest 2 via ALVR - absolutely no problems.
WINEDLLOVERRIDES="Mod1.dll=n,b Mod2.dll=n,b" %command%
Rare crashes when an extreme number of particle effects (from mods) are rendered.
You can load mods that have DLL's by simply adding;
WINEDLLOVERRIDES="MysticHands.dll=n,b SpellUndying.dll=n,b TheOuterRim.dll=n,b" %command%
to your launch options.
Quest 2 (V40) with ALVR 18.2.3 (USB), and B&S U11b2
Runs perfect out of the box. Some mods require a launch option.
Some mods include a .dll file. These require you to add WINEDLLOVERRIDES="dllname.dll=n,b" %command% for each .dll from the mods. To add more than one .dll, seperate them by spaces: WINEDLLOVERRIDES="dllname1.dll=n,b dllname2.dll=n,b" %command%
The game is playable, but performance issues make it extremely difficult
Seemingly low framerates and frequent stuttering, even after lowering graphics settings
Crashed regularly while changing settings
Experienced the same view misalignment issues other users reported on the main branch and Linux branch of SteamVR and all versions of Proton, switching to the beta branch fixed this for me
All prior problems have gone away since my last report
Not sure what changed, but performance is on par with Windows now, and scripted mods work. Could be a newer Proton version or a distro change.
Extremely unstable. Otherwise fine. Proton 6.3
Almost every time play is clicked, frequently when loading, or launching, sometimes during gameplay
The game runs great apart from a minor performance decrease. However, mods with .DLL files do not work.
Performance was slightly worse than when I played on Windows, but nothing too bad.
In my case, any mods present containing a .DLL file prevented the game from loading. This encompasses mods that add mechanics the original game didn't have like spells, tweaks, etc.
Most weapons and maps work just fine, but I would like to see a workaround for the more complex mods.
Eyes don't line up properly.
It's like having your eyes crossed. It is present even in the loading screens and menus. Completely unplayable. It was working fine before recent update.
Graphical issues
Right eye offset, impossible to look at. Unplayable.
couldn't get it running on 6.3-6 but under 5.13-6 it runs and mods work too.
