Skip to main content
BudWheizzah99
Participant
February 10, 2026
Question

Latest update ignores Airlink bitrate setting completely

  • February 10, 2026
  • 18 replies
  • 1202 views

Since the latest update Airlink runs at 15Mbps and ignores all bitrate settings. This has rendered the interface unusable. Please do not incompetently deploy updates as some of us are actually using these headsets.

    18 replies

    BudWheizzah99Author
    Participant
    February 10, 2026

    Side note: Link (USB) appears unaffected.

    steve40
    steve40
    Honored Contributor
    February 10, 2026

    Really? I got v85.0.0.232.552 seven hours ago and AirLink is working fine at 200 Mbps.

      BudWheizzah99Author
      Participant
      February 11, 2026

      That would be the way it normally works, yes... but now it just stays at this very low bitrate, I even tried using the debug tool to force it and it just ignores it. Ditto for the in-app menu. (232.552 as well)

      Long live Virtual Desktop I guess.

      AEFox
      Up and Coming
      February 11, 2026

      Did you restart the service after you put the value in DebugTool?, now that step it's required. Try put 360 mbits for example, then restart the service, then link again and check it.

      Porly1985
      New Participant
      February 11, 2026

      I had the same issue. Check that you have the Encode Bitrate set to 0 in the Debug Tools. Then you can adjust the desired bitrate in the UI settings. If Encode Bitrate is not set to 0, the UI settings will be ignored, and the link speed will stuck around 15 Mbps

       

        steve40
        steve40
        Honored Contributor
        February 12, 2026

        I'm not seeing that behaviour (v85.0.0.232.552).

          genuine3000
          New Participant
          March 13, 2026

          Same problem here makes it unusable artifacts all over the place nothing change even if you change it in oculus tool. After updating it brokes had the same problem before they fixed it in the past and now it's back again after updating it to 2.1.locked at 10mb seriously fixed your stuff.... Seems there are not a lot of people not reporting it and just use the cable or maybe 50 serie prob.also link with cable unstable often hang use a lot of resources hourglass keeps popping up when games are loading asw is broken if you enable it your frames goes from 100 to 50fps no mather what auto force reinstall everything. All happening when microsoft changed maked major changes in hags. But again thank god for having a closed system get your **bleep** together meta regards genuine

            007x007
            Up and Coming
            March 13, 2026

            I have same problems. I use link cable. I had to disabled HAGS. For me it make microstutters in beat saber.

            • Fixed bitrate locked to any value. I can put there even 2000 and nothing happen.
            • artifacts
            • ASW status is unknown and PTW is always enabled.

             

              BudWheizzah99Author
              Participant
              March 20, 2026

              So there is something up with the ASW setting after all. It "felt" like it was on, but then from checking framerates I was getting, it did not seem to be on... but the PTW being enabled is strange. Makes me want to go back and frame-by-frame some video to see what it's doing. Sigh, this update.

              ScottyPiligrim
              New Participant
              March 20, 2026

              Same here on the airlink. Found workaround for now. Afte you connected airlink and rif dash is loaded, you need to set Encode bitrate to 0. After that you can set whatever value you want, but unfortunately values over 200 Mbs will be ignored still. 

                BudWheizzah99Author
                Participant
                March 20, 2026

                Yep, even after the latest updates, that's exactly the issue. If you have anything set in Encoder Bitrate in the debug tool, it will default to 15 no matter what until you set it to 0. I discovered this accidentally as I had simultaneously updated and reset all my debug tool settings, then later tried to take manual control again.

                This definitely needs to be fixed, but I can live with using the slider in the settings menu for now, since my manual setting is just 250, I can endure 200 for a while.

                arkglad
                New Participant
                March 23, 2026

                I read the entire discussion and i have exactly the same issue (RX6750xt idk if it can help). 

                The thing is i can't use h265 because my GPU is bad with this one. So i was using H264 at 500mbps and it worked fine until the last update... When i set the bitrate in oculusdebugtool bitrate drop to 10 mbps...

                I can still use my quest 3 at 200 mbps but in h264 its ugly... 

                Schinakoch
                New Participant
                April 3, 2026

                same here and i can admit:
                for airLink:
                if in ODT the value Encode Bitrate (Mbps) is set to another value then "0" the ethernet rate is falling to 15 Mbit and what causes bad compresion artefacts.
                If the value is on "0" all is fine and ethernet rate is 200 Mbit

                mcmsbrcoe
                Meta Employee
                August 17, 2026

                Thank you for this report.  I've confirmed this issue (bitrate getting stuck at 10 Mbps when setting a fixed bitrate override in ODT) and have a fix that will be included in an upcoming release. I'll circle back with an update when that rolls out. In the meantime, setting the Encode Bitrate to 0 and restarting the session (as described by OP) should restore the default bitrate. As a further mitigation, the bitrate can be increased to as high as 200 Mbps after having launched Link, via the in-headset setting (rather than ODT). When the fix rolls out, values higher than 200 Mbps will once again be accepted/take effect from ODT. 

                  steve40
                  steve40
                  Honored Contributor
                  August 18, 2026
                    Terms & ConditionsAccessibility statement