Great thanks!
Khrull
Recent community posts
Yes, I have it search the user selected media library for the file if it cant find it in the same path passed back by the remote control.
I use the same code I use for Deo that I use for HereSphere. Not sure that was a good thing though cause Deo's implementation is kind of jank. Seriously, who uses 0 for true?! Still, dev wise, It was nice to not have to do much to the existing code. The only differences being DeoVR would pass back the web link URL directly if the streaming link was a url launched in the browser. I also didn't need to add the download attribute to the clicked link for it to play in the Deo native player.
Not a huge deal.
TBH you can leave it the way it is as I've already compensated for it and it works pretty well for me now.
I was just asking cause something seemed off about a remote control machine receiving a inaccessible path internally on the quest.
I'm glad to see a good VR player on quest finally has this feature.
Thanks!
I don't know what this incomplete SMB path looks like but I'm not sure an internal URI would be useful for any external remote controls.
The file name is an absolute necessary for me in any case.
Do you have any documentation for the remote control API yet? I have not found any but thought Id ask just in case I missed it.
Hey I'm the developer of XTP a funscript player for tcode sync. Im am looking at the remote API in HereSphere. I notice the path to the media playing has bee changed to "/storage/emulated/0/Interactive/<media>" for SMB and "download" links. My player needs to know where the media is located so I can pickup the script remotely. But it cant do this if the path to the original media has been modified.
Is this intentional? It would seem to me any remote software would require the path to the original file. Even if that IS on the local filesystem.
Thanks