Anyone know what it might take to make a software bridge for lovense?

im trying out the demo on steam and there isnt an option for butplug io

Wild Life seems to want the actual IP of localhost(127.0.0.1).
Though the spoofer had some problems with parsing the commands, I made some fixes here, but tested it only with the menu test, so you should probably wait for the devs integration.

1 Like

is this still not working on the handy?

I made a new app based on this that does work with the handy with very limited testing. I only tested the game Carnal Instinct, and it does not currently have any wiring for pattern-based games as i couldn’t find any that use that.

it converts oscillatory “intensity” based events into motion for the handy, using the handy API and not bluetooth/intiface (that never worked properly for me anyway, jittery and unstable.)

2 Likes

Do you think this could be used to control the handy from chaturbate tips?

Almost certainly not. Too specific of a usecase i think, unless somehow chaturbate exposes a server like games do with the right ports and all, which does not sound likely. Not a platform I’ve used so i could be wrong.

1 Like

very nice UI on the lovense-handy-bridge, connects just fine to game and handy and motion works with the idle fallback.

however, none of the game commands (e.g. Game command: Function action=Vibrate:1,Thrusting:1,Suction:1,Rotate:1,Fingering:1,Pump:1 timeSec=0) seem to be translated to any motion :frowning:

tested with Third Crisis: Neon Nights

does this by chance work with third crisis, i got it connected but having issues to get the handy moving lol

with Take Me To The Dungeon and lovense-handy-bridge it shows connect but even during sex scenes still nothing. was really excited. maybe one day

Latest update of Intiface finally made my OSR2 respond! And there’s Virtual devices so I can test the Lovense Bridge! I can test out the LR_Spoofer and see if anything sticks out to me on why it might not be working. This is gonna be a huge help!

2 Likes

Bro, I am so annoyed. I just spent hours of my life making a lovense emulator so I could mod Lust’s Cupid only to see someone already did all that work for me… I totally missed this thread when I was doing research. I decompiled like 10 .dlls and scoured through them and went and found the lovense API and everything.

And the worst part is that I figured out too late that the lovense doesn’t actually track positional data so my work was double for nothing haha; I ended up needing to track animators in unity instead.

Ya, I think the Solace Pro can take positional, but lovense mostly deals with vibs and oscillation. I haven’t poked at this project in a while, but I think it would be worth revisiting, and a collab on it would be welcome

I’ve built a bridge that translates positional data into something usable for t-code USB serial devices, in python; totally avoiding buttplug.io since I’ve had bad experiences with it in the past. Currently needs that positional data to come from a .dll for BepInEx since Lust’s Cupid is a unity game. Works on my computer currently, but working on rebuilding so it can be dragged + dropped on other systems.

Also need to delete all the lovesense stuff happening on 20010 since it’s not being used, but haven’t bothered to do any code cleanup yet

The problem with the lovesense bridge idea for stroker devices is that the dev needs to specifically build for the solace pro / feed relevant positional data to the toy, but very few games actually do that. Most are built for vibrators and oscillators as you say

2 Likes

The latest Intiface update (buttplug.io) actually made a GREAT update to how it handles TCode v3. My OSR2 functions fine for linear scripts now. It doesn’t really do multi-axis, and I don’t think qdot has plans to expand that as a priority, but it’s good to keep in mind that routing lovense to intiface can work better now. We might need to make a translator for oscillation to linear position.

1 Like

I’ll have to give it a try again, thanks for letting me know