• Support

  • "error loading project data - timeout" - March 2021

https://forum.sexlikereal.com/d/689-error-loading-project-data/18

Schnart 2 days ago
Hi ! I just wanted to state that I suffered from the same error message today aswell. SLR App updated itself to the latest version when I started it and afterwards I got the same error message in VR. Blank screen (completely black) and the words: Error loading project data. -> Operation time out.
Nothing more happens.

fluxys 13 hours ago
I´m having the same problem here with Quest 2 from germany right now. "Error loading project data - timeout".
Would be nice if someone could have a look. Thx!

Bobson Yesterday at 7:58 PM (Discord)
Hey - today is the second evening SLR wont load on my Quest2.
Error: "error loading project data - timeout"
Tried twice in 30min ....
Do you have another idea than buying 10TB hardrives and download all the stuff I like ...? 😅
My internet connection is fine

Rakly3 changed the title to "error loading project data - timeout" - March 2021 .

Hi.
This looks like a problem with the provider. I think we need to start with a speed test to make sure our service is available. And also make sure that it is not blocked by a firewall...

I've had this problem on 11th March, yesterday and today. Sometimes it works (2 hours ago) and now it doesn't work again.
I tried to deactivate ipv6 support (cause that was an issue related to speed problems) and I've tried the SLR app (normally the DeoVR app) on my Quest 2.

Think I will cancel my premium subsription and use the plexi server only, cause it just doesn't make any sence to pay for something you can't use.

Sadly SLR is unavailable for me again ... this morning it worked (just started it for testing) now the same error.
Seems like the new update SLR with DeoVR is so unreliabel (at least in Europe?).

  • Yar replied to this.

    Anton
    Hello!
    Can you provide your speedtest number? There are no technical problems on our side.
    Perhaps you need to deal with your ISP?

        Sure (:

        My speedtest ID is 57408

        Do you maybe have any idea what I can do with my ISP?
        When the error occur I am still able to download SLR content with max speed

        (with Windows / Firefox ofc)

        (maybe this helps the devs🙂 )
        I have this problem (at least the last three days) only in the evening - during the daytime it works fine

        Seems like it became a permanent problem 😩
        Sadly I'm not able to watch SLR on my Quest2 anymore (at least not in the evenings)

        I think it s a German server - issue since I m also located in Germany...

        What I've tested right now:
        (While the error occured on the Quest2/DeoVR) setup DeoVR on my smartphone - same error.
        Then used Norton (on my smartphone) to route over a VPN (Austria) - then DeoVR/SLR worked.
        Sadly there s no VPN option for the Quest ...

        It s weird - Saturday / Sunday morning the error only happened in the evenings.

        Guys .... pleeeeeaaaase fix it ....
        (please please ....)

        sounds like an ISP routing something problem. had something similar with a videogame server that wouldnt connect with only german people so probably only solution to wait it out.

        would be nice to see if SLR might be able to find a fix tho

        After doing some tests with Anton it does look like the connection is deliberately blocked.

        Connection(s) during day, works.
        Wired connection from home, Quest 2, DeoVR, evening, doesn't work.
        Mobile connection but with same ISP, Android, DeoVR, evening, doesn't work.
        VPN, same devices, works.

        About half the routing to the SLR servers he has is the same as mine, I have no issues (other ISP).

        I was setting up a VPN server so we could try him connecting through my connection, and now my firewall is all messed up 😢 Nothing of inbound protocols work any more, FTP, DLNA, HTTP ... sigh

        working again for me.

        hope it was just an ISP hiccup. thanks for the elaborations on the issue and testing.

        really appreciated!!

        For me sadly not....
        17:27 worked fine / 19:44 the same error