Skyrim Utility Mod (LE)

[Tseverin]

Hey. I'm using the 1.6.640 AE build along with Sex LabFramework AE v1.65. It reports that I need to go back to v1.62 sexlab and that v1.65 is untested in a pop up. On the system tab of SUM 2.50, however, it says the current sexlab build is ok. In it's loading messages in the upper left hand screen it says SUM failed to meet the requirements or something like that in red. DDE and POP seem to work ok. It then crashes or freezes my pc up completely.

Edited October 16, 2022 by Tseverin

[SerenadeOfLight]

On 10/16/2022 at 3:36 PM, Tseverin said:

Hey. I'm using the 1.6.640 AE build along with Sex LabFramework AE v1.65. It reports that I need to go back to v1.62 sexlab and that v1.65 is untested in a pop up. On the system tab of SUM 2.50, however, it says the current sexlab build is ok. In it's loading messages in the upper left hand screen it says SUM failed to meet the requirements or something like that in red. DDE and POP seem to work ok. It then crashes or freezes my pc up completely.

 

I have a similar error message, but I haven't so far gotten crashes or freezes (but I'm still working on some other mods so I haven't played very far yet). Everything in the MCM lists OK. Potentially doesn't know to look for higher versions of mods it is looking for?

[Inte]

On 10/16/2022 at 3:36 PM, Tseverin said:

Hey. I'm using the 1.6.640 AE build along with Sex LabFramework AE v1.65. It reports that I need to go back to v1.62 sexlab and that v1.65 is untested in a pop up. On the system tab of SUM 2.50, however, it says the current sexlab build is ok. In it's loading messages in the upper left hand screen it says SUM failed to meet the requirements or something like that in red. DDE and POP seem to work ok. It then crashes or freezes my pc up completely.

 

4 minutes ago, SerenadeOfLight said:

I have a similar error message,

 

I need a screenshot of your SUM 'System' page so I can fix it for the next version. 

[squidwardd]

On 10/16/2022 at 3:36 PM, Tseverin said:

Hey. I'm using the 1.6.640 AE build along with Sex LabFramework AE v1.65. It reports that I need to go back to v1.62 sexlab and that v1.65 is untested in a pop up. On the system tab of SUM 2.50, however, it says the current sexlab build is ok. In it's loading messages in the upper left hand screen it says SUM failed to meet the requirements or something like that in red. DDE and POP seem to work ok. It then crashes or freezes my pc up completely.

im also having a similar issue, no idea what's causing it tho
i have a save earlier with everything running fine but i guess i mustve fucked with something i shouldnt have earlier lmao 



ill also post my system page here incase that helps 
im like 90% its my fault, probs didnt read a mod req right or skipped a download
 

Spoiler

 

 

 

[Tseverin]

1 hour ago, squidwardnutsack said:

im also having a similar issue, no idea what's causing it tho
i have a save earlier with everything running fine but i guess i mustve fucked with something i shouldnt have earlier lmao 



ill also post my system page here incase that helps 
im like 90% its my fault, probs didnt read a mod req right or skipped a download
 

  Hide contents

 

 

 

Thanks. I planned on posting this. I just haven't got around to doing it.

[Tseverin]

No more freezing. My system tab has a different report.

Edited October 19, 2022 by Tseverin

[Tseverin]

[Inte]

On 10/18/2022 at 10:01 PM, squidwardnutsack said:

ill also post my system page here incase that helps 

 

22 hours ago, Tseverin said:

My system tab has a different report.

 

Thanks for the screenshots, it will be fixed for the next version.

[LuxaLegacy]

Hello, this is the first time i wrote here so i hope i'm not going anything wrong. Sorry if my english is not good, that's not my native language 

So, that been a couple of days i try to make everything work but... 2 problems stays, so i need your help.

I have try to uninstall/install again PapyrusUtil but nothing to do, modify with SexLab priority files in Nexus Mod Manager, but that don't work.

And i find nothing about the System.json file, he's here but nothing happen, i don't understand.

 

I expect anybody will find why that doesn't work and help me.

Have a nice day ❤️

[Inte]

On 10/21/2022 at 5:11 PM, LuxaLegacy said:

I expect anybody will find why that doesn't work and help me.

Install the newest PapyrusUtil version for your game version and allow it to overwrite everything. 

[Buckshot87]

Additionally, to the things Tseverin already mentioned I've also encountered this error log while going through my debug with Wrye Bash :

 

mod_files.py  250 load: Error in Skyrim - Utility Mod.esm
Traceback (most recent call last):
  File "bash\brec\advanced_elements.py", line 492, in load_mel
KeyError: 20

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):
  File "bash\brec\record_structs.py", line 580, in loadData
  File "bash\brec\advanced_elements.py", line 494, in load_mel
bash.exception.ModSizeError: Skyrim - Utility Mod.esm: WEAP.CRDT: Expected one of sizes (16, 24), but got 20

 

The above exception was the direct cause of the following exception:

 

Traceback (most recent call last):
  File "bash\mod_files.py", line 227, in load
  File "bash\brec\record_groups.py", line 71, in load_rec_group
  File "bash\brec\record_groups.py", line 229, in _load_rec_group
  File "bash\brec\record_structs.py", line 548, in __init__
  File "bash\brec\record_structs.py", line 381, in __init__
  File "bash\brec\record_structs.py", line 594, in loadData
bash.exception.ModError: Skyrim - Utility Mod.esm: ModSizeError(FName('Skyrim - Utility Mod.esm'), (b'WEAP', b'CRDT'), (16, 24), 20)

 

I hope this helps with the next update

 

EDIT: I was about to post this in the POP thread, but this is pretty much identical and by the same author, so this might relate to another:

 

mod_files.py  250 load: Error in xazPrisonOverhaulPatched.esp
Traceback (most recent call last):
  File "bash\brec\advanced_elements.py", line 492, in load_mel
KeyError: 20

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):
  File "bash\brec\record_structs.py", line 580, in loadData
  File "bash\brec\advanced_elements.py", line 494, in load_mel
bash.exception.ModSizeError: xazPrisonOverhaulPatched.esp: WEAP.CRDT: Expected one of sizes (16, 24), but got 20

 

The above exception was the direct cause of the following exception:

 

Traceback (most recent call last):
  File "bash\mod_files.py", line 227, in load
  File "bash\brec\record_groups.py", line 71, in load_rec_group
  File "bash\brec\record_groups.py", line 229, in _load_rec_group
  File "bash\brec\record_structs.py", line 548, in __init__
  File "bash\brec\record_structs.py", line 381, in __init__
  File "bash\brec\record_structs.py", line 594, in loadData
bash.exception.ModError: xazPrisonOverhaulPatched.esp: ModSizeError(FName('xazPrisonOverhaulPatched.esp'), (b'WEAP', b'CRDT'), (16, 24), 20)

Edited November 1, 2022 by Buckshot87

[Herowynne]

7 hours ago, Buckshot87 said:

Additionally, to the things Tseverin already mentioned I've also encountered this error log while going through my debug with Wrye Bash :

 

mod_files.py  250 load: Error in Skyrim - Utility Mod.esm
Traceback (most recent call last):
  File "bash\brec\advanced_elements.py", line 492, in load_mel
KeyError: 20

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):
  File "bash\brec\record_structs.py", line 580, in loadData
  File "bash\brec\advanced_elements.py", line 494, in load_mel
bash.exception.ModSizeError: Skyrim - Utility Mod.esm: WEAP.CRDT: Expected one of sizes (16, 24), but got 20

 

The above exception was the direct cause of the following exception:

 

Traceback (most recent call last):
  File "bash\mod_files.py", line 227, in load
  File "bash\brec\record_groups.py", line 71, in load_rec_group
  File "bash\brec\record_groups.py", line 229, in _load_rec_group
  File "bash\brec\record_structs.py", line 548, in __init__
  File "bash\brec\record_structs.py", line 381, in __init__
  File "bash\brec\record_structs.py", line 594, in loadData
bash.exception.ModError: Skyrim - Utility Mod.esm: ModSizeError(FName('Skyrim - Utility Mod.esm'), (b'WEAP', b'CRDT'), (16, 24), 20)

 

I hope this helps with the next update

 

EDIT: I was about to post this in the POP thread, but this is pretty much identical and by the same author, so this might relate to another:

 

mod_files.py  250 load: Error in xazPrisonOverhaulPatched.esp
Traceback (most recent call last):
  File "bash\brec\advanced_elements.py", line 492, in load_mel
KeyError: 20

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):
  File "bash\brec\record_structs.py", line 580, in loadData
  File "bash\brec\advanced_elements.py", line 494, in load_mel
bash.exception.ModSizeError: xazPrisonOverhaulPatched.esp: WEAP.CRDT: Expected one of sizes (16, 24), but got 20

 

The above exception was the direct cause of the following exception:

 

Traceback (most recent call last):
  File "bash\mod_files.py", line 227, in load
  File "bash\brec\record_groups.py", line 71, in load_rec_group
  File "bash\brec\record_groups.py", line 229, in _load_rec_group
  File "bash\brec\record_structs.py", line 548, in __init__
  File "bash\brec\record_structs.py", line 381, in __init__
  File "bash\brec\record_structs.py", line 594, in loadData
bash.exception.ModError: xazPrisonOverhaulPatched.esp: ModSizeError(FName('xazPrisonOverhaulPatched.esp'), (b'WEAP', b'CRDT'), (16, 24), 20)

 

SSEEdit indicates an error when a Weapon record is missing the Critical Data field, so I add the Critical Data field to the Weapon records for SUM and POP when I do the SE conversions for @Inte. I do not convert the SUM and POP esm/esp files from form 43 to form 44.

 

Based on your report, it looks like Wrye Bash does not expect the Weapon record Critical Data field in a form 43 esm/esp file.

 

In other words, SSEEdit and Wrye Bash have the opposite behavior for the Weapon record Critical Data field.

 

If Wrye Bash has a support channel of some kind, you may want to report this issue with Wrye Bash. Wrye Bash probably should not fail with an exception when it encounters the Weapon record Critical Data field in a form 43 esm/esp file.

 

 

Edited November 1, 2022 by Herowynne

[Tseverin]

On 10/19/2022 at 11:08 PM, Inte said:

 

 

Thanks for the screenshots, it will be fixed for the next version.

Thanks for the update. It means a lot.

Edited November 2, 2022 by Tseverin

[MisterTime]

Thanks you for update !!

[merctime]

Hmm, just like everyone else, it looks like using SUM 2.60 for SE is still throwing a 'disabled DLL' message for me when I try to run Skyrim through MO.  I've also tried SUM 2.50, and 2.42 (I think, maybe it's 2.45)  

 

Is there an actual fix around for that, or is downgraded TRULY the only way to get sexlab working?

 

Also, I had to downgrade Papyrus to .39 for MO not to tell me that .44 was out of date for the game, too, lol... But now, .39 papyrus won't run the other programs that need it xD

 

This is hilarious.  And infuriating.  

 

Anyone know if there has been any updates on these DLL's?  

[Herowynne]

8 hours ago, merctime said:

SUM 2.60 for SE is still throwing a 'disabled DLL' message

Please post a screenshot of the message. Thanks!

[neodraconis94]

these errors pop up

i checked system.json is in right place

using MO2 Skyrim SE

 

DDe also says cannot find System.json

Edited November 7, 2022 by neodraconis94

[Violence6884]

Hello! Just a quick question; Is it normal that on the STATUS page, ISUMMiscQ and ISUMLeashQ are indicated as Failed? I don't get any errors or problems, nor any warnings- Just noticed that now, on a fresh installation and fresh start.

 

[Edit] Never mind! Just needed a reset! Forgot to add this earlier. So... Friendly tip, reset it on a fresh start if you get the same "Issue"! ^_^

Edited November 24, 2022 by Violence6884

[Tseverin]

Hey.

 

I'm getting this message when I make my bashed patch:

 

mod_files.py  250 load: Error in Skyrim - Utility Mod.esm
Traceback (most recent call last):
  File "bash\brec\advanced_elements.py", line 492, in load_mel
KeyError: 20

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "bash\brec\record_structs.py", line 580, in loadData
  File "bash\brec\advanced_elements.py", line 494, in load_mel
bash.exception.ModSizeError: Skyrim - Utility Mod.esm: WEAP.CRDT: Expected one of sizes (16, 24), but got 20

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "bash\mod_files.py", line 227, in load
  File "bash\brec\record_groups.py", line 71, in load_rec_group
  File "bash\brec\record_groups.py", line 229, in _load_rec_group
  File "bash\brec\record_structs.py", line 548, in __init__
  File "bash\brec\record_structs.py", line 381, in __init__
  File "bash\brec\record_structs.py", line 594, in loadData
bash.exception.ModError: Skyrim - Utility Mod.esm: ModSizeError(FName('Skyrim - Utility Mod.esm'), (b'WEAP', b'CRDT'), (16, 24), 20)

 

Is there something you think I'm doing wrong or should I not be concerned about it?

Thanks for keeping POP around.

[Herowynne]

3 hours ago, Tseverin said:

Hey.

 

I'm getting this message when I make my bashed patch:

 

mod_files.py  250 load: Error in Skyrim - Utility Mod.esm
Traceback (most recent call last):
  File "bash\brec\advanced_elements.py", line 492, in load_mel
KeyError: 20

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "bash\brec\record_structs.py", line 580, in loadData
  File "bash\brec\advanced_elements.py", line 494, in load_mel
bash.exception.ModSizeError: Skyrim - Utility Mod.esm: WEAP.CRDT: Expected one of sizes (16, 24), but got 20

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "bash\mod_files.py", line 227, in load
  File "bash\brec\record_groups.py", line 71, in load_rec_group
  File "bash\brec\record_groups.py", line 229, in _load_rec_group
  File "bash\brec\record_structs.py", line 548, in __init__
  File "bash\brec\record_structs.py", line 381, in __init__
  File "bash\brec\record_structs.py", line 594, in loadData
bash.exception.ModError: Skyrim - Utility Mod.esm: ModSizeError(FName('Skyrim - Utility Mod.esm'), (b'WEAP', b'CRDT'), (16, 24), 20)

 

Is there something you think I'm doing wrong or should I not be concerned about it?

Thanks for keeping POP around.

That error is due to Wrye Bash not accommodating the Weapon critical data field in a form 43 record, which I added by using SSEEdit.

 

In other words, Wrye Bash is not compatible with that feature of SSEEdit.

[Tseverin]

On 11/29/2022 at 8:38 PM, Herowynne said:

That error is due to Wrye Bash not accommodating the Weapon critical data field in a form 43 record, which I added by using SSEEdit.

 

In other words, Wrye Bash is not compatible with that feature of SSEEdit.

Should I disable SUM and all of it's dependencies before I make a bashed patch? It'd be nice if I could flip an .esm to a form 44 without trying to convert it to an .esp first, at least that's the only way I know how to change an .esm. I switched over POP and DDE for my load order.

Edited December 1, 2022 by Tseverin

[Herowynne]

3 hours ago, Tseverin said:

Should I disable SUM and all of it's dependencies before I make a bashed patch?

Yes, that is probably a good idea.

[alternateaccounts]

Hi, this mod seems to break Sexlab Separate Orgasms.

[Sathar]

Experimenting with getting Sexlab P+ to work, SUM pops up a SL version warning similar to those posted above (SL P+ currently seems to be detected as "SL 2.0.0").  Would you please update the version check, assuming that it is not a hard incompatibility?

[ElizabethEC]

Just throwing another report on the pile for a fully updated fresh install of the entire SUM, DD, and Papyrus set resulting in SUM failing to detect any of the versions and files, just throwing up an endless barrage of error screens. Wasn't a problem on my prior install, but just returned to the game after a year+ break and re-did my whole setup, and now it won't work at all.