![]() Might be that that's the cause, if it's in fact using that script. Now that I think about it, where do you source the vortex-symlinks from? I think there's a git repo somewhere hosting a file called "vortex-symlinks.sh". Saw it is also missing the symlink from/to $stl/vortex/downloads as well.Verified that Vortex is able to find steamapps/common now.manual changes might help in your situation but don't help with the initial problem - so the results are unrelated Added that particular symlink manually.Saw it was missing the symlink from steamapps/common (Arch) to steamapps\common (Windows) (Or the other way around), among others (Possible cause for failure to discover Steam Library? libraryfolders.vdf exists and point to $HONE/.steam/steamapps) ah, haven't checked your log yet, but that very likely IS the problem.Checked symlink config using stl vortex symlinks.NET 4.x, etc a separate install log file is created in /dev/shm/steamtinkerlaunch/ Watched the script install the STL Proton Version.Installed Vortex through the STL UI (Main Menu -> Vortex -> Install) using Proton-6.17-STL **internally this simply starts the command line installer, but might cause conflicts with a 2nd running steamtinkerlaunch instance (don't think so, though).Should happen automatically, but might be a good idea to separately install vortex into its own prefix here initally via command line Set STL as launch argument for F:NV I recommend using it always as compatibility tool for windows games and only as launch argument for native linux binaries, the launch argument code might be outdated and might be even removed, depending on how much time I spend into the project in the future.Switched over to my nvidia card using optimus-manager.directory /dev/shm/steamtinkerlaunch/ would have been the better step here sure why not, but should not be related - instead removing the temp. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |