OSex+ The Greatest Virtual Sex Ever

[bieber96]

very good job as always bro one thing i would like her to have orgsams are semen textures

Edited December 16, 2021 by bieber96

[MayDayCray]

18 hours ago, CEO 0S said:

Guys just a heads up I need another day to finish the orgasms, sorry for the delay. I'm working hard but the animations are very intricate, long and detailed and are taking me a bit longer. Here's the female orgasm ALMOST COMPLETE, male hands and a few other things still have to be resolved but I think it's coming out well.
 

 

 

Wow! A woman finishing first. You are not new to this, CEO. That was absolutely punishing

Will the guy be able to compel consecutive withdrawals, is the question.

[CEO 0S]

This will be disappointing to many but I know the majority here just want content and not drama so I'll be to the point about my intentions. Dealing with some elements of the Stim community have been too much trouble and hassle to facilitate compatibility and compromise.

 

Things are the same as when I returned so people can pretend I don't exist if they are outside of my project. I will create and animate, moving forward to create the greatest animations in Skyrim and awesome new systems for my new OSA but it will be in a way that does not interact with Stim from this point forward and I will not make compatibility for or troubleshoot Stim. 

I will continue to work as hard as I can to make awesome animations and great content and hope in time you will see the true spirit of this project and what I am capable of and you will always be welcome! With this move I will shut out all the drama and completely restore this project to the honor, art, and innovation it has always been known for.

 

I will be updating the OSA version I control in the next few days to a new format which will represent this move forward, it will not be OSA+ but a preemptive step so I can continue to release animations as the Prone Pack has been a huge success! My animation work from here on out will be purely for my new version. Please have the compassion to not support manipulation or abuse of my work to come. I absolutely want all future work and tools I develop to belong solely to my own future projects. For everyone that comes with me, thank you for your support!

[Erstam]

Looks like I poked into a hornets nest. Sorry for that. It was not my intention to stoke drama.

[Guest]

FYI, comments criticizing CEO's recent stance on Ostim are apparently being deleted, as mine was. Anything besides glowing praise is not allowed in this thread it seems. 

[CEO 0S]

On 12/16/2021 at 7:23 PM, Erstam said:

Looks like I poked into a hornets nest. Sorry for that. It was not my intention to stoke drama.

 

You didn't start any drama at all, I had to make an announcement but nothing to do with your post specifically.

 

Some of the things you mentioned already exist the pre-scripted sequences is possible albeit undocumented and OSA can do up to 99 scenes at once so those are covered but without me active the methods might have got lost.

 

Mouse movement might be possible but gets messy when mixed with how skyrim controls the camera, I'd be interested in trying it but I could never get it working in Flash, I did try a few times.

 

The core issue with a lot of these things is that OSA on it's own is supposed to just play multi actor animations nicely with awesome effects, not specifically a sex engine. Having OSex be such a large part of it confused people though and sets a tone but it really can support any kind of cutscene, cool action, grapple, kill move, it's possible. I always wanted it to just have all the tricks needed for any kind of animation. There is a trade off to that though however that the more specific OSA got the better it could do that job, for example if I had OSA only handle sex and nothing else, it would be easier or if i had it only be able to run my module and no one else's it would also get easier and stronger. There's a lot of compromise at play. 

 

I've gone back and forth in development of PLUS in gamifying the system more or leaving it abstract and where I'll land I'm not certain yet so the feedback is helpful. A strange thing about this project I find is that many people tell me they don't like it because it's not like SexLab and suggest for me to make it more like SexLab. SexLab is awesome and fills it's usage very well and I think mimicking functionality or experience of SexLab most likely is a mistake. I think maybe it comes down to picking what works best for my strengths and sticking to that and I think that's animation( specifically seamless animation) and fresh cinematic effects. Perhaps just a massive controllable interactive scene focused on awesome effects and cinematics is all it really needs to be.

 

It is a point too that OSA on it's own can't corrupt or bog a save down, perhaps there's value to a framework that lets sex happen but doesn't really tie into skyrim at all unless the player wants to call a scene.

 

I'm not saying I'm closed to it though, I'm just musing. I think your ideas are very valid and that might be what it winds up becoming. I love all the thoughts and traffic that picked up here today and it's great to have some input on direction for OSA+. I hope people keep giving more, I'm just giving my current state of mind.

