ositools: [Linux] DLL does not seem to be loaded with Proton

It seems that when playing D:OS2 on Linux via Proton on Steam, the DLL is not being loaded.

Using Proton, the game is launched via EoCApp.exe after applying the following workaround:

mv ./bin ./bin.bak && ln -s DefEd/bin bin && cd bin && mv ./SupportTool.exe ./SupportTool.bak && ln -s EoCApp.exe SupportTool.exe

(create a backup of folder ‘bin’, make a symlink ‘bin’ that points to ‘DefEd/bin’, change directory to ‘bin’, create backup of file ‘SupportTool.exe’, make a symlink ‘SupportTool.exe’ that points to ‘EoCApp.exe’)

Essentially launching ‘EoCApp.exe’ directly via Steam. Mods subscribed to in the Steam workshop show up normally in the game. Mods that require ositools cause an error that the story could not be created. Mods that do not require ositools work fine.

Linux version: openSUSE Tumbleweed x86_64 running Kernel 5.5.7-1-vanilla. Proton version: Proton 5.0-4 Game version: v3.6.58.1306

If any further information or help is required, I’ll try to assist to the best of my abilities.

About this issue

Original URL
State: open
Created 4 years ago
Comments: 31 (10 by maintainers)

Most upvoted comments

Thanks for this. Using WINEDLLOVERRIDES="DXGI.dll=n,b" %command% is enough with Proton-5.9-GE-8-ST. Confirmed I got achievements with several Gift Bag features enabled.

(Proton GE also has a built-in launch fix so none of the other steps with the moving and linking files are needed. Just install, choose Proton version, add the launch option and done.)

jn64 on Dec 31, 2020

I have found out that actually I pasted the command WINEDLLOVERRIDES="DXGI.dll=n,b" PROTON_NO_ESYNC=1 %command% in the launch option for two times, because after the first paste, the launch option still seems empty, showing only the end of the paste actually, so I had to paste again, resulted in an invalid launch option. After fixing this, the extended script finally works!

otakutyrant on Sep 17, 2020

Thanks for the info, I’ve amended the instructions on the release list

Norbyte on Sep 1, 2020

So, I came here to write a new issue ticket asking Norbyte to tell Proton users in the release notes how to make this work using WINE, because it’s really easy.

All you need to do is launch WINE/Proton using WINEDLLOVERRIDES="DXGI.dll=n,b" after following the other install instructions.

So, for Steam+Proton,

Right-click the game in the games library in Steam
Click Properties...
Click SET LAUNCH OPTIONS... button
Enter WINEDLLOVERRIDES="DXGI.dll=n,b" PROTON_NO_ESYNC=1 %command%

Close and launch, enjoy script-extended mods.

folknor on Sep 1, 2020

Launching via the bink2w64.dll wrapper included in “Achievements -Definitive Edition” loads the DLL and launches with the Debug console on the desktop. The debug console logs a (probably unrelated) message “Unable to read VR Path Registry from … Local Settings\Application Data\orpenvr\openvrpaths.vrpath”, but seemingly continues to load, then tries to update OsirisExtender.

Updating OsirisExtender fails after successfully downloading the Update.zip file with a popup dialog “Unable to extract Script Extender update package. IShellDispatch::NameSpace() call failed on zip file …\Update.zip”

Enabling trace on shell and seh results in the following log (exception occurs around line 15,000)

steam-435150.fail.log

chicken42 on Apr 20, 2020