[Airlink 101 Usb Serial Adapter Driver Windows 7
Luther Lazaro
Like many others I have been experiencing severe issues with oculus link and more so with both link and airlink since v28. I've gotten some way in understanding the issues and causes, and wanted to share here for the benefit of other users AND THE OCULUS DEVELOPMENT TEAM - who I hope can quickly address the issues.
My issue: Pre v28 oculus link would connect but with major stutter and crashes linked to oculus software utilising the wrong GPU (not listed as running on the NVIDIA). Since 28 both link and airlink launch to a black screen then after a few seconds crash back to the oculus home screen (not in link). DEVS - PLEASE NOTE THE THIRD PARTY VIRTUAL DESKTOP APP WORKS FLAWLESSLY. YOU CANNOT CLAIM THIS ISSUE IS CAUSED BY MY LAPTOP OR EVEN THE OCULUS HARDWARE. THE PERFECT FUNCTIONING OF THE THIRD PARTY SOLUTION MEANS THIS IS A PROBLEM WITH YOUR SOFTWARE.
OCULUS are not the only devs with this issue - I actually found this solution because it is the same fix which solves an issue with the steam version of Doom64 not working (not VR, standard desktop game). My guess is that both pieces of software are doing some test for presence of a suitable GPU, are finding the not suitable onboard GPU then giving up, hence disabling the onboard GPU solves the issue.
So with those specs for the PC the limiting factor becomes the wifi connection (because the PC is doing all the work, the oculus is largely just a display with virtual desktop). With a 5ghz wifi connection from the oculus to the router and a wires Ethernet connection from the router to the laptop I can have everything at max. Despite it not being recommend I can have the laptop and the oculus on the 5ghz wifi and get away with medium graphics with minimal stutter but will depend on your setup (even down to the material your walls are made of if you are not in the same room as the router)
I am having the same issue with Razer 14" laptop with Radeon and RTX 3070. Air and USB link both fail. The oculus app even reports my Ryzen 9 5800HS / RTX 3070 doesnt meet the needed performance specs!
On my machine I think what Windows does when you disable the AMD is that it indeed reverts to the standard Microsoft video driver for the main display but then pushes any graphics processing straight to the Nvidia which is why whatever test the Oculus is running is then passed.
Since I have the exact same laptop as you I want to share my experience in trying to fix this issue. To fix oculus trying to use the integrated GPU, first open up Armoury crate, once you open that select windows mode at the bottom, next go to Nvidia control panel and select Auto select for preferred GPU. Last hit the windows key and search for graphics settings, once you get there scroll down to "Choose an app to set preference" click browse first find OVRSerer_x64.exe, add that, then find OculusClient.exe, add that aswell, you should be able to find the file location for both with a simple google search as I did. Last find the two added files below the browse button, click on both and then options and set it to high performance. After you have done that you should be able to launch the oculus home without having to disable the integrated GPU, running smoothly if you did it correctly.
P.S. If you are planning on playing games from steam, you more than likely will face the same problem as I did where the games actually end up trying to use the integrated GPU as well, to fix this you do the same thing first go to C: drive>Program files(x86)>Steam>Steamapps>Common>(the game your wanting to play) and in said folder find the .exe file, add that and do the steps from before.
My system is AMD Ryzen 9 5900HX 16GB RAM with integrated AMD Radeon Graphics + NVIDIA RTX 3060 6GB.
This method doesn't work for me. The only way is to disable my integrated AMD graphics card in Device Manager, I don't know if it's because my computer don't have Graphics Processing Unit Direct. it's so inconvenient
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
I tried both the One-Click and the WHCK downloads from the Sierra Source page but was not able to get either to work.
Do you know if there was a specific way the driver had to be installed? Run the One-Click in compatibility mode, Windows 7, Windows 8? Be connected to the MP70 before running the install?
Is there any error after you install the driver from the source page? If yes, please tell me the content of that error.
After installing the driver, what does your Device Manager page show, please give me a screenshot.
According to your screenshot, the device is using with USB serial port. You can use Tera Term or PuTTy to type AT commands.
For purposes of getting Location reports, refer to Table D-24: Location AT Commands on page 574 of the AirLink MP Series Software Configuration Guide at the following link: _reference_docs/airlink-mp-series---configuration-guide/#sthash.M58puwU6.dpbs
Ever since Radeon-Software-Adrenalin-2020-21.10.2-Win10-Win11-64Bit-Oct25 came out, none of the updated ones work properly with VR applications without some sort of problem and this kept going... two years later and this latest 22.5.1 and 22.5.2 is even worst, I think AMD forgot about VR and all related to that so i strongly recommend if your card is supported on the last properly working driver 21.10.2 please use that one otherwise i'm sorry for you, your only alternative is using virtual desktop with h264 encoding.
This is the part where some dev, community manager or anyone that can deliver this small list to the drivers team that actually has a quest 2 and is not blind so it can check easily and see how terrible it is (most likely this will die here like all the threads related).
Airlink: For some reason bitrate is capped at 65-75Mbps (i think this cap appeared with 22.5.x), looks awfull, tons of compression artifacts, stuttering every few seconds, depends on the driver version sometimes you get like a bad reading on the controls and the screen keep shackin like you'r moving while staying still. And the encoder HEVC from AMD is not supported and seems like it never will be, why not reach out to the meta team? and get support from the most used headset on the market?.
ALVR: The configuration of 150% scale, 90hz, 150Mbps, HEVC that worked smoothly now has stuttering issues, white dots appearing and makes the app unstable with possible crashing but H264 gets very choppy forcing a scale of 100% tops, unfortunely making it look blurry.
Virtual Desktop: The only app that works BUT the encoder has to be H264 otherwise you will crash in games, in SteamVR, some at the moment of loading like Hellsplit: Arena, or other like GORN or Into the Radius will crash after a few minutes or hours and when it happens you will be lucky if you don't need to reboot the system in order to get the Adrenalin menu to work again or steam to launch a game properly.
+1 for this. Air Link quality has been getting progressively worse and more restricted, and Virtual Desktop HEVC support has been outright broken, resulting in driver crashes when trying to play games. VD's developer claims these are issues with AMD's encoder. I don't know if there has been any word from Oculus about why Air Link's image quality has degraded but I'm guessing it is for the same reason. Getting really tired of finding yet another problem with VR/video encoding support every time I update my driver... it would be nice if AMD acknowledged the issue and took it's encoder stability more seriously. Apparently this is now a running joke within the VD/VR community.
Virtual Desktop works, but only with x264, HEVC crash video driver. Without HEVC you have 40-50 latency and worst picture. With HEVC you have about 15-20 latency.
Interesting thing that this problem is not a problem for AMD at all, I haven't see any "known issues" in driver release notes. That's really frustrating.
I wonder if the majority of the users aren't noticing the issue. It was clear and obvious to me when the image quality took a nose dive but maybe it's not so noticeable when using Airlink at a lower render resolution.
On 22.5.1 the Oculus software pretends AMD cards with HEVC support have no support for HEVC and encodes in AVC/H264, although as a bonus, you can now push the Air Link bitrate back up to 200mbps now that there is a supported Oculus profile for AMD RDNA1/2 as of the latest Oculus software release. On 22.5.2 even H264 is broken, resulting in log spam from the AMF encoder stating "Warning: SetProperty ReferenceBPicturesDeltaQP not found" and weird Oculus Home tracking behavior, although this doesn't seem to stop games from playing properly (all I tested was Alyx and Beat Saber). Even at 200mbit, the H264 quality is noticeably lower than the working HEVC implementation from last year.
It would be nice to see AMD at least acknowledge there is a problem with the HEVC encoder as this is a feature these cards are marketed as including. There isn't that much info out there to the end user who is considering buying a Quest 2 and an RDNA2 card expecting to use HEVC that this combo hasn't been working properly for months.
So, are you saying that 22.5.1 works like 22.2.3, but the image quality is reduced? In my last attempt, I tried the latest 22.5.2 with the same results and a severely capped bitrate. I don't think I tried 22.5.1 and Airlink together.
It's weird, because I was pushing 400+ megabit through the network when using airlink and 22.2.3. It seems that there is no limit. Obviously it was a laggy mess and wasn't playable, but the transfer rate was WAY over the 200mbit limit/cap. I only noticed this because I forgot to reduce bitrate back from when I was using the USB cable and regular link.
795a8134c1