Vortex Not Allowing Game to Start

[Guest deleted34304850]

.

[sopmac45]

I as one person, would prefer this "safeguard" removed or at least the option to ignore, coin flip method worked for me and as a casual mod player whos fallout 4 was playing fine until the latest update and now can't play though vortex or even use FINS in skyrim now didn't need this to happen, games played fine before and I really don't care enough to wanna deal with with 30 plus guessing of what goes where

 

 

If you just give yourself a chance to read, learn and trust Vortex, you will end up happy with Vortex. I am a casual mod player who plays with certain amount of mods ( I prefer quality not quantity ) and what I wanted with the new Nexus mod manager was, among other things, the capability for the mod manager to almost automate everything for me with minimal assistance from me and Vortex provided me exactly that.

 

I did not try to do things my way, but the way Vortex expected me to do. The problem is that you belong to a group of users that do not want to adapt to the new way Vortex is implementing modding and load ordering a game and instead, you want to do it your own way. And the other problem is that you belong to a group that do not want to read, learn and apply exactly what dozens of procedures ( already in place ) are advising everybody to do, to be successful with Vortex.

 

You have 2 options : go back to your previous mod manager or stay with Vortex. If you decide to stay, then remember something : read, learn, trust and apply exactly what the instructions are saying. Try to do something different and you will be end up very frustrated and blaming Vortex.

[TheVambrony]

 

I as one person, would prefer this "safeguard" removed or at least the option to ignore, coin flip method worked for me and as a casual mod player whos fallout 4 was playing fine until the latest update and now can't play though vortex or even use FINS in skyrim now didn't need this to happen, games played fine before and I really don't care enough to wanna deal with with 30 plus guessing of what goes where

 

 

If you just give yourself a chance to read, learn and trust Vortex, you will end up happy with Vortex. I am a casual mod player who plays with certain amount of mods ( I prefer quality not quantity ) and what I wanted with the new Nexus mod manager was, among other things, the capability for the mod manager to almost automate everything for me with minimal assistance from me and Vortex provided me exactly that.

 

I did not try to do things my way, but the way Vortex expected me to do. The problem is that you belong to a group of users that do not want to adapt to the new way Vortex is implementing modding and load ordering a game and instead, you want to do it your own way. And the other problem is that you belong to a group that do not want to read, learn and apply exactly what dozens of procedures ( already in place ) are advising everybody to do, to be successful with Vortex.

 

You have 2 options : go back to your previous mod manager or stay with Vortex. If you decide to stay, then remember something : read, learn, trust and apply exactly what the instructions are saying. Try to do something different and you will be end up very frustrated and blaming Vortex.

 

 

yeah, going back, the only thing that I prefer about vortex is that its really good organizing plug ins, but as far as MO2 goes, I don't know what im doing but im able to idiot savant things into working, ive played a maxed out mod list and its worked fine, and its really stupid when instead of just overwriting the file as I install with a prompt like "overwrite this picture frame from this other mod by the same dude cuz its the same in this mod as the other one" but now I gotta do all this after redownloading 200 mods(I prefer quantity and world rebuilding) and theres 91 things I gotta go though, and the I get mod circles or whatever, no, in this case im the old man yelling at clouds, give me my flip phone over this smart phone, im sure its great for most everyone but I want deal with the devil I know, just sucks that im gonna have to restart everything again

[TheVambrony]

 

I as one person, would prefer this "safeguard" removed or at least the option to ignore, coin flip method worked for me and as a casual mod player whos fallout 4 was playing fine until the latest update and now can't play though vortex or even use FINS in skyrim now didn't need this to happen, games played fine before and I really don't care enough to wanna deal with with 30 plus guessing of what goes where

 

If the coin flip method worked for you in the past, then apply it here to Vortex. You don't have to do any guessing - just randomly pick any file overwrite option until you've completed your "thirty plus guessing of what goes where." Then start your game. Doing this is no different in principle from what you did in the past when a mod manager would ask you to choose what mod will overwrite what mod. The only difference with Vortex is that you're being asked to make that choice after you've installed your mods and not while you're installing your mods.

 

If you like flipping coins when deciding file overwrites, then you should love Vortex. Vortex would allow you to flip coins all day long without having to uninstall and reinstall a mod every time you flipped the coin! :smile:

 

Seriously, though, coin flipping for mods is a haphazard approach and dangerous to the health of your game. I absolutely do not recommend it.

 

 

ok, but lets say im downloading nearly everyone of say, the jk-skyrim and t'skyrim land mods that can work together, and oops, now they want me to mess with like 25 things and figure out how "order" the files, except, most of the issues are just like, picture frames that are the same thing and that's why they conflict, can't the thing be made to deal with that?

[CryoticShell]

The dialogue addressing unsolved file conflicts is a safeguard function of Vortex.

 

Vortex informs you when you have unsolved file conflicts and prompts you to address them before you start your game. All you would do by running the game from outside Vortex would be ignoring an issue in your mod load order and flip a coin as to how that conflict will be handled by the game.

 

