Vortex Not Allowing Game to Start

[Guest deleted34304850]

.

[Guest deleted34304850]

.

[TheVambrony]

 

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

[CryoticShell]

you're calling foul because it wont let you mess up your game?

as i posted above - the simple solution is - don't use vortex - problem solved - sort of - but not really.

 

 

 

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".

 

 

TheVambrony is right, we're literally saying that nothing was messed up and everything was working fine. I think I may have said that almost word for word even. Everything that's "conflicting" is being automatically resolved because there's a default load order in place based on the order you install mods.

 

Literally everything was working fine days ago, and suddenly I'm not allowed to play something I own because a third party says so. Unless you search hard for NMM, you're not going to find it because it's not supported anymore, and the last version I had wouldn't let me uninstall mods even.

 

If Vortex is dictating whether or not I am allowed to play what I paid for, I'm not going to support it.

[AugustaCalidia]

Well, this thread has become quite entertaining. We have some who complain that Vortex has no right to prevent them from playing a game that they paid good money for. We have others who complain that Vortex has no big, red workaround button labeled "Damn the mod conflicts, full speed ahead!" (to paraphrase U.S. Admiral David Farragut). Presented with these original thinkers, I eagerly await their next round of creative complaints.

 

P.S.: There is a way to go around unsolved mod conflicts, but it's known only to a privileged few. :smile:

[CryoticShell]

Well, this thread has become quite entertaining. We have some who complain that Vortex has no right to prevent them from playing a game that they paid good money for. We have others who complain that Vortex has no big, red workaround button labeled "Damn the mod conflicts, full speed ahead!" (to paraphrase U.S. Admiral David Farragut). Presented with these original thinkers, I eagerly await their next round of creative complaints.

 

P.S.: There is a way to go around unsolved mod conflicts, but it's known only to a privileged few. :smile:

 

Again, the only conflicts are texture conflicts that resolve themselves because of the load order already in place. Mere days ago I had the exact same number and exact same conflicts, and Vortex wasn't doing this.

[Grestorn]

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.

[Guest deleted34304850]

.

[sopmac45]

This is off the chart ... I guess is getting better by the minute and I am so grateful to belong to the "privileged elite of a few with access to Vortex' secrets" not everybody have ( as Augusta Calidia well said it ... ) and also because I have been enlightened to be wise like a genius which is the opposite to be ignorant ( as 1ae0bfb8 well said it ... ) ... :laugh:

 

... unbelievable !!! :ohmy:

 

... what's next ? Probably that Vortex is infecting their PC with a Trojan Horse virus !! :sick:

[Tannin42]

 

@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.

 

Well, one problem with that is: If the auto-derived order is wrong then it is actually Vortexes fault when things go wrong because it would really just be guessing.

The other thing is: Vortex is built to do things in batches, e.g. as a premium user you can have up to 3 parallel downloads - small files finish first so if you start downloading and then install a large mod and patches at the same time, the patches will be finished first and then the auto derived order based on install order is exactly wrong.

 

I'm currently working on making suggestions based on file time (the original time when the author packed the mod), so if all files in mod a are newer than all files in mod b then Vortex will suggest the "load mod a after mod b" option, assuming that a patch/option will be newer than the main file and if they are independent mods the newer mod might have been made compatible with the older one but certainly not the other way around.

Still, we don't have a loot for mod order (yet) where the community had the opportunity to fix the cases where the algorithm goes wrong so it still has to be decided by the user.