I’m currently developing an adult game (not very far into the development yet) and just recently stumbled upon funscripts and bought a handy so I currently do not know my way around all the options and software and libraries.
So my main question to you guys is: How do I support the most devices without having to implement each one? My first thought was just using the API for the Handy but I think that is very limiting. My first impression after reading a bit on this site is to use the buttplug library as it seems to be well maintained and seems to support a wide variety of devices.
My secondary/side question is: What would you like to see as a feature when your toy is natively (or via buttplug) supported in the game?
My very limited ideas so far are: adjustable base-stroke when no action is on the screen and action based movement when there is action on the screen. As said I’m pretty new to this and would love to hear your input.
Probably mainly through Intiface and add other rare devices manully.
Personaly I’d like to have native support for Tcode devices bc my devices are using it
A scene to test and adjust the toys settings (e.g.
1.Set device’s range
2.Set devices behaviour for different scenario
3.A button/entity to test device’s functions)
Ease of Use/Manual: Had not thought about the manual part. Would probably make sense to have a manual for people who don’t know how intiface works.
Settings for Intensity: Of course.
sync: makes sense, probably latency adjustability with hotkeys (e.g. like in scriptplayer with +/-)
base-level: yep, that’s what I meant by base-stroke when no action is on the screen.
Yeah, Intiface is the User side for the buttplug library. So yeah, that’s what I thought.
In that train of thought: Does Intiface support your devices and what would be different when it was natively supported?
Because maintaining multiple different native devices would be a pain in the ass and honestly I probably won’t do it. Sorry. Your input is still welcome though.
Makes sense. I think it’s also the only way to change the intensity if Liquids whish of perfect sync is fulfilled.
Could you elaborate? As said I’m new to this and only have the Handy so a single axis stroker device and only recently found funscripts. The only thing coming to mind directly is having a stroke with bump and without bump. Maybe different behaviors for cumshot scenes (full strokes, quick/vibrating strokes on top)
I’m new to this field too (a few weeks), in my experience connecting Intiface to MultiFunPlayer has a little different beaviour than connecting devices directly in MultiFunPlayer (espesialy when value intensely changes, probably bc of update rate or something, I’m not that in to it yet)
That is very understandable. If it is possible you can leave some modding space so it will be easier for others to make mod to support other devices.
this is an inspiration from EDI, When in different scene loop play different script to “keep warmed up” / fit the vibe
Yeah, It seems Intiface has some limitations. Not sure about it myself but I notice the difference when connecting the ScirptPlayer directly or via Intiface (see here: Best Funscript Player for Handy (with vibrations)?)
I’m going to answer your question, but first the TLDR - you’re on the right track, use buttplug and build a great game, rather than stressing about Tcode.
Intiface has VERY basic support for T-Code. It can make a Tcode device go up and down. They’ve been TALKING about real support for the OSR2+ / SR6 for a while, but it hasn’t happened yet. But there are another 2-6 axes that Intiface just ignores. Twist, pitch, roll, surge, sway, suck. As someone who recently upgraded from the Handy to the OSR2 with pitch and twist… it’s a mindblowing experience when you find a set of scripts that utilizes the extra axes well. I’m going to add the suck cap, too. So, that’s what you’re losing by not supporting it natively.
But the simple commercially available strokers have SO MUCH MORE market share, I think a solo part-time developer would be crazy to do anything OTHER than just send linear stroke and basic vibrate commands to buttplug and call it a day. Even though I’d benefit from you giving it native support, I can’t really suggest you do it, unless that kind of nuanced haptic magic is the WHOLE POINT of the game, don’t worry about it. If it IS just a next-gen blowjob simulator, then by all means, build yourself an SR6 with twist and switch to focusing on Tcode devices as your main target, with buttplug linear stroker support as the afterthought!
