Vortex install hangs, there's no way to uninstall it?

[zmaint]

System Information

• SteamTinkerLaunch version: 12.12
• Distribution: Solus Plasma
• Installation Method: EOPKG (package manager)

Issue Description

Vortex mod manager downloads, install starts, hangs on installing .net. Waited over an hour, still stuck. Closed it. It thinks its installed (it's not, most likely just a borked prefix). There is no way in Steam Tinker to remove that broken prefix, browse to it, or even see the path so I can remove it manually. Where is this being installed at??

Logs

-->

[sonic2kk]

Sounds like this issue is because you are using v12.12 and not using master as the issue template and all other closed Vortex issues in the last months have directed. However, I am not against anyone uninstalling Vortex, as it is a godawful tool. But if you do want to use it, I recommend using an up-to-daate SteamTinkkerLaunch.

There is no way in Steam Tinker to remove that broken prefix, browse to it, or even see the path so I can remove it manually

The wiki documents this already... The most likely place is at ~/.config/steamtinkerlaunch/vortex. You can delete the whole folder. If you do want to use Vortex, make sure to do this before updating to SteamTinkerLaunch from master. It is always recommended to use the latest version from master, even when v14.0 comes out, only the latest commit to master will ever be supported.

The changelog (which the issue template suggested to check) also detailed various changes to Vortex that might've been good to check before using a version of SteamTinkerLaunch that is over a year out-of-date, despite semi-regular updates being made to the project.

[zmaint]

I was able to get it removed.  Thankfully the install process had gotten far enough along that it had made a start menu icon and I was able to find the path to the prefix from there.  Deleted it.  Switched to proton GE 8.4 and it installed without issue. Would be extremely helpful if there was a way to easily browse to the prefixes or there was a listing provided in the app for the install paths.   I don't like Vortex either but MO2 has literally never worked for me and I hate manually installing hundreds of mods lol. Thank you for the quick response.

…

---- On Tue, 02 Jul 2024 20:02:51 -0500 Eamonn Rea ***@***.***> wrote --- Sounds like this issue is because you are using v12.12 and not using master as the issue template and all other closed Vortex issues in the last months have directed. However, I am not against anyone installing Vortex, as it is a godawful tool. But if you do want to use it, I recommend using an up-to-daate SteamTinkkerLaunch. There is no way in Steam Tinker to remove that broken prefix, browse to it, or even see the path so I can remove it manually https://github.com/sonic2kk/steamtinkerlaunch/wiki/Paths#compatdataprefix-paths... The most likely place is at ~/.config/steamtinkerlaunch/vortex. You can delete the whole folder. If you do want to use Vortex, make sure to do this before updating to SteamTinkerLaunch from master. — Reply to this email directly, #1134 (comment), or https://github.com/notifications/unsubscribe-auth/AV76U3K7OD6ZNERUYUPTCATZKNETXAVCNFSM6AAAAABKIRCEUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBUHAYTKMZWGY. You are receiving this because you authored the thread. Zach Semonick 620.249.1233 ***@***.***​

[sonic2kk]

Would be extremely helpful if there was a way to easily browse to the prefixes or there was a listing provided in the app for the install paths.

This is already implemented with steamtinkerlaunch vortex getprefix. The equivalent command for MO2 is steamtinkerlaunch mo2 getprefix. You can see these when running steamtinkerlaunch help as well. These are only available in master and are noted on the Changelog.

These commands were implemented over a year ago in #811.

I don't like Vortex either but MO2 has literally never worked for me and I hate manually installing hundreds of mods lol.

Installing manually is always the way to go, but if you mean MO2 has not worked for you with SteamTinkerLaunch, perhaps you were not using SteamTinkerLaunch after it pinned for v2.4.4 for compatibility.