Got a puzzling thing here I'm hoping you could maybe provide some insight into Blackread. I know below you told someone below this doesn't interact at all with Dyndolod (which makes complete sense), however when I run dyndolod it gives a warning saying the formID NPC_ 00000007 is being overwritten with a NAVM 00000007 from this plugin. I fired up xedit and sure enough, 00000007 is present as a navmesh record instead of NPC. That to me makes absolutely no sense as they're completely different record types. Dyndolod says this can cause CTD and not knowing more details myself I can definitely believe it. However, the form is referenced by some other Navmesh records in the plugin, and since 00000007 is well-known as the player record, I can't fathom this is a typo or oversight. Could you possibly explain what's going on here in more detail and how it *doesn't* cause a CTD? Since I don't see anyone else mentioning this here either I'm the first to encounter it or it's fine and everyone else just ignored the warning.
Would appreciate any clarification you could give.
You need to update your tools. DynDOLOD support for the extended form ID range was added in Alpha 157 and xEdit supports it starting with version 4.1.5b. Newest xEdit builds are available on Discord.
Your official masters must also have the new header version of 1.71 to resolve that issue, so you would need to update to the most recent 1.6.1170 version for this mod to work.
Edit: I misunderstood. Plugins with masters that are header version 1.71 should also have the same 1.71 header version to properly display new records in the extended ESL range.
I'm not entirely sure that's the case, but you should be using up-to-date data files anyway. The executable version doesn't matter as long as BEES is being used if on an older game version.
Thanks for the replies all. I am using the latest game version (1170) and the latest Dyndolod version which is alpha 169. I've confirmed that the main Skyrim and DLC files have 1.71 in the record header in xedit. Is there something else I could be doing wrong?
EDIT: I actually have a hunch as to what might be the issue...checking it out
Figured it all out. You were correct that my xedit was not up to date enough - I thought I was running 4.1.5b but I was only running 4.1.5. After download 4.1.5c the error goes away when I try loading just this plugin.
As for why the error was happening with Dyndolod, it ended up being a Synthesis patcher I had that I overlooked the first time since it just copied the record so I focused on where it was copying from which was this plugin. Throw in the bad xedit version and I came to the wrong conclusion.. Whatever that synthesis patcher is doing is messing things up so I disabled it, reran and now everything checks out.
Terribly sorry for dragging you into what turned out to be user error as always. I would delete my original post as to not spread any misinformation but I don't think I can. I'll instead refer to this post for anyone who comes along so they know it was all my fault.
Hello, I would like to report a question that I don't understandI found a strange situation when I was using LOOT sorting, as long as this mod order is higher than Separated Slash Effects X, it will cause CTD problems, if the loading order is lower than Separated Slash Effects X, it will not cause CTD,https://www.nexusmods.com/skyrimspecialedition/mods/99506?tab=filesHowever, Separated Slash Effects X has nothing to do with Bruma, but after several sorting attempts, it was determined that this mod had a sorting conflict
Separated Slash Effects doesn't edit any vanilla records, so it doesn't conflict with anything. Your issue is something else. What game version are you on? Do you have Backported Extended ESL Support?
Slightly controversial opinion, but stop using LOOT. You need to be able to understand your own load order yourself and how to properly sort it, or else conflicts and issues will arise or, worse even, LOOT will create issues of its own or lead you to believe the cause is something else. It has marginal use as a baseline sorter or for very controlled modlists that don't stray beyond the plugins it has up-to-date info for, but anything beyond beginner level modding will likely push it beyond its limits and from there on its output shouldn't be trusted. Like in this case, where it's coming up with almost certainly completely unrelated culprits to whatever real underlying CTD issue you have. It's a waste of your own time as well - any time you might've 'saved' by using LOOT will be lost in duplicate in troubleshooting the issues it causes or following its leads for other issues.
Use xEdit to look at the conflicts between those two mods, and compare them when you swap their load orders. You should see some kind of difference that is likely causing the crash.
I also got this error from loot, but I was gonna also assume it was a false positive? I know people don't like loot, but I kind of just view it as a foundation and then edit from there.
EDIT: I just realized this is probably due to the BEES ESL thing and should be disregarded. Will probably see a lot more of these eventually
Excellent job. I've heard that the Navmesh process is quite annoying, so kudos. I wonder if this fix and unofficial will be included when Beyond Skyrim - Cyrodiil is shared?
This is great. Finally some good news for Bruma. I thought that this was forever abandoned. Excellent. I never ceases to amaze me the amount of dedication that the community has for a 12+ y/o game. Subscribed. No wait...endorsed!!
Bruma itself is in maintenance mode, because the team is developing the main mod (Beyond Skyrim: Cyrodiil). But even Bruma got an official update a year ago, and apparently they are integrating some fixes from Beyond Skyrim - Bruma - Unofficial Patch in a future update, so it's not completely abandoned.
It doesn't conflict with my plugin, but it does have some minor conflicts with the Bruma Unofficial Patch by the same author, which is a requirement of my mod. But I think it should work out quite well if you just load the DBM patch after the unofficial one.
Hey Blackread, thanks so much for the hard work it sounds like this demanded - every time I see you it kinda seems like you're either helping someone troubleshoot some impossibly obscure bug, or providing amazing mods like this. Thanks for doing what you do. Also, as someone almost entirely unfamiliar with how the game handles meshes and navmeshes, I thought I'd ask whether you advise re-running DynDOLOD for the Bruma worldspace, or at all, after installing this? If a re-run is necessary, would we also need to include the Tamriel worldspace, considering Skyrim's side of the border was (I believe) also touched up by this mod?
37 comments
Got a puzzling thing here I'm hoping you could maybe provide some insight into Blackread. I know below you told someone below this doesn't interact at all with Dyndolod (which makes complete sense), however when I run dyndolod it gives a warning saying the formID
NPC_ 00000007is being overwritten with aNAVM 00000007from this plugin. I fired up xedit and sure enough, 00000007 is present as a navmesh record instead of NPC. That to me makes absolutely no sense as they're completely different record types. Dyndolod says this can cause CTD and not knowing more details myself I can definitely believe it. However, the form is referenced by some other Navmesh records in the plugin, and since 00000007 is well-known as the player record, I can't fathom this is a typo or oversight. Could you possibly explain what's going on here in more detail and how it *doesn't* cause a CTD? Since I don't see anyone else mentioning this here either I'm the first to encounter it or it's fine and everyone else just ignored the warning.Would appreciate any clarification you could give.
Edit: I misunderstood. Plugins with masters that are header version 1.71 should also have the same 1.71 header version to properly display new records in the extended ESL range.
EDIT: I actually have a hunch as to what might be the issue...checking it out
As for why the error was happening with Dyndolod, it ended up being a Synthesis patcher I had that I overlooked the first time since it just copied the record so I focused on where it was copying from which was this plugin. Throw in the bad xedit version and I came to the wrong conclusion.. Whatever that synthesis patcher is doing is messing things up so I disabled it, reran and now everything checks out.
Terribly sorry for dragging you into what turned out to be user error as always. I would delete my original post as to not spread any misinformation but I don't think I can. I'll instead refer to this post for anyone who comes along so they know it was all my fault.
Yes I have "Backported Extended ESL Support" installed (version 1.2)
I also got this error from loot, but I was gonna also assume it was a false positive? I know people don't like loot, but I kind of just view it as a foundation and then edit from there.
EDIT: I just realized this is probably due to the BEES ESL thing and should be disregarded. Will probably see a lot more of these eventually
Quick question, is this compatible with LOTD - Pale Pass Extension?
Regardless, thanks for all your work Blackread!