@Gmadu1993 

This is great news. Kudos to TPLINK for taking action. Hopefully we can recommend this router again soon!

@Gmadu1993 

I got the ax10 ready in a box to be sent back, and an ax50 I am now using as the daily house router. Hopefully they can push this out fast enough that I can RMA the Asus router as well and only have to use the ax50 

@XZlayeD we will see. After a period of time elapsed, it seems the issue came back, albeit with less intensity. However, it was a stark improvement and I've already asked to schedule another appointment.

@Gmadu1993 May I ask how you record your gameplay (shadowplay)? I never did that and I have a session with support today.... How they connect with your teamviewer... Did you provided your Id and password?

Hi Everyone

Glad to see the remote sessions are making progress.  If anything in detail is shared with me I will share it and once we have a full resolution I will work with the team to create a FAQ and post it here. 

Hey @Rcaldieri, I don't know if you've already had your appointment with them, but yes just email them your TeamViewer ID and Password that you see when you open the program. As for the recordings, I'm not using shadowplay. I have my home PC and Oculus quest 2. I simply pressed the right controller home button, looked to the left hand side where it says record video, and gave it a click.

When finished, I connected it to my PC, then used side quest to download the video from quest to PC.

I have same issue with AX50 on virtual desktop and oculus quest 2. Will it be fixed with future firmware updates or should i return my AX50?

@kansav 

the good news is, tplink is actively working on the issue.  the bad news is, we don't know when the fix will be out (hopefully it can be fixed).  so if you have a short time limit for your returns, you have to take that into account 

@kansav 

Honestly, until this issue is fixed, I think the only thing to say on this matter is that no one at this point in time can suggest or promote these routers as a good choice for VR.

At best, we will see a firmware fix within this year.

At worst, it's a hardware issue and we will all have to return the units to the manufacturer anyways.

Frankly, I don't expect a fix anytime soon. But with the recent increase in communication with the TP-link R & D team, I do have hope that we might eventually​​​​​​​ see a fix.

I just came here looking for help, as I was recommended to use this router model for Quest 2 by other Virtual Desktop users. However, I am seeing 15-19 ms of network latency nearly always, even though it is dedicated exclusively to streaming to the Quest 2 in Virtual Desktop. The best I have seen was 9 ms, but it does not spend much time that low.

This is in contrast to my 6 year old AC router in general, mixed household use - which is due to be replaced - that is delivering 6-8 ms to my Quest 2 when not loaded excessively by other devices.

The bottom of my router shows ver. 1.26 (and is a US model). From this thread, it looks like this issue has been live for a few months now, and although some progress appears to have been made, there is still no ETA. Should I return the router?