I spent the last years trying to create a plugin that could help with massive penetration and increase stability and performance at same time.
So here it is, my creation, Deeper plugin.
Most of the time it can handle automagically things for you, but for the ones that require some tuning, I exposed an incredible number of variable to help them.
Almost everything exposed can be a variable in timeline.
This plugin pack some morphs I collected around from notorius creators, whose I really thanks for the amazing work of them.
Some morphs needed some vertices fixes, others are handmade by myself.
This plugin try to have support for BodyLanguade(at least v43) and DildoLanguage (at least v12.f2), since most of you love them so much.
NOTE: Using the GenCollidersFixer is not compatible with BL hands and cleverage triggers detection, because this feature turns the native
penis colliders into triggers and...
... BL just skips triggers.
The documentation about this plugin is to be considered in wip, since it's a lot to document, just explore the options you'll understandand
I tested this plugin a lot in various scenarios, and everytime something wrong came up I fixed it, so most of the time don't expect bugs, of course may exist some on edge cases.
Strength points of this plugin:
- Support for Dildo toy, CUAs (where is possible (please, read the spoiler for details)), and Primitives (Shapes);
- Managed penis colliders that behave the same of default ones but better, especially with particular male genitals;
- Managed receiver colliders for pelvis, torso and head-neck areas;
-Fully customizable settings;
- Presets support;
- Save-load support;
- Data stored directly inside poses and appearance json and reloaded from there;
- and many others to discover..
DeeperPlugin expose to atom storeables almost every control, you can fint if searching for "_Boris47.DeeperPlugin_Bridge"
GenCollidersFixer is a special feature that replace default colliders, which are not disabled but set as triggers, with new ones completely plugin managed.
No more gap between gen colliders.
Use my other plugin https://hub.virtamate.com/resources/genbonesfixers.57151/ to fix the bones positons and everything should work fine.
Example:
I will listen to all coming suggestions, and hoping for more free time I want to return to full developing speed around it.
It's mainly design to be a session plugin, so just add it and save to user default.
But it can be used as scene plugin also.
NOTE: If there are both, session and scene plugins running, the scene plugin have higher priority, so session plugin do nothing in that case.
There is a local preset system, for quick apply of changes.
NOTE: Preset system relies on current view and sub views only. Example: save a preset while viewing the Penis item, only store changes of that view and Penis features, it doesn't store other items changes.
For more complex preset store them at higher level, like directly in compesed atom view (Where every items and modules are listed)
Some infos are stored in the pose JSON, some other are stored in the appearance JSON, most of them are stored in the scene only if modified from default.
Testable scene for the final result (removing or disabling attached collider editor):
hub.virtamate.com
NOTE: I spent a great deal of time search for ways to make this plugin compatible with other plugins such as Body Language, and the reasult are great atm, only tiny thing I found: If using the gen colliders fixer feature, don't save the scene during penetration since atm BL don't recognize correctly the colliders interactions of penis
DETAILS:
The plugin create composed atoms instances for supported atom:
- Person
- Toys
- CUA
- Prmitives
Composed atoms could have items and/or modules.
Starting from version 1.0.9 the data serialization is much clear for use using interface items that helps to understand where data are stored, here is a recap:
- Updated labels in order to understand where data are serialized:
---- [S|L] Scene and Look
---- Scene Only
---- [L] Look Only
---- [DEV] Are dev controls, they are not stored
I'll continue to extend the overview of this plugin as much as I can.
So here it is, my creation, Deeper plugin.
Most of the time it can handle automagically things for you, but for the ones that require some tuning, I exposed an incredible number of variable to help them.
Almost everything exposed can be a variable in timeline.
This plugin pack some morphs I collected around from notorius creators, whose I really thanks for the amazing work of them.
Some morphs needed some vertices fixes, others are handmade by myself.
This plugin try to have support for BodyLanguade(at least v43) and DildoLanguage (at least v12.f2), since most of you love them so much.
NOTE: Using the GenCollidersFixer is not compatible with BL hands and cleverage triggers detection, because this feature turns the native
penis colliders into triggers and...
The documentation about this plugin is to be considered in wip, since it's a lot to document, just explore the options you'll understandand
I tested this plugin a lot in various scenarios, and everytime something wrong came up I fixed it, so most of the time don't expect bugs, of course may exist some on edge cases.
Strength points of this plugin:
- Support for Dildo toy, CUAs (where is possible (please, read the spoiler for details)), and Primitives (Shapes);
- Managed penis colliders that behave the same of default ones but better, especially with particular male genitals;
- Managed receiver colliders for pelvis, torso and head-neck areas;
-Fully customizable settings;
- Presets support;
- Save-load support;
- Data stored directly inside poses and appearance json and reloaded from there;
- and many others to discover..
DeeperPlugin expose to atom storeables almost every control, you can fint if searching for "_Boris47.DeeperPlugin_Bridge"
GenCollidersFixer is a special feature that replace default colliders, which are not disabled but set as triggers, with new ones completely plugin managed.
No more gap between gen colliders.
Use my other plugin https://hub.virtamate.com/resources/genbonesfixers.57151/ to fix the bones positons and everything should work fine.
Example:
I will listen to all coming suggestions, and hoping for more free time I want to return to full developing speed around it.
It's mainly design to be a session plugin, so just add it and save to user default.
But it can be used as scene plugin also.
NOTE: If there are both, session and scene plugins running, the scene plugin have higher priority, so session plugin do nothing in that case.
There is a local preset system, for quick apply of changes.
NOTE: Preset system relies on current view and sub views only. Example: save a preset while viewing the Penis item, only store changes of that view and Penis features, it doesn't store other items changes.
For more complex preset store them at higher level, like directly in compesed atom view (Where every items and modules are listed)
Some infos are stored in the pose JSON, some other are stored in the appearance JSON, most of them are stored in the scene only if modified from default.
Testable scene for the final result (removing or disabling attached collider editor):
cockzilla - Toolkits + Templates -
Size does matter ? This is a simple scene to those looking for the following themes: Giant dicks A ridiculous cumflation bulge Over the top amounts of cum Queefing and cum pumping sounds If you don't care for these themes then it's probably...
hub.virtamate.com
NOTE: I spent a great deal of time search for ways to make this plugin compatible with other plugins such as Body Language, and the reasult are great atm, only tiny thing I found: If using the gen colliders fixer feature, don't save the scene during penetration since atm BL don't recognize correctly the colliders interactions of penis
DETAILS:
The plugin create composed atoms instances for supported atom:
- Person
- Toys
- CUA
- Prmitives
Composed atoms could have items and/or modules.
The Person composed atom can be Male, Female or Alternative Futa:
- Male atom has all limbs and penis for penetration and anus and mouth for receiving and all basic modules
- Female has anus, vagina and mouth for received and only limbs for penetration.
-Alternative futa has all genitals and all limbs for receive and penetrate.
Based on this plugin design there could be items and/or modules:
- Items are use to receive or penetrate.
- Modules are the logic around those items core logic and other items interaction.
Elements of ComposedAtom are kind of extension of it with some more data and logic.
Some ui elements on hover show details like shown below
The curve system I studied is the way to help penetration check and path following for penetrator items thenk to the path Follow Module, it's bases of non morphed vertices, colliders center positions and mid points. During my test I found quite a reliability on this system at start so I build almost every logic on it.
Modules:
All person composed atoms have following modules:
Body Morpher module: Morph atom genital and mouth area based on what and from where is receiveng penetration.
Bulger: No much to add, big thing, big bulges.
Collision Handler: My first developed module, that handle which colliders should collider with others and when.
Colliders Manipulator: Core module for big things that handle all native colliders involved in interaction with penetrators.
Enlarger: Another core module that handle orefices enlargment based on penetrating items.
Path Follow: Quite simple outside, in the core it helps guide long penetrators once enough inside the receiver.
Receiver: Is a generic module that help about receiving items and penetration paths preview.
Triggers Handler: As name says, using all know curves about current atom, handle position of native atom triggers (Labria Triggers, Vagina Trigger, Throat Trigger, ...) in a reactive way base on penetrating items:
Items
- Limbs are penetrator items, they can penetrate orefices
- Penis is a penetrator item as well
Items use curves to calculate peenetration and depth.
Note about my penis feature GenCollidersFixer:
Despite other plugin my plugin use a custom class to access no morphed vertices position, this means that many feature, like GenCollidersFixer are not subject to pose morphs, for instance foreskin morphs and custom colliders are faithfully computed like the native ones but way better, so there is no more gap or oversized colliders on un-natural male genitals.
When saving a scene, my plugin don't store any morph, instead store data used by components and on restore (load) phase set morphs again to computed values.
When saving appearance some data are stored in the json, thisa data are used once that appearance is loaded like those:
Most users should ignore those implementation details.
Elements are other data used by composed atom modules or/and items.
I left UI as it is for debug purpose by design.
- Male atom has all limbs and penis for penetration and anus and mouth for receiving and all basic modules
- Female has anus, vagina and mouth for received and only limbs for penetration.
-Alternative futa has all genitals and all limbs for receive and penetrate.
Based on this plugin design there could be items and/or modules:
- Items are use to receive or penetrate.
- Modules are the logic around those items core logic and other items interaction.
Elements of ComposedAtom are kind of extension of it with some more data and logic.
Some ui elements on hover show details like shown below
The curve system I studied is the way to help penetration check and path following for penetrator items thenk to the path Follow Module, it's bases of non morphed vertices, colliders center positions and mid points. During my test I found quite a reliability on this system at start so I build almost every logic on it.
Modules:
All person composed atoms have following modules:
Body Morpher module: Morph atom genital and mouth area based on what and from where is receiveng penetration.
Bulger: No much to add, big thing, big bulges.
Collision Handler: My first developed module, that handle which colliders should collider with others and when.
Colliders Manipulator: Core module for big things that handle all native colliders involved in interaction with penetrators.
Enlarger: Another core module that handle orefices enlargment based on penetrating items.
Path Follow: Quite simple outside, in the core it helps guide long penetrators once enough inside the receiver.
Receiver: Is a generic module that help about receiving items and penetration paths preview.
Triggers Handler: As name says, using all know curves about current atom, handle position of native atom triggers (Labria Triggers, Vagina Trigger, Throat Trigger, ...) in a reactive way base on penetrating items:
Items
- Limbs are penetrator items, they can penetrate orefices
- Penis is a penetrator item as well
Items use curves to calculate peenetration and depth.
Note about my penis feature GenCollidersFixer:
Despite other plugin my plugin use a custom class to access no morphed vertices position, this means that many feature, like GenCollidersFixer are not subject to pose morphs, for instance foreskin morphs and custom colliders are faithfully computed like the native ones but way better, so there is no more gap or oversized colliders on un-natural male genitals.
When saving a scene, my plugin don't store any morph, instead store data used by components and on restore (load) phase set morphs again to computed values.
When saving appearance some data are stored in the json, thisa data are used once that appearance is loaded like those:
Most users should ignore those implementation details.
Elements are other data used by composed atom modules or/and items.
I left UI as it is for debug purpose by design.
The Dildo composed atom is preatty easy as it is.
It's involved just in the path following logic and collision exlusion at the moment, but I have some plan for it.
It's involved just in the path following logic and collision exlusion at the moment, but I have some plan for it.
The CUA composed atom is to be considered experimental.
If you wnat to use a cua as penetrator item, it must contain at least one collider and a renderer or a mesh filter, and you need to attach to it the other script in the same DeeperPlugin var, called
CUAPenetratorDataScript.rls.cs
Default behaviour is to guess the extreme points of penetrator curve, but the CUAPenetratorDataScript.rls.cs sript allow to manually set those point in case the gues logic is not good for selected asset.
I invite creator not to create hyper detailed asset since, beside this plugin, those mesh collider can have a huge impact on performance, especially in VR.
Dildo Language: Deeper can automatically recognize if a CUA is Dildo Language, no need for other scripts to be attached.
If you wnat to use a cua as penetrator item, it must contain at least one collider and a renderer or a mesh filter, and you need to attach to it the other script in the same DeeperPlugin var, called
CUAPenetratorDataScript.rls.cs
Default behaviour is to guess the extreme points of penetrator curve, but the CUAPenetratorDataScript.rls.cs sript allow to manually set those point in case the gues logic is not good for selected asset.
I invite creator not to create hyper detailed asset since, beside this plugin, those mesh collider can have a huge impact on performance, especially in VR.
Dildo Language: Deeper can automatically recognize if a CUA is Dildo Language, no need for other scripts to be attached.
The Primitives (Shapes) composed atom is simpler than CUA ones.
Currently supported as penetrators are Capsule and ISCapsule
Currently supported as receiver are ISTube.
('IS' means 'Independent Scale' )
If you want to use them in Deeper logics you need to attach the PrimitivePenetratorDataScript.rls.cs (for both as penetrator or receiver)
Currently supported as penetrators are Capsule and ISCapsule
Currently supported as receiver are ISTube.
('IS' means 'Independent Scale'
)If you want to use them in Deeper logics you need to attach the PrimitivePenetratorDataScript.rls.cs (for both as penetrator or receiver)
Starting from version 1.0.9 the data serialization is much clear for use using interface items that helps to understand where data are stored, here is a recap:
- Updated labels in order to understand where data are serialized:
---- [S|L] Scene and Look
---- Scene Only
---- [L] Look Only
---- [DEV] Are dev controls, they are not stored
I'll continue to extend the overview of this plugin as much as I can.
