Hello everyone, welcome to the Regolo Engine 1.8 release post!
New month, new release, new functionalities, new animations, as always.
Every time is a race against time because I want to put all the good stuff I started developing during the previous weeks, and this one makes no exception.
Check the video and the feature list and I think you will be pleased 😎 .
The 1.8 video
What's new
Here's an overview of the new stuff, check the proper section for insights and instructions.
Fixes
I was on a rush on this since all the extra stuff bundled, so let me know if you notice something wrong, I will look into it as soon as possible.
The new composed behaviour
I experimented this time too and created something that went really further than my expectations. A new class of behaviours that are able to mix and match different sub-behavioural sets melting them in a balanced and harmonious way.
In simple terms, in this new behaviour the girl has a lot of sexual actions in her arsenal and can transit from one to another seamlessly, going as far as to merge them. This means that while past behaviours were executed like isolated happenings, this new one merges different behaviours in a big composed one.
So, for example, she knows precisely when and how to place every body part according to what she wants to do in a particular moment. I'm sure the video can explain better what my poor English is not able to properly communicate 😜.
Obviously they are all compatible actions but nonetheless before this it was impossible to make them live together, and in this new generation the synchronicity of the actions has reached the next level. There is still a gigantic work of refinement behind, but the harmonious alternation of the gestures was simply not possible before.
As hinted in the feature list I also developed a sort of interruption system to make this possible. Through it movements can alternate instantly. Unfortunately, this capability is not heritable from old behaviours because they belong to the previous generation and are not easily upgradable (at least in terms of time to be spent)
Clearly this is very experimental, I fixed a lot of bad matching but it is possible I could have overlooked some nasty moves. There are a lot of potential combinations here too so expect some bad transitions occasionally.
Important note: since all the random collisions that come with this tight pose, I strongly recommend to disable the soft body physics. It gave me a lot of inconsistencies when on.
If you want to check the new animations immediately choose the "Mix @Chair" obsession or even put it in the animaObsession section of the config file
Lastly, this is the first part of a work that will end next month. The second part will enrich the animations set, will give some love to audio and will provide a bit of control on the execution flow too
The new dance UI
Firstly, starting with this release you have to place songs used for dancing in a "Dance" folder, to be created inside the RegoloEngineAudio one.
This means all the songs have to put under:
<VaM>\Custom\Assets\RegoloEngineAudio\Dance
The plugin will load all the songs present in such folder at load time, meaning you will not have to write the song names in the config file and restart the plugin every time. This also implies that the dance section in the config file should not be used for now, and surely not for such purpose.
That being said, you can now manage the dance songs directly in the plugin UI.
This can be done through the following functionalities.
All the above settings should give a good degree of control over music flow for dance behaviour. Let me know if you think something else should be added 😉 .
The dawn of the external tools integration
I'm pretty sure most of you know TempestVR. He is the super smart guy that built the OSR3 (and 2 now), a sex robot machine that works great with VaM (and not only with it) and that promises to deliver wonders in the future.
I had the chance to talk with him about the potential synergies of our two plugins and after few days I started working to a direct interface between them.
I made some tests and I ended up implementing a custom version of his TCode plugin builtin directly in the Regolo Engine.
It wasn't easy since I still have not built the OSR for myself (Lego's my limit 😂), so it was some kind of blind coding. Anyway with tempest's help the result is native compatibility between OSR and Regolo Engine.
Some info on what this really means:
This is what you will see once enabled:

Some other info:
TLDR: activate the Tempest addon from the config file, set optionally the auto-connect parameters in it, choose the "Blowjob @Kneeling" behaviour and enjoy 😁 .
New behaviours will be enabled for this synergy in each release, and I promise to build the OSR2 asap in order to free the poor Tempest from the test builds tsunami that I threw to him last week lol.
This is his Patreon page by the way: https://www.patreon.com/tempestvr. He definitively deserves attention and support.
Let me know your feedback on this brand new dimension of the engine.
How to use it
Regolo Engine 1.8 has been built and tested on VAM 1.18.2.1.
If you have the Enchanter version the first thing to do is to put the RegoloEngineAudio folder under Custom/Assets. Please note that the Enchanter room will try to load all the audio files (500+) directly at the beginning, so be sure to have placed in in the correct spot. The songs for the dancing load at the beginning too.
Also an important recommendation: safest way to start over the plugin execution is to clear it, reset girl's pose manually (from the person -> control panel) and then reload it. The plugin tries to automatically reset the pose at every start but it's not always perfect.
Please remember the furniture list known by the girl, below. You can delete and add duplicates but there always must be one and only one couch with the guy over it. Also, don't create steeplechases and create a regular environment as the standard room provided, please.
Bugs and caveat
- The Enchanter room tries to load 500+ audio files at the beginning, but it doesn't need to do that again if you just reset the plugin.
- Being it totally procedural, there can be better and worse runs
- Some behaviours have really a large spectrum of possibilities, so some unlucky variations are unavoidable.
In the end
And that's it, folks. We have the long, comfy wall of text of the monthly post, we have the new release, and the month isn't over yet 😁. I'm happy with the result, I hope you will enjoy it as well.
Next stop is 1.9 in March, stay tuned!
RegoloVR
Zuzakiin
2020-03-01 09:37:35 +0000 UTCMpMan
2020-02-28 20:42:17 +0000 UTC