Plugins + Scripts BodyLanguage

[CheesyFX]

For clothes, you can set triggers in the Actions section of PoseMe (I think the best way is to have some clothing preset first and load them through the Actions triggers I mentioned, but if you use Runrudolf's Erection and Foreskin Plug-in with its cum clothing set active, you might loose it, and I haven't found any proper way to reload Runrudolf's cum clothing set but manually). A workaround is to set Actions triggers to disable a certain clothing item simulation and to set its alpha (transparency) to zero. For plug-in settings, I guess you can set some person's plug-ins to enabled or disabled through Actions triggers as well. BTW, @CheesyFX has been missin for a while now. Anyone knows if he/she is OK?

I'm fine, thanks

 

[Virtamales]

Hello! Maybe whis was already asked somethere, but I constatly get this error log during penetration, and I don't know waht to do to solve it. I get it on Alt-Futa females havif Bodylanguage plug-in, no matter what position Bodylanguage has in the plug-in list (higher or lower).

!> System.NullReferenceException: Object reference not set to an instance of an object
at CheesyFX.Orifice.SetPenetrated (Boolean val) [0x00000] in <filename unknown>:0
at CheesyFX.Vagina.SetPenetrated (Boolean val) [0x00000] in <filename unknown>:0
at CheesyFX.Orifice.set_isPenetrated (Boolean value) [0x00000] in <filename unknown>:0

I have another query: When I load a scene that I have edited, in which one character has Bodylanguage with many Levels, Poses, and Cameras, the pose buttons cannot be clicked except for the active pose, and I have to reload Bodylanguage for the buttons to become active again. Is there maybe a limit of how many poses/levels/cams Bodylanguage can handle?

Any help with these issues will be much appreciated.

Hi @CheesyFX , I'm glad you're OK. I wrote the post above some days ago: in some scenes I tweaked (Mr.Orange's Pleasure Room for instance), sometimes I get constant, looped error logs as above (The fourth line changing to "at CheesyFX.Throat.SetPenetrated…" or "at CheesyFX.Orifice.SetPenetrated…" depending on what is being penetrated in a specific pose. I don't know what is causing it. In order to mimic the conditions under which it happens, I can only say I use males with big penis (not huge, just above VAM average), and my female (the one having BL plug-in) are all Alt-Futas some of them have ColliderEditor presets that supposedly make penetration easier, but I've seen this happening with ordinary females as well. I also made one FillMeUp UserDefault preset (some BL updates ago) in which all Vagina thrusts and magnet are disabled and all Anus thrust and magnet enabled, but I don't know if my constant error logs are related to that. Any help with this issue will be much appreciated.

I also wrote that in some tweaked scenes the pose icons become unclickable and that I gotta reaload BL to make them work again. After reading some old posts here, I think it's just I have reached your plug-in's very limits, with scenes weighting more than 50 Mb, with about 5 levels, so many poses per level (up to 60-62 poses in total), 5 to 9 cams per pose, and some triggers per pose. I think in scenes this big, BL just won't work properly anymore: pose icons become unclickable and triggers won't even save. I write it here just because it might be helpful for crazy guys like me who try to create huge scenes.

 

[bash23]

Is it just me or the 'Show screen overlay on orgasm' doesnt work anymore

 

[Virtamales]

Is it just me or the 'Show screen overlay on orgasm' doesnt work anymore

I never saw anything when I had it ticked on... what was it supposed to do?

 

[bash23]

I never saw anything when I had it ticked on... what was it supposed to do?

iirc whenever she starts to orgasm a number will float on screen how many times she has cum

 

[Chris237]

I dont know what happened but its just stopped working. Every time im done with a pose and add it, the other poses just get completely missaligned. Like it does NOT saves the person main control position and rotation. Its always uses the lats saved control position and rotation for every other earlier finished and saved poses and F's up everything. Position and rotation is NOT locked. It worked perfectly before but now its just died. No other script is used, all i did is load a different female model. Thats all. I dont have any other script loaded.

 

[Virtamales]

I dont know what happened but its just stopped working. Every time im done with a pose and add it, the other poses just get completely missaligned. Like it does NOT saves the person main control position and rotation. Its always uses the lats saved control position and rotation for every other earlier finished and saved poses and F's up everything. Position and rotation is NOT locked. It worked perfectly before but now its just died. No other script is used, all i did is load a different female model. Thats all. I dont have any other script loaded.

It seems @CheesyFX hasn't been around for a while... Hope he/she is alright. Recently a couple of new plug-ins that also save/load poses with icon UIs have been released, maybe you could try them out till CheesyFX is back on the hub...

 

[itclanon]

I've got a question that I cannot figure out for the life of me.

I'm trying to parent a dildo and hand (not hand control, as i'm using movement options to generate random movements of the hand), but between poses the dildo decides to move to a totally different location, and still stay parented. Almost as though the positioning is forgetting where it is on the Y axis (it ends up behind the person atom)

Boxes are checked for the dildo and person in the pose menu, and i've tried using different parent setups, but even after multiple saves of the pose it seems as though the parent option is causing it to relocate itself, specifically on one axis. Is this some kind of limitation to how the plugin operates? Or is there a way to get it to stay in the location I want it to be in?

 

[Pown]

@Pown The refactoring isn't exactly the problem. It's the issues that need to be resolved by adding new features like automated pose transitions. Aside from other things, it's not an easy task to blend 2 arbitrary poses and take care of any penetrations that are supposed to happen or end. But I just got a break-through I think

Planning a path between two arbitrary poses has quite the complexity. There are so many things to consider to even just have a path that has no collision and looks natural for a single hand movement. Maybe allowing the user to add some guiding transition poses could be used for a semi automated approach. Or limiting it even further, to only have sub pose states between which can be transitioned at random.

---

When using BL my impression was that whats actually missing is some slight variation inside a pose. For example, a procedural animation that controls the hands/arms. The head / upper body is already pretty cool with your gaze, and the action animation takes care of most of the lower body.
But the hands/arms are very static. I have made some basic experiments with procedural animation of the hands - basically choosing some random target touch points on its own body and then animating a hand control to move towards it.
Using some curves from a to b and simple raycasts to detect and avoid imminent collisions. I used a vector for the body and and shoulder to get some basic movement intelligence so the hand would not rotate around the wrong side of the body etc.

Anyway, its way harder than expected to get even remotely natural looking movements - and I only tried to animate a single hand that touches the own body.

Maybe it makes more sense to have some "procedural behaviours" that are part predefined and part dynamic. For example, some procedural "move your hand over your hair" / "touch your but" / etc. Something between a keyframed animation and a completely coded up animation. The system would then choose behaviours depending on the current context / whats possible to reach.

Last but not least, thank you for the immense time it must have taken to make VAM interesting for the "non animation" people!

 

[CheesyFX]

Maybe allowing the user to add some guiding transition poses

Transitions can span across an arbitrary amount of poses. There's an algorithm that selects the most meaningful path from pose A to lets say R in terms of steps in between and direction (pose order). There're no explicit "intermediate poses" the user can define tho. I thought about it but I'm not that happy with the UI representation etc. Also, my approach doesn't care about the starting pose at all. The current state - wheter it's a pose or not - is analysed and a transition to the target pose is performed. Using intermediate poses would contradict to this, cause the intermediate would only be useful for a destinct starting pose you had in mind.

When using BL my impression was that whats actually missing is some slight variation inside a pose

Press "Configure Idles" in the pose tab and adjust the settings to your liking. But don't forget to enable the global and the pose specific toggle. Destinct movements like stroking hair etc. won't be possible with this though. Better use Movements for that or timeline/idleposer.

 

[screwy]

I'm having a slight issue with body language at the moment, some features such as the throat/sucking sound effects, x-ray, and other minor things will stop working after a while or reloading the scene. The only way I've been able to fix so far is by reloading the bodylanguage plugin as a whole which works great and then I can press a button to just reload the presets, boom done. Only problem is I'd like to either be able to reload the plugin on scene load or be able to trigger the reload with a UI button so you can stay in "play" mode. Maybe I've missed something but there doesn't seem to be a way to do that in vam. Also curious if anyone else has had the same issue or if it could be a conflict with another plugin, there is a lot going on in this scene but I'm pretty sure there's nothing that should be causing an issue at this point. Thanks in advance!

 

[CheesyFX]

I'm having a slight issue with body language at the moment, some features such as the throat/sucking sound effects, x-ray, and other minor things will stop working after a while or reloading the scene. The only way I've been able to fix so far is by reloading the bodylanguage plugin as a whole which works great and then I can press a button to just reload the presets, boom done. Only problem is I'd like to either be able to reload the plugin on scene load or be able to trigger the reload with a UI button so you can stay in "play" mode. Maybe I've missed something but there doesn't seem to be a way to do that in vam. Also curious if anyone else has had the same issue or if it could be a conflict with another plugin, there is a lot going on in this scene but I'm pretty sure there's nothing that should be causing an issue at this point. Thanks in advance!

I never ever had this issue with missing SFX. There has to be a confict in your scene. The sucking sounds are loaded from the assetbundles within VAMMoan package. Do you have an instance of VAMMoan in your scene or do you load those bundles through other means like a CUA or another sound plugin? Also, what did you change creating your preset?
XRay can be buggy in that the male looses his skin (grey). But this happens very rarely like in one of 500 plugin reloads for me. Did you perhaps toggle it off globally either through the UI or by pressing Alt+x?

One can reload plugins programatically using MVRPluginManager.ReloadPluginWithUID(uid) but this should be a feature of an utility plugin and not BL itself. I'd recommend sorting out your conflicts first though.

 

[screwy]

I never ever had this issue with missing SFX. There has to be a confict in your scene. The sucking sounds are loaded from the assetbundles within VAMMoan package. Do you have an instance of VAMMoan in your scene or do you load those bundles through other means like a CUA or another sound plugin? Also, what did you change creating your preset?
XRay can be buggy in that the male looses his skin (grey). But this happens very rarely like in one of 500 plugin reloads for me. Did you perhaps toggle it off globally either through the UI or by pressing Alt+x?

One can reload plugins programatically using MVRPluginManager.ReloadPluginWithUID(uid) but this should be a feature of an utility plugin and not BL itself. I'd recommend sorting out your conflicts first though.

Thanks for getting back to me. I do have an instance of VAMMoan on the male atom, I also had one on the female atom early on but got rid of it because I noticed it would completely disable any moan type of audio. But even with both gone after saving and reloading the var the issue persists. I have noticed that part of the issue may be that FillmeUp isn't detecting any depth from the penetrator for the throat, which is why I won't hear any suck sounds and continue to hear normal moans. I'll attach a screenshot so you can see what I mean. This is also true for the anus, vagina, and other until reloading the plugin and it works as intended. As for what I changed in my presets for body language, I disabled force thrust for anus and vagina, increased volume to 2 for sex slaps in touchme (which I also noticed is broken until reloading, and then I also tweaked a few of the voice, expression, and ahegao settings for readmylips.

These are the plugins I'm using on the female atom:
Body Language
Naturalis
ForceForge
Orifice Dynamics
FloatParamRandomizer
Thigh Compressions and Vibrations
Glance
Movement helper

And these for the male:
Divining Rod
Embody
Force Forge
Glance
FloatParamRandomizer

And then I'm using JaxZoa Simple Keybind as a scene plugin. I'm curious if any of these plugins will be seem like conflicts right off the bat to you. Also, if possible could you elaborate on how the MVRPluginManager.ReloadPluginWithUID(uid) works? Is that a session plugin or something or is it like a script? Sorry if that's a dumb question haha. Appreciate any insight you can provide!

 

[CheesyFX]

Thanks for getting back to me. I do have an instance of VAMMoan on the male atom, I also had one on the female atom early on but got rid of it because I noticed it would completely disable any moan type of audio. But even with both gone after saving and reloading the var the issue persists. I have noticed that part of the issue may be that FillmeUp isn't detecting any depth from the penetrator for the throat, which is why I won't hear any suck sounds and continue to hear normal moans. I'll attach a screenshot so you can see what I mean. This is also true for the anus, vagina, and other until reloading the plugin and it works as intended. As for what I changed in my presets for body language, I disabled force thrust for anus and vagina, increased volume to 2 for sex slaps in touchme (which I also noticed is broken until reloading, and then I also tweaked a few of the voice, expression, and ahegao settings for readmylips.
View attachment 555392
These are the plugins I'm using on the female atom:
Body Language
Naturalis
ForceForge
Orifice Dynamics
FloatParamRandomizer
Thigh Compressions and Vibrations
Glance
Movement helper

And these for the male:
Divining Rod
Embody
Force Forge
Glance
FloatParamRandomizer

And then I'm using JaxZoa Simple Keybind as a scene plugin. I'm curious if any of these plugins will be seem like conflicts right off the bat to you. Also, if possible could you elaborate on how the MVRPluginManager.ReloadPluginWithUID(uid) works? Is that a session plugin or something or is it like a script? Sorry if that's a dumb question haha. Appreciate any insight you can provide!

It really sounds like you have the penis mesh collider plugin installed or any other plugin that modifes/disables the penis colliders. This plugin is not compatible with BL. The penis colliders have to be untouched, else penetrations are not recognized, which means no sounds, no XRay and no stimulation. Thrusting forces won't work either, but you don't seem to use them for some reason. The Tongue Flutter/Mesh Collider Plugin causes issues, too.
Glance is incompatible with my Gaze feature. Disable either one ore the other.
I could elaborate why ForceForge is also not needed with BL but if you want you can use it instead of the inbuilt Movement features.

MVRPluginManager.ReloadPluginWithUID(uid) is a command that could be used inside a script and hooked to a trigger. But reloading BL really isn't the way to fix this like I said.

 

[screwy]

It really sounds like you have the penis mesh collider plugin installed or any other plugin that modifes/disables the penis colliders. This plugin is not compatible with BL. The penis colliders have to be untouched, else penetrations are not recognized, which means no sounds, no XRay and no stimulation. Thrusting forces won't work either, but you don't seem to use them for some reason. The Tongue Flutter/Mesh Collider Plugin causes issues, too.
Glance is incompatible with my Gaze feature. Disable either one ore the other.
I could elaborate why ForceForge is also not needed with BL but if you want you can use it instead of the inbuilt Movement features.

MVRPluginManager.ReloadPluginWithUID(uid) is a command that could be used inside a script and hooked to a trigger. But reloading BL really isn't the way to fix this like I said.

The scene doesn't currently have any plugins that mess with penis colliders, but I did mess around with them a little very early on in the scene's production using AcidBubbles ColliderEditor. As far as I can tell everything was reset to default and the plugin was removed, but could it still be causing issues you think? After some more testing, I can say definitively now that until reloading body language it doesn't register the Man/Gen3 in the debug menu for "Penetrated by." I've tried removing bodylanguage, saving, and then re importing the poses but still having that issue. And changing the male's appearance hasn't been successful yet either. I'd really hate to have to rebuild it from scratch to fix this so curious what other things I could try to get this collision issue fixed. And not saying this is body languages fault at all, clearly I was a little too reckless with potential conflicts

 

[CheesyFX]

The scene doesn't currently have any plugins that mess with penis colliders, but I did mess around with them a little very early on in the scene's production using AcidBubbles ColliderEditor. As far as I can tell everything was reset to default and the plugin was removed, but could it still be causing issues you think? After some more testing, I can say definitively now that until reloading body language it doesn't register the Man/Gen3 in the debug menu for "Penetrated by." I've tried removing bodylanguage, saving, and then re importing the poses but still having that issue. And changing the male's appearance hasn't been successful yet either. I'd really hate to have to rebuild it from scratch to fix this so curious what other things I could try to get this collision issue fixed. And not saying this is body languages fault at all, clearly I was a little too reckless with potential conflicts

Then it's Orifice Dynamics. See this post.

Plugins + Scripts - Orifice Dynamics

Skynet updated Orifice Dynamics with a new update entry: update v16 Read the rest of this update entry... worked like a charm - nice!

hub.virtamate.com

 

[screwy]

Then it's Orifice Dynamics. See this post.

Plugins + Scripts - Orifice Dynamics

Skynet updated Orifice Dynamics with a new update entry: update v16 Read the rest of this update entry... worked like a charm - nice!

hub.virtamate.com

Holy crap that was it! Toggling off deep penetration solved the issue. Thank you so much, you are amazing!!

 

[CheesyFX]

Holy crap that was it! Toggling off deep penetration solved the issue. Thank you so much, you are amazing!!

Glad it's resolved
For the future: If there are issues with one plugin, try removing all the others one by one and see what happens. At least the auxiliary ones not crucial for the scene, and espicially the ones that do similar things like in this case.

 

[3rdStoryline]

How do I disable the penis morph usage? They are totally fkn up my altfuta character. Also How do I disable the auto thrusting stuff. xD I just want the facial expressions, and the extra wiggle of thighs and what not. The rest isn't needed for my setup, but I'm having a difficult time narrowing down everything to disable the unneeded, but couldn't find the penis morphs anywhere. It kept applying (i think) jackaroo morphs. Disabling the plugin entirely got rid of them right away.

You see, I have my own erection, foreskin, and other animations for the male gen of my futa character all done in various AnimationPattern Atoms. And the plugin is overriding all of that entirely.

 

[MimeRubberneck]

There is a small bug in the "Extract" feature of "PoseMe". Let's say I am extract poses from a scene where there are two Person atoms, "Person" and "Person#2". In my scene there are two Person atoms, "Girl" and "Guy". I define the mappings appropriately: "Person => Girl" and "Person#2 => Guy". This will silently fail if the pose has a slap and the slap target is "Person#2". The code for loading slap tries to get the atom with id "Person#2" which returns null. It should try to get the atom with id "Guy" according to the mapping instead. This line causes the crash:

                var parent = targetAtom.GetComponentsInChildren<Transform>(true)
                    .FirstOrDefault(x => x.name == jc["parent"].Value);

It also crashes if my scene does not have a mapping for "Person#2". I think the plugin should skip adding slaps for targets that don't exist.

 

[CheesyFX]

There is a small bug in the "Extract" feature of "PoseMe". Let's say I am extract poses from a scene where there are two Person atoms, "Person" and "Person#2". In my scene there are two Person atoms, "Girl" and "Guy". I define the mappings appropriately: "Person => Girl" and "Person#2 => Guy". This will silently fail if the pose has a slap and the slap target is "Person#2". The code for loading slap tries to get the atom with id "Person#2" which returns null. It should try to get the atom with id "Guy" according to the mapping instead. This line causes the crash:

                var parent = targetAtom.GetComponentsInChildren<Transform>(true)
                    .FirstOrDefault(x => x.name == jc["parent"].Value);

It also crashes if my scene does not have a mapping for "Person#2". I think the plugin should skip adding slaps for targets that don't exist.

Thanks for the detailed bug report!

 

[CheesyFX]

How do I disable the penis morph usage? They are totally fkn up my altfuta character. Also How do I disable the auto thrusting stuff. xD I just want the facial expressions, and the extra wiggle of thighs and what not. The rest isn't needed for my setup, but I'm having a difficult time narrowing down everything to disable the unneeded, but couldn't find the penis morphs anywhere. It kept applying (i think) jackaroo morphs. Disabling the plugin entirely got rid of them right away.

You see, I have my own erection, foreskin, and other animations for the male gen of my futa character all done in various AnimationPattern Atoms. And the plugin is overriding all of that entirely.

ReadMyLips/Males/Foreskin Enabled & FillMeUp/<Orifice>/Forces
The thigh wiggeling is done by ShakeIt, not BodyLanguage.

 

[Virtamales]

Hi @CheesyFX , I'm writing this again because when I wrote it 2 months ago, I didn't have a reply in some scenes I tweaked (Mr.Orange's Pleasure Room for instance), sometimes I get constant, looped error logs (The fourth line changing to "at CheesyFX.Throat.SetPenetrated…" or "at CheesyFX.Orifice.SetPenetrated…" depending on what is being penetrated in a specific pose. I don't know what is causing it. In order to mimic the conditions under which it happens, I can only say I use males with big penis (not huge, just above VAM average), and my female (the one having BL plug-in) are all Alt-Futas some of them have ColliderEditor presets that supposedly make penetration easier, but I've seen this happening with ordinary females as well. I also made one FillMeUp UserDefault preset (some BL updates ago) in which all Vagina thrusts and magnet are disabled and all Anus thrust and magnet enabled, but I don't know if my constant error logs are related to that. Any help with this issue will be much appreciated.

I also wrote some time ago that in some tweaked scenes the pose icons become unclickable and that I gotta reaload BL to make them work again. After reading some old posts here, I think it's just I have reached your plug-in's very limits, with scenes weighting more than 50 Mb, with about 5 levels, so many poses per level (up to 60-62 poses in total), 5 to 9 cams per pose, and some triggers per pose. I think in scenes this big, BL just won't work properly anymore: pose icons become unclickable and triggers won't even save. I also have a scene which crashed to desktop while saving and since there, all pose thumbnails become unclickable as well. Reloading BL won't work, nor hard-resetting. Maybe the json file got corrupted? How could I check if the save is corrupted? I write it here just because it might be helpful for crazy guys like me who try to create huge scenes.

 

[CheesyFX]

Hi @CheesyFX , I'm writing this again because when I wrote it 2 months ago, I didn't have a reply in some scenes I tweaked (Mr.Orange's Pleasure Room for instance), sometimes I get constant, looped error logs (The fourth line changing to "at CheesyFX.Throat.SetPenetrated…" or "at CheesyFX.Orifice.SetPenetrated…" depending on what is being penetrated in a specific pose. I don't know what is causing it. In order to mimic the conditions under which it happens, I can only say I use males with big penis (not huge, just above VAM average), and my female (the one having BL plug-in) are all Alt-Futas some of them have ColliderEditor presets that supposedly make penetration easier, but I've seen this happening with ordinary females as well. I also made one FillMeUp UserDefault preset (some BL updates ago) in which all Vagina thrusts and magnet are disabled and all Anus thrust and magnet enabled, but I don't know if my constant error logs are related to that. Any help with this issue will be much appreciated.

I also wrote some time ago that in some tweaked scenes the pose icons become unclickable and that I gotta reaload BL to make them work again. After reading some old posts here, I think it's just I have reached your plug-in's very limits, with scenes weighting more than 50 Mb, with about 5 levels, so many poses per level (up to 60-62 poses in total), 5 to 9 cams per pose, and some triggers per pose. I think in scenes this big, BL just won't work properly anymore: pose icons become unclickable and triggers won't even save. I also have a scene which crashed to desktop while saving and since there, all pose thumbnails become unclickable as well. Reloading BL won't work, nor hard-resetting. Maybe the json file got corrupted? How could I check if the save is corrupted? I write it here just because it might be helpful for crazy guys like me who try to create huge scenes.

Sorry for not answering. I remember why, it was because I don't had a satisfying answer to your problem. And I'm sad to say that I still don't have one. Not sure what's wrong in those scenes and I don't have the time and patience to dig through third party scenes that are not intended to be used with BL. All I can say is that unless you use a dildo and stuff it all the way inside till the base hits the trigger everything should be alright. ColliderEditor can mess up things fo sure though. The size of the dick shouldn't matter. I use rather large ones myself as you can see in the videos in the update section. Did you ever experience those errors whithin a custom scene made from scratch? If so, what causes it?
Generally, it's kinda pointless for me to debug v71 issues right now cause my dev build is so much different from the current release.

I don't think there's a limit for the plugin, unless you have low system ram. I have scenes with 120 poses that work just fine aside from slow loading. Buttons being unclickable is a sign of errors occuring during pose load. It's very strange that this persists after reload. Is this your scene and do you know its contents? If you saved the scene after an error occured the save could be corrupt. You could check if the poses are still there in the json by searching for "poses", but the issue could be anywhere. Try removing BL, save to a backup, then add BL again and use the Extract feature to import the poses from the original. Maybe this works.

If you want to know how to patch your BL to load like twice as fast with many poses, go visit my discord. There's a diy-fixes section. Those are all included in v72 but I'm not sure when I get to release it.

 

[Virtamales]

Sorry for not answering. I remember why, it was because I don't had a satisfying answer to your problem. And I'm sad to say that I still don't have one. Not sure what's wrong in those scenes and I don't have the time and patience to dig through third party scenes that are not intended to be used with BL. All I can say is that unless you use a dildo and stuff it all the way inside till the base hits the trigger everything should be alright. ColliderEditor can mess up things fo sure though. The size of the dick shouldn't matter. I use rather large ones myself as you can see in the videos in the update section. Did you ever experience those errors whithin a custom scene made from scratch? If so, what causes it?
Generally, it's kinda pointless for me to debug v71 issues right now cause my dev build is so much different from the current release.

I don't think there's a limit for the plugin, unless you have low system ram. I have scenes with 120 poses that work just fine aside from slow loading. Buttons being unclickable is a sign of errors occuring during pose load. It's very strange that this persists after reload. Is this your scene and do you know its contents? If you saved the scene after an error occured the save could be corrupt. You could check if the poses are still there in the json by searching for "poses", but the issue could be anywhere. Try removing BL, save to a backup, then add BL again and use the Extract feature to import the poses from the original. Maybe this works.

If you want to know how to patch your BL to load like twice as fast with many poses, go visit my discord. There's a diy-fixes section. Those are all included in v72 but I'm not sure when I get to release it.

Hi @CheesyFX , and thank you for your reply! I know Pleasure Room is not the most proper scene for BL, I disabled all the plugins and stuff that were not compatible. Anyways, after testing several scenes, I've seen a pattern here: the only one I've found so far that doest not give this error is one in which BL is the first plugin on the list of the "passive" Person, and AltFuta is the third, right after Timeline. In this scene the "top" or active person is AltFuta as well, and it works smoothly. In all scenes (tweaked or made by myself) that give the mentioned error logs (...at CheesyFX.Orifice.SetPenetrated… etc), all have AltFuta plugin higher on the list and BL plugin quite low, sometimes at the bottom of the list. There's also one scene made by myself that, gives an error that says somthing like : "... CheesyFX Person ResetColliders ( ) (0x00000) in Filename unknown >0", I tried to write it down the best I could, just in case it helps. After this error, the log displays the aforementioned ones. There's even one scene in which the error log shows up even if there's no pose selected, penetration just performed through Timeline, so I guess the problem has to do with FillMeUp. When testing the original scenes before I tweaked them adding AltFuta plugin, everything seems OK. Next thing I'm gonna test in those scenes is moving AltFuta plugin under BL on the plugins list, and see what happens. I'll let you know.

Regarding the unclickable thumbnails, I think the save file is corrupted, and the other one is a big mess of actions, triggers and pose levels, so nevermind, I'll try to fix it with PoseSaver. I think it's always good to have a couple of plugins that do similar things (like your amazing BL and PoseSaver) so we can achieve different things with them. I'm glad you are working on a new update for BL, I'm sure it'll be awesome, as always! I didn't know you had a discord, I'll search it, for sure! Thank you very much for everything!