Unable to pull in downloads to vortex #1143
Comments
|
You didn't provide a log, so there's not much I can do here. It works on my end still. You even explicitly removed the section for the log which contains a comment asking you to provide one, and with instructions on where to find it. Also, please download mods manually where possible instead of supporting these types of links. |
sonic2kk
added
the
Vortex Mod Manager
|
apologies. wasn't on the same machine. should've been. |
|
Just wondering, did you accidentally close this issue or did you manage to resolve it? If the issue is not resolved, are you running Vortex with If not, does running it without If neither of these work, then this is an issue with Vortex and Wine. It works for me, but I don't use Vortex very often, and I have the option to disable automatic updates enabled, so this could be a thing that is broken in newer Vortex releases. If the latter works, then I guess not all Vortex versions are as friendly to the argument order, and maybe the URL has to go at the end. |
|
must've accidentally closed, but i tried appending that to steamtinkerlaunch vortex start with no success. i imagine i was doing it incorrectly. when/how do i run that command? |
|
Sorry if I was unclear, I didn't mean to append it. I was checking that you were running Vortex with The steps should be:
It might also be worth trying |
|
launched vortex with the command, which i have been up to this point. i had this open while running the below. hopefully i understood correctly. first command ends in > in terminal waiting for further input, nothing in vortex. second is exactly the same, > and awaiting further input with nothing in vortex. all of this was off of a fresh install. I had removed steamtinkerlaunch-git from my system, removed everything from .cache and .config, then reinstalled. |
Oh, maybe the NXM URL needs quotes? Maybe the mod URL also expired, could be worth copying the URL from Nexusmods. I'm not sure how to get it, maybe Inspect Element for the NXM URL on the mod manager button? |
quotes cause shell to throw that error |
|
missing close quotes before Vortex.exe -d .... adding them throws this error on both commands |
|
Oh, huh, the SteamTinkerLaunch command does not have the full path to the Vortex exe! That was a silly mistake on my part, very sorry. I will make a note to update that logging because that is frustrating. I believe the path to
|
|
path exists. second command worked! not sure what this means or how to make it work without a long ass command, but hell yeah! |
|
That command that you ran is the exact same one that SteamTinkerLaunch is running from your log because I copied it from there 😄 -- well, with some additional quoting that SteamTinkerLaunch already does internally (but is missing from the logging because STL just prints This does confirm that this is not a Wine issue or a change with Vortex behaviour thankfully. Does running If this works, then it is very bizarre, as this shorthand command is the one SteamTinkerLaunch uses to build the command you ran (it gets the Vortex wineprefix, Proton version, paths, etc). And there is nothing in your log that suggests anything is wrong. |
i tried with quotes around the URL as well, no dice |
|
I switched to bash and got the following: it shows the entire --help menu, then hangs. i have to cancel with ctrl+c, then see the following: |
|
You have included a dash in the command, it is In general, SteamTinkerLaunch commands do not use dashes. Sometimes you can use dashes in some commands, but they should all work without dashes. |
neither resulted in the mod being downloaded |
|
I just realised in your earlier reply, you explicitly called out that the second command worked, that is the one without If so, does that mean the command with If that is the case, does swapping when that argument gets passed fix the issue? That is, does |
|
yes that's correct, the second worked previously. additionally, the second command in this last reply worked as well, the first did not |
|
Very interesting, it seems it's the I'll see about moving the order of the argument around to put the For what it's worth, this change was merged quite a while ago (044e24b) and this is the first time it has come up as an issue, which does lead me to suspect this is a Vortex change. |
It seems if this goes at the end of the arguments, Vortex will not parse other arguments correctly. Most notably if this argument is after `-d`, Vortex will not interpret NXM urls. May help #1143.
|
Pushed a change with f899d3c which moves You can verify that you have the correct version by ensuring that it is |
|
confirmed working again. thank you! I have one last question before closing this thread. here you said to avoid these links and use manual downloads. Curious as to why you'd consider that a best practice? |
|
Glad to hear the problem is resolved! It was an unusual issue so I appreciate the troubleshooting.
These types of links from browsers are incredibly brittle and, as a developer, it is incredibly disheartening to see their popularity. Other developers share the same mentality. There are far too many variables for these to break and that is amplified when it comes to working with Wine. The problem is not specific to Linux either, for the couple of years I dual-booted with Windows I never once had these work, and most of the time they don't work on my day job Mac! They are a nightmare, and I advocate against them any opportunity I get. If you must use a mod manager at all, I implore you as a developer to download the mods manually - Especially when it comes to big Nexusmods mod packs! In short, they are unreliable and developers like myself lose sleep over their prominence. |
System Information
Issue Description
unable to pull in nxm links to vortex.
firefox launched through terminal sends this after attempt:
sed: -e expression #1, char 0: no previous regular expression
I've set vortex as option for nxm and nxm-protocol through xdg-mime. Handle mod manager download is enabled in vortex. I can open links from vortex into firefox.
The text was updated successfully, but these errors were encountered: