[Bug]: Encoding speed is capped when using Oculus AirLink with GPU driver >22.2.3 #364
Comments
Anoobizzz
changed the title
|
Checking.... |
|
I've rolled back to 22.2.3 to give comparison: Logs: Service_2022-12-02_18.09.37.txt Only difference i see in properties set is: |
|
There's a claim on the VD Discord that 22.11.2 works fine with HEVC above 100Mbps. I was on 22.4.2 yesterday and saw 200-500 Mbps reported to be working fine from Oculus over wired Link (AVC); the overlay updated with the set bitrate. |
I'd say it's simply not possible. When |
|
The fix is under development, stay tuned. |
|
With Air Link, I get limited to around 50-55 Mbps with both HEVC and AVC when I use driver 22.11.2 (latest). Can't go higher nor lower with fixed bitrate. With 21.10.2 driver also with Air Link, I'm limited to around 20 Mbps with HEVC (can't go higher nor lower), but AVC seems to work fine 10 Mbps to 200 Mbps. For some reason, it seems Oculus is doing something different with bitrate depending on the driver. However with ALVR and 22.11.2 driver, I can throw seemingly any bitrate with HEVC from 200 Mbps up to 600 Mbps with expected network load. So it seems ALVR is not limited with bitrate in the same way Oculus is. On an unrelated note, there's something seriously wrong with Oculus's runtime because ALVR works notably better for Quest 2 PCVR than I've ever seen since Q2's launch. |
The behavior is weird. it gets limited to 50~55Mbps when running 72hz, but if you put it 120hz, then it can go up to 90Mbps (If I remember correctly) That means it's not a driver issue only. Airlink is also doing something wrong (probably) |
|
This issue has gotten worse for me after the latest update to Oculus on driver version 22.11.2 There's a new issue for me where I'll be already running at an already lowered bitrate of 50-75Mbps but then suddenly drop to 5-6Mbps for an extended period of time making airlink unusable before returning to the 50-75Mbps. Before all of these issues I was running at 145Mbps at 90hz but with every update it's been getting progressively worse. |
3 Support tickets, countless wasted hours fiddling and talking to support that has no idea what they are doing or talking about. 10 months later? Stay tuned? For another 12 months? All this happening during the dumbest rebrand and re-name in history. |
|
AirLink's picture quality has been unusable for quite some time now as I'm also reaching a 60Mbps cap for some reason. In the current state the only solution I had is Virtual Desktop which would run HEVC at 150Mbps with a noticeable bump in quality (although not sure if that's with filler data, considering the 100Mbps cap mentioned by other more knowledgeable people on GitHub). |
|
Airlink was broken/crippled for AMD cards in March 2022 starting with AMD's drivers 22.3.1 |
ALVR is a free alternative to Virtual Desktop. |
|
Has anyone tried toggling the With wired Link on 22.2.3, the bitrate defaulted to 200 Mbps, but changing Changing the I didn't disable the dynamic option when testing other drivers prior to this. It's possible the I'm not sure if any of that would workaround AMF's bitrate limit in newer drivers. |
|
I'm having a similar issue on a 7900 XTX when using the ALVR server. |
|
Hi, I have this issue on my 7900 XTX as well. Could we get a update on status of this issue? |
|
There isn't a status update. It hasn't even been mentioned by either company. AMD seems to be scrambling to fix their "rushed to market" 7900 series. Metaculus is more worried about pushing a $1500 HMD that no one will buy because it isn't much better than the $300 one that they stopped supporting. I have a 7900xt. It's underwhelming and crashes quite often. My 6900 was the opposite. |
Ok, so what was changed after 22.2.3 to cause this? It sounds like bitrates were fine up until 22.2.3, then someone decided to change it. Why? And why is it not as-simple as just undoing whatever was changed? Or maybe 22.2.3 and lower aren't as-ideal as they appear? Video encoding really doesn't seem like something that should be this complex to suddenly have varying behavior and breakage all of a sudden on architectures that are supposed to be stable. Why not just do what you've been doing for years with game-specific profiles, make something that works specifically for Oculus (as to not break anything else even more :p), ship it now, and then do whatever you want to properly fix this later? This is affecting the most popular VR headset, has been for months, and just looks bad. Whatever the fix was for the wobbly dashboard since August(?) drivers still isn't implemented in the latest development drivers for W11 Insider (December), but sure enough the bitrate issues are present. Although I'd prefer to be using newer drivers just cause, luckily the rest of my games and everything else seem fine on 22.2.3 with my 6600 XT. It's so outdated that Windows Update wants to "update" it, and there's only two methods that reliably work to prevent this (wushowhide or blocking device ID driver changes with group policy) that no average-user is going to know about. |
|
@Espionage724 you should feel lucky to have an older driver that works. 7000 series owners don't have this luxury. |
|
@MikhailAMD, I know it's not specifically your fault, but I own an RX 6800XT (Reference Edition) which used to be considered a high-end GPU up until Dec 13th, 2022 when 7900 was released. It's my first time on an AMD GPU and I must say the hardware itself is fine, though the driver situation is - to put it mildly - a bit bitter...
Hopefully, the next driver update will be released soon. |
|
I understand, thanks for your patience, but can only say things related to AMF: the fix for 100MBit limitation is in testing. |
@tonineri It's not due to the 100Mbit limitation only. Airlink is also doing something wrong. ALVR and VD have a much better visual quality than Airlink if you are using the latest drivers. You can see that airlink will only use 50~60Mbps in the task manager, as mentioned in the first post. So I suggest trying those alternatives while the fix isn't out. |
|
@MikhailAMD please send this information forward to the driver development team. Its unacceptable for a 6800XT or 6900XT or even 6950XT to have these kinds of peformance issues and limitations in VR. VR is the future of gaming if we accept it or not. Having a high end product performing worse than 1080TI or 2080TI in VR is a very very bad picture for AMD. This needs to be fixed real soon because people are flooding the forums on internet with returning cards and switching to Nvidia. I like my 6800XT but this is not the way to treat your customers. We've bought these cards with hard earned money during difficult times and we get what in return ? Ignorance for months ? |
|
They seem to have bigger problems on their plate now with the 7000 series as the last 3 drivers are specifically targeted for that. One of the engineers promised on AMD reddit that a merge with the mainline branch is happening 'early January' but that obviously did not happen. |
|
What is weird is that the 100mbit limit on the slider bar within the VR menu for airlink was increased to 200mbit somewhat recently for AMD cards. Unfortunately, it's only for looks because it still doesn't exceed 60-65Megabit in actual throughput. |
What kind of change needs to be made (if it's not just for Meta of course)?
If you inspect the bitstream generated with any driver past 22.3.1 and CBR with filler data enabled, it's exactly about the empty data. We're not talking about rate control logic and it's not about the latency either. 470mbps will be RBSP and only 30mbps is actually useful data. I already mentioned this in my other reply to this thread here #364 (comment). Same thing is still observed with 23.2.1. |
|
23.2.2 just dropped with the 100Mbps limit bug being listed under fixed issues. |
|
This seems to be actually fixed with 23.2.2. At least not an issue for ALVR anymore. |
It seems like there were multiple issues. One of the issues could be fixed from AMD side (as in ALVR is now supposedly fine?), |
|
I just tried airlink last night on my RX 590 and I was capped at 100. A lot
more usable than what it was before but not uncapped by Meta higher than
100 still.
…On Wed, Feb 22, 2023, 12:50 PM Anoobizzz ***@***.***> wrote:
23.2.2 <https://www.amd.com/en/support/kb/release-notes/rn-rad-win-23-2-2>
just dropped with the 100Mbps limit bug being listed under fixed issues.
This is very confusing as I just got the signal from this thread that they
just discovered this is in fact a Meta implementation issue. Was this issue
addressed on AMD's part as well or just investigated and passed along to
Meta?
It seems like there were multiple issues. One of the issues could be fixed
from AMD side (as in ALVR is now supposedly fine?),
but AirLink still is 60 ish~ mb on 23.2.2 and can only be fixed by Meta.
At least this is my understanding.
—
Reply to this email directly, view it on GitHub
<#364 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJ5ZDCLPZQGEDKKLLPS7XKTWYZNZDANCNFSM6AAAAAASP6SERI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
We've been waiting for almost a year now, what's a couple of months extra? Frustrating but at least we have a sense of progression. |
|
Talked to Meta. There is more then set filler data property. Something related to driver version detection. They are investigating. |
Please help us VR guys. We want to be able to be on par with the green team on this one ! |
|
No news?? |
|
Nothing has been fixed. Zero. Metazuckerbook more worried about stupid rebranding and sabotaging TikTok rather than fixing their own products. This has been broken for a year. |
|
Please calm down, github is a place for technical discussion on open source code and their issues/bugs, not youtube comments where you rage against whatever company or entity that you think slighted you. Also for your information if you've actually read this thread, you would know that the issue was only patched on AMD's side last month on the 23.2.2 driver release, so Meta has only had less than a full month to fix the encoder bitrate negotiation on their end, not a year. |
|
Oculus has V51 in PTC, has anyone tried it? Also, have any encoder issues affected wired Link? I'm pretty sure bitrate looked good at 200 Mbps with drivers newer than 22.2.3 with wired Link, but I'm not aware of how to check bandwidth over USB. |
|
Sadly, it won't work with V51 PTC. Same bitrate as V50 ~ 60Mbps. |
|
I got a word from Meta developer:" the fix should be released in v53 version that should be released until the end of April to the Public Test Channel" |
|
They are going to skip a version? I'm only at v51 public test. If that's not weird enough, now I have to keep the console window open again or I start dropping frames like crazy with link. I thought they fixed that before. |
|
This is all I have for now. |
|
@MikhailAMD thanks for letting us know. |
|
Finally! With V53 airlink bitrate works like a charm! Sadly, at least for me, questlink (wired) doesn't work at all (doesn't boot anymore). |
|
Yep they fixed it in V53 alright. |
|
Tested with latest drivers + v53 PTC Oculus: |
|
Anyone tried if wired link works with v53? Thanks in advance:) |
|
Like people before me I can confirm the fix is working in V53. |
|
But does the image quality look alright? |
What do you mean? The image looks as normal but more crispy and detailed than before due to high bitrate :) |
|
I forgot about this trick. Before doing this an Airlink connection had about a 10% chance of success. Certain apps such as Robo Recall would drop frames like mad and then eventually crash. After this, it connects on the first try almost every time plus no more crashing. This is copied from a thread of the internet somewhere. I can confirm that the bitrate is no longer crippled. Finally. Right click on "My computer" then properties Then right hand side "advanced system settings" On the Advanced tab choose Environment Variables In THE SECOND window click NEW Enter name OPENSSL_ia32cap Enter value ~0x200000200000000 Then click OK 1 last important step REBOOT SYSTEM |
|
Oculus games work and look normal, but all steamvr games display below 144p, an extremely low resolution. I used my PC to look at the settings since I couldn't make out anything, and my resolution was around 100,000 for some reason. Very strange. |
|
Nice to see an update for AMD VR. Could you tell me the max working bitrate if you play with Oculus debugtool please ? I don't have yet an AMD GPU (I'm waiting for 7900 fixed VR issues driver). Thanks |
|
Anyone else with the same issue than @theprestigiousguy ? |
|
Sliced encoding seems to be broken on AMD cards |
Describe the bug
Submitting bug reports to AMD\Meta doesn't do anything, so I'm attempting bug report here instead. Since driver version >22.2.3 an issue with encoding bitrate appeared, no matter the settings it doesn't go above 70mb for me.
There are multiple other topics discussing the same problem:
https://forums.guru3d.com/threads/amd-amf-and-gpu-encoding-issues-and-discussion-notably-for-vr.443275/page-2
https://community.amd.com/t5/drivers-software/amd-drivers-and-vr/m-p/526584#M156416
GPUOpen-LibrariesAndSDKs/Radeon-ReLive-VR#132 (comment)
To Reproduce
Steps to reproduce the behavior:
Setup (please complete the following information):
Debug Log (please upload or paste):
OVRServer logs attached.
Expected behavior
Screenshots
Service_2022-11-30_17.28.29.txt
The text was updated successfully, but these errors were encountered: