The remote control API follows the same structure as DeoVR: https://deovr.com/app/doc#remote-control
The SMB path starts with the shared folder. Anything above that shared folder is unknown, so you won't be able to get the full path with the drive letter. Is it absolutely necessary that you have the complete path? Can't you scan designated folders to see if the filename matches and just use that instead?
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!
