Map is missing/bugged

[dbs_64]

When I open my map, it looks like this[i.imgur.com]. When I bring up the map, it's almost like the camera moves to look straight up and through some walls/ceiling.

This has happened before after I installed some new mods. I somehow fixed it by disabling the new mods one at a time until it worked. However, when I reenabled them, the map still worked. I didn't think twice about it and carried on.

Today, all I did was reinstall some old mods that weren't behaving properly (I just wanted my shield on my back!). Once I fixed the issue, I continued playing until I went to fast travel. That's when I noticed my map was gone again.

Disabling and reenabling the mods I messed with today fixed nothing. The same goes for deleting the .ini files in my Documents\My Games\skyrim folder. Looking for answers online only gets people asking for help with missing quest objectives or missing map textures. I'm hoping someone here might have an idea. I can't play without a working map :(

[BushiNeko]

If they were old misbehaving mods.. they are probably all out of date / conflicting. Once you activated them you dumped whatever is in the scripts / etc back in. LOOT and TESVed are no help for finding problems from orphan files...

You need to look at what you removed today.. and open your Skyrim Data folder and use search to look for any orphans that are most likely still in there.. That is most likely your suspect.. If you do that and it's still dorked.. then verify the cache. Deleting the .ini is a good fix..but also useless when dealing with orphans.. A lot of old or steam mods are terrible for leaving behind files...

[JDaremo Fireheart]

Install a map mod and see what that does

[dbs_64]

Installing a map mod was the first this I did the first time this happened, and it did nothing (although it was nice to have when the issue fixed itself).

As for looking for orphans and verifying the cache, how would I go about doing that? Sorry, when it comes to modding, I know just enough to be dangerous.

[dbs_64]

I forgot to mention all my mods are up to date. The mods I messed with today were Dual Sheath Redux, Immersive Animations, XPMSE, Realistic Ragdolls and Force, and FNIS. I've also used Wrye Bash, LOOT, and the patching programs for Dual Sheath Redux and FNIS. I have no idea how any of these could cause my map to disappear.

[BushiNeko]

Originally posted by dbs_64:

I forgot to mention all my mods are up to date. The mods I messed with today were Dual Sheath Redux, Immersive Animations, XPMSE, Realistic Ragdolls and Force, and FNIS. I've also used Wrye Bash, LOOT, and the patching programs for Dual Sheath Redux and FNIS. I have no idea how any of these could cause my map to disappear.

None of those would touch your maps in anyway. And I can say with all assurance I ve never heard of any issue like that with them.
Bash however.. if your using a patch that was made before removing the map mods you had before? Well... most likely its holding the bag.
I am still, just based on this accusing orphan files.

Best bet is to remove any Bash that had the old maps in them originally.
Verify the cache.
Then clean the DATA of orphans. ( which you really need to check for anytime you remove script or ' change ' making mods ) To clean orphans open your local Skyrim. Click on Data folder then in the folder search type in the name of the mod as shown on the ESP. IE Recorder. Then any files associated to the ESP will show if they are still lingering.

A lot of times orphans will be ignored in game.. but they eventually catch up to you. Either in still activating for a mod that should not even exist anymore, or simple save bloating. And we all know how that works out over time... :-p

[dbs_64]

I fixed it. Apparently I needed to build a fresh bashed patch in Wrye Bash from scratch. Rebuilding the old one wasn't enough. I also verified the cache, so I'm not sure if that had any effect, but the issue wasn't resolved until I rebuilt the bashed patch.

I'm just glad it worked. My next step would have been to reinstall Skyrim and all my mods from scratch. That would have taken several hours.

[BushiNeko]

Originally posted by dbs_64:

** Snip ** My next step would have been to reinstall Skyrim and all my mods from scratch. That would have taken several hours.

That is never, ever an option.. unless you realize you have completely.. and no way to fix it.. broken something. Which is pretty rare once you have done it once and learned about how the whole thing works together... Yeah. Thats why I pointed to removing your Bash if it was from the old.. thats just like salvaging a save with removed script mods.. you can do it.. but it ' aint ' usually going to work out well or pretty.

[Arsenyk]

For anyone coming across this post and still having this issue, I might have a fix for you, I posted it there : https://steamcommunity.com/app/72850/discussions/0/133256240730373255/

The issue is basically Wrye Bash setting the wrong values in Bashed Patch, 0.esp for still unknown reasons, but there is a quick way to fix it without rebuilding the patch.