Edited December 20, 2021 by CEO 0S

[bieber96]

 

personally i like osex osa much more than sexlab the animations look much better

 

 

Edited December 17, 2021 by bieber96

[CEO 0S]

14 hours ago, bieber96 said:

personalmente me gusta mucho más osex osa que sexlab las animaciones se ven mucho mejor

 

 

Thanks a lot Bieber! I'm going to make a sexlab plugin out of the vanilla animations that nexus owns now so you'll be able to get the anims there, could be a compromise for people that don't like my scene style maybe?

Edited December 17, 2021 by CEO 0S

[CEO 0S]

On 12/16/2021 at 4:54 PM, MayDayCray said:

Wow! A woman finishing first. You are not new to this, CEO. That was absolutely punishing

Will the guy be able to compel consecutive withdrawals, is the question.

 

Thanks MayDayCray,  glad you liked it, that's exactly what I was going for!

Edited December 19, 2021 by CEO 0S

[MonkeyKoala]

On 12/15/2021 at 9:49 PM, CEO 0S said:

Guys just a heads up I need another day to finish the orgasms, sorry for the delay. I'm working hard but the animations are very intricate, long and detailed and are taking me a bit longer. Here's the female orgasm ALMOST COMPLETE, male hands and a few other things still have to be resolved but I think it's coming out well.
 

 

 

Love that leg shake. That's excellent.

[CEO 0S]

Female Orgasm and transition out of AfterGlow is up. Still need male orgasm and female orgasm is missing Sex Thuds. Timing on those will take some time.

 

Everyone just want to say thank for support Prone Pack. You got it into the top 2 spot on hot files for both LE an SE. It's only there for 2-3 more hours so check it out the glory of it while you still can. If you haven't please vote and endorse both, the hype is a huge help to get attention on the project, and thank you for this honor!

 

https://www.nexusmods.com/skyrimspecialedition/mods/59981

https://www.nexusmods.com/skyrim/mods/110088

 

Special Edition:

https://www.nexusmods.com/skyrimspecialedition

 

Spoiler

 

 

 

 

 

 

 

 

 

 

 

Legacy Edition:

https://www.nexusmods.com/skyrim

Spoiler

 

 

 

Edited December 19, 2021 by CEO 0S

[kevindijkstra1]

Hi, What are the Requirements of this mod?

[CEO 0S]

Team, I need a break from orgasms, making the female orgasm really kicked my ass. I am going to focus on coding OSA+ for a few days and when I need a rest from that I will complete my male orgasm.

 

11 hours ago, kevindijkstra1 said:

Hi, What are the Requirements of this mod?

 

My OSA mod, which has a few foundational requirements (FNIS, SKSE, SKYUI). Total list is:   OSA, OSex, FNIS, SKSE, SkyUI, PapyrusUtils.

Edited December 20, 2021 by CEO 0S

[bieber96]

new osa is compatible with 1.5.97?

[CEO 0S]

8 minutes ago, bieber96 said:

new osa is compatible with 1.5.97?

 

Yea, I haven't moved to AE yet. Might be an AE version coming soon but I'll support SE until AE does everything SE does now and the modding community has moved forward. LE will always be supported. I feel like since SE is basically AE there will come a day when SE is not needed.

[amarkxxx]

I have a few questions regarding to the future of this mod, just let me know if i'm crossing my boundaries asking irritating questions as an end user.

OSA+ and OSex+ will contain new animations? Or it'll be a rewrite to your original mod with new features?
We will get more animation packs along the way in future?

It's just a constant battle between Sexlab and OSex for me. Sexlab got tons of quality animations and addons but it just lacks the intimacy feel that your mod OSex provides. 
I'm just hopeful one day i can experience best of both worlds in just one place and don't have to choose between mindless sex with variety and more immersive experience with intimacy.

I hope it didn't look like i'm comparing both of these amazing mods with any bad intentions, just seeing you back in the scene i'm optimistic that you'll create that perfect experience with your talent and hard work going forward. Best regards.

[CEO 0S]

10 hours ago, amarkxxx said:

I have a few questions regarding to the future of this mod, just let me know if i'm crossing my boundaries asking irritating questions as an end user.

OSA+ and OSex+ will contain new animations? Or it'll be a rewrite to your original mod with new features?
We will get more animation packs along the way in future?

It's just a constant battle between Sexlab and OSex for me. Sexlab got tons of quality animations and addons but it just lacks the intimacy feel that your mod OSex provides. 
I'm just hopeful one day i can experience best of both worlds in just one place and don't have to choose between mindless sex with variety and more immersive experience with intimacy.

I hope it didn't look like i'm comparing both of these amazing mods with any bad intentions, just seeing you back in the scene i'm optimistic that you'll create that perfect experience with your talent and hard work going forward. Best regards.

 

I appreciate the questions a lot and the interest, you're not crossing any boundaries so ask away!

I want to start off with your question about SexLab:

 

Sexlab vs OSex

These 2 frameworks are not competing but instead compliment each other, I use both in my game and recommend anyone interested in adult content in Skyrim do the same. It's a reality of developing a Sex Mod that you can't have the awesome features of both in one. As a developer you have to pick a path and that comes with sacrifices. Fortunately the 2 frameworks do not conflict at all with each other and you can use both the integration and variety of SexLab and the cinematic detail of OSex in harmony in your games! I can say after years of doing this with certainty that a system that checks all the boxes and perfectly blends the features of the two would not be possible without a massive budget and team size, and even then I'm not sure that would pull off much more. (At the end of that path is most likely just the effect of osex + sexlab installed with a mode that lets you switch between the two on the fly.)

 

 

In Terms of OSA+ / OSex+ (Technical Writeup)

Primarily OSA+ is a rewrite of OSA with new features to address all of it's short comings. I'll go over some details and use this post as my general write up as I been getting similar requests and questions in my Discord lately:

 

OSex Animations

OSex is ported to OSA+ so the scene as you know it will work just fine and be improved in some ways. I will be adding new animation packs to OSex+ which will be my primary work endeavor here once OSA+ settles in.

 

Legacy Limitations

There's many regrettable parts of OSA in which I was already too deep in development to change by the time I realized them. These make limitations that don't need to exist which hold back the potential of animation. The biggest one is body scales being easier to control by the animator per animation. Genital Anatomy scaling etc. also get effected. In many other ways OSA has it's hands in some things that wound up not being needed and that restricted a lot of nice potential on the animation level.

 

API

This is the area that got the most improvement. There are 3 Objects now that can be interacted with in a fun and easy object oriented way. They provide access to the entire engine and everything a mod developer might need:

 

Scena MyScene = OSA.Get().CreateScene()
Actra MyActor0 = MyScene.AddActor(PlayerRef)
Actra MyActor1 = MyScene.AddActor(Fione)
MyScene.Begin()
MyScene.PlayAction("osex.adore")

 

OSA: Talk to the engine itself (Primarily to create a new Scene)

Actra: Make changes or get data from any OSA Actor.

Scena: Make changes or get data from any OSA Scene.

 

This unlocks the entire engine to any papyrus mod developer to customize the scenes, get data from them, or add effects as needed. It would improve the experience of writing story driven mods like AA but also writing effect plugins like fertility, or relationship.

 

Some quick examples of how these work:

 

MyActor0.SetMood("happy")
MyActor0.SetIntimateVoicePack(FormList)
MyScene.PlayRandomActionFromTags("sex,doggystyle")
if(MyActor1.HasOrgasmed())
     MyScene.PlayAction("osex.prone")
EndIf

 

I believe this is an easy and very fun way of interacting with OSA which will be both very powerful and satisfying but also quick to learn, since there are only a few objects that have to be interacted with.

 

Scene and Menu Modularity

OSA currently has 1 scene type that has an elaborate set of rules to try to accommodate for the different things you currently see OSA do. To give clear examples of this, complications like speed control, head look direction, approach angle, multi actor all continued to pile on increasing complexity onto the main OSA scene class both in terms of upgrading and improving it but also for module creators writing documents for it. This is also true for the nav menu which  has become "fused" to the scene data and is hard to adjust.

 

OSA+ has simpler scene types that serve specific purposes, the rules and way a scene is handled is chosen by the module creator and a specific document is used for that type. This keeps the documents a lot easier and still powerful and if we need a different scene that does some specific cool thing instead of bogging down the main scene I can create a new scene. Nav menu is now also modular in the same way, and specific menu systems can be used to control specific scenes. 

 

An Example of a new Scene Type: I'm developing a scene where the actor gradually restores stamina and recovers themself, similar to the "bleed out" animation in default Skyrim, but this scene type facilitates updating animation over time as a "stat" fills up. This allows for something like the bleed out effect but with much cooler animation and effects showing the full recovery.

 

An Example of a new Nav Type: OWhipCream has a menu specifically for pumping whip cream which replaces the classic osex menu when you are on a whip cream scene. It responds to button being held down as if you are holding down the button on the bottle and you can pump dollops for as long as you like (within reason). So what is gained here is both a new visual type of menu with new interactions (button held - button released) as well.

 

 

PreLoaded  Data

Current OSA on demand streams it's documents as needed which was a cool solution but also results in OSA not knowing what scenes are available and information on those scenes. This results in important information like tags, autonavigation, and even more convenient animation pack systems become impossible to implement. OSA does a multithreaded load now of all documents and the speed is nice, it can load 5 osexs worth of data in under a second. All of this information and control is available to the API.

 

Folder Structure and DataFormat

Some of the most intimidating and error prone parts of module and personality development were dealing with all the nested folders that were required to be set up properly to function. OSA+ now has a single folder per module that includes all possible actions in the module. (As a note these documents are now json based instead of xml to make them easier to parse and adjust via script by third party libraries.)

 

This facilitates authors making small plugins much easier as well, OSA can on the fly adapt navigation menus to what "AnimationPacks"  are currently available. OSA knows ahead of time all actions that could be available and if they are or are not currently installed.

 

I provide a script for module developers in OSA+ which creates a manifest of the entire module's files instantly. In the case of OSex it winds up outputting what we call internally as "The Wall of Sex":

 

Faster Scene Start

I've reduced the time it takes for scenes spinning up to be basically instant, and I hope this will start to facilitate OSA to be used for combat and controllable grapple moves like I always dreamed.

 

Interact Menu

OSA now has an inspect menu which scenes can register for like action moves. This is openable on mouse cursor hover and shows a list of interactions you can do. Modules can register their own actions to this menu with conditions that decide when to present the option. This allows for moves to be triggered like actions but it also aids in interacting with already live scenes. Each OSA action can have it's own interact menu which provides options like joining in from a 2 person scene to a 3 person scene.

 

MCM Menu

OSA currently relies on my right side menu for config, and while I think it's cool I do think it's a cause of a lot of trouble shooting and stress for end users that are expecting MCM. I will move a majority of the config into MCM. Somethings are not able to be handled by MCM and will stay in OSA's own menu system in some fashion. The most important thing here is alleviating keybind issues for controller and users without a numpad.

 

Scribe

As much as I can i will be providing simple graphic interfaces for developers to write out the custom data OSA needs without having to ever mess around in the json itself. These will be simple web pages with clearly labeled fields that ouput the documents for you.

 

Connectivity

Any module's actions can connect or inject connections into any other module's actions now. This allows other mod developers to provide optional bridges back and forth between modules without having to overwrite the files.  If the module being injected to is not installed by the user OSA will simply recover by hiding the option.

 

Terminology

To prevent confusion in the future i changed some terminology to make it easier going forward.

 

• Pack: An animation plugin like Wizard Sex for example has been renamed to "Pack" short for "Animation Pack".
• Action: Any paired or solo animation playback OSA+ can do is now called an Action. "Adore" for example is an example of an action. 
• Scene: Scene now means an entire scene that is currently being played. If you start OSex with someone OSA creates a Scene which can play many different Actions. 

Edited December 22, 2021 by CEO 0S

[DonutBoi812]

Hi there! Outstanding mod first and foremost, it's worked relatively perfect for me up until the most recent patch released. I've noticed that when I try to start a scene, the actor names aren't appearing. In the first file, my character name does not appear, and in the second file, a targeted actor's name doesn't appear as well as the target's gender symbol being wrong. Is this an issue with the framework, SkyUI, or SKSE? I've tried reinstalling, made sure FNIS was updated properly, and so on. Any advice? Ty!

[CEO 0S]

1 hour ago, DonutBoi812 said:

Hi there! Outstanding mod first and foremost, it's worked relatively perfect for me up until the most recent patch released. I've noticed that when I try to start a scene, the actor names aren't appearing. In the first file, my character name does not appear, and in the second file, a targeted actor's name doesn't appear as well as the target's gender symbol being wrong. Is this an issue with the framework, SkyUI, or SKSE? I've tried reinstalling, made sure FNIS was updated properly, and so on. Any advice? Ty!

 

Hey thanks for the support! This could be a number of things but it's hard to say without a back and forth conversation. Best bet would be to come onto my Discord and use the #techsupport channel I have the most excellent tech support team that can get you fixed up. This is a confusing time for techsupport because of AE launch making things very complicated. If you open skyrim's game menu, like where you save load game  from what version does it say your Skyrim is? 

Edited December 22, 2021 by CEO 0S

[Pauduan]

On 12/20/2021 at 11:47 PM, CEO 0S said:

LE will always be supported.

Good to see you back, CEO, and good to read this.

 

LE batter in this corner - I will give your plus versions a whirl soon as I can. I still have your first 0SXKY mod and it's in some install backup somewhere. 

[Paladox]

18 hours ago, MyFamilySims said:

Too bad we do not find this mod with such rendering in the sims4.

If only mods could be free from the chains that bind them.
Tons of games could benefit besides Sims 4, including Kenshi, She Will Punish Them, Dragon's Dogma, etc..

Or maybe someone should convert Skyrim into a Sims game. ?

[SunWukongIV]

Hi i don't know if this question fits here so please excuse it when it does not. I have a problem with the undressing of NPCs during scenes, i can undress them but after a few seconds the just put the clothes back on and no new udnress is possible. Does anyone here had a similar problem and knows how to use it?
 

Best Regards

[amarkxxx]

On 12/21/2021 at 10:06 PM, CEO 0S said:

 

I appreciate the questions a lot and the interest, you're not crossing any boundaries so ask away!

I want to start off with your question about SexLab:

 

Sexlab vs OSex

These 2 frameworks are not competing but instead compliment each other, I use both in my game and recommend anyone interested in adult content in Skyrim do the same. It's a reality of developing a Sex Mod that you can't have the awesome features of both in one. As a developer you have to pick a path and that comes with sacrifices. Fortunately the 2 frameworks do not conflict at all with each other and you can use both the integration and variety of SexLab and the cinematic detail of OSex in harmony in your games! I can say after years of doing this with certainty that a system that checks all the boxes and perfectly blends the features of the two would not be possible without a massive budget and team size, and even then I'm not sure that would pull off much more. (At the end of that path is most likely just the effect of osex + sexlab installed with a mode that lets you switch between the two on the fly.)

 

 

In Terms of OSA+ / OSex+ (Technical Writeup)

Primarily OSA+ is a rewrite of OSA with new features to address all of it's short comings. I'll go over some details and use this post as my general write up as I been getting similar requests and questions in my Discord lately:

 

OSex Animations

OSex is ported to OSA+ so the scene as you know it will work just fine and be improved in some ways. I will be adding new animation packs to OSex+ which will be my primary work endeavor here once OSA+ settles in.

 

Legacy Limitations

There's many regrettable parts of OSA in which I was already too deep in development to change by the time I realized them. These make limitations that don't need to exist which hold back the potential of animation. The biggest one is body scales being easier to control by the animator per animation. Genital Anatomy scaling etc. also get effected. In many other ways OSA has it's hands in some things that wound up not being needed and that restricted a lot of nice potential on the animation level.

 

API

This is the area that got the most improvement. There are 3 Objects now that can be interacted with in a fun and easy object oriented way. They provide access to the entire engine and everything a mod developer might need:

 

Scena MyScene = OSA.Get().CreateScene()
Actra MyActor0 = MyScene.AddActor(PlayerRef)
Actra MyActor1 = MyScene.AddActor(Fione)
MyScene.Begin()
MyScene.PlayAction("osex.adore")

 

OSA: Talk to the engine itself (Primarily to create a new Scene)

Actra: Make changes or get data from any OSA Actor.

Scena: Make changes or get data from any OSA Scene.

 

This unlocks the entire engine to any papyrus mod developer to customize the scenes, get data from them, or add effects as needed. It would improve the experience of writing story driven mods like AA but also writing effect plugins like fertility, or relationship.

 

Some quick examples of how these work:

 

MyActor0.SetMood("happy")
MyActor0.SetIntimateVoicePack(FormList)
MyScene.PlayRandomActionFromTags("sex,doggystyle")
if(MyActor1.HasOrgasmed())
     MyScene.PlayAction("osex.prone")
EndIf

 

I believe this is an easy and very fun way of interacting with OSA which will be both very powerful and satisfying but also quick to learn, since there are only a few objects that have to be interacted with.

 

Scene and Menu Modularity

OSA currently has 1 scene type that has an elaborate set of rules to try to accommodate for the different things you currently see OSA do. To give clear examples of this, complications like speed control, head look direction, approach angle, multi actor all continued to pile on increasing complexity onto the main OSA scene class both in terms of upgrading and improving it but also for module creators writing documents for it. This is also true for the nav menu which  has become "fused" to the scene data and is hard to adjust.

 

OSA+ has simpler scene types that serve specific purposes, the rules and way a scene is handled is chosen by the module creator and a specific document is used for that type. This keeps the documents a lot easier and still powerful and if we need a different scene that does some specific cool thing instead of bogging down the main scene I can create a new scene. Nav menu is now also modular in the same way, and specific menu systems can be used to control specific scenes. 

 

An Example of a new Scene Type: I'm developing a scene where the actor gradually restores stamina and recovers themself, similar to the "bleed out" animation in default Skyrim, but this scene type facilitates updating animation over time as a "stat" fills up. This allows for something like the bleed out effect but with much cooler animation and effects showing the full recovery.

 

An Example of a new Nav Type: OWhipCream has a menu specifically for pumping whip cream which replaces the classic osex menu when you are on a whip cream scene. It responds to button being held down as if you are holding down the button on the bottle and you can pump dollops for as long as you like (within reason). So what is gained here is both a new visual type of menu with new interactions (button held - button released) as well.

 

 

PreLoaded  Data

Current OSA on demand streams it's documents as needed which was a cool solution but also results in OSA not knowing what scenes are available and information on those scenes. This results in important information like tags, autonavigation, and even more convenient animation pack systems become impossible to implement. OSA does a multithreaded load now of all documents and the speed is nice, it can load 5 osexs worth of data in under a second. All of this information and control is available to the API.

 

Folder Structure and DataFormat

Some of the most intimidating and error prone parts of module and personality development were dealing with all the nested folders that were required to be set up properly to function. OSA+ now has a single folder per module that includes all possible actions in the module. (As a note these documents are now json based instead of xml to make them easier to parse and adjust via script by third party libraries.)

 

This facilitates authors making small plugins much easier as well, OSA can on the fly adapt navigation menus to what "AnimationPacks"  are currently available. OSA knows ahead of time all actions that could be available and if they are or are not currently installed.

 

I provide a script for module developers in OSA+ which creates a manifest of the entire module's files instantly. In the case of OSex it winds up outputting what we call internally as "The Wall of Sex":

 

Faster Scene Start

I've reduced the time it takes for scenes spinning up to be basically instant, and I hope this will start to facilitate OSA to be used for combat and controllable grapple moves like I always dreamed.

 

Interact Menu

OSA now has an inspect menu which scenes can register for like action moves. This is openable on mouse cursor hover and shows a list of interactions you can do. Modules can register their own actions to this menu with conditions that decide when to present the option. This allows for moves to be triggered like actions but it also aids in interacting with already live scenes. Each OSA action can have it's own interact menu which provides options like joining in from a 2 person scene to a 3 person scene.

 

MCM Menu

OSA currently relies on my right side menu for config, and while I think it's cool I do think it's a cause of a lot of trouble shooting and stress for end users that are expecting MCM. I will move a majority of the config into MCM. Somethings are not able to be handled by MCM and will stay in OSA's own menu system in some fashion. The most important thing here is alleviating keybind issues for controller and users without a numpad.

 

Scribe

As much as I can i will be providing simple graphic interfaces for developers to write out the custom data OSA needs without having to ever mess around in the json itself. These will be simple web pages with clearly labeled fields that ouput the documents for you.

 

Connectivity

Any module's actions can connect or inject connections into any other module's actions now. This allows other mod developers to provide optional bridges back and forth between modules without having to overwrite the files.  If the module being injected to is not installed by the user OSA will simply recover by hiding the option.

 

Terminology

To prevent confusion in the future i changed some terminology to make it easier going forward.

 

• Pack: An animation plugin like Wizard Sex for example has been renamed to "Pack" short for "Animation Pack".
• Action: Any paired or solo animation playback OSA+ can do is now called an Action. "Adore" for example is an example of an action. 
• Scene: Scene now means an entire scene that is currently being played. If you start OSex with someone OSA creates a Scene which can play many different Actions. 

Thank you so much for your detailed explanation. It makes me so excited for the future of this mod.  ❤️

 

One last thing though and i guess it's problem on my end since your gifs look completely fine. I don't know what I'm doing wrong but in some scenes, specially missionary, the schlong doesn't go in the vagina but instead it's either above that or below it. It didn't bother me when i used it a long time ago without any body with vagina physics, but now i use 3BBB CBBE so it looks completely weird since the vagina keeps opening and closing as if the schlong is going in and out properly but in reality it's either going in below or above the hole through the body. All the animations are completely aligned properly, there's no problem with that, just i don't know why I'm having this issue no matter what body preset i use. What am i doing wrong? Any clue? I just SOS and 3BBB CBBE SMP Body. 

Edited December 23, 2021 by amarkxxx

[CEO 0S]

 

This is my completed draft for the new standard nav menu in OSA+. Please ignore the heart spam for now I'm using that icon as a placeholder. This is going to get set in stone soon so please critique! The biggest sacrifice was removing my illustrations which I liked a lot but ultimately they were to difficult to fill out for niche movements and made it less friendly to other module developers who had to rely on me to illustrate their moves, or pick from only what I had done so far. I wanted to give it a fresh new face lift in general and make it more of a sleek universal UI. 

 

To visualize further this is a scrollbox which shows 7 at a time but can continue to scroll upwards. The heading element "Romance" is an optional block if a module developer wants to group by category.

 

- Removal of the 3 tier nested menus so that options can be clearly seen.

- Each option can have it's own rule set, like how speed has + -, press and hold is viable as well, options can do random stat checks with different outcomes based on results, (For example sword skill check for a success scene or fail scene), and any other feature we might want.

- Easier document to write with standardized icons and stylings.

- Subtle background so it's easier to read outdoors.

- Nostalgic fantasy theme halfway between Zelda and Skyrim.

- Tracked stat gauges, visibility set by module or specific action. Health / Arousal currently shown.

- Hideable and Injectable Nav Options allow other modules to connect two ways without overwriting xmls, and api to disable options.

- Optional notice if "Pack" or "Module" is not installed. Unavailable moves can still be shown but inaccessible.

- Visible keybind reminders.

 

Edited December 24, 2021 by CEO 0S

[lordkimbo29]

Can the navigation commands be bound to keys of our choice. The screenshot shows the keys "Z" and "Q" as being used for accessing more options for the "Kiss Fione" scene. I already have those keys bound to other Skyrim commands. 

 

So to check for understanding, the three tier nested menu was the nav system that would appear below the scene descriptor image (the little triangles), correct? The one that would allow for minor pose changes (lift head for example) or could be the pathway to a new set of scenes (pull out, mount higher). How would that type of stuff be handled wit this new system? Separate nav entries in the scroll list as is displayed in your screenshot?

 

While I can live without the old system, I kind of liked having them nested as a means of organizing UI elements. Maybe use a slight indent on the UI elements in the scroll list to signify the same type of options (lift head, mount higher, etc)?

 

Personally, I thought using the numpad was perfect for OSA navigation. Hate to lose that.

 

I also liked how you could flip to the other participant in some scenes in a single keystroke to access option just for that participant, e.g. "Lift Head", etc.

(Could be wrong tho. Truth be told, my Dragonborn is often too busy to engage in any extracurricular activity, so I may not be remembering the keystroke sequence correctly.)

 

Judging by this screenshot, it looks like I would have to access "Scene Options" first, then "Lift Head"? 

 

Anyway, just a nitpick. Other than that I like the new layout. Having branching animations based on game data (sword check) is really neat.

 

The display dividers (Romance) could be useful in situations where a lot of scenes would be available at once.

 

Where would the injectable nav objects get displayed? Actually, what options would be contained in the Scene Options menu?

 

Also, while I have your attention, I would like a feature request. Basically, I like my altmer tall and my bosmer short. I wonder if it would be possible to add an animation scene or too where one of the participants had an obvious height difference from the other?

 

Thanks.