Vortex fails to install, using git version
#989
Comments
|
Vortex does not work on SteamOS as far as I know, sorry. It works on my Linux PC last time I tried a while back. If it's fixable, no one has come forward to fix it. It's possible this is a Wine compatibility issue as well, but SteamOS is just a bad platform to mod games on, and I am probably not going to support STL on SteamOS for much longer (#859 (comment)). I got my Steam Deck OLED and am planning to sell my LCD Steam Deck, and I have no plans to use STL on my new Steam Deck.
This has nothing to do with ProtonUp-Qt, and you can install STL-git using ProtonUp-Qt. The Vortex wiki also states on Steam Deck to never use STL v12.12, ever. As noted in my comment on the issue you linked, the Steam Deck installation docs were also updated. Here is the diff given on that issue. |
sonic2kk
added
the
Vortex Mod Manager
|
I would say to make sure you tried to install Vortex into a fresh prefix and not one installed with STL v12.12 (i.e you removed You could also try downloading an older Vortex EXE and installing that into a fresh prefix, using the option on the GUI to install a custom Vortex executable. You could try and figure out which one works, v1.8.0 is one I remember working on SteamOS. Then you can update from there. But that was on an older SteamOS version that it was tested, and likely an even older Steam Linux Runtime, there could be all kinds of incompatibility now, even though I suspect most of it comes from Vortex. |
|
You should also be aware that Vortex Mod Manager is going to be discontinued soon and replaced with a new Vortex project that is written in C# and .NET instead of Electron and NodeJS. This will have native Linux support but the Vortex team are undecided about supporting Proton games, and will not support the application running under Wine since they will have a native version. Once this is released, Vortex support will be pulled from STL and likely many other projects since this is an entirely different application. Just something to be aware of, you probably 1) do not want to mod games on SteamOS, 2) don't want to use Vortex Mod Manager since it is slated to be replaced with an entirely different application that will have zero backwards compatibility even on Windows. |
sonic2kk
added
the
Steam Deck
|
First off, thank you for the detailed response, this is great. And yea, I'm learning mod tools on Steam Deck isn't a good fit, which isn't so great. I'll give the "clean" a shot when I am free and I'll post here with what happens. I've seen a few guides for how to "hack things in" which I'll give a shot if I need to. As for the VMM replacement, I had heard that it was going to be a while, but it does look like Proton support is there from PRs against issues Nexus-Mods/NexusMods.App#152 and Nexus-Mods/NexusMods.App#150, but given the super-alpha state and some functions specifically named for Skyrim, I'm guessing it's rough around the edges. Do you have any suggested alternative methodology? Such as modding in Linux and rsyncing the game folder onto the deck? |
|
I don't have any alternatives, sorry. My advice to everyone I know with a Steam Deck is to stay away from mods that aren't just simple patch installers (such as re4hd or the Committee of Zero visual novel patches). I stay well away from any kind of modding on my Steam Deck, and as far as I know there's no clean way. ModOrganizer 2 seems to work better, assuming you ran the That's good news about the newer Vortex app supporting Proton, the sooner STL can get away from people using it to mod games, the better. It was originally intended afaik to complement the tinkering for the enthusiast crowd and not as a one-click mod installer, which is simply not possible for such complex tools under Wine. Also, practically no one came forward to help with it, and since I don't use Vortex I had no way to maintain the implementation that the previous maintainer developed apart from high level troubleshooting. I don't use STL on my LCD Steam Deck and almost definitely won't be installing it anytime soon at least on my OLED Deck, so I can't troubleshoot anything specific to the Steam Deck. I have asked for community contributions but it seems too many people using STL aren't developers anymore... There was zero activity on #859, and when the Steam Deck became widely available, there was an extreme influx of rude and entitled users that killed much of my motivation for this project for a while. When Steam Deck issues come in I usually get frustrated so I apologise for my less than appropriate responses. And at that point it's justified to say "why not pull Steam Deck support if you don't like STL on it", and if no one comes forward, that's what will happen next year unfortunately. And to be entirely fair, even if the Steam Deck ran Windows, my advice would still be to stay away from modding, because of how troublesome it would be on a handheld. |
Well that's sad, fully understand the response method given the situation. You make this for free, people need to respect that. If I had the time to contribute, I would, but modding is more of a "oh I'll try this" kind of thing for me so I wouldn't be able to dedicate the time to getting things working beyond maybe troubleshooting any issues in what will be my last attempt using https://github.com/pikdum/steam-deck, which I'm sure you're already familiar with. Perhaps by the time the Vortex replacement launches I'll be addicted to modding and jump in then ;) |
|
Yes, Pikdum created this after the experience we had with trying to get Vortex running with STL. A number of users came here complaining to me that Pikdum's tool didn't work, when we are unaffiliated entirely with each other's project. I didn't look much further into it other than it, too, seems to be a bit of a mixed bag, with different use-cases working and not working (much like a similar project for installing MO2 on Linux seems to be hit-and-miss on SteamOS, and users have also come to me complaining about that tool not working on SteamOS when me and that project lead are also entirely unaffiliated). Good luck with your modding and I do hope for the best :-) |
|
Ouch. I did take a bit of time to look through the bash script in hopes of making a PR here. I've tried a few different proton versions by hard coding them (is there a configuration place to change the version of proton for the Vortex install that I'm missing?) but no luck yet. Btw, I tried changing I seem to have the same problem with MO2, I'm wondering if it's specific to my deck or because I'm using an SD card. Hrm.. |
|
You might want to try MO2 again, I made a mistake recently and resolved it in For Vortex, if even going back to v1.8.0 in the Vortex version settings doesn't work, then I guess it's just totally borked on SteamOS for some reason. Sorry :-( |
System Information
masterIssue Description
When doing a Vortex install, system hangs on "Installing 'Vortex'".
I originally tried this using the "latest stable release" (12.12) as described in the docs: https://github.com/sonic2kk/steamtinkerlaunch/wiki/Installation#protonup-qt
I then saw a message from September saying to use the
gitversion: #901 (comment), so I tried that. Note: If the stable release is so far out of date, the ProtonUp-Qt docs should probably be updated to tell users they must use thegitversion.My process:
It never gets to Dot Net.
Logs
It then stalls until I kill things. I also tried in game mode and the same thing occurs.
The text was updated successfully, but these errors were encountered: