A bad week with Skyrim mods taught me a cheap lesson

Honestly, last Tuesday I spent like 4 hours trying to get a simple texture pack to work for Skyrim, and it kept crashing my game. Turned out I had two mods editing the same mountain mesh in Riverwood, and Vortex wasn't flagging the conflict. Has anyone else wasted a whole evening on a dumb conflict that a quick load order tweak could fix?

2 comments

2 Comments

anthony12716d ago

Dude, same thing happened to me with a grass mod and tree replacer.

noahchen16d ago

Oh man, I feel your pain but you gotta check Vortex again. It actually does flag conflicts by default in the little lightning bolt icon on the mod tab. Not saying it's perfect or anything, but it'll show you red warning signs if two mods touch the same files. The trick is you gotta actually click into the mod and look at the "Conflicts" section on the right side panel, it lists every single file that's being overwritten. Sounds like you mightve been looking at the wrong section or had the filter set to hide conflicts. I wasted a solid night on the same thing with a water mod and a lighting overhaul before I realized Vortex was telling me the whole time, I just wasnt looking in the right place. Once you get used to where it hides that info it's actually not that bad for sorting stuff out.