it also gives me this at almost all VR AV1 videos, even if i had KL codecs before, and updated them to latest after seeing this error. It doesn’t go away
Guess i go back to 0.47b again, all above it has way more problems(
You checked “Use the media back end of the OS” on the system tab? AV1 is NOT supported in v0.5b + default codecs. I hope this will change soon. It will work in XTP Web though. It should also work if the above option is checked.
well, i tried both check\uncheck on this option - changed nothing
funny enough 0.5b support it, but 0.57 isn’t
You restarted the app? It changes the backend on app load.
I did…
Just go back to 0.47b again i guess, it’s stable
I’m sorry, the video is playing normally while I’m running, but my OSR can only run in the stroke direction. Do I need to change any buttons to support multi axis script playback .
But when I drag them in the motion button, they can swing normally again.
Can you help me clarify my doubts
I think I need more information but ill just give you an overview.
Funscript:
The original 1.0 funscript standard is:
videoname.funscript
videoname.mp4
Multi-funscript (MFS)
videoname.<channel>.funscript
// Where <channel> = the channel name for example. roll would be videoname.roll.funscript
videoname.funscript
videoname.mp4
If the files are named according to the above format, then XTP will just load them.
Note: There is a bug where it doesnt see it on first scan. If this happens reload the library. If it still has issues try updating the media item metadata by right clicking it on desktop and using the context menu in web.
Funscript v2.0 (SFMA)
XTP greater or equal to v0.55b. You can also download the funscript 2.0 version here on eroscripts and all channels should load from a single funscript file. (There is a setting you may need to change on eroscripts to set 2.0 as the default format. v1.5 is NOT SUPPORTED IN XTP).
Random motion:
If the media does not have any the multi axis scripts listed above, checking the random motion checkbox on the motion tab will add motion. Below is an example of random motion on the roll axis.
Theres a few other settings that affect the motion.
Link:
If you want say the pitch to match the stroke actions 1:1, you can check link to script and select Stroke. This will move the pitch the same rate to the stroke.
Speed:
If Speed is enabled you can set the value to be a multiple to what ever the current speed of the linked script is. In other words making it move slower or faster than the linked funscript speed.
Hope this helps!
1 Like
Thank you for your detailed response to my question. After using random motion to control its roll and twist, it was able to move normally. Perhaps the script I used did not include these directions of motion, but I included them when running the script in Multifunplayer, or perhaps the software itself enabled this feature. Anyway, this issue has been successfully resolved. Thank you again
1 Like
If you scroll down to the bottom of the motion tab, youll find the channel map.
The script loading is controlled by the Track column. So in this case, TCode channel R1 is linked to roll so:
videoname.roll.funscript
will load and send commands to R1 on the tcode device.
The scripts have to have the videoname.<track>.funcscript for XTP to see load them.
I did end up figuring out this issue. Seems that if you run the application on Wayland it’ll cause this artifacting.
I fixed it by running the program in the terminal with “QT_QPA_PLATFORM=xcb [application path]” which I believe forces QT to use X as it’s platform. After that the program works just fine.
1 Like
Oh odd, Im running on wayland in Debian 13.
Maybe Debian 13 is automatically running it through X? No idea, the same issue happened for me on Bazzite and CachyOS. Both were fixed with the terminal command I used.
2 Likes
A few days ago XTP just stopped streaming from my PC to DEOVR on Quest 3. I can see the videos in the headset, but when I click on them, it just gives me a buffering swirl forever and the video never loads. I’ve reset the player settings, checked I’m on the latest release and I’m stuck. Any ideas?
Yes, some one brought this to my attention yesterday.
DeoVR has broken streaming from XTP web somehow. Streaming still works fine in Heresphere and the web browser.
I recommend Heresphere over DeoVR mainly for the fact you can interact with the web page while the video is streaming. It also has many options that Deo just doesn’t have. Also, the developer is not some faceless elusive company. I know its a paid app and that’s not feasible for every one.
If you need a free alternative and you’re on Quest, you can use the Oculus browser to stream 180 videos but its implementation is even more limited than DeoVR. The main downside for me is you can’t rotate the skybox (last I tried anyways). So its upright position only. If that doesn’t matter to you it may be a decent choice for you.
Here’s how to use the quest browser. Its been a while since I’ve done this but it should be the same.
- Open the Oculus browser and navigate to the XTP Web URL.
- Make sure “External player” is UNCHECKED
- Make sure XTP Web is selected on the Connections tab > Input connections
- Start a video with the internal XTP web media player.
- Click the fullscreen button on the bottom right.
- There should be buttons at the bottom of the full screen video for setting the format of the video. 180, SBS etc.
I will look at the Deo issue when I find the time.
2 Likes
Thanks. Is there a guide on how to connect Heresphere on Quest3 to XTPlayer? I’ve got the demo version of Heresphere and I can’t see how to connect to the PC for streaming, but I’m also half-wondering if it’s just the limitations of the demo version.
UPDATE - I think I’ve figured it out.
I’ve got Heresphere working fine on the Quest3 and I can see the XTPlayer videos and stream them via the web browser in HereSphere, but I can’t seem to get XTP to connect and play scripts. I saw a guide on how to connect and it said about putting in the Quest 3 IP into the ‘HereSphere’ part of the connections tab in XTP, but I just get ‘waiting’ - do I have to change the ‘23554’ port, or is there some other setting I’m missing? I know on DEOVR you had to set ‘remote control’ options or something like that, but I can’t see anything about that on HereSphere.
Yes in the User settings theres a setting you need to toggle on for remote. Side note, theres a bug in herespehere that every once and a while you need to toggle off and back on for XTP to find it.
Theres a PDF in the XTP windows build zip. For Linux and Mac users its also in the github
That’s worked perfectly. Thanks for your help and time! 
1 Like
How to load subtitles for playback in XTP?
1 Like
You cant currently, sorry.
Ok, that’s not totally true, You can in XTP Web player as long as the subtitle is in vtt format. You can convert srt files to vtt on lots of websites.
You need to name the vtt file the same as the video and funscript for XTP to see it. It should auto load it in the web player. You can also download it from the web player if the web browser supports it. Spoiler alert, no browser on the quest 3 will download it last I tried. I dont know why.
Still should work in the XTP web player, just not external players like heresphere.
1 Like