Plugins + Scripts HK FullPersonControl

Horing Koning submitted a new resource:

HK FullPersonControl - Person Automation and Control

BETA​

These are complex systems that require some refinement. Community feedback welcomed.

Click to expand...

Male characters have limited support. Default expressions, automatic intensity via male genitalia colliders, and joint settings are not yet available.

Click to expand...

Targeting is WIP, some targets on Persons can be detected as obscured when they aren't.

Click to expand...

Manual change: Disable Auto Expressions and Auto Blinking on...

Click to expand...

Click to expand...

Read more about this resource...

Neat, an alternative to BodyLanguage. I'll be looking forward to how it continues to develop.

I'm sure you have a massive list of things on your TODO list already, but I hope you don't mind if I drop a couple of items that would make me use it more often, even in this early state, of which I'm sure some are on your list:

• The freedom to assign targets to the eye tracking feature is pretty robust and will go a long way. One recommendation would be to either hardcode an interpolation timer between saccades, and target switching. Ultimately allowing the user to adjust it would be great, but right now the instantaneous jumping between targets is a bit unnerving.
• The one thing that would really encourage me, at the least, to use this plugin is trigger hooks. Hooks on almost every state. Value change updates, like arousal rate, and major and minor events, like climax, and any future events you plan to implement.

I was going to mention something about editing the expression groups, but just noticed the note saying that editing them is not supported yet. Though, when you do enable editing, allowing users to edit the default expression, or at least a copy of the default expressions would be really helpful.

Anyhow, great to see new work in this area of plugins, I wish you all the best!

- Cheers

Oh yeah, and one more thing I just noticed: Cleanup when disabling individual features and the plugin as a whole. Currently systems like eye targeting continue to execute even after the plugin has been disabled. Also, disabling the plugin leaves any expression morphs frozen in their last state, it will go a long way to default or zero out any of the morphs in the current expression group when the plugin or sub-feature is disabled.

These aren't criticisms, but these are things that will get more people using your plugin more often, and aside from the ensuing internet points that comes with, more bugs will be found as well as more feedback.

Found another cleanup issue, which is a bit more troublesome. The Eye Targeting system breaks eye tracking on a VaM Session level. If I completely remove the plugin, and load the same scene again (without the plugin in that scene), then native eye tracking for that person atom will not function and requires a hard reset of VaM. I didn't test whether a plugin like Glance would work or not.

Anyhow, important bug, thought you'd want to know.

I love plugins like these, I just know one day, some creator will create an artifical soul just because they want to jerk it to the male dress up sex game.

@Metix, thank you for your feedback, I appreciate it.

My plan is to create the base systems first and then expose fine control and parameter adjustments.
The defaults are designed to be realistic and I want to get that batted down first.

Feedback like this helps me adjust these systems to be more lifelike where possible, so they are encouraged.

Regarding the saccades, I made an update before this release to remove other jarring behavior and it seems like they are set outside of the eye movement logic, bypassing the interpolation. I will look at resolving this in the next update.

As for the cleanups, they aren't currently cleaning anything. Disabling features essentially pauses execution, but I should be able to relatively easily add some cleanup logic.

Found another cleanup issue, which is a bit more troublesome. The Eye Targeting system breaks eye tracking on a VaM Session level. If I completely remove the plugin, and load the same scene again (without the plugin in that scene), then native eye tracking for that person atom will not function and requires a hard reset of VaM. I didn't test whether a plugin like Glance would work or not.

Click to expand...

I will investigate this, but I theorize this would only happen if VaM does not completely remove and/or reset loaded objects when a scene is loaded. The aforementioned cleanup logic could assist here if this is the case.

Thanks again for your feedback.