-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⚠ [HOWTO] Vortex Game Mods can't be deployed #418
Comments
A (more than) complete list with steps for a clean test (to iron out possible 3rd party side effects/bugs) using Fallout New Vegas for the example:
|
Following the steps exactly as writting above on Pop_Os! 21.10, clean up first by reinstalling new STL and clean FNV Vortex does not autodetect FNV so I set the path myself to my z drive Comparing the values with Which seem to refer to invalid paths I do note some warnings and errors in the terminal that starts vortex: I assume it fails an attempt to symlink to the vortex prefix |
Thanks for testing. Please append the corresponding log (will add that to the steps above as well) Edit: Seems like autogenerating/creating a compatible staging directory did not work for you (maybe a more common problem(?) Adding a staging path is also possible via steamtinkerlaunch commandline like: Edit2: Please see also the corresponding wiki: https://github.com/frostworx/steamtinkerlaunch/wiki/Vortex#vortex-stages |
Setting a stagepath using |
Please append the corresponding log edit: ah, thx for the log. I'll soon add some more corresponding logs and validity checks in functions |
please retest with above commit. |
Running with the new commit |
Excellent - those two lines are important:
Will look into this soon when I find the time. |
@henkery what does |
iroha@pop-os:~$ steamtinkerlaunch list am | grep 220200 |
thx for the quick test. Please test if above commit already fixes the problem. |
With the new commit it works straight away regardless if I set a stagepath before run |
Thanks a lot for testing, very appreciated! :) |
Edit: I fixed it by changing the file permissions, so that my user can access the txt-file. Now Fallout 4 is detected and added to Vortex! I'll test if I can actually add mods now. No idea why the permissions weren't correct though. In any case: sorry for the noise, and thanks for your work! Edit2: Everything including f4se seems to work now! Great! Previous message: Hi, I use the latest STL (steamtinkerlaunch-v9.1.20220220) on Linux Mint 20.3. Unrelated to this I have a problem though: when STL tries to detect the games I see an error in the console: After that Vortex starts fine, but it doesn't show any autodetected games (Fallout4 in my case, which has the steam id 377160). Here is the relevant section in the stl.log, the IDs are reported as not listed, but that's probably simply the failing grep calls.
I could try to change the owner for |
apparently there is no interest to contribute to this list, so closing here |
steamtinkerlaunch
tries to autodetect and autoconfigure all Vortex compatible games installed.That feature (for now) utilizes a static self-rolled list (
/usr/share/steamtinkerlaunch/misc/vortexgames.txt
)with their SteamAppid , the actual name and the "nexusgameid".
Most games should work, bur several others can't be setup automatically, often because the nexusgameid changed.
This commit fixes the issue for Fallout New Vegas, Skyrim SE and several other titles.
If someone has an idea how to best drop that static list completely, you're very welcome to share it.
Until then, the bundled list needs to be tested and maintained permanently.
When you enable an autodetected game in Vortex and see something like this
you can check if the Vortex internal name (underlined in the scrot) is equal to the one ion above static list.
If not, it might help to replace the string in the list with that you found. Either way it would be nice if you contribute your finding here and therefore help others with the same problem.
When everything looks correctly (like in the next scrot), it would be nice as well if you confirmed it here.
Of course any hints or PRs for wrong, outdate or missing entries are very welcome as well.
Compatibility List (checked means working - unchecked is untested, plrease report non-working in separate comments)
(I barely mod anything, so I leave it up to you to fill the checks)
The text was updated successfully, but these errors were encountered: