![]() ![]() If the toy cannot handle what is in the script, it should automatically divide speed by two if necessary, but this should be the job of the driver, not of the encoded data in the script IMHO. So it seems to me the correct way would be to have the funscript scripts encoded very faithfully to the source, then have buttplug or any other toy "driver" make the corrections. What you describe is a limitation of the launch, it may not be present in other toys. I don't think it's the right way to go if you want funscript to be an universal, reference format. Definitely interested to see what you build! :D Depending on how you're planning on mounting things, cellphone vibrators might be a bit small or too high frequency, but it's worth a shot and you can iterate on motor choice once your basic toy is together. Their big secret was varying the size of the offset weight on the motors, so it provided different frequencies throughout. That was an interesting toy idea, as they made it so you could basically relay "stroking" motions through vibration. Sounds like you're trying to build something similar to the original virtual hole: Bluetooth could be added to the motors controller with compatible commands so it instantly becomes compatible with the rest of the system. They would need to be well isolated to prevent the circuit from becoming an un-intended Stim machine. Is there somebody who experimented with mini motors used to make cell phone vibrate? I've got this idea of creating a poor-man's-launch using a few of those to create the buzz.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |