sankaku is like this as well. it is what it is
Anyone know what the difference between HAMP and HDSP is?
So I’ve installed the ‘Moaning’ mod that uses MelonLoader, and I can’t seem to run both MelonLoader and BepInEx at the same time - any chance of porting this to MelonLoader? I don’t know how much of an ask that is, so if that takes a lot of work, no worries.
working on the melonloader version
HAMP (Harmony Alternating Motion Protocol):
Continuous back-and-forth movement at a variable velocity (speed). You set a velocity percentage (0-100%) and the device moves continuously at that speed. This is what HandyMod uses — it maps the in-game sex speed to a HAMP velocity value. Simple and smooth.
HDSP (Harmony Direct Stroke Protocol): Direct position control. Instead of setting a speed, you tell the device to move to a specific position (0-100% of the stroke range). To create a stroking motion, your code must alternate between two positions at timed intervals, essentially generating the stroke pattern yourself. This gives more precise control over stroke length and timing, but requires more complex logic to produce natural-feeling movement.
TL;DR: HAMP = “move at this speed”, HDSP = “move to this position”. HAMP is easier to implement and works well for mapping game speed to device speed. HDSP is better when you need exact control over where the device is at any given moment.
Here are all versions:
Windows versions are tested
Linux versions need to be tested
4 Likes
ngl, awesome to see this, sad its still locked to using strokers and doesnt have the ability to work with just vibe toys. Any plan for that or no ?
that should work already.
If you connect a vibrator instead of an stroker device the speed is not translated into patterns, it just runs the vibration at this speed.
Intensity can be modified with the multiplicatin setting
Thanks for the mod, it works very well and the game is very nice too 
As an addition to the mod, do you think that would be possible to implement a simple filler while not in a sex scene ?
during the whole game?
You legend!
Yea that would be cool if possible, sometimes there are large gaps between scenes, or at least in the early game it feels like
new version available
links have been updated
1 Like
Thanks for the quick melonloader implementation! I can’t seem to find the config file though, am I just blind or is it missing?
found it → \UserData\MelonPreferences.cfg
Since the game has manual movement, does the mod use HAMP for auto speed, and HDSP for manual? Overall I think I would prefer HDSP, since the blow job scene requests change the movements.
It is using HAMP mainly.
HDSP is prepeared but not actively used at the moment.
I need to implement some syntetic stroke patterns, but since the game is not delivering any position data it will never match any animation.
I will put that into the next version.
Have you been able to test it with a non stroker? Ive tried about every combo of changes i can come across and nothing has worked.
Vibe on and connected to initface, fresh game download, v0.95.16 for windows
Tried downloading both melon and bepinex version, tried installing by putting the files from your pack into the game folder only, into their own folder only, both in game folder and not.
Running installer from game folder returns an "in use " error so i run the one outside of the game folder and its successful.
For both melon and bepinex, in game ive removed all mods and tried a fresh game download, as well as a fresh save. i can slide the toy in initface ot make it vibrate but the game doesnt change it.
The ONLY thing that seems to have any change on the toy, from in game, is ending the scene with the back arrow at the bottom right.
Any insight you have would be fantastic lol
no, i cannot test non stroker as i dont have a device.
the installer i meant to be run from its own folder.
But your tests give me a hint.
Which intiface version are you using?
files habe been updated
__
Hey, thanks for the detailed report! I’m pretty sure I found the issue.
Short version: Vibrators weren’t being recognized correctly due to a protocol change in newer versions of Intiface Central. v1.11.0 should fix this.
What was happening: Intiface Central uses Buttplug protocol v3, which reports vibrators as ScalarCmd instead of the older VibrateCmd. The mod was only looking for VibrateCmd, so your device got detected as “unknown type” and never received any commands during scenes. The only thing that worked was StopDeviceCmd on scene end, which is universal — that matches exactly what you described.
To confirm this was the issue, can you send me your log file from v1.10.0?
- MelonLoader: MelonLoader/Latest.log
- BepInEx: BepInEx/LogOutput.log
Look for a line like:
- Device found (unknown type): YourDevice — that’s the bug
- Device found (vibrate): YourDevice — that’s what it should say
To fix it: Grab v1.11.0 and install it the same way. If you want extra debug output, set DebugLogging = true in the config — it’ll show speed values, velocity updates, and device commands in real time.
Let me know if it works!
1 Like
I cannot seem to get it installed correctly. Followed the instructions exactly. Perhaps it is because I am on Bazzite? I did make the files executable before attempting install