Integration for those games seems pretty cool. I don’t play them because they make me sick, but definitely seems more interesting than funscripts.
I will say that the waveform thing they are working on right now won’t do any good for that either haha.
Thanks for testing and for the detailed feedback.
The pause behavior you saw definitely isn’t what I expect: the app is intentionally supposed to auto-park the OSSM on pause, but on my setup that means retracting of course, not going to full extension. May I ask how the reverse checkbox was ?
So before changing that behavior, I want to understand why the same park command is being interpreted differently on your machine. I’m going to check the Reverse/orientation mapping and the assumptions I made around the OSSM position range.
Your Min/Max software range suggestion also makes sense and I’ve noted it.
I also will update the documentation to explicitly explain how to enable the HereSphere Timestamp Server.
Thanks again — I’m collecting the feedback first and will roll the fixes into the next test build rather than pushing changes one by one (doing this on sparetimes).
I don’t believe I had the reverse checked because I was using a script designed for the machine.
I would say, I’d prefer pause stay in current location rather than move to beginning of rail. It goes back to that situation I mentioned with the setup of percent rail youre using. Let’s say Youve set your rail to only use 60%-85% of rail. This would be just inserted to full depth. If you need to pause to re-lube, then you’d want it to either stay in current (still matching where it is from the script) or go to only the minimum depth Youve set so that you can easily insert it again before starting the script. If it goes back to 0% then you may have problems aligning it again, especially if youre at a relatively fast section of the script.
Indeed. And I had the same problem before.
The problem is: we need a “stop” able to fully retract the arm as an “emergency” command. But Heresphere timestamps doesn’t seem to make a difference between a “pause” and a “stop” (or maybe I missed smth, I’ll re-check this).
If so, I should keep this pos=0 feature as security measure but maybe I could add a “restart feature” including a slow comeback to a deeper position before reading the script (with its fast section) ?
Just wanted to say, this looks like great stuff! Especially since multifunplayer does not work on linux!
i thought that pos=0 on scripts were full depth on the ossm? (i know it’s backwards compared to other devices). if you’re using reverse option, maybe it’s applying to that? I was under the impression that the actual emergency stop thing was a specific command to the ossm and not just position 0. i believe it behaves differently. i remember when the emergency stop is triggered by the ossm itself, it will actually just completely disable the unit until restart.
as for the security feature, perhaps that should be upon exit of heresphere not a pause. i know i’d definitely prefer it stay in the exact position it started on a pause, and that’s how it works on the ossm funcscript player.
One thing i would suggest is to compare behavior on the same script between this player and the one on https://docs.researchanddesire.com/ossm/tools/funscript-player if you havent already.
Ok got it.
I have what you need ! See below. One checkbox for autopark (who will be on low position, reverse checked or not) which will gently come back to its previous position before reading the script again. Not checked, the arm won’t move on pause but only by video change or double stop or quit the app.
About the R+D script reader, it should be the same since the communication language is the same.
About other toys, have you a specific request ?
thanks. tested it. minimum depth is working great. maximum not so much. it seems to stay at 100% for maximum. i have it at 51% as a test and it still looks like it’s either full rail or nearly full rail. (which is the same as it looks at 90%).
The stopping is working great.
another feature that would be good for use as well as testig would be a test section where you can manually slide from 0% to 100% without heresphere so you can test the positioning and verify the depth settings you want before starting the script.
Had any opportunity to look at the max depth setting issue? No rush, just wondering.