Vortex Not Allowing Game to Start

[rmm200]

Tannin, since you dropped in...

Please come up with a BSA solution so potential conflicts are not hiding inside the BSA.

Either peek inside BSAs - or just unpack them. Maybe unpack them for conflict resolution then delete the loose files.

Whatever works - but conflicting files hiding is a problem.

[Grestorn]

The load order of bsa files are determined by the load order of their respective .esps.

 

And loose files are always overwriting bsa files, no matter what.

 

So the only thing would be an option to unpack bsa files. Actually, that's why mod authors should give the user the option to use loose files or a bsa

[rmm200]

As a mod user, especially for problem resolution, I would really like to know when conflicts occur,

even if Vortex can't fix it. Maybe just flag the BSA as overridden - and let the user worry about if he wants that other mod to change the BSA.

[CryoticShell]

Umm... One question:

 

If NMM asks you whether to "overwrite files..." when installing a mod... and you refuse to answer that dialog, because you don't know the correct answer and you can't be bothered with figuring out what the tool wants from you.

 

Well, you know what? Unless you answer that dialog, you cannot go on either. It's just the very same! You have to resolve the issue before continuing.

 

So you're complaining about something that's an inherent problem with modding. Get over it. The only difference between Vortex and NMM is, that you're actually allowed to install mods and resolve the conflicts later. But you have to resolve them either way!

 

This whole thread just proved that you guys really have no idea what you're doing.

 

 

@Tannin: I have a recommendation for you: Add a simple "auto derive install order" option for people who seem to be unwilling to deal with the install order. That option would react like the "Overwrite all" option in NMM, i.e. each new installed mod automatically overwrites all previously installed mods.

 

The problem is that there is no option in Vortex's dialog box to move past it, literally just "okay i won't play" and "show me the conflicts"

 

There's no reason to resolve conflicts that aren't actually conflicts and have been taking care of themselves for a month now

 

 

 

 

 

I agree with you man, but I think its time to just go back to MO or the OG NMM if its still around, it will take a day to remod for me at least but atleast it will work

 

you wrote "at least it will work" - I think what you really mean, based on the ass-backwards logic on display here is " at least it wont stop you from messing up your game".

 

 

hey, knock knock, you listening? our games worked, nothing messed up, if there was something on the mod page that said hey, X mod doesn't work with Y mod, im only gonna use one of them, if its just a matter of the same textures for the same thing from the same author in 2 mods that happen to use the same picture I shouldn't have to mess with them, and its wouldn't be so bad if it wasn't for the fact that the same author has 20 mods I wanna use, and now I gotta f with them and guess where I should put what for 30 mins to a hour, so yes im going back to something that has you overwrite them as soon as they are installed, so that when I install Castle mod whiterun and it has Picture.crap and I install castle mod riverwood and it also uses picture.crap I can just hit, yes overwrite or merge or whatever as I do it, either I wil find away to go back to whatever vortex version it was before this one, or ill go to MO2, hey im not saying vortex is s*** or anything, I guess I just prefer other things, and ill be more careful next time instead of dropping what im using just cuz something shiny and new show up

 

i'm not listening, but i am reading.

bottom line is this, you do not have the first idea of what you're talking about, and that's fine, the world is full of ignorant people.

the solution, as i've written at least twice, is to not use vortex and your "problem" goes away. what you're asking for - i hope will never be implemented in vortex, because it will cause problems. the way vortex is now, is fine. you disagree, that's fine, and you're entitled to do it - but - you need to understand the problem - and why what you're asking for is a terrible idea.

are you reading?

are you?

 

 

Then there's you. Vortex already had a way of saying "there's conflicts, conflicts might screw everything up" and not lock people out of their games. It was fine until some point in the past week. What you're not realizing is that a "conflict" doesn't mean "actual game breaking problem" and can often be perfectly fine. As for your solution to just not use Vortex, it's the primary (and now only official) mod manager for nexus mods. NMM is no longer supported or updated.

 

All you're saying is "Hey, you use mods? Your mod manager is causing a problem? Don't use either, what are you, stupid? It's that obvious."

[Guest deleted34304850]

.

[CryoticShell]

it seems that you still don't get it, don't understand it, don't understand the point you're making and why it's bad.

here's another helpful hint - read up on what you're asking, why it happens and what you need to do to solve it in vortex, and what you did to solve it in whatever mod manager you used previously, because, believe it or not you DID solve it in your mod manager previously, but you're obviously not aware of what you did to resolve it so that you could play your game.

or, you can carry on with your nonsense posts - and honestly, i'm not making this up - they are absolute nonsense. however, if i were you and i wanted to get on with playing the game you paid for - i'd be figuring out what i need to do to fix it, not posting rubbish on t'interwebs.

 

This is literally as simple as I can make it.

 

Days ago, there was no problem.

 

Nothing changed.

 

Suddenly, there's a problem.

 

Do you see what it is now? No mods were added, no mods were activated/deactivated, installed/uninstalled. There's no reason Vortex should have been like "hey no this won't work now" after it working exactly how it was for a month, and even less of a reason for Vortex to decide whether or not I should be allowed to play a game I legally own that I didn't buy from Vortex or its owners.

[AugustaCalidia]

:smile: This thread now has the potential of turning into a crime thriller. There has been issued an ominous warning that Vortex is obstructing the lawful launching of a legally owned game. What will happen next? Will Tannin be charged before the ICC? Will Dark0ne as well be implicated in this nefarious plot to deny legal game owners their rights? Stay tuned for further developments! :smile:

[Grestorn]

 

it seems that you still don't get it, don't understand it, don't understand the point you're making and why it's bad.

here's another helpful hint - read up on what you're asking, why it happens and what you need to do to solve it in vortex, and what you did to solve it in whatever mod manager you used previously, because, believe it or not you DID solve it in your mod manager previously, but you're obviously not aware of what you did to resolve it so that you could play your game.

or, you can carry on with your nonsense posts - and honestly, i'm not making this up - they are absolute nonsense. however, if i were you and i wanted to get on with playing the game you paid for - i'd be figuring out what i need to do to fix it, not posting rubbish on t'interwebs.

 

This is literally as simple as I can make it.

 

Days ago, there was no problem.

 

Nothing changed.

 

Suddenly, there's a problem.

 

Do you see what it is now? No mods were added, no mods were activated/deactivated, installed/uninstalled. There's no reason Vortex should have been like "hey no this won't work now" after it working exactly how it was for a month, and even less of a reason for Vortex to decide whether or not I should be allowed to play a game I legally own that I didn't buy from Vortex or its owners.

 

 

Yes, you changed something. You changed to another mod manager and practically reinstalled all your mods.

 

And when you installed all your mods the first time in NMM, you DID resolve the conflicts. Each time, when you answered that "Overwrite files" dialog.

 

Vortex has no way to know how you answered that dialog when you used NMM, since NMM doesn't keep track of that. So it cannot use that information. You have to tell it again - or stick with NMM.

[Tannin42]

 

 

This is literally as simple as I can make it.

 

Days ago, there was no problem.

 

Nothing changed.

 

Suddenly, there's a problem.

 

Do you see what it is now? No mods were added, no mods were activated/deactivated, installed/uninstalled. There's no reason Vortex should have been like "hey no this won't work now" after it working exactly how it was for a month, and even less of a reason for Vortex to decide whether or not I should be allowed to play a game I legally own that I didn't buy from Vortex or its owners.

 

Look, when Vortex says there is a conflict there is definitively a conflict, conflicts that you have not resolved so they get resolved randomly.

 

a) It's possible that in your case due to luck the conflicts were randomly resolved in such a way that it works, but even then: With the next mod you install the random resolution may end up completely different or we change something in a future Vortex version that affects how this "random" resolution pans out.

We don't want to shackle ourselves, always having to consider how our changes may affect the "random" resolutions. We don't want to have a situation where a few months or years from now we change something completely innocent and suddenly thousands of users come crying "yesterday my mods worked but now Vortex deploys different files".

 

b) But more than that: A large number of users had less luck than you, their conflicts were "random"-resolved incorrectly and many of those didn't then go and resolve their conflicts, instead they complained about bugs to mod authors. We had mod authors despairing over an insane amount of complaints and help requests and that's simply not acceptable. Sorry, but as much as I want to provide the most convenient tool for users, that can't be at the expense of the people who actually provide the content.

So because users will - instead of trying to find a solution themselves, because they understand that they've ignored the notifications and warning signs - go running for help, we have to prevent the errors from happening in the first place as much as possible.

And that may not be you, maybe you're the kind of person who would first try to read up and solve the problem yourself, but I'm sure you understand that we have other users to deal with as well - but even then argument a) is still relevant to you.

[Guest deleted34304850]

.