Vortex Not Allowing Game to Start

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

 

 

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.

 

 

I didn't change mod manager, Vortex was working fine a week before this issue started, and nothing changed since then.

 

 

 

 

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.

 

 

The issue with conflictions is that they actually DO resolve themselves and have been since I started using Vortex, and wasn't once notified of anything more than "oh these things do something similar"

 

 

 

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.

 

this is hilarious. One MASSIVE thing changed, you transitioned to Vortex.

 

You ARE aware of that, right? It seems you're not aware of a lot, but you surely must be aware that you decided, off your own back, to use Vortex, and you haven't read up on what you need to do to transition correctly, nor have you read up about what a mod conflict is, what it means, how YOU need to fix it, you've instead, spent days crying about a conflict and blaming everyone but yourself.

 

By now, I am, rather heartlessly, laughing at your self-inflicted predicament and your absolute refusal to do anything to fix it, except to attack Vortex, and attack anyone who gives you the time of day to help you to try and fix it.

 

BTW - all this "legally own" crap is 100% irrelevant. If you want to use the game you "legally own" then learn to mod it properly, using a mod manager you can understand, or don't mod it at all. (I think I may have said that previously).

 

 

Yet again, you're refusing to actually read what I'm saying. I've said multiple times that Vortex was working fine and then suddenly it isn't. I clearly was using Vortex before the issue started. I'm not "attacking" Vortex, and I'm not "attacking" anyone trying to help me, just asking that this gets fixed.

 

And, yet again, my mods were working perfectly and even though nothing changed over the course of a few days, the issue arose. You can't be any more ignorant of what I'm saying.

[Grestorn]

Well, ok, the only thing that could have changed is that you've installed a newer version of Vortex itself, because the check if there are still conflicts and to deny to start the game because of that, was just recently added, if I'm not mistaken.

 

That still doesn't change the fact that there are conflicts and that until you resolve them, your mods are just not properly installed.

[Tannin42]

 

 

The issue with conflictions is that they actually DO resolve themselves and have been since I started using Vortex, and wasn't once notified of anything more than "oh these things do something similar"

 

No they definitively don't. Just because you didn't get an error message before doesn't mean you didn't have an error before, that's like saying "My car doesn't have a warning light for the engine so the engine is indestructible".

We just added a warning light, we didn't introduce a new problem!

 

I wrote this mod manager, you will just have to trust me when I tell you that the conflicts weren't magically resolved on their own before this update. I know that because we're all out of magic pixie dust.

 

Look, I can't do anything but repeat one more time: If you believe that conflicts "resolved themselves" before then you do not understand what file conflicts are. Please, try to investigate what this is even about before you make your next post.

[TheVambrony]

 

 

 

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.

 

 

I didn't change mod manager, Vortex was working fine a week before this issue started, and nothing changed since then.

 

 

 

 

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.

 

 

The issue with conflictions is that they actually DO resolve themselves and have been since I started using Vortex, and wasn't once notified of anything more than "oh these things do something similar"

 

 

 

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.

 

this is hilarious. One MASSIVE thing changed, you transitioned to Vortex.

 

You ARE aware of that, right? It seems you're not aware of a lot, but you surely must be aware that you decided, off your own back, to use Vortex, and you haven't read up on what you need to do to transition correctly, nor have you read up about what a mod conflict is, what it means, how YOU need to fix it, you've instead, spent days crying about a conflict and blaming everyone but yourself.

 

By now, I am, rather heartlessly, laughing at your self-inflicted predicament and your absolute refusal to do anything to fix it, except to attack Vortex, and attack anyone who gives you the time of day to help you to try and fix it.

 

BTW - all this "legally own" crap is 100% irrelevant. If you want to use the game you "legally own" then learn to mod it properly, using a mod manager you can understand, or don't mod it at all. (I think I may have said that previously).

 

 

Yet again, you're refusing to actually read what I'm saying. I've said multiple times that Vortex was working fine and then suddenly it isn't. I clearly was using Vortex before the issue started. I'm not "attacking" Vortex, and I'm not "attacking" anyone trying to help me, just asking that this gets fixed.

 

And, yet again, my mods were working perfectly and even though nothing changed over the course of a few days, the issue arose. You can't be any more ignorant of what I'm saying.

 

 

im just remoding and going through and dealing with conflicts as I go instead of at the end, and if 2 of the exact same textures conflict im just gonna set them like they already are in the load order...