Vortex saying I have unsolved conflicts when there are none...

[SuzanoSho]

I have no actual notification of unsolved file conflicts. Every little lightning bolt is green. I've deployed several times to ensure nothing is being overlooked. Still no notification.

Anytime I click on one of the tools or try to start SKSE through Vortex, a toast message pops up saying that I have unsolved conflicts and that it may cause issues, blah blah, with only two options at the bottom of the window: "Cancel" and "Show"...

Clicking on "Show" closes the message window and does absolutely nothing else.
Clicking on "Cancel" closes the message window and does absolutely nothing else.

Going back to the mods tab reveals absolutely nothing new, everything seems to be in order.
Restarting Vortex does not solve the problem.

I can not start my game, Bodyslide, DynDoLOD, Outfit Studio, LOOT, SSEEdit, etc. from Vortex at all because of this message.

UPDATE: I seem to have gotten around it for now by closing Vortex, sorting with LOOT, and then opening Vortex again. I have not deployed mods with Vortex since doing so but at the very least I was able to use tools through Vortex.

[BigBizkit]

If I get this right Vortex prevented you from launching the game (and other tools) because it thought there are unresolved conflicts, but you are sure there weren't any? Clicking "show" did not bring up anything?

 

Which version of Vortex are you on?

 

Can you attach your log file?

 

1. Windows Key + R

2. type in %appdata% and hit enter

3. in the Vortex folder, grab the newest Vortex.log (you might need to rename it to txt to be able to attach it here).

[meyer10101]

There really needs to be a way to right click on the little orange bells and set Vortex to "ignore" them, preferably with an "ignore once" meaning that it would reset the "ignore" after Skyrim is launched/closed (for testing purposes) and a setting for "always ignore" where it will specifically ignore that .esm file for errors that prevent launching/running attached tools.

 

Heck, not letting tools like TES5edit or LOOT run when there is an error is already inconvenient.