• SLR

  • Broken PT AI Crashes Video

The video in question is this:
https://www.sexlikereal.com/scenes/raw-taboo-innocent-promises-22033
I'm using the Quest Pro.
Every time I load it up and then turn on PT AI (no matter the preset), it eventually gets stuck at some point of the scene (usually early 10-15min). I can still hear the audio in the background, but the image is frozen. The only way to unfreeze the image, is to clear app cache. Restart doesn't fix it.
Additionally, the PT Mask, is not working as well. I can see a few things are getting passed through, but 95% of the image isn't (no matter the preset).

Please look into this. Thanks!

    I am using Quest 3 and don't get same problems watching mentioned video as you. There are definitely still some problems.

    After the 13.17 DeoVr update (april 2024) my Quest 3 also experiences crashes. This usually happens after 20 minutes of PT AI use. First picture vanish, then controllers stop working. Then it crashes. Notification says: There is not enough memory to run DeoVR. I just have to start DeoVR again. Not same problem as yours but suggests something is not right with AI PT in general.

    PT mask works ok, girl is crisp and no background detectable. After 20 minutes of video I can see some out of sync. Not bad but you can see it. After 50 minutes out of sync is horrible. It is even worse than the trouble SLR had week ago: https://forum.sexlikereal.com/d/8260-ai-pt-mask-out-of-sync

    I have never seen this kind of video. It starts ok, but the out of sync increases by the minute and at the end of the video it is worst I have ever seen. Really weird??

      milky97 hey
      What do you mean by "clear app cache"?
      Which version of the app do you use?

        Picouser yeah, we have some masks generated with different FPS. That's why sync issue aggregates over time.
        Looking for a proper solution.

            iddqd Ok, thanks for clarification. That's the reason.

            SLR has many 90/120 FPS videos and AI PT does not work with them (This is shame and should be fixed). I think it works only 60 FPS. Am I right? Do you mean you have for example 59,94 FPS mask for 60 FPS? But why do you use wrong FPS mask? Does it save time or power? Sounds silly.

            I am curious. What proportion of masks are "wrong" FPS compared to whole mask library? This is the first one I have seen and I have watched a lot 🙂 Mask should be redone. That is proper solution.

                Picouser Yeah, the problem is only with 59.94 vs 60. That's going to be fixed soon, I know it is strange. Just an artifact of development