TudorStefan26 wrote:
Hello everyone,
I would like to ask if anyone has been encountering issues after the last April update, around 24th April to be exact. I mainly use the headset with wired link to play VR sim racing. Before this update, I had absolutely no issue, shortly after the install, the VR connection is lost after about 15-30, after an intense session.
Is there any fix for this? I saw that there is no way to roll back the driver... which is quite a shame. I was so excited after I bought it and set it up, only to have it crash now every half an hour.
Both my Q3/512Gb and QPro are working fine with the latest non-ptc v76.1024. I've tested this out with some longish (+1.5hr) flights with msfs2020, which is probably one of the most resource hungry PCVR apps out there. I also helped setup a friends Q3 with Link a couple of days ago and it also worked fine with non-ptc v76. So, I'm not sure that the problems using Link are caused by the v76 update.
I'm not sure what could be causing your disconnects but I guess the main thing is that at least you're getting connected properly to begin with, lol! I've been using Link since it first came out +5 years ago, starting with a Q1, and some earlier updated were a bit hit and miss, but I haven't had any issues for the last few years with a Q2, Q3, and QPro.
Generally I've found that occasional disconnects can be caused by a number of things. Mainly caused by a damaged link cable, poor usb connection at the PC or headset, and failing to disable all usb power savings. Other things that can cause this is having too many unnecessary usb devices that may swamp your usb bandwidth and may be drawing more power from your motherboard than it can handle. Also, there are other things like windows, Steam, and GPU driver updates that can also cause issues. This can also be caused by running too many background apps (or startup apps). Check your windows task manager and see if you can identify any large usages, esp. after a disconnect happens.
Besides going through the typical Link Troubleshooting steps like you can find on the meta support website, it's pretty hard to tell what the cause of your problem is caused by and how to sort these out. I think your best bet may be to contact meta support including your log files (google how to do this) and see if they can identify what's causing your issues.
Sorry I can't be of more help. Good luck mate and cheers.
