Program fails on Startup...

[AncientFireBeast]

Pastebin - https://pastebin.com/R3fxZxFd

Program starts, reads my modlist, gets to "Update" and then crashes. Says something about Calcelmo, but I don't know what any of it means.

I appreciate any help you're willing to give, thank you for the mod.

[focustense]

Quoting relevant part here:

2021-09-08 18:23:54.846 -05:00 [ERR] Exception was not handled
System.AggregateException: One or more errors occurred. (Specified argument was out of the range of valid values.)
 ---> RecordException  => Calcelmo (01338E:Skyrim.esm<Npc>): Specified argument was out of the range of valid values. System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
   at Noggog.ReadOnlyMemorySlice`1.Slice(Int32 start, Int32 length)
   at Mutagen.Bethesda.Plugins.Binary.Overlay.BinaryOverlayList.FactoryByCountPerItem[T](OverlayStream stream, BinaryOverlayFactoryPackage package, Int32 itemLength, Int32 countLength, RecordType subrecordType, RecordType countType, SpanFactory`1 getter, Boolean skipHeader)
   at Mutagen.Bethesda.Skyrim.Internals.NpcBinaryOverlay.FillRecordType(OverlayStream stream, Int32 finalPos, Int32 offset, RecordType type, Nullable`1 lastParsed, Dictionary`2 recordParseCount, RecordTypeConverter recordTypeConverter)
   at Mutagen.Bethesda.Plugins.Binary.Overlay.PluginBinaryOverlay.FillSubrecordTypes(OverlayStream stream, Int32 finalPos, Int32 offset, RecordTypeConverter recordTypeConverter, RecordTypeFillWrapper fill)
   at Mutagen.Bethesda.Plugins.Binary.Overlay.PluginBinaryOverlay.FillSubrecordTypes(IMajorRecordCommonGetter majorReference, OverlayStream stream, Int32 finalPos, Int32 offset, RecordTypeConverter recordTypeConverter, RecordTypeFillWrapper fill)   at Mutagen.Bethesda.Plugins.Binary.Overlay.PluginBinaryOverlay.FillSubrecordTypes(IMajorRecordCommonGetter majorReference, OverlayStream stream, Int32 finalPos, Int32 offset, RecordTypeConverter recordTypeConverter, RecordTypeFillWrapper fill)
   at Mutagen.Bethesda.Skyrim.Internals.NpcBinaryOverlay.NpcFactory(OverlayStream stream, BinaryOverlayFactoryPackage package, RecordTypeConverter recordTypeConverter)
   at Mutagen.Bethesda.Plugins.Records.Internals.GroupMajorRecordCacheWrapper`1.ConstructWrapper(Int32 pos)
   at Mutagen.Bethesda.Plugins.Records.Internals.GroupMajorRecordCacheWrapper`1.TryGetValue(FormKey key)
   at Focus.Providers.Mutagen.Analysis.GroupCache.LoadAll[T](IFormLinkGetter`1 link)+MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Focus.Providers.Mutagen.Analysis.GroupCache.<>c__DisplayClass9_0`1.<GetAll>b__0(FormKey _)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
   at Focus.Providers.Mutagen.Analysis.GroupCache.GetAll[T](IFormLinkGetter`1 link)
   at Focus.Providers.Mutagen.Analysis.GroupCacheExtensions.AllFrom[T](IFormLinkGetter`1 link, IGroupCache cache)
   at Focus.Providers.Mutagen.Analysis.GroupCacheExtensions.GetRelations[T](IGroupCache groups, IFormLink`1 link, String pluginName)
   at Focus.Providers.Mutagen.Analysis.NpcAnalyzer.Analyze(String pluginName, IRecordKey key)

This error actually comes from Mutagen, so it might not be something I'm able to fix in EasyNPC. I've never seen it before. However, we can probably narrow it down to the specific plugin or record. Can you go and grab version 0.9.3 from the releases page, and also turn on debug mode by adding -d to the command-line arguments?

Version 0.9.3. added the thread ID to logs, which should help identify which plugin generated the error, and debug mode may give more information about which records are being processed. You'll know if debug mode is enabled correctly because the log will say "Debug mode enabled" within the first few lines.

If you can post a log from v0.9.3 with debug mode on, I think it should have enough info to pinpoint the record.

[AncientFireBeast]

Log_20210908_195432_2787296.txt

Here's the log, I am going to be away from the computer for a few hours after this reply, so please forgive my absence.

I say again, thank you for the help, I really appreciate it, and thank you for the program. this really is one of those things that I'm sure thousands of people have been wanting for ages.

[focustense]

That log is still from v0.9.2, so it doesn't have the thread ID. It's sort of important to get that for this type of issue.

If you've been looking on Nexus, the release is not there yet. Only up on GitHub right now: https://github.com/focustense/easymod/releases/tag/v0.9.3

[AncientFireBeast]

Log_20210908_215450_2056868.txt
Here's the new log in debug mode through the newest version.

My apologies, had to jump through some hoops to find the 0.9.3 download page, never used GitHub before.

[focustense]

Thanks. What I'm seeing is, unfortunately, that the exception is being passed back to the main thread before being logged, so I'm not getting the information I'd hoped out of it (not your fault, though).

What I didn't notice the first time is that there actually is a bit more information in the nested exception here:

 ---> (Inner Exception #4) System.ArgumentException: Unexpected record type: COCT != PRKR
   at Mutagen.Bethesda.Plugins.Binary.Overlay.BinaryOverlayList.BinaryOverlayListByStartIndexWithRecord`1.get_Item(Int32 index)
   at Mutagen.Bethesda.Plugins.Binary.Overlay.BinaryOverlayList.BinaryOverlayListByStartIndexWithRecord`1.GetEnumerator()+MoveNext()
   at System.Collections.Generic.EnumerableHelpers.ToArray[T](IEnumerable`1 source, Int32& length)

The bottom line here is that one of your plugins has a corrupted Perks (PRKR) or Perk Count (PRKZ) subrecord, or just a corrupted NPC record in general. I'm pretty sure that any positive number should be valid for PRKZ, as well as zero, so this would mean it's seeing a negative number. Similarly, the second error is saying that it found a start-of-inventory (or "count-of-container", COCT) record where it was supposed to be seeing a perk record.

However, I'm not sure if I'd read too much into the specific errors here - that is, these errors are more consistent with random data corruption than a specific problem with the perks. Perks are just where it's first showing up.

I think the only thing to do at this point is to open up your load order in xEdit, find this NPC and check what's affecting it, paying particular attention to these two sub-records (perks and perk count). Most likely, xEdit is going to report an error/warning before you even get to that point, and likely tell you which plugin is corrupted. But if not, I'm thinking it will be visible in some way when you look at the records side by side.

---

There's one other thing that I can tell you which might be somewhat helpful. From the log, I can see which plugins started analysis but never completed before the exception happened. That won't narrow it down to a single culprit, but it does narrow it down to a half dozen or so possibilities, which are:

• [xPatch] Modpocalypse NPCs (v3) SSE - AI Overhaul - Enhanced Skyrim NPCs SE.esp
• [xPatch] Modpocalypse NPCs (v3) SSE - Enhanced Skyrim NPCs SE.esp
• Enhanced Skyrim NPCs SE.esp
• Modpocalypse NPCs (v3) SSE.esp
• Unofficial Skyrim Special Edition Patch.esp

It's not very likely to be USSEP unless you've edited that plugin. Given how new Modpocalypse is, I'd place my bets on one of those patches.

Which, by the way, you shouldn't have. The FAQs and Getting Started guide for EasyNPC all explicitly state, do not use patches for NPC overhauls, which the first two items in the list above definitely are. So if you don't get useful information out of xEdit, the very next thing I'd do is start disabling some of the plugins listed above, starting with the first two, which shouldn't be enabled anyway.

Anyway, see if the above helps.

[AncientFireBeast]

This was it. My bad man, I should have read that part of the mod, I guess I glossed over it in excitement to actually try something like this.
Anyways, thanks for all your help, it's really impressive (At least to me) how well you know what's going on in the innerworkings of this thing, I mean... One would hope most creators would understand their creations, but still... pretty cool stuff, I envy that talent, I'd love to dip my toes in the Skyrim mod creation side at some point, rather than just consuming.

[focustense]

No worries, it shouldn't be expected that patches would actually crash anything - that's not why that step is emphasized, I just emphasized it here so you wouldn't have doubts about whether or not it was OK to disable them.

For the benefit of other modders, though, can you tell us which plugin ended up having the problem? Did you confirm it e.g. in xEdit? If so, then I would suggest reporting it to the mod author as well. Record-level corruption is actually pretty rare and I'm sure they'll want to fix it.

[AncientFireBeast]

Wow... that was way more in depth than I expected... I didn't understand a lot of it, but I certainly appreciate you diving in that much. Thank you so much for your help, I'll check some of that, and report back with my findings. If it is the patches, my apologies for wasting your time.

…

On Thu, Sep 9, 2021, 11:22 AM focustense ***@***.***> wrote: Thanks. What I'm seeing is, unfortunately, that the exception is being passed back to the main thread before being logged, so I'm not getting the information I'd hoped out of it (not your fault, though). What I didn't notice the first time is that there actually is a bit more information in the nested exception here: ---> (Inner Exception #4) System.ArgumentException: Unexpected record type: COCT != PRKR at Mutagen.Bethesda.Plugins.Binary.Overlay.BinaryOverlayList.BinaryOverlayListByStartIndexWithRecord`1.get_Item(Int32 index) at Mutagen.Bethesda.Plugins.Binary.Overlay.BinaryOverlayList.BinaryOverlayListByStartIndexWithRecord`1.GetEnumerator()+MoveNext() at System.Collections.Generic.EnumerableHelpers.ToArray[T](IEnumerable`1 source, Int32& length) The bottom line here is that one of your plugins has a corrupted Perks (PRKR) or Perk Count (PRKZ) subrecord, or just a corrupted NPC record in general. I'm pretty sure that any positive number should be valid for PRKZ, as well as zero, so this would mean it's seeing a negative number. Similarly, the second error is saying that it found a start-of-inventory (or "count-of-container", COCT) record where it was supposed to be seeing a perk record. However, I'm not sure if I'd read too much into the specific errors here - that is, these errors are more consistent with random data corruption than a specific problem with the perks. Perks are just where it's first showing up. I think the only thing to do at this point is to open up your load order in xEdit, find this NPC and check what's affecting it, paying particular attention to these two sub-records (perks and perk count). Most likely, xEdit is going to report an error/warning before you even get to that point, and likely tell you which plugin is corrupted. But if not, I'm thinking it will be visible in some way when you look at the records side by side. ------------------------------ There's one other thing that I can tell you which might be somewhat helpful. From the log, I can see which plugins started analysis but never completed before the exception happened. That won't narrow it down to a single culprit, but it does narrow it down to a half dozen or so possibilities, which are: - [xPatch] Modpocalypse NPCs (v3) SSE - AI Overhaul - Enhanced Skyrim NPCs SE.esp - [xPatch] Modpocalypse NPCs (v3) SSE - Enhanced Skyrim NPCs SE.esp - Enhanced Skyrim NPCs SE.esp - Modpocalypse NPCs (v3) SSE.esp - Unofficial Skyrim Special Edition Patch.esp It's not very likely to be USSEP unless you've edited that plugin. Given how new Modpocalypse is, I'd place my bets on one of those patches. Which, by the way, you shouldn't have. The FAQs and Getting Started guide for EasyNPC all explicitly state, do not use patches for NPC overhauls, which the first two items in the list above definitely are. So if you don't get useful information out of xEdit, the very next thing I'd do is start disabling some of the plugins listed above, starting with the first two, which shouldn't be enabled anyway. Anyway, see if the above helps. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#115 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVRMP67SEEL2P54FHLOWIK3UBDNLBANCNFSM5DV4O2AQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.