SexLab p+ Dev/Feature Discussion

[b7b]

18 hours ago, Someone92 said:

It seems the error SUM throws it is simply because it hasn't been updated yet to treat p+ as a legit SexLab version. Below is a possible fix:

https://www.loverslab.com/topic/115377-skyrim-utility-mod/?do=findComment&comment=4011346

 

 

Does Cursed Loot overwrite native SexLab files?

I want to kiss you.

That SUM hotfix seems to have resolved both of my issues.

Just a theory, but cursed loot may have been fucked off during SUM's version mismatch temper tantrum. Either that or it's just miraculously decided to work again out of nowhere as skyrim mods usually do. 

Regardless, thanks!

Edited April 5, 2023 by b7b
(:

[Генаh]

Всем привет как его устанавливать поверх sexlab или наоборот!!!

[Velezarius]

Привет! Конечно поверх SL надо ставить Р+!

[libertyordeath]

About the animation registry and how animations are managed:

 

The one thing i always found most frustrating about sexlab itself was that first i have to fix offsets on every other animation, and then i lose all those tweaks whenever i have to reset the anim registry. And those resets happen all the time, for various reasons. Nevermind starting a new game. If anyone asked me in RL "Hey, do you know sexlab?", i would answer: "Oh, you mean offset-corrector: The game?"

 

Anyways, if i'm interpreting the way the new anim registry works correctly, then userdata like offset corrections would no longer be lost, since there's nothing to "reset" anymore? Or am i understanding this wrong?

 

EDIT: Oh, and i voted "something else" in the poll. Other than reducing offset hell, i'd like to see builtin cumshot functionality. Yes, i know SL Cumshot already exists. It's also abandonned and has been buggy as hell for its entire existance. Meanwhile OStim - which is much younger than SL - has a cumshot-mod that just works. 

Edited April 13, 2023 by libertyordeath

[Lulu the Milky Succubus]

Do we have a list of currently incompatible mods? From reading, I've seen that Sexlab Tools and anything Separate Orgasm are currently incompatible, anything else that currently cannot be used with P+?

[Someone92]

If you use Mod Organizer 2, simply install the mod you want to try out.

If it has conflicts with SexLab p+, meaning it overwrites scripts from SexLab, assume it is not compatible.

If it has no conflicts it is most likely compatible with SexLab p+. There might be exceptions when I mod accessed functions that it should not have, and those functions have been altered or removed in SexLab p+.

 

There is also this github list:

https://gist.github.com/MissCorruption/887725102fb18d96d43e26555e008bbb

Edited April 15, 2023 by Someone92

[jf8350143]

For some reason this mod stops all voices and sfx from happening.

 

At first I thought it was because I was using extra voices add on but even when I disable the mod there is still no sound or sfx.

 

edit:nevermind starts a new save and now it works fine now. 

 

Edited April 18, 2023 by jf8350143

[wintersouls23]

Mod does not work, I don't get it. I installed [SexLab Framework PPLUS - V1.8.2.3 - LATEST.zip] for [Skyrim V1.5.97] with [SexLab V163]. I even started a new game like the mod page says to.

Edited April 19, 2023 by wintersouls23

[Someone92]

As stated on the discord, mods that overwrite SexLab scripts are incompatible with p+.

Also make sure nothing overwrites p+

 

The only exception currently is

SexLab

SL Separate Orgasms

p+

SLSO p+ patch

[Rex226]

Any chance this could be made compatible for the GOG version of the game? I'd love to develop my mod with this project as the framework. I know SexLab has support for the GOG version, so I am not sure how difficult it would be to add support to this as well.

Edited April 22, 2023 by Rex226

[petronius]

I understand how popular SLSO and the whole sex minigame are popular these days - but please, make they always be entirely optional/toggleable for the sake of us who also play skyrim and only need an animation framework for the extra "immersion"  Permanent, reliable autopilot so I can go grab a bite while the animation plays, and then move on with the game.

[petronius]

On 4/13/2023 at 3:59 AM, libertyordeath said:

EDIT: Oh, and i voted "something else" in the poll. Other than reducing offset hell, i'd like to see builtin cumshot functionality. Yes, i know SL Cumshot already exists. It's also abandonned and has been buggy as hell for its entire existance. Meanwhile OStim - which is much younger than SL - has a cumshot-mod that just works. 

Not to mention visuals suck. Would be nice to see "cum objects" colliding with the body mesh/skeleton and activating an overlay/decal closest to the collision spot.

[Scrab]

On 4/22/2023 at 5:04 PM, Rex226 said:

Any chance this could be made compatible for the GOG version of the game? I'd love to develop my mod with this project as the framework. I know SexLab has support for the GOG version, so I am not sure how difficult it would be to add support to this as well.

GOG should already be compatible afaik

 

8 hours ago, petronius said:

I understand how popular SLSO and the whole sex minigame are popular these days - but please, make they always be entirely optional/toggleable for the sake of us who also play skyrim and only need an animation framework for the extra "immersion"  Permanent, reliable autopilot so I can go grab a bite while the animation plays, and then move on with the game.

 

The exact way how SL Scenes are implemented heavily depends on the overall design of the desired outcome. The more I work on SLSB, the more clear and refined the shape of SL animations becomes. There are some drastic changes here, especially in the way orgasms work

 

A little info on how I plan on executing scenes:

 

Spoiler

 

When you look at default SL, animations usually follow this general build up here:

 

 

There is some start animation, followed by a variety of looping stages and an ending stage with an orgasm

When you then install SLSO, your animations essentially turns into this (I think):

 

 

Where every scene becomes essentially an "orgasm stage"

Now, heres the issue: The animation represented by this little tree here is exactly the same but only one of these stages is an actual stage which gives you a visual representation and ideally this is represented by a proper transition in some way

 

In p+, this kind of approach would require something like this here:

 

What I did here is giving every stage an "orgasm stage" associated with the original motion and while doesnt look too bad, its just 2 more animation to create a proper "orgasm feeling", consider that p+ animations may be much larger than that, the scalability of it isnt really there, imo and just skipping to some end (there may be multiple as youll see in a second) may disrupt scene flow too much

 

This here would be an example of what p+ considers the upper limit of an ideal scene:

 

Ideally, p+ scenes follow a specific flow that starts from wherever the animation starts to a certain end state which is usually (but doesnt have to be) an orgasm stage. Putting an orgasm stage in here everywhere doesnt always make sense of course but its also not feasible to put a requirement on this. This example is admittedly a poor one since all of the stimulation loops do include an orgasm outro, but this does not always have to be like that

 

For that matter, the way Ed implemented orgasms isnt suitable for the way SL wants to interpret scenes

This then leaves the question "What about seperate orgasms" and "what about stimulation"

 

1. Seperate Orgasms:

By default, p+ will treat orgasms as separate. The above scene for example could represent a consent oral scene and all of these pink boxes represent an orgasm, but the only one that has to orgasm in these stages is the actor receiving the fellatio/handjob. Unlike in default SL, the taker here will not have any kind of orgasm. Only the receiver will (that is, assuming the taker does not masturbate)

 

2. What about stimluation

Because the graph dictates the exact behavior of a scene, stimulation in the current interpretation is simply being scrapped. Itll be the animators job to make a proper, believable and dynamic scene and I wish to intervene in an animators vision as little as possible

That being said, if you really wanted to create an stimulation system, the ideal way would be to block certain paths under certain conditions. For example, you could disable entering an orgasm stage while stimulation is below a certain point. This would probably the preferred way to implement such an "stimulation gate keeping" as it allows stimulation to be of central importance without interrupting this natural scene flow

 

 

 

Edited May 13, 2023 by Scrab

[petronius]

1 hour ago, Scrab said:

The exact way how SL Scenes are implemented heavily depends on the overall design of the desired outcome. The more I work on SLSB, the more clear and refined the shape of SL animations becomes. There are some drastic changes here, especially in the way orgasms work

 

A little info on how I plan on executing scenes:

 

  Reveal hidden contents

 

When you look at default SL, animations usually follow this general build up here:

 

 

There is some start animation, followed by a variety of looping stages and an ending stage with an orgasm

When you then install SLSO, your animations essentially turns into this (I think):

 

 

Where every scene becomes essentially an "orgasm stage"

Now, heres the issue: The animation represented by this little tree here is exactly the same but only one of these stages is an actual stage which gives you a visual representation and ideally this is represented by a proper transition in some way

 

In p+, this kind of approach would require something like this here:

 

What I did here is giving every stage an "orgasm stage" associated with the original motion and while doesnt look too bad, its just 2 more animation to create a proper "orgasm feeling", consider that p+ animations may be much larger than that, the scalability of it isnt really there, imo and just skipping to some end (there may be multiple as youll see in a second) may disrupt scene flow too much

 

This here would be an example of what p+ considers the upper limit of an ideal scene:

 

Ideally, p+ scenes follow a specific flow that starts from wherever the animation starts to a certain end state which is usually (but doesnt have to be) an orgasm stage. Putting an orgasm stage in here everywhere doesnt always make sense of course but its also not feasible to put a requirement on this. This example is admittedly a poor one since all of the stimulation loops do include an orgasm outro, but this does not always have to be like that

 

For that matter, the way Ed implemented orgasms isnt suitable for the way SL wants to interpret scenes

This then leaves the question "What about seperate orgasms" and "what about stimulation"

 

1. Seperate Orgasms:

By default, p+ will treat orgasms as separate. The above scene for example could represent a consent oral scene and all of these pink boxes represent an orgasm, but the only one that has to orgasm in these stages is the actor receiving the fellatio/handjob. Unlike in default SL, the taker here will not have any kind of orgasm. Only the receiver will (that is, assuming the taker does not masturbate)

 

2. What about stimluation

Because the graph dictates the exact behavior of a scene, stimulation in the current interpretation is simply being scrapped. Itll be the animators job to make a proper, believable and dynamic scene and I wish to intervene in an animators vision as little as possible

That being said, if you really wanted to create an stimulation system, the ideal way would be to block certain paths under certain conditions. For example, you could disable entering an orgasm stage while stimulation is below a certain point. This would probably the preferred way to implement such an "stimulation gate keeping" as it allows stimulation to be of central importance without interrupting this natural scene flow

 

 

I understand. But there could be an autopilot option? A routine that could be toggled, and replaced the need for any kind of user input and always let to orgasm, like Sexlab currently always ends in orgasm? So that a stimulation mechanic that currently is optional doesn't become enforced on people who don't care about it.

 

As I mentioned, I reckon this is a matter of opinion, but I'll try to explain my point of view: watching a scene in "autopilot" mode to me is like watching a cut scene, a moment in the game where I relax and enjoy whatever preparations I made for it, be it seduction, trade or combat related. Playing a stimulation minigame feels like playing with puppets, something I take no enjoyment in. Game actors no longer feel like characters in a movie, momentarily independent of my action, they feel like dead ragdolls that only get animated by me, that act exactly in the way I make them act, which is a HUGE turnoff. That, in a couple of lines, is what puts me off of SLSO, OSex and every other minigame type mod.

 

What I enjoy the most about Skyrim mods, 11 years into the game's history, is complex, well coded followers with stories that aren't centred on the player and make it feel like the world of the game somehow doesn't simply react to the player's actions. Sure, to a great extent it's an illusion, but often a well crafted one.

 

Opinions will vary, I just wish it were possible for you to maintain, as much as possible, an option to let the framework play sex scenes out, independently of player input, to an expected outcome.

 

In any case, my many thanks for your effort in streamlining the sluggiest, but "bestest" animation framework for this game, so far unsurpassed by any newer alternative.

[Scrab]

1 hour ago, petronius said:

Opinions will vary, I just wish it were possible for you to maintain, as much as possible, an option to let the framework play sex scenes out, independently of player input, to an expected outcome.

I promise you youre not alone with that opinion

 

I do plan on putting a great amount of thought into an "autopilot" feature. Scenes should be accompanying an authors story, not be the main focus of it and to that end, I dont intend on introducing any complicated mechanics or doing things that would otherwise be distracting

Stimulation may not even be part of SL itself and instead SL will only expose various API elements to have another mod manually adjust the paths the animation can take

 

I take my inspiration mostly from Wild Life and try to evolve the actual design with things authors and animators wish from a framework and the play style that users expect from it

[petronius]

8 minutes ago, Scrab said:

I promise you youre not alone with that opinion

 

 

Thank goodness! I feared the world were doomed, if people had lost enjoyment of healthy traditional porn and became obsessed with controlling computer sprites' vagina muscles instead... ? Godspeed!

[Someone92]

Will it be possible that a scene does not end when the scene reaches an orgasm stage?

[Scrab]

1 hour ago, Someone92 said:

Will it be possible that a scene does not end when the scene reaches an orgasm stage?

Up to the animator

 

The scene will last until a scene hits a dead end

In the example I posted above, there is another stage called "lick fingers" after an orgasm. You could technically put an entire additional graph after that if you wanted

 

Mind you in regards to "putting scenes together", what you currently have available is still incredibly slow compared to what the end result should look like, so butchering stages together in an attempt to create "fluent transitions" may not be necessary to achieve a fluent transitions between 2 otherwise unrelated scenes

Edited May 13, 2023 by Scrab

[LeeFowl]

One feature that I would prefer to be native is an option to prevent enemies/allies attacking me/my partner during sex scenes. Right now you have to install like three different (outdated) mods just for that feature.

Edited June 15, 2023 by LeeFowl

[dwayk8]

Need help! An error appears during compilation.

Spoiler

Starting 1 compile threads for 1 files...
Compiling "TIF__040036C8"...
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(314,48): NudeSuit is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(315,26): NudeSuit is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorAlias.psc(1442,24): cannot call the member function ContinueStrip alone or on a type, must call it on a variable
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(660,27): ForbiddenFaction is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(661,27): DummyWeapon is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(662,27): NudeSuit is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(664,27): BaseMarker is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(665,27): DoNothing is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(667,35): CumOralKeyword is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(668,35): CumAnalKeyword is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(669,35): CumVaginalKeyword is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(670,35): CumVaginalStackedKeyword is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(671,35): CumOralStackedKeyword is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(672,35): CumAnalStackedKeyword is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(674,29): Vaginal1Oral1Anal1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(675,29): Vaginal2Oral1Anal1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(676,29): Vaginal2Oral2Anal1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(677,29): Vaginal2Oral1Anal2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(678,29): Vaginal1Oral2Anal1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(679,29): Vaginal1Oral2Anal2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(680,29): Vaginal1Oral1Anal2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(681,29): Vaginal2Oral2Anal2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(682,29): Oral1Anal1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(683,29): Oral2Anal1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(684,29): Oral1Anal2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(685,29): Oral2Anal2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(686,29): Vaginal1Oral1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(687,29): Vaginal2Oral1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(688,29): Vaginal1Oral2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(689,29): Vaginal2Oral2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(690,29): Vaginal1Anal1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(691,29): Vaginal2Anal1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(692,29): Vaginal1Anal2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(693,29): Vaginal2Anal2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(694,29): Vaginal1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(695,29): Vaginal2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(696,29): Oral1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(697,29): Oral2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(698,29): Anal1 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(699,29): Anal2 is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(701,34): CumVaginalOralAnalSpell is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(702,34): CumOralAnalSpell is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(703,34): CumVaginalOralSpell is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(704,34): CumVaginalAnalSpell is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(705,34): CumVaginalSpell is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(706,34): CumOralSpell is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\sslActorLibrary.psc(707,34): CumAnalSpell is not a property on script sslsystemconfig or one of its parents
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\SexLabFramework.psc(384,17): GetIsActorValid is not a function or does not exist
C:\Games\The Elder Scrolls - SkyrimAE\Data\Scripts\Source\temp\TIF__040036C8.psc(16,25): cannot name a variable or property the same as a known type or script
No output generated for TIF__040036C8, compilation failed.

Batch compile of 1 files finished. 0 succeeded, 1 failed.
Failed on TIF__040036C8

 

[Scrab]

5 hours ago, dwayk8 said:

Need help! An error appears during compilation.

Youre mixing default SL & SLp+ sources together

[kaxat]

@Scrab I am considering trying to patch portions of SexLab Tools to be compatible with P+. A temporary solution until you have developed the replacement UI.

 

I have spent some time reviewing its sources and cross referencing the P+ papyrus source. I have not yet noticed any functions or properties that Tools uses which are outright removed in P+. I have found a few calls to functions that are now marked legacy, deprecated, or internal. Presumably these will break in upcoming versions of P+.

Do you have any idea what major difficulties I might face getting Tools to be compatible with the latest release of P+? Again the goal is just to create a temporary patch. I fully expect to lose compatibility as you revamp sslThreadModel and similar internal classes. Particularly once branching stages have been released. But you also plan to create your own replacement for Tools. So this patch is destined to be obsolete at some point. Its only goal is to be a stop gap for now. Because users like me hesitate to start a new P+ game without some Tools capabilities.

[Scrab]

2 hours ago, kaxat said:

@Scrab I am considering trying to patch portions of SexLab Tools to be compatible with P+. A temporary solution until you have developed the replacement UI.

 

I have spent some time reviewing its sources and cross referencing the P+ papyrus source. I have not yet noticed any functions or properties that Tools uses which are outright removed in P+. I have found a few calls to functions that are now marked legacy, deprecated, or internal. Presumably these will break in upcoming versions of P+.

Do you have any idea what major difficulties I might face getting Tools to be compatible with the latest release of P+? Again the goal is just to create a temporary patch. I fully expect to lose compatibility as you revamp sslThreadModel and similar internal classes. Particularly once branching stages have been released. But you also plan to create your own replacement for Tools. So this patch is destined to be obsolete at some point. Its only goal is to be a stop gap for now. Because users like me hesitate to start a new P+ game without some Tools capabilities.

Honestly I have no idea

 

I assume its got something to do with how I swap between stages. This "change in swapping animation" is also why most of the things in SL now completely reset the animation, I can no longer "resetart" an specific scene but have to either go +1 or back to Stage 1

The next version however will make changes to how the FNIS.txt is written for SL animations to allow the branching logic to be properly implemented, which might also mean SL Tools will just magically work again

[kaxat]

Thanks for the response.

I have not yet tested to find the issues. Only read in your list that it was incompatible. I am putting together a new load order. Your comment convinced me to do P+ and Tools together and see about creating needed patches.

 

If the main thing that needs patching is just the stage changer I think that will actually be easy to fix. It looks like I can pretty easily swap out the list of Stages with a simple << First Stage | Next Stage >> buttons. And then adjust the Sexlab API call.

To your knowledge does skipping a stage work? If I wanted to skip from Stage 1 to Stage 3 is that possible? Or does the new logic need Stage 2 in between. I suppose if you don't know I will find out soon enough.

PS. While looking through your latest commits I think I found a bug. The Set() function for the sslThreadModel.Animation property calls SetAnimationImpl(akAnimation). Which in turn does Animation = akAnimation. Unless I have missed something that's a recursive call.

[Scrab]

48 minutes ago, kaxat said:

To your knowledge does skipping a stage work? If I wanted to skip from Stage 1 to Stage 3 is that possible? Or does the new logic need Stage 2 in between. I suppose if you don't know I will find out soon enough.

No, you can only go "Stage + 1" or "Stage = 1"

 

48 minutes ago, kaxat said:

PS. While looking through your latest commits I think I found a bug. The Set() function for the sslThreadModel.Animation property calls SetAnimationImpl(akAnimation). Which in turn does Animation = akAnimation. Unless I have missed something that's a recursive call.

If you look through the current scripts on my git you see that Im in a large refracture of the actual code base, and laying out logic that is public/internal/legacy. Im essentially undoing majority of the changes I made in p+ as they are no longer needed in SL+ and also improve backwards compatibility in the process by reintroducing some old code

 

The code that is currently available on my git is NOT SLp+ but the WIP for SL+. They have about as much in common as SLp+ and default SL

Edited July 4, 2023 by Scrab