For the version, of course I am using the latest one, 1.4.2.
What are the settings you are talking about? I’m not sure I changed any settings compared to the default ones, but I will check.
For the second point - I think you should check how ScriptPlayer works. Basically, it can either work as a local video player, but also (and I think this is much more useful) ONLY as a funscript player (no need to have access the video) that syncs with an external video player.
Technically, I think ScriptPlayer periodically polls the external player via their API (either Kodi, VLC, or HereSphere - most useful is HereSphere since it has VR support), gets the name of the currently playing video there, loads the same .funscript file, and syncs the timing.
I think ScriptPlayer or MultiFunPlayer are open source, so you could just have a look at the code there and port it to FFD. That would be fantastic.
(Note that, no, I am not playing videos from the PC. Only the Quest access the videos - either locally or via SMB/NFS. The PC only needs access to the funscript files, that’s the point)
By the way, note that this external video player synchronisation thing has nothing to do with VR in itself. I could use it as well to play standard videos from my Raspberry Pi with Kodi.
You can even sync to a player on the same physical device (ie localhost) which is probably easier for development / debugging. For instance Kodi on Android (note that VLC cannot work locally as the Android version does not have the same API as the PC one).
I did get a slight bug with the edging feature using the kirroo pulse interactive where on some occasions it would keep vibrating at a constant rate even when I press the edge button. I am not surecif this is a bug with the edging button, intiface or the toy itself.
Here are my settings for the Titan 1.1. Again, they are the default ones. I tried to change them a bit but always the same result. What’s interesting is that I think the test button does what it’s supposed to do (I hear a motor activating, then half a second later the motor stops, then again after a second later the low intensity motor activates).
So it’s like it’s missing a command to tell him to stop, or something like that.
@Sasong I reproduced the edge bug and it should be fixed
@mirdanhel I never reproduced your bug but I still tried to change how I’m stopping devices (I now send the stop command every frame). Let me now if it’s better
Unfortunately, the new version does not fix the bug. It may be even worse as I think now the test command does not activate the right motor, but I am not 100% sure about that.
When you say you cannot reproduce, what do you mean? Do you have a Kiiroo Titan to test with? If you don’t, I don’t think you’ll be able to reproduce. But if i can help by sending debug logs or things like that on mine, let me know.
What about synchronisation to external players? Did I convince you that it would be a killer feature to have?
For me this would be even more important than fixing the Titan issue.
It’s very unlikely that the change broke the activation of your right motor.
Nah, I don’t get a Kiiroo Titan but I tried with other vibrating devices. If the bug was from the app logic I could have reproduce the bug.
I don’t really know what to test. Can you confirm that the bug appear even when you have no script selected and you are using the test button ? At this time the Kiiroo Titan never stops ?
Yeah I looked if it was possible with HereSphere and how it was implemented in MultiFunPlayer because the doc from HereSphere is really bad. The difficulty is I don’t own Meta Quest but I also seen that there is a demo of HereSphere available on Steam. So if it works the same if will be possible to implement it.
Unfortunately I don’t think I will have the time to work on it soon
Yes I think the bug happens only with a Titan, that’s the issue. Other vibrating devices wont show the issue. However this is still an app bug, not an Intiface / buttplug problem as other players dont suffer from this.
Indeed it happens even with no script selected/loaded. Just clicking the Test button is enough to send him into a never ending low intensity vibration. As I already wrote, i think it happens once the test part / command is over. Ie, the low vibration starts not immediately but about after 1-2 secs. If you create a specific version where the test button would activate for 10 secs, i could confirm the issue only appears after 10 secs.
Apart from that i dont know what i can send you to help you identify the bug. Probably i can obtain intiface logs at a very low level (high verbosity). Would that help?
Yes about HereSphere you don’t need a Meta Quest at all. Just install the steam version of HereSphere (and same with VLC / Kodi, but they are much less useful than HereSphere anyway).
For HereSphere I did a simple proof of concept and it’s working. Now I need to adapt everything to handle the script, UI and all shit together So it will definitely be in the next version !
Very good news for HereSphere. Impatiently waiting for that next version then! Yes indeed if HereSphere is supported, Kodi / VLC are more like bonuses.
About the logs - how do I obtain them or capture them? And where should I send them? You dont have a GitHub for this project?
Seems like the edge button issue still persists. Im encountering two types of them. First is a minor one being you have to press the edge button twice sometimes to get it to stop the device and second is when you press any button but the kiiroo pulse seems to keep playing at a constant vibration like it has been disconnected which has ruined a few sessions.
@mirdanhel@Sasong I am trying another fix for the next release that might fix both problems hopefully
HereSphere integration is complete ! Now I need to test if I didn’t break anything else because I had to make huge changes in the code. So expect the next release this week
So it will definitely be in the next version !