Vortex is an unmitigated disaster

[Guest deleted34304850]

what would you gain from drag/drop versus doing exactly the same thing by setting rules? you'll have to forgive me, but i don't see any benefit.

 

if you think that your load order is wrong - and mod x needs to load after mod y - and you want to do that with drag and drop - but you can do exactly the same by setting a rule or using a group - what is the difference?

 

well, for me the difference is this - with drag and drop you have no idea, at first glance, why mod x is loading after mod y - because drag and drop would not leave any trace. it's simply dragged mod x and mod y into a specific position with no documentation as to why.

 

if you have a rule that specifically says mod x needs to load after mod y - and then you find that this is in fact, incorrect - all you need to do is remove the rule, sort and redeploy. at that point, all the work is done for you. mod x and mod y will revert to their original position in the load order.

 

if you drag and drop - are you aware where you dragged your mod from if you come to put it back days/weeks/months later?

[Guest deleted34304850]

All it did to me was to ruin my savegames by messing up my mods xD

I didn't even install anything new, just imported the NMM mods and now even the NMM can't run them. Not sure what vortex did, but it sure did make a mess of everything. Impressive seeing as to how I never even used it to change or install any of my mods yet xD

let me put this right for you;

 

all it did to me was what i told it to do, but because i didn't read anything, nor understand what i'm trying to do, i caused my own games to become messed up. next time, i will be sure to read, understand and carefully back up my environment and deploy my mods, one at a time, because i know that my nmm log wasn't set correctly.

 

hth

[Zanderat]

BTW - just try an install of the NMC's Texture Pack with Vortex for an example of what I am talking about.

I did. No issues.

[HadToRegister]

 

What about the fact that Vortex doesn't work with exFAT?

 

 

I would say , It's 2018

[Guest deleted34304850]

i have some 5.25 floppy disks in a box in my attic. does vortex support that medium?

No?

worst. program. ever.

[pndragon65]

what would you gain from drag/drop versus doing exactly the same thing by setting rules? you'll have to forgive me, but i don't see any benefit.

 

if you think that your load order is wrong - and mod x needs to load after mod y - and you want to do that with drag and drop - but you can do exactly the same by setting a rule or using a group - what is the difference?

 

well, for me the difference is this - with drag and drop you have no idea, at first glance, why mod x is loading after mod y - because drag and drop would not leave any trace. it's simply dragged mod x and mod y into a specific position with no documentation as to why.

 

if you have a rule that specifically says mod x needs to load after mod y - and then you find that this is in fact, incorrect - all you need to do is remove the rule, sort and redeploy. at that point, all the work is done for you. mod x and mod y will revert to their original position in the load order.

 

if you drag and drop - are you aware where you dragged your mod from if you come to put it back days/weeks/months later?

Will I remember where I dragged it from? Almost certainly not. But if I set the rule correctly I won't have to. But just in case I might need to know at a later date, I can write a note in the mod info pane.

 

I would be only be using the drag-and-drop to get close enough to where it should be to help me figure out what the rule should be without having to test each mod/plugin until I find what I need. Once the rule is set, I can deploy it and resort so that Vortex places it where it needs to be.

 

I am not trying to subvert the developers intended usage (though I am sure others would but I really don't give a flying fig what they do). I just want to narrow down potential conflicts until I can find the rule I need to make for my particular needs.

 

I don't want to try and drag everything to the bottom of my load order. It is lazy and inefficient. And impossible. Not everything can be the last plugin loaded. If you can tell me a better way to locate the conflicts that LOOT seems to be unable to find sometimes, I would be happy to use it.

 

I am not trying to argue with you. I just want to clarify my position and seem to be doing a horrible job. If there is a more recent tutorial video than Gopher's I will be happy to watch it because I am obviously missing something and would like to rectify that.

[pndragon65]

I haven't had a problem with NMC. It is working for me on fo3, fnv and fo4 without any problems.

[pndragon65]

i have some 5.25 floppy disks in a box in my attic. does vortex support that medium?

No?

worst. program. ever.

Does that mean I won't be able to use any of the code I've wriiten in COBOL and stored on reel-to-reel tape that I keep in the cold vault in my basement? Bummer days, man.

[Guest deleted34304850]

honestly the rules for load order are pretty simple and don't require a lot of thought.

 

you have your masters, they go above esp's - all good. you have esl's - creation club and a few user mods - they are loaded in slot FE. then the rest esp's.

 

some mod authors say put the mod at the bottom of the load order, and yes, you're right not everything can go at the bottom. all you need to do is figure out what the mod is changing, you can do this with xedit and simply make sure that the mod you need to go last in a sequence is last in a sequence and nothing is loading after it that could interfere with what that mod is changing.

 

you can do it manually - but as you just said - you wouldn't remember where the mod was dragged from - and nor should you - because that's not your job - thats the job of the mod manager. all you need to do is tell the mod manager put mod x before mod y - always - until i say different, and it will do that.

 

if you decide at some point that you dont want that load order any more, you simply remove the rule - re-sort the mods and re-deploy. the mod manager will happily do this for you. the whole point here is that you let the mod manager do its thing for you so you dont need to. its a program, it will do what you want it to do so much better than any human can.

 

I think from your reasoning, you know what you want, but you're just not certain (yet) whether vortex can do it. All I can say to that is - try it. Set up a rule so that in your load order your mods load in the way YOU want them to load. It is a very simple procedure - you just have to dive in and do it.

 

And here's the kicker - let's say you make a rule and you put mod z before mod a and your game gets ctd's all over the place - all you need to do is remove that rule so that mod z goes back down the order behind the rest of your mods and redeploy - job done. you will be up and running with your reverted load order in minutes rather than trying to remember what you dragged from where and if you put it back in the right place.

 

my advice to you - map out the order you want your mods - then sort them in vortex, then look at the order in your load order file - then make a rule to change 1 thing - and do the same thing again - see if the change you made worked in your load order file - and do it again, and again, until all the mods you want to be sorted your way are set that way. it looks daunting - i assure you, it really isn't

[HadToRegister]

 

 

I don't want to try and drag everything to the bottom of my load order. It is lazy and inefficient. And impossible. Not everything can be the last plugin loaded. If you can tell me a better way to locate the conflicts that LOOT seems to be unable to find sometimes, I would be happy to use it.

 

 

And there is the subtle beauty of it.

 

If you put all of those "NEED TO GO AT THE BOTTOM OF THE LOAD ORDER" esps into either the "Dynamic Patch" group, or the "Override" group, they will ALL get put at the bottom of the load order, (and here's where Vortex shines), then vortex will sort those esps inside the group, into the proper load order for that group.

 

Cool huh?