It is much more preferable to actually proceed to address the file conflict in question in Vortex. This part of the documentation explains how: https://wiki.nexusmods.com/index.php/Managing_File_Conflicts

 

 

File conflicts have to be resolved. They have to be resolved in NMM. They have to be resolved in MO. They have to be resolved in Wrye Bash and they have to be resolved when you manually install a mod.

The only difference is that with Vortex you can resolve the conflict at any time between installing a mod and running the game instead of being forced to resolve them immediately when installing the mod, so that you can install mods in batches and then resolve the conflicts afterwards.

 

If you think you want to run the game with unresolved file conflicts or that that is sensible then you have misunderstood what "file conflict" means.

If "start the game outside vortex so you can run without resolving file conflicts" catches on as a workaround, all that does is force us to remove this convenience entirely. That's not helping anyone.

 

I kind of have to call out both of these replies. As of mere days ago, I could play Skyrim SE just fine with the conflicts I had. All of them are texture conflicts, and my game ran just fine as they were with absolutely zero issues. As of right now, I'm apparently not allowed to play Skyrim SE without resolving the issues that aren't causing any issues in the first place. The load order is already perfectly fine, there's no reason for me to manually tell it to do what it's already doing.

 

EDIT: I should at least be able to tell Vortex "hey no everything here works fine, they just think they conflict because of technicalities" or something like that so that I can still play my game in this situation.

[TheVambrony]

 

The dialogue addressing unsolved file conflicts is a safeguard function of Vortex.

 

Vortex informs you when you have unsolved file conflicts and prompts you to address them before you start your game. All you would do by running the game from outside Vortex would be ignoring an issue in your mod load order and flip a coin as to how that conflict will be handled by the game.

 

It is much more preferable to actually proceed to address the file conflict in question in Vortex. This part of the documentation explains how: https://wiki.nexusmods.com/index.php/Managing_File_Conflicts

 

 

File conflicts have to be resolved. They have to be resolved in NMM. They have to be resolved in MO. They have to be resolved in Wrye Bash and they have to be resolved when you manually install a mod.

The only difference is that with Vortex you can resolve the conflict at any time between installing a mod and running the game instead of being forced to resolve them immediately when installing the mod, so that you can install mods in batches and then resolve the conflicts afterwards.

 

If you think you want to run the game with unresolved file conflicts or that that is sensible then you have misunderstood what "file conflict" means.

If "start the game outside vortex so you can run without resolving file conflicts" catches on as a workaround, all that does is force us to remove this convenience entirely. That's not helping anyone.

 

I kind of have to call out both of these replies. As of mere days ago, I could play Skyrim SE just fine with the conflicts I had. All of them are texture conflicts, and my game ran just fine as they were with absolutely zero issues. As of right now, I'm apparently not allowed to play Skyrim SE without resolving the issues that aren't causing any issues in the first place. The load order is already perfectly fine, there's no reason for me to manually tell it to do what it's already doing.

 

EDIT: I should at least be able to tell Vortex "hey no everything here works fine, they just think they conflict because of technicalities" or something like that so that I can still play my game in this situation.

 

 

this guy

[Guest deleted34304850]

.

[CryoticShell]

 

 

The dialogue addressing unsolved file conflicts is a safeguard function of Vortex.

 

Vortex informs you when you have unsolved file conflicts and prompts you to address them before you start your game. All you would do by running the game from outside Vortex would be ignoring an issue in your mod load order and flip a coin as to how that conflict will be handled by the game.

 

It is much more preferable to actually proceed to address the file conflict in question in Vortex. This part of the documentation explains how: https://wiki.nexusmods.com/index.php/Managing_File_Conflicts

 

 

File conflicts have to be resolved. They have to be resolved in NMM. They have to be resolved in MO. They have to be resolved in Wrye Bash and they have to be resolved when you manually install a mod.

The only difference is that with Vortex you can resolve the conflict at any time between installing a mod and running the game instead of being forced to resolve them immediately when installing the mod, so that you can install mods in batches and then resolve the conflicts afterwards.

 

If you think you want to run the game with unresolved file conflicts or that that is sensible then you have misunderstood what "file conflict" means.

If "start the game outside vortex so you can run without resolving file conflicts" catches on as a workaround, all that does is force us to remove this convenience entirely. That's not helping anyone.

 

I kind of have to call out both of these replies. As of mere days ago, I could play Skyrim SE just fine with the conflicts I had. All of them are texture conflicts, and my game ran just fine as they were with absolutely zero issues. As of right now, I'm apparently not allowed to play Skyrim SE without resolving the issues that aren't causing any issues in the first place. The load order is already perfectly fine, there's no reason for me to manually tell it to do what it's already doing.

 

EDIT: I should at least be able to tell Vortex "hey no everything here works fine, they just think they conflict because of technicalities" or something like that so that I can still play my game in this situation.

 

you're calling out the author and the support who are posting the real, correct and factual reasons why this is a thing?

you, my friend have got some stones! much love.

 

 

Yes, I am, because there's no reason I should be locked out of something I bought that I didn't buy from them because their program doesn't like something, and it's worse when they say "no don't use a workaround" because that's basically deciding if someone who's a total stranger to you is allowed to use something they bought.

 

Texture mods conflict, yes, because they work with the same things, but this doesn't break the game, especially when they automatically sort the issue out themselves and have been for months. NMM never had this issue. NMM never locked you out of something you purchased because it felt like it.

[TheVambrony]

 

 

The dialogue addressing unsolved file conflicts is a safeguard function of Vortex.

 

Vortex informs you when you have unsolved file conflicts and prompts you to address them before you start your game. All you would do by running the game from outside Vortex would be ignoring an issue in your mod load order and flip a coin as to how that conflict will be handled by the game.

 

It is much more preferable to actually proceed to address the file conflict in question in Vortex. This part of the documentation explains how: https://wiki.nexusmods.com/index.php/Managing_File_Conflicts

 

 

File conflicts have to be resolved. They have to be resolved in NMM. They have to be resolved in MO. They have to be resolved in Wrye Bash and they have to be resolved when you manually install a mod.

The only difference is that with Vortex you can resolve the conflict at any time between installing a mod and running the game instead of being forced to resolve them immediately when installing the mod, so that you can install mods in batches and then resolve the conflicts afterwards.

 

If you think you want to run the game with unresolved file conflicts or that that is sensible then you have misunderstood what "file conflict" means.

If "start the game outside vortex so you can run without resolving file conflicts" catches on as a workaround, all that does is force us to remove this convenience entirely. That's not helping anyone.

 

I kind of have to call out both of these replies. As of mere days ago, I could play Skyrim SE just fine with the conflicts I had. All of them are texture conflicts, and my game ran just fine as they were with absolutely zero issues. As of right now, I'm apparently not allowed to play Skyrim SE without resolving the issues that aren't causing any issues in the first place. The load order is already perfectly fine, there's no reason for me to manually tell it to do what it's already doing.

 

EDIT: I should at least be able to tell Vortex "hey no everything here works fine, they just think they conflict because of technicalities" or something like that so that I can still play my game in this situation.

 

you're calling out the author and the support who are posting the real, correct and factual reasons why this is a thing?

you, my friend have got some stones! much love.

 

 

hey, all he's saying is that there should be the option to f up your game if that's your purgative, it was there in the last version, and so far now 2 have said their stuff works/was working, just add a disclaimer saying if you chose to ignore this don't b...h if your mods don't work...id be fine with that and wouldn't even be here if this hadn't become a thing...

[TheVambrony]

 

 

 

The dialogue addressing unsolved file conflicts is a safeguard function of Vortex.

 

Vortex informs you when you have unsolved file conflicts and prompts you to address them before you start your game. All you would do by running the game from outside Vortex would be ignoring an issue in your mod load order and flip a coin as to how that conflict will be handled by the game.

 

It is much more preferable to actually proceed to address the file conflict in question in Vortex. This part of the documentation explains how: https://wiki.nexusmods.com/index.php/Managing_File_Conflicts

 

 

File conflicts have to be resolved. They have to be resolved in NMM. They have to be resolved in MO. They have to be resolved in Wrye Bash and they have to be resolved when you manually install a mod.

The only difference is that with Vortex you can resolve the conflict at any time between installing a mod and running the game instead of being forced to resolve them immediately when installing the mod, so that you can install mods in batches and then resolve the conflicts afterwards.

 

If you think you want to run the game with unresolved file conflicts or that that is sensible then you have misunderstood what "file conflict" means.

If "start the game outside vortex so you can run without resolving file conflicts" catches on as a workaround, all that does is force us to remove this convenience entirely. That's not helping anyone.

 

I kind of have to call out both of these replies. As of mere days ago, I could play Skyrim SE just fine with the conflicts I had. All of them are texture conflicts, and my game ran just fine as they were with absolutely zero issues. As of right now, I'm apparently not allowed to play Skyrim SE without resolving the issues that aren't causing any issues in the first place. The load order is already perfectly fine, there's no reason for me to manually tell it to do what it's already doing.

 

EDIT: I should at least be able to tell Vortex "hey no everything here works fine, they just think they conflict because of technicalities" or something like that so that I can still play my game in this situation.

 

you're calling out the author and the support who are posting the real, correct and factual reasons why this is a thing?

you, my friend have got some stones! much love.

 

 

Yes, I am, because there's no reason I should be locked out of something I bought that I didn't buy from them because their program doesn't like something, and it's worse when they say "no don't use a workaround" because that's basically deciding if someone who's a total stranger to you is allowed to use something they bought.

 

Texture mods conflict, yes, because they work with the same things, but this doesn't break the game, especially when they automatically sort the issue out themselves and have been for months. NMM never had this issue. NMM never locked you out of something you purchased because it felt like it.

 

 

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