Sexlab Sexual Fame RELOADED

[NymphoElf]

4 hours ago, Uffda said:

V2.9 - I got an tattoo applied, and got into a continously loop saying "SLSF Reloaded - ERROR: Body tattoo Subcategory invalid. No way to get rid of it, and its no way to edit the sub category, as it is greyed out. 

So what to do? I dont find a way to set up Subs for the tatoo, they are all greyed out....

 

Your Body Tattoo Subcategory shows as "(NONE)" which was the default value prior to 2.6+

 

The new default value is "-NONE-"

 

This means you didn't perform one of the updates correctly.

[rfgggg]

This is from the latest update on a new save after a good 10+ hours into the save.

 

Papyrus log is filled with entries like these:

 

https://pastebin.com/G2ZimKRX

 

This snippet of the log is from when I was simply running through the area outside of Whiterun.

 

Not sure if this is a problem with my setup, or the mod. Either way I guess I'll start a new save and see what happens.

[Uffda]

7 hours ago, NymphoElf said:

 

Your Body Tattoo Subcategory shows as "(NONE)" which was the default value prior to 2.6+

 

The new default value is "-NONE-"

 

This means you didn't perform one of the updates correctly.

I did use fame saver in 2.4, then unloaded - then cleaned with re-saver, and when i put in 2.9 game crash at launch with resaver...so i disabled it, but could try to import inside 2.9 - but it said no save found.
When I loaded the save before I did clean it with resaver, it worked... so I continued playing with that. So, even tho i did update from 2.4 to 2.9 - it should work in theory...or do I have to update 1 and 1 step and save each step?

So, is it a way to fix it - or do I have to clear all fame? 
 

 

Edited January 7, 2025 by Uffda

[NymphoElf]

3 hours ago, Uffda said:

I did use fame saver in 2.4, then unloaded - then cleaned with re-saver, and when i put in 2.9 game crash at launch with resaver...so i disabled it, but could try to import inside 2.9 - but it said no save found.
When I loaded the save before I did clean it with resaver, it worked... so I continued playing with that. So, even tho i did update from 2.4 to 2.9 - it should work in theory...or do I have to update 1 and 1 step and save each step?

So, is it a way to fix it - or do I have to clear all fame? 
 

 

 

If you fully cleaned your save, then the variables should have reset when 2.9 initialized.

 

As for the Data Saver, you have to use Data Saver v1 to import if you exported with it (the data saver got updated when fully integrated to 2.6+). Install Data Saver v1 and allow it to overwrite whatever version you're using, then use the Data Saver MCM (not the normal one) to import.

 

Perhaps I should release a v2 to alleviate this complication.

 

5 hours ago, rfgggg said:

This is from the latest update on a new save after a good 10+ hours into the save.

 

Papyrus log is filled with entries like these:

 

https://pastebin.com/G2ZimKRX

 

This snippet of the log is from when I was simply running through the area outside of Whiterun.

 

Not sure if this is a problem with my setup, or the mod. Either way I guess I'll start a new save and see what happens.

 

What version of the mod are you using? I also need the full log, not just a snippet. From what you've shown me it seems like you're equipping and unequipping something far too much, but since it's only a snippet I can't say for sure.

 

You also ran the Uninstall function. Why? (If you're removing the mod that's fine, but if you did for some other reason then I'd like to know)

Edited January 8, 2025 by NymphoElf

[Arasu69]

been getting this since i installed older SF

[NymphoElf]

4 hours ago, Arastal said:

been getting this since i installed older SF

 

And you clearly didn't read it

[rfgggg]

11 hours ago, NymphoElf said:

 

What version of the mod are you using? I also need the full log, not just a snippet. From what you've shown me it seems like you're equipping and unequipping something far too much, but since it's only a snippet I can't say for sure.

 

You also ran the Uninstall function. Why? (If you're removing the mod that's fine, but if you did for some other reason then I'd like to know)

On 2.9, ran the uninstall in the hopes of being able to save the save, but didn't try too hard so had no luck there. Had limited time before work earlier but seem to have narrowed down what causes the start of the issue, when Unforgiving Devices tries to equip an item as that was the only thing done in the save this log is from beyond loading. IDK which mod the problem originates from or if it's a problem with my setup but its pretty reproducible for me.

Log.txt

[NymphoElf]

7 hours ago, rfgggg said:

On 2.9, ran the uninstall in the hopes of being able to save the save, but didn't try too hard so had no luck there. Had limited time before work earlier but seem to have narrowed down what causes the start of the issue, when Unforgiving Devices tries to equip an item as that was the only thing done in the save this log is from beyond loading. IDK which mod the problem originates from or if it's a problem with my setup but its pretty reproducible for me.

Log.txt 509.95 kB · 2 downloads

 

Yeah this seems like something in your mod list is messed up. It just instantly Stack Dumps on game load from what it looks like. I can only speculate as to why.

 

Have you tried starting a new game and seeing if the issue persists?

[Uffda]

On 1/8/2025 at 2:24 AM, NymphoElf said:

 

If you fully cleaned your save, then the variables should have reset when 2.9 initialized.

 

As for the Data Saver, you have to use Data Saver v1 to import if you exported with it (the data saver got updated when fully integrated to 2.6+). Install Data Saver v1 and allow it to overwrite whatever version you're using, then use the Data Saver MCM (not the normal one) to import.

 

Perhaps I should release a v2 to alleviate this complication.

 

 

What version of the mod are you using? I also need the full log, not just a snippet. From what you've shown me it seems like you're equipping and unequipping something far too much, but since it's only a snippet I can't say for sure.

 

You also ran the Uninstall function. Why? (If you're removing the mod that's fine, but if you did for some other reason then I'd like to know)

The solution was to just run 2,9 - export data. Then disable mod, and load and save and use re-saver to clean it... Then enable mod again, and import. Now it seems correct - so something must have gone wrong... but working now 🙂

[NymphoElf]

1 hour ago, Uffda said:

The solution was to just run 2,9 - export data. Then disable mod, and load and save and use re-saver to clean it... Then enable mod again, and import. Now it seems correct - so something must have gone wrong... but working now 🙂

 

Wonderful! Glad it's fixed 

[normal24yearoldstudent]

A little confused by the description...Is the current version working with PPlus?

 

i saw the support being removed since 2.5, but its still listed in the requirements as "Sexlab P+ 2.10.2.0 (or newer)" and "should still be compatible as-is" ?

 

what exactly does it mean? I imagine it should work for the most part with some minor bugs? what dosent work well out-of-the-box with Pplus and thus needs a dedicated Pplus version in the future?

 

 

[NymphoElf]

17 hours ago, normal24yearoldstudent said:

A little confused by the description...Is the current version working with PPlus?

 

i saw the support being removed since 2.5, but its still listed in the requirements as "Sexlab P+ 2.10.2.0 (or newer)" and "should still be compatible as-is" ?

 

what exactly does it mean? I imagine it should work for the most part with some minor bugs? what dosent work well out-of-the-box with Pplus and thus needs a dedicated Pplus version in the future?

 

 

 

I used to have code that used the P+ dominant and submissive detection. However, I've pretty much recreated that system in my own code, so I removed the detection hook.

 

I need to take a closer look at P+ scripts to understand the differences and what may need to be tweaked for the mod.

 

The core Sexlab Framework script is different in P+. Many things are the same, but there are a few differences such as inherently determining who is dominant and who is submissive. I also believe the cum layer detection may be different. Other than that they should be the same. But I can't make any promises. Plus with how many other things that don't work with P+ inherently, I don't know how that might cascade into further problems.

 

It's a bit difficult to explain because P+ is so similar to Sexlab but also distinctly different.

 

EDIT: I tried to clarify that in the description. Sorry about the confusion.

Edited January 10, 2025 by NymphoElf

[UserXz]

If updating from v2.4 with export/import data, DataSaver v1 should be removed (completely uninstalled from MO) after importing?

confused a bit, because v2.6 instructions says to remove and v2.5 instruction doesn't mention it

[NymphoElf]

4 hours ago, UserXz said:

If updating from v2.4 with export/import data, DataSaver v1 should be removed (completely uninstalled from MO) after importing?

 

Yes. The way Data Saver v1 saves your data and the way 2.6+ saves your data is different. I just slapped together something functional for v1 while I refined the feature for the full implementation into the mod.

 

Also, now that I think about it, you should probably follow the 2.6 instructions instead.

 

4 hours ago, UserXz said:

confused a bit, because v2.6 instructions says to remove and v2.5 instruction doesn't mention it

 

Because it didn't exist when I wrote those update instructions.

Edited January 10, 2025 by NymphoElf

[noctred]

Hello,

 

For starters, thanks for this mod - a modernized SLSF is welcome. That said, I'm running into an issue where SLSFR appears to be doing... nothing.

 

When fame events occur, I see them trigger in the original SLSF - notifications pop up and fame counts are correctly incrementing and visible in its MCM. SLSFR, however, shows no signs of life - no notifications and no incrementing fame counts in its MCM. This occurs regardless of whether the "Overwrite Legacy SLSF" toggle is enabled. The fact I'm getting notifications from the og SLSF to begin with probably implies that SLSFR isn't overwriting SLSF's settings the way the guidebook says it should.

 

Furthermore, right after the first time my character fucks someone, opening the 'General Information' tab in the SLSFR MCM soft locks the entire MCM - all I can do is back out to the main Skyrim MCM list. Reproducible 100% of the time.

 

Papryus log is attached. It's around 5 minutes of play, starting in the ASLAL cell on a brand new game, porting to Riverwood, and then running around and getting fucked for a bit. I don't see any stacks from SLSFR at all but then I don't really know what I'm looking for. Tracing is enabled in the SLSFR MCM and in skyrim.ini.

 

I'm on AE 1.6.1170, SLSFR 2.9 (fresh install), and the latest available SL P+. I know there are some issues with SLSFR and P+ but probably not these kinds of issues? PapyrusUtil, po3's Papyrus Extender, and Papyrus Tweaks NG are all installed with nothing overwriting any of them.

 

Thanks.

Papyrus.0.log

Edited January 11, 2025 by noctred

[B3juc0]

On version 2.9 there a possibility to get suspended stacks if there are lot of sex scenes involving the PC. Mind you this is on a high end system (7800X3D/4090 that should minimize papyrus bottlenecks ) The FPS is way over 60 yet papyrus still struggles even with Papyrus Tweaks NG set at iMaxOpsPerFrame = 2000. But... if you set the timescale to something lower (I'm trying 8 ) so far no suspended stacks. 

[Þursona]

5 hours ago, noctred said:

Hello,

 

For starters, thanks for this mod - a modernized SLSF is welcome. That said, I'm running into an issue where SLSFR appears to be doing... nothing.

 

When fame events occur, I see them trigger in the original SLSF - notifications pop up and fame counts are correctly incrementing and visible in its MCM. SLSFR, however, shows no signs of life - no notifications and no incrementing fame counts in its MCM. This occurs regardless of whether the "Overwrite Legacy SLSF" toggle is enabled. The fact I'm getting notifications from the og SLSF to begin with probably implies that SLSFR isn't overwriting SLSF's settings the way the guidebook says it should.

 

Furthermore, right after the first time my character fucks someone, opening the 'General Information' tab in the SLSFR MCM soft locks the entire MCM - all I can do is back out to the main Skyrim MCM list. Reproducible 100% of the time.

[...]
 

I'm on AE 1.6.1170, SLSFR 2.9 (fresh install), and the latest available SL P+. I know there are some issues with SLSFR and P+ but probably not these kinds of issues? PapyrusUtil, po3's Papyrus Extender, and Papyrus Tweaks NG are all installed with nothing overwriting any of them.

 

I am experiencing the exact same issues and I'm using regular SexLab, not P+. So that is not the cause of issues.

[NymphoElf]

4 hours ago, B3juc0 said:

On version 2.9 there a possibility to get suspended stacks if there are lot of sex scenes involving the PC.

 

What do you mean by this? How can there be more than one sex scene involving the PC?

 

@noctred @Þursona I will try to find some time to investigate this issue. I'm so far unable to reproduce the issue, and the lack of information from the logs makes this harder to understand how to fix. It could be as simple as an upload error on my part, or it could be an obscure issue I couldn't have predicted.

[yacky91]

I've been using 2.3 version along the og sexual fame framework + fame comments and I plan to start a new game due to many mods updates lol.

So I wanna know something, I've seen that Sexlab Cum Overlays Extended removed, does that mean it's no longer supported?

Edited January 11, 2025 by yacky91

[NymphoElf]

8 hours ago, yacky91 said:

I've been using 2.3 version along the og sexual fame framework + fame comments and I plan to start a new game due to many mods updates lol.

So I wanna know something, I've seen that Sexlab Cum Overlays Extended removed, does that mean it's no longer supported?

 

Correct. SCOE is an abandoned project. If it gets revived I might re-add the support, but for now it's no longer supported. I'd rather not support potentially unreliable mods if I don't have to.

[UserXz]

14 hours ago, B3juc0 said:

On version 2.9 there a possibility to get suspended stacks if there are lot of sex scenes involving the PC. Mind you this is on a high end system (7800X3D/4090 that should minimize papyrus bottlenecks ) The FPS is way over 60 yet papyrus still struggles even with Papyrus Tweaks NG set at iMaxOpsPerFrame = 2000. But... if you set the timescale to something lower (I'm trying 8 ) so far no suspended stacks. 

I think I have something similar with 2.9:
1) ReSaver reported few times about suspended stacks, I used previous save
2) VM Overstressed permanently and following in log:
 

Spoiler

[01/11/2025 - 05:17:36PM] ###############Stack Dump Summary Start################

[01/11/2025 - 05:17:36PM] Event: SF_mannyLoS_Quest_Scene2_0101322E.Fragment_0, Frequency: 1

[01/11/2025 - 05:17:36PM] Event: WIDeadBodyCleanupScript.OnDeath, Frequency: 1

[01/11/2025 - 05:17:36PM] Event: darkbrotherhood.OnUpdate, Frequency: 1

[01/11/2025 - 05:17:36PM] Event: ihudcontrolscript.OnUpdate, Frequency: 1

[01/11/2025 - 05:17:36PM] Event: slsf_reloaded_playerscript.OnMenuClose, Frequency: 1

[01/11/2025 - 05:17:36PM] Event: slsf_reloaded_playerscript.OnPlayerLoadGame, Frequency: 1

[01/11/2025 - 05:17:36PM] Event: sslActorAlias.OnUpdate, Frequency: 1

[01/11/2025 - 05:17:36PM] Event: slsf_reloaded_visibilitymanager.OnUpdate, Frequency: 2

[01/11/2025 - 05:17:36PM] Event: slsf_reloaded_playerscript.OnSexLabAnimationEnd, Frequency: 3

[01/11/2025 - 05:17:36PM] Event: slsf_reloaded_playerscript.OnSexLabAnimationStart, Frequency: 3

[01/11/2025 - 05:17:36PM] Event: slsf_reloaded_playerscript.OnLocationChange, Frequency: 15

[01/11/2025 - 05:17:36PM] Event: slsf_reloaded_playerscript.OnUpdateGameTime, Frequency: 18

[01/11/2025 - 05:17:36PM] Event: apropos2actoralias.OnObjectEquipped, Frequency: 24

[01/11/2025 - 05:17:36PM] Event: slsf_reloaded_playerscript.OnObjectUnequipped, Frequency: 32

[01/11/2025 - 05:17:36PM] Event: slsf_reloaded_playerscript.OnObjectEquipped, Frequency: 50

[01/11/2025 - 05:17:36PM] ###############Stack Dump Summary End##################

tried ~5 times from save without stacks issue, after update 2.4 -> 2.9 (btw everything seems fine with update process, slsfr works, data transfered)
if there is no way to fix saves (ReSaver can't open one now) I guess, I'll stay with 2.4. hope that it is possible to use old save 

[NymphoElf]

@noctred @Þursona @UserXz

 

I believe I've identified a couple of things.

 

1. The update I made to the time manager seems to return a bad time on New Game load, which results in no periodic fame for the first day of gameplay. This is likely an issue with the GetCurrentGameTime function when starting a new game returning a value that is around 1 (or possibly preserving the last known GameTime value from previous games?) and being set to 0 afterwards, or perhaps Alternate Start modifies the GameTime until the player loads their start? The exact cause is unclear, but the issue remains the same.
   • This issue also stalls the Legacy Overwrite function, because it's tied to the Time Manager.
2. It seems that it may be necessary to avoid Installing/enabling SLSF Reloaded until Sexlab has been properly installed/initialized on your save. The visibility manager script goes a little crazy if the variables it's looking for in Sexlab are not initialized yet, and this could potentially be the cause of early-game Papyrus Overload.
   • However, I'm not 100% sure if this is related to other Papyrus overload issues. The common trait I see between the other cases is high counts of Equip/Unequip actions, but this should only send a single update instance to the Visibility Manager. Perhaps adding a longer delay in this update call will help? (currently 0.1s, but could be increased to 1.0 instead to help prevent instant re-calls)
3. I believe I found the cause of the MCM soft-lock and the Papyrus Overload. Somehow it's related to another issue in the PlayerScript that I messed up. I accidentally created an infinite While Loop, which is likely the cause of the Papyrus Overload, because the PlayerScript can never finish its original task.

I'm not sure how I missed this in my tests, but clearly I did and I apologize. I should have a version up soon that has these issues resolved.

[AlyssaAwoo]

Hey, so I noticed this Reloaded mod currently supports SLSF Comments via a bridge to the old SLSF, but how safe would ditching this method be mid-savegame once SLSF Comments adds proper support for this mod? I've been holding off for a while to wait for it, but the itch to start up Skyrim again is there. 

[UserXz]

28 minutes ago, NymphoElf said:

However, I'm not 100% sure if this is related to other Papyrus overload issues. The common trait I see between the other cases is high counts of Equip/Unequip actions, but this should only send a single update instance to the Visibility Manager. Perhaps adding a longer delay in this update call will help? (currently 0.1s, but could be increased to 1.0 instead to help prevent instant re-calls)

just note about this, more precisely about 0.1s - VisibilityManager.RegisterForSingleUpdate(0.1) was there also in 2.4 and I didn't experience Papyrus overload

now, I reverted back to v2.4 - will try to pay attention on that

[NymphoElf]

3 minutes ago, -Ayleth- said:

Hey, so I noticed this Reloaded mod currently supports SLSF Comments via a bridge to the old SLSF, but how safe would ditching this method be mid-savegame once SLSF Comments adds proper support for this mod? I've been holding off for a while to wait for it, but the itch to start up Skyrim again is there. 

 

It should be safe. SLSF Reloaded uses the old SLSF's method of data tracking and simply overwrites the designated areas with Reloaded's own data values. It shouldn't be any less safe than removing the old SLSF is. Reloaded checks installed mods on every game load, and if the old SLSF is missing it will disable and nullify all related values.

 

5 minutes ago, UserXz said:

just note about this, more precisely about 0.1s - VisibilityManager.RegisterForSingleUpdate(0.1) was there also in 2.4 and I didn't experience Papyrus overload

now, I reverted back to v2.4 - will try to pay attention on that

 Fair enough. It's entirely possible that my infinite while loop is the real culprit, but I also know that the Visibility Manager is rather intensive at times due to what it needs to do, so perhaps delaying the check can be a partial solution.