Are dependencies Vortex page dependent?

[JamesRook]

If I am on the MODS page of Vortex, I can drag a line between 2 dependencies icons and a menu pops up that will establish a rule. Thereafter a little green bolt will appear by the icon to signal there is a rule. But if I am on the PLUGINS page and try the same operations, I get multiple red "Failed to Render" errors and no rule will be made, even though there is an initial popup menu that says to drag and drop to make a rule. I think this is how Vortex is supposed to work, but I don't understand the idea behind it. Doesn't it make more sense to be able make the dependencies configurable from the page where you can also see the LO?

[Pickysaurus]

If you're getting "failed to render" errors that implies that something in your install is broken.

 

Try reinstall the latest version of Vortex over what you have already.

[JamesRook]

Thanks for the reply. I DL'd a copy of Vortex and did a reinstall as per your suggestion. No change. I can make the dependency/deployment selections on the MODS page but trying to do it on the PLUGINS page will result in the red "Failed to Render" errors and no other change. I'm guessing this operation is blocked because it would, in effect, allow you to manually adjust the LO a bit very conveniently. What I mean by that is say you are on the PLUGINS page and checking the LO and notice that Mod Z is loading before mod A because LOOT didn't sort properly. It would make a lot of sense and be very easy to just use the dependencies feature from there. Instead, you must go to the MODS page and do the adjustment from there. When you have hundreds of mods dragging from Z to B is really finicky and an ordeal. Just very irritating that an included "feature" that you think you can use and would be incredibly useful doesn't work.

[showler]

Don't "dependencies" on the MODS tab only affect file overwrites? Like when two mods both have versions of the same mesh/texture/script file and are conflicting because of that?

 

Load order would be an entirely different thing and my first question for that would be "did you disable the LOOT auto-sorting?". Because if the auto-sort is still on then you would be fighting it to make manual changes to your load order.

[Deleted6174501User]

Failed to render error sounds like a failed extension or incompatible/out of date theme. Check vortex extensions tab to see if they're all enabled (Mod Dependency Manager, Gamebryo Plugin Management, etc)

Edited March 2, 2023 by Guest

[JamesRook]

I did a reinstall of Vortex with the latest (which I was already using) version. All extensions except Collections are enabled and up to date. I do understand that there is a difference between LO and dependencies but fixing the conflicts is what I want to be able to do from the PLUGINS page. For example, I have a multi follower mod B but want the single follower mod A to overwrite. On the MODS page I can drag the dependencies icons and set a rule to load B before A or A after B depending on which mod I select first. If I am on the PLUGINS page, doing the same selection of the dependency icon lets me drag a line from one mod to another but changes nothing and gives no menu choices, except that If auto-sort is on I will get the error. I turned auto-sort off as a test and the errors did not appear, but there were also no changes. If someone wouldn't mind doing a test on their copy of Vortex - go to your PLUGINS page and see if you can set a rule from there by dragging from one icon to another, I would appreciate it. I think this is just the way Vortex is made.

[showler]

Okay, just so you know I tried doing the "drag dependency" thing on both the MODS tab and the PLUGINS tab.

 

With the MODS tab, I got the pop-up, the green line, and then a window appeared with "must deploy before/must deploy after/etc." options for the mods in question.

 

With the PLUGINS tab, I got the pop-up, the green line, and then a window appeared with the "Set rules" including a filter box, a list of existing rules and a section below to add a new rule.

 

So, if you're getting an error and no other results, it seems something is broken with your Vortex. Re-installing didn't seem to fix it, so you might need to remove your settings folder and let it be rebuilt.

[JamesRook]

Thanks for doing the test showler. That answers whether this feature is supposed to work in Vortex, which it is, so indeed, something in my copy is broken. I will try your fix and see what happens. Since I'm going to be purchasing a new computer in the near future I'll install a new copy on it that should work as designed. Thanks again for the help.