So the workshop tools will now show up, but you will run into the next problem. You can work around that problem by creating another script that launches steamtours.exe without the VR related parameters. And by that previous versions are not part of the custom vrclient.dll in Proton even though the native vrclient.dll/ vrclient.so shipped with SteamVR include them. The problem here is, that when VROverlayView was added to the official OpenVR API the version string was already IVROverlayView_003. the custom vrclient.dll in Proton is missing IVROverlayView_002, which steamtours.exe requests when launched from steamtourscfg.exe.But sadly that's not enough because Clicking "Launch" in steamtourscfg.exe will result in a crash. Once you have a hybrid installation of SteamVR you need to create a shell script that launches the steamtourscfg.exe through proton and modify the tools.vrmanifest to use this script for the workshop tools. So to even have a chance to run the workshop tools you have to play a bit around with Steam to also download the Windows part of SteamVR without erasing the Linux part (which you absolutely need because it includes the executables/libraries that allows OpenVR based software to use the headset either natively or through the custom vrclient.dll in Proton, unless you move that part of SteamVR elsewhere and modify openvrpaths.vrpath accordingly). SteamVR on linux doesn't include the executables/libraries for the workshop tools, which are steamtourscfg (for creating new addons and launching the editor) and parts of the steamtours executable (which exists on linux but is most likely missing the editor parts/the parts that load the corresponding libraries).I tested around a bit and I think there are three main problems when it comes to using the workshop tools on Linux:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |