search

GPUOpen-LibrariesAndSDKs / Radeon-ReLive-VR

156 stars 19 forks source link

[Question]: Is AMD aware of the drivers problems with vr? #132

Open Falita7 opened 2 years ago

Falita7 commented 2 years ago

Hi, I know this is not related to relive itself but i would like to know, is amd aware that the drivers after 21.10.2 have problems with any third party software that uses the encoder/decoder for vr wirelessly?.

After discussing things with the dev and people of Virtual Desktop, some from ALVR and the forums of oculus for the airlink software is clear that this is going downhill after the release of this latest drivers 22.5.x that broke airlink bitrate.

Here more info about it: https://community.amd.com/t5/drivers-software/amd-drivers-and-vr/m-p/526584#M156416

pendragonmikel commented 2 years ago

It would really be great if we could get this addressed. As of the current version of drivers (22.6.1) the AirLink bitrate is broken and the ReLive VR web interface is broken.

pendragonmikel commented 2 years ago

This appears to be fixed in driver 22.7.1 at least in the Oculus software. I was able to play Skyrim VR via Airlink at 200mb bitrate. It was the best experience I've had in airlink to date. (Even against a NVidia based laptop) Someone else might want to check this out on other software.

Anoobizzz commented 2 years ago

This appears to be fixed in driver 22.7.1 at least in the Oculus software. I was able to play Skyrim VR via Airlink at 200mb bitrate. It was the best experience I've had in airlink to date. (Even against a NVidia based laptop) Someone else might want to check this out on other software.

Got limited 75~ mb bitrate after updating to 22.7.1. Reverting back to 22.2.3 - last driver without issue.

pendragonmikel commented 2 years ago

Did you try a clean install?

Both relive vr and Airlink are the best they've ever been for me with this driver.

Anoobizzz commented 2 years ago

Did you try a clean install?

Both relive vr and Airlink are the best they've ever been for me with this driver.

Clean installation 22.7.1 RX 6800 XT, Oculus Quest 2 Air Link 200mb -> image

And here is back to 22.2.3 -> image

pendragonmikel commented 2 years ago

It seems i stand corrected. Airlink is super crisp standing still. That and the return of the 200MB option made me think this was resolved, but upon testing in this way, it isn't. Also not sure if this is an AMD driver issue, or an Oculus/Meta issue, but everything but the desktop when connected via Airlink is wobbling. I thought it was a one time thing, but it is consistent. Good thing is that ReLive VR still works at the 170M setting as measured via task manager.

angelfor3v3r commented 2 years ago

This is really saddening to hear, espescially to someone whos wanting to get into VR. Heres hoping AMD resolves this sooner than later. Thanks for all your testing, please keep us up to date!

Nico04 commented 2 years ago

Any news on this issue?

Anoobizzz commented 2 years ago

@Nico04 Tested on RX 6800XT with latest 22.10.1 drivers - still same issue with bitrate + wobbly Oculus dashboard.

Nico04 commented 2 years ago

Tested on 6900 XT with 22.9.1, same issue with bitrate + wobbly Oculus dashboard.

pendragonmikel commented 2 years ago

The wobbly dashboard is fixed as of 22.10.2, however bitrate on airlink and alvr both still seem to be broken (ignores settings - shows high bitrate, but doesn't actually send at that rate as @Anoobizzz shared above.

Rinshun commented 1 year ago

Maybe they are not aware. Fill out a bug report in the AMD Software: Adrenalin Edition

Anoobizzz commented 1 year ago

@Rinshun Already did and also managed to contact support directly (after long generic conversation they transfered ticket to higher level) and seems like they are lookin into it, last email from them:

Thank you for your email and patience.

We are looking into this issue. When I have more information I can share with you I will let you know.

Also opened bug on their GitHub: https://github.com/GPUOpen-LibrariesAndSDKs/AMF/issues/364 But that one was dormant for a while.

Anoobizzz commented 1 year ago

I'd say its a win, got a response:

I've checked with our driver engineering team and we are aware of this issue. Although I cannot provide you with a timeframe for a fix, we do intend to resolve the issue in a future driver update.

When the issue has been resolved, we will list in the driver release notes under the resolved issue section.

Until that time, we appreciate your patience

Falita7 commented 1 year ago

Hoping they fix the issue for all AMD users, I switched to nvidia 6 months ago and not coming back to amd if they take 2 years to fix a MAJOR driver issue since the bug reporting tool seems to be a waste of time.

ceisma commented 1 year ago

Same here. I'm still subscribed to this issue but switched to Nvidia a couple of months ago because this doesn't seem to be a priority for AMD to fix.

On Fri, Dec 16, 2022 at 6:48 PM Falita7 @.***> wrote:

Hoping they fix the issue for all AMD users, I switched to nvidia 6 months ago and not coming back to amd if they take 2 years to fix a MAJOR driver issue since the bug reporting tool seems to be a waste of time.

— Reply to this email directly, view it on GitHub https://github.com/GPUOpen-LibrariesAndSDKs/Radeon-ReLive-VR/issues/132#issuecomment-1355302867, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALMR2Z5DA462WD3OJMDFY43WNSTM7ANCNFSM5X5K6P5A . You are receiving this because you are subscribed to this thread.Message ID: <GPUOpen-LibrariesAndSDKs/Radeon-ReLive-VR/issues/132/1355302867@ github.com>

Rinshun commented 1 year ago

"We are not allowed to comment about future plans, or to give a timeframe for a fix"

I googled translated it, and it returned me the following:

"We are not fixing it and we don't care about a small fraction of our customers who have this problem"

PSA: For anyone having problems with wireless PCVR gaming, I suggest ALVR. It's working almost flawlessly. It still has the 100mbps limitation, but using HEVC, the image quality is great.

GennadiyAMD commented 1 year ago

@Rinshun - Google Translate can give incorrect translations sometimes. This is one of those cases. :)

AMD is aware of the problem and the fix is being worked on, according to the information I have. We just cannot provide specifics on the fix availability date for various reasons - hope you all can appreciate this.

We certainly would love to resolve every issue promptly, or even better, not have them in the first place, but our resources are not infinite and we have to prioritize what we are working on first. But rest assured, it is being looked at, so stay tuned...

Falita7 commented 1 year ago

@GennadiyAMD thing is, this was an issue that affected the direct functionality of the card with PCVR for 2 years and I can only assume this is being worked on because the 7000 series made changes to the encoder and since that is being worked on it will also fix the problems of the 6000 series, i would love to buy an 7000 series but what if the driver is broken again?, how much time a user would have to wait after reporting the problem on the official forum, reddit page, support ticket and reporting tool messages are sent with no feedback at all.

Also it would't hurt to contact meta about supporting your product with a working h265 encoding to at least have some level of competition against nvidia using the same codec on the most popular pcvr headset in the market.

Sorry for the rant but having to wait a year and then exchange my 6900xt for a 3080 just to use vr without problems left a bad taste for the amd brand.

Rinshun commented 1 year ago

@Rinshun - Google Translate can give incorrect translations sometimes. This is one of those cases. :)

AMD is aware of the problem and the fix is being worked on, according to the information I have. We just cannot provide specifics on the fix availability date for various reasons - hope you all can appreciate this.

We certainly would love to resolve every issue promptly, or even better, not have them in the first place, but our resources are not infinite and we have to prioritize what we are working on first. But rest assured, it is being looked at, so stay tuned...

I knew google couldn't be trusted. I'm going to use bing next time!

Jokes aside, I've had an AMD graphics card for over a decade and never had any problems with them until today. Consequently, I just have high expectations from the brand. So it shocks me that such an important problem remains unfixed for so long.

But I'm happy AMD knows, acknowledge publicly and communicate with the community about the issue. I'll stay tuned for driver updates

ovakisan commented 1 year ago

DISCLAIMER not a useful post Came here to say someone was right when they said 7000 series drivers will be shit for VR and ofc AMD is "working on it". @GennadiyAMD

tonineri commented 1 year ago

@GennadiyAMD , 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... That said, it's been 2 months since the last driver update, and:

Hopefully, the next driver update will be released soon. Hopefully, it'll include the 100Mbit PC VR limitation under the "Fixed issues" section.

GennadiyAMD commented 1 year ago

@tonineri - the fix for the 100Mbps limitation is in testing right now as far as I know.

bernek9000 commented 1 year ago

I really hope so ! 6800XT here and having problems with drivers newer than 22.2.3 :) this one works great 300-350 Mbps via AirLink H264. With HVEC it only goes to 150 Mbps. Not sure why. I have ALVR / VD and AirLink of course which is the most interesting of them all to have it working as it should !

bernek9000 commented 1 year ago

Well it seems they messed up again ... "Maximum encode bitrate is limited to 100Mbps for certain applications." is still on the to be fixed list ... what a fail from them after all these months.

tonineri commented 1 year ago

It's good the issue has finally been "officially acknowledged" at least. I'm pretty sure that when AMD "fixes" the encoding limit, they'll need to work with Meta for an updated Oculus client since Meta also knows about this limitation: Meta: Oculus Link | AirLink Known Issues

bernek9000 commented 1 year ago

They dont need to work with Meta since older drivers work perfectly. Also modded drivers do. Its their encoder that is crap and their sofftware drivers.