Sorry for the necro, but somehow, unbeknownst to me, my mod set the maxheightdata in the Tamriel worldspace--to a number which comes into conflict with other masters. I'm thinking at some point I picked up the Max Height Data from Dawngaurd, and later when the mod added Dragonborn as a master, then that became the source of the conflict (assuming the two values are different, the first few numbers are the same, in hex it looks like, but there is a lot of data). In any case it was red flagged by TESVedit. Since I'm cleaning up the dirty edits, I deleted the MaxHeightData since my mod has no reason to be involved with such a thing. The red flag remained with the field left blank. So I copied the information from Dragonborn, to my mod, and the TESVedit flag went from red to yellow. I still wish the max height data remained untouched, but I can live with yellow.
Appreciate the effort here, but this really isn't doing much of anything.
This MHDT data is speculated to have something to do with dragon height data. Telling them where they can and can't fly while airborn. Sort of serving as their navmesh. There is no solid proof of this though.
Here's the thing. If this was true at all, this would have been discovered within hours of Dawnguard's initial release since it's the first DLC to introduce this field. There are no widespread reports of people being unable to access Castle Volkihar by way of the boat. There are no widespread reports of people getting thrown back to Solstheim trying to return to Windhelm. There are a scattered few incidents of both of these that can be traced back to misunderstanding what an ILS is.
The scenario you are describing where you get the load screen but are thrown back is EXACTLY what I've found to happen through my own testing when the game borders are wrong. Or when you attempt to fast travel to a map marker that exists outside of them.
With thousands of mods in the game not forwarding this data (because why would they - it requires DLC) there is no way that it being missing is going to matter. Every mod would break the game. Bethesda's own DLC would break the game, because Dragonborn's MHDT data will clearly not be taking Dawnguard into account, and vice-versa. So just the mere presence of Dragonborn in the game should cause Castle Volkihar to get blocked.
And before someone says this can only be corrected for PC with mods, stop and think. The consoles are using all of the same data files we are. Beth's forums and tech support would be awash in complaints if this data had the effect that's being claimed here. They have no means to patch their games on consoles.
what is then not allowing me to reach DLC1VampireIsland with Real Shelter ? as soon as I de check it in Launcher I can travel there ... haven't reached it yet on my new playthrough ...
I have in fact noticed this in quite a bit of mods, ranging from old to new, but I never truly understood what the significance behind this value was. Beyond your explanation that an incorrect Max Height Data hinders access to Dayspring Canyon and the like, is there a more in-depth explanation for this value available that I can refer to?
EDIT: And it would seem that a lot of my loaded mods (besides 2 that I had manually fixed this in) were blanking out Max Height Data. Endorsement for you as having this at the end of the load order solves this handily.
Though I will point out that apparently I was running with a blanked Max Height Data and I was accessing Dayspring Canyon and such fine. Wonder how that works.
"Endorsement for you as having this at the end of the load order solves this handily." Should I even place this mod after Bashed Patch and/or ASIS (ASIS is behind bashed patch) ?
in second TESVed screenshot you can see in my mod list that Realshelter is the last one to edit MHDT data. What I would say is : yes, ignore conflicts for MHDT through mods. And, no, don't ignore blank value for last data that modifies it.
Actually, it would be nice if someone knowledgeable did full list of records that can be safely ignored because they are merged at runtime in the game and doesn't causes conflicts. When forwarding changes in TES5Edit I am many times left in dark whether to forward something or not. So far I have found this list but it is hardly complete:
I really, but really don't know how does MHDT affect some locations, but, I noticed that with Real Shelter enabled I cant acces Castle Volkihiar and Dayspring Canyon. I have Fast Travel Enabled but don't use it at all (Frostfall - manage fast travel = 0), so, after discovering TES5Edit and learning how to use it I started digging and found out that Real Shelter modifies MHDT value for Block 3C (Tamriel World) and made this little patch. I'm unsure is it the right thing done, since I don't really remember did I travel to such places yet (again, not using fast travel, starting new characters with some new mods installed). Anyway, I hope this does help you in terms reaching those lands if U're using Real Shelter, Quaxes WInterhold Rebuilt, Coins Of Tamriel and such.
In my opinion, mods that don't affect wheather shouldn't silently overwritte MHDT, but, some do.
blattgeist: well, I haven't noted any problems in Windhelm (so far) and if I do, I'll be back on digging, even for MHDT.
bottom of loading order, nothing behind it if U're doing a merged patch, be sure that this file dominantes. It contains only Header data of block 3C, so no subblocks are affected by it.
EDIT: if U can't acces Dayspring Canyon (have your vision black-blured when trying to acces it via cave) or have a glitch with Ice watter jetty when placed before bashed patch, then yes.
Following that logic, ALL mods ever created for Skyrim that modify exteriors are broken since CK never propagates those values in plugins, which is highly unlikely.
not really, much modds contain 3C MHDT and don't allow such things, since most modds are made for Dawnguard / Dragonborn, and allready contain MHDT for 3C
21 comments
This MHDT data is speculated to have something to do with dragon height data. Telling them where they can and can't fly while airborn. Sort of serving as their navmesh. There is no solid proof of this though.
Here's the thing. If this was true at all, this would have been discovered within hours of Dawnguard's initial release since it's the first DLC to introduce this field. There are no widespread reports of people being unable to access Castle Volkihar by way of the boat. There are no widespread reports of people getting thrown back to Solstheim trying to return to Windhelm. There are a scattered few incidents of both of these that can be traced back to misunderstanding what an ILS is.
The scenario you are describing where you get the load screen but are thrown back is EXACTLY what I've found to happen through my own testing when the game borders are wrong. Or when you attempt to fast travel to a map marker that exists outside of them.
With thousands of mods in the game not forwarding this data (because why would they - it requires DLC) there is no way that it being missing is going to matter. Every mod would break the game. Bethesda's own DLC would break the game, because Dragonborn's MHDT data will clearly not be taking Dawnguard into account, and vice-versa. So just the mere presence of Dragonborn in the game should cause Castle Volkihar to get blocked.
And before someone says this can only be corrected for PC with mods, stop and think. The consoles are using all of the same data files we are. Beth's forums and tech support would be awash in complaints if this data had the effect that's being claimed here. They have no means to patch their games on consoles.
EDIT:
And it would seem that a lot of my loaded mods (besides 2 that I had manually fixed this in) were blanking out Max Height Data. Endorsement for you as having this at the end of the load order solves this handily.
Though I will point out that apparently I was running with a blanked Max Height Data and I was accessing Dayspring Canyon and such fine. Wonder how that works.
Should I even place this mod after Bashed Patch and/or ASIS (ASIS is behind bashed patch) ?
Search for "general patch". But your mod is a nice method to make people aware of the issue
I noticed that I have at least 5 mods that alter the MHDT for WindhelmWorld. Should we maybe do the same for that record too?
http://wiki.step-project.com/STEP_Patches_for_Packs
When forwarding changes in TES5Edit I am many times left in dark whether to forward something or not. So far I have found this list but it is hardly complete:
http://forum.step-project.com/topic/4468-tes5edit-which-record-types-dont-need-conflict-patches/
In my opinion, mods that don't affect wheather shouldn't silently overwritte MHDT, but, some do.
blattgeist: well, I haven't noted any problems in Windhelm (so far)
Is that true? I always wondered about mods setting XCLW and MHDT to 0 or default.
if U're doing a merged patch, be sure that this file dominantes. It contains only Header data of block 3C, so no subblocks are affected by it.
EDIT:
if U can't acces Dayspring Canyon (have your vision black-blured when trying to acces it via cave) or have a glitch with Ice watter jetty when placed before bashed patch, then yes.