MadWizard25

Already did. Everything looks good in WB. Tes5edit loads it without missing master complaints, and check for errors finds no unresolved references. Tried cleaning and sorting masters, no dice. Real head scratcher

Its theoretically a good idea, unfortunately my conflict resolution patch is about twice the size of Neo's, making that an extremely daunting task.

I have been building a custom conflict resolution patch based on the SR:LE one (downloaded). It was working great until recently. Now whenever I have the patch enabled, Skyrim will crash at the start screen. The dragon logo appears, but right before it starts spinning and the menu text should come up, the game CTDs. I cant track down the error, I made too many edits to be sure which one it is. I tried creating versions of the patch where I deleted 1 group, such as Activators or Worldspace, etc. This didnt help. Which either means something wrong in 2 or more groups, or something else that I dont know about or is subtle. If its an issue in 2 or more of the groups, Its way too hard to track down by process of elimination. The CTD type is indicative of a missing master, but as far as i can tell I have no missing masters, or unresolved references. Would anybody have an idea how I broke my conflict resolution patch?

Probably because I have not gotten past Whitrun for play testing

Does anyone else have clipping/ floating objects in Whiterun with Wet and Cold holidays and REGS? I have a flags and ropes outside bannered mare that slope up into the sky with no support. Is this something I can only fix with the CK?

I get those as well, would be good to know. Ive been deleting them, but maybe i shouldnt?

You can ignore MO warnings, apparently they are false positives? Unless its about the overwrite folder

REGS pack/ ETaC would be incompatible for sure since it changes building positions. Shame, because ive been waiting for something like this

Huh, I thought your were STEP only I run ugrids 7, however I believe my script overload is a result from being 100 plugins over the 255 limit, some of them script intensive. I was getting stack dumps and thrashing. Doubling pap ini values solved it, at the cost of 3 fps give or take. Yeah, load order was a pain. I dropped BOSS for LOOT though, ill see how that goes. Need far less rules. Additionally I have a huge conflict resolution patch, so as long as thats last all should be golden. Makes troubleshooting and fixing much easier as well with tesedit. Edit: Argh, still get stack dumps, just much later

Well, seems AOS 2 fixed bird script error, and the masseffectfielf from requiem is harmless, happens due to unloaded NPCs from other mods. Great I think I have managed to almost fix everything obvious. Running 350 plugins requires some serious papyrus ini setting modification though, default values cant handle the script load, requiem pushes it right over the edge

I have been using LOOT the past two days. As far as I can tell it works fine. The load order is radically different from BOSS. I have had some issues with incorrectly placed plugins, but it requires far less maintenance since i dont need to make dozens of BUM userlist rules. I like the lesser priority option, which drops plugins earlier in the load order. No more userlist rules unless a plugin has to go right after another. What was surprising is that LOOT tells you what plugins it finds that conflict. Well it found about 6, but I know from tes5edit that I have many more conflicting plugins, so Im not sure what LOOT is doing. In any case, so far so good. Then again I have not gotten past Riverwood and Whiterun yet, and am still doing vurts stress test. I haven't been able to test the particulars of my mod load order.

Ok, ill update AOS when step 2.2.9 is out. The mass effect is definitely a requiem script. However, I cant find reference to it at all in tes5edit. REQ_ are all requiem based. Im currently going through pap log to solve errors, and i have been able to find everything else referenced and fixed some of them, so odd...

Been testing STEP Extended + SR:LE + REGS + Requiem + Additional mods. I found that the sheer number of scripts was causing stack dumps and i guess as a result CTDs. I bumped my papyrus values and it solved the issue. I didnt raise the values much higher. My papyrus is spamming; [04/01/2014 - 11:15:11PM] Error: Unable to call RegisterForUpdate - no native object bound to the script object, or object is of incorrect typestack:[None].REQ_MassEffectField.RegisterForUpdate() - "<native>" Line ?[None].REQ_MassEffectField.onBeginState() - "REQ_MassEffectField.psc" Line ?[None].REQ_MassEffectField.GotoState() - "ActiveMagicEffect.psc" Line ?[None].REQ_MassEffectField.OnObjectUnequipped() - "REQ_MassEffectField.psc" Line 20 and 04/01/2014 - 11:03:12PM] Error: Unable to set the sound's positionstack:[ (000BCD35)].Sound.Play() - "<native>" Line ?[ (0010C334)].FXBirdFleeSCRIPT.OnCellAttach() - "FXBirdFleeSCRIPT.psc" Line 17[04/01/2014 - 11:03:13PM] Error: Unable to set the sound's positionstack:[ (000BCD35)].Sound.Play() - "<native>" Line ?[ (0010C334)].FXBirdFleeSCRIPT.OnLoad() - "FXBirdFleeSCRIPT.psc" Line 26 I noticed Nicopad had these logs as well. Has anyone worked out what they are?

Moving Moon and Star mod earlier than SDO has fixed the blue roof LOD issue. Cleaning quest_pitfighter.esp also solved the minor minor conflict issue reported in tes5edit. Definitely screwed up my REGS install at some point, thankfully was pretty minor. Now everything REGS related is fixed! Thanks everyone

This looks interesting. Im setting up a play through with Requiem. Depending on how difficult I find it, I might use this to give me an edge. Will have to experiment with AOS 2.0, mix and match. I can see myself retaining some AOS atmospherics, like rockfalls and animal calls, and removing the rest, then using this mod to remove vanilla soundtracks. Thanks!

Good idea, ill try to make my brain memorize that.

Doh, yeah, I meant ill move them up the list. I think I need a break.

Alrighty, ill move the 13 oranges mods down. Cheers. This is worrisome. I know I cleaned the esp, as per the guide. Which means it reverted, or didnt save. This coupled with the post on nexus by the Moon and Stars author regarding the LOD issue being fixed by moving SDO after Moon and Stars (which didnt work for me), makes me suspect that somewhere along the line I rolled back my mod setup. No idea how. Im gonna have to double check my REGS install.

MoonAndStar_MAS.esp Worldspace 0001691D <WindhelmWorld> 0001691F Persistent 0001696E Or just 0001696E :P quest_pitfighter.esp overrides MoonAndStars_MAS.esp in my load order (using LOOT). I guess its not a conflict per say, but moon and stars has a VMAD record, while pit fighter has nothing. I just noticed that I dont have the latest version, still on 1.03. Dont know if 1.04 changes this. Ill update in a bit and check. So in regards to Layers, I should not bother with them for conflict resolution? I can add that to my list of records not to bother with if thats the case

Im running ugrids 7. Thanks for the info, I will edit my post on the nexus page I appreciate you checking the nexus forums CJ2311, thats twice you have saved me from either looking like an idiot or spreading erroneous information. Ta! :: Would it possible for to give me quick description of the Layers records, like VTXT, ATXT, etc. I tried google search but nada. The UESPWiki Tes5 record page has nothing either. Now that the merge script issue is solved im creating my conflict resolution patch, and it would be nice to know what Layers does. Edit: Can only conclude that if the issue is a conflict, then its not related to REGS or STEP Extended. That actually narrows it down quite a bit. Must be requiem (doubt it), or SR:LE, or perhaps one of the additional mods I added.

Yep, can confirm that mod load order does not solve this issue. Additionally moving the plugin to almost the end of my plugin list makes no difference either. Looking at the records in the esp I couldnt find anything either. Lots of worldspace edits, but nothing that would cause blue LODs. In any case, I posted the issue on the mods nexus page.

Ok, an update. I have gotten rid of the errors. Apparently, the merge script is sensitive to load order of the plugins to be merged in regards to their masters. All plugins to be merged MUST be moved after the last master they reference. By manually moving everything below 3DNPC.esp, the last master in the list of REGS patches, I merged the patches with Renumbering FormIDs, and hey presto, no unresolved references. In this case BOSS is not the answer. Unfortunately, this information was not available on the mods nexus description and instructions. All credits go to noobzor on the nexus forums for figuring this out. I have no idea why it happens, but its solved.

I am currently trying to merge mods using the Merge Plugins TES5Edit Script v1.6 by Mator. With some great help from the folks from the REGS thread, I have already done a little bit of troubleshooting, but as of yet the problem remains unresolved. I decided to post a new thread on the issue since the subject was a little off topic for the REGS thread. The script seems to have installed fine (tried twice already), it executes fine, and my Tes5edit is up to date. Currently I am trying to merge these mods, none which are masters and are therefore technically safe to merge; ETaC - Complete LoS Patch.esp ETaC - BFT Patch.esp REGS Patch - NSutR.esp REGS Patch - CRF.esp REGS Patch - ORS.esp REGS Patch - STEP Extended.esp REGS Patch - 3DNPC.esp The merge works fine. However, when reloading the merged plugin via tes5edit, and checking for errors, I get quite a few unresolved reference errors; I have tried with renumbering FormIDs and without, and the error results are the same. I have posted on the mods nexus thread, however, the author is currently irritated (assumes I am merging masters ), and has yet to respond to my follow up response, whenever that might be. I would really appreciate some help

Yeah, I have stayed away from script mods. So I have no worries there. Perhaps the only issue with scripts is the merged requiem patches, for example the BOYD patch. Your right, this is better suited to a new thread. I will open one shortly if I cannot resolve the issue, thanks for the help Edit: Thanks CJ2311, ill fix that on the forum thread asap. Edit: Edit: Only REGS patches, renumber FormID unchecked, and I still receive unresolved reference errors. Im gonna open up a new thread. Edit: Edit: Edit: New thread in support forum opened. I have posted the errors I get with and without renumbering FormIDs, if you gentlemen would be so kind as to take a look. Last edit, I promise

Oops, I assumed REGS patches equaled those mentioned in the REGS 3.2.2 packages, my mistake. Hmmm, well there goes my baseline for merging. I assumed that any type of patch would be fine. How can I determine what patches are possible to merge without trial an error? I made separate merges of requiem patches and another merge of additional mod patches with a few standalone mods with no scripts such as weapon and armor mods. I know they have unresolved references as well. I have yet to start playing so this is all good :) Weird, when I view the nexus forums it looks like the spoiler tags worked? Will try the merge minus the prometheus patches.