PSA AGESA 1.2.0.2 has fixed my Reverb G2 USB issues.

[SakerVVS]

As title says. The new AGESA update has fixed the usb connectivity issues with my Reverb G2. I was previously recommending against AMD 500 series chipsets for VR use. So far I have been able to use my usb C port (which previously did not work) with no issues.

Gigabyte Aorus B550itx/5600x/3090.

Edited April 5, 2021 by 6./ZG26_Saker
Clarity

[SCG_Fenris_Wolf]

I've read reports that the screens lose fidelity / turn darker. There's quite a few guys that have mentioned that on Reddit.

 

Can you confirm / deny / don't know that ? I've held off with the FW update so far (as my headset is mostly stable unless I jank sound from 50 to 80 suddenly.)

[shirazjohn]

I think the op is referring to the recent bios update rather than the firmware update but i updated my firmware about a week ago and i can't say I've  noticed the screens being darker.

[SakerVVS]

I haven't had audio issues, I did do the firmware update but I haven't noticed it getting any darker, although I can see where they might have gone that route due to the godray type of reflection from the lenses sometimes. I was referring to the USB issues on AMD boards making G2s very finicky in certain configurations.

Edited April 7, 2021 by 6./ZG26_Saker

[AFsparrow1968]

hello,

 

i expect to buy a reverb g2 but There's so many issues reported by community (black screen, device disconnects or not recognised....etc) specifically on AMD chipset b550 and x570. I am afraid to invest in my first vr headset. my rig is you 1080ti, asus rog strix f gaming wifi b550, CPU 5600x, 32 ram gskill trident 3600 mhz. I have updated motherboard with last official bios 2206 (agesa 1.2.0.1 patchA) but AMD users continue to have issues.  it is so sad that many users had to revert to pcie gen3, buy pci USB cards and even with that, problems still persist. this post is great and I hope people will report behaviour with bios / agesa 1.2.0.2 to confirm if it definitely squashed USB issues with reverb g2 as this headset is the most recommended for simulation. 

or I will finally choose a quest 2.

 

thanks in advance for feedback and to the devs for this great sim....?

 

[HunDread]

1 hour ago, AFsparrow1968 said:

hello,

 

i expect to buy a reverb g2 but There's so many issues reported by community (black screen, device disconnects or not recognised....etc) specifically on AMD chipset b550 and x570. I am afraid to invest in my first vr headset. my rig is you 1080ti, asus rog strix f gaming wifi b550, CPU 5600x, 32 ram gskill trident 3600 mhz. I have updated motherboard with last official bios 2206 (agesa 1.2.0.1 patchA) but AMD users continue to have issues.  it is so sad that many users had to revert to pcie gen3, buy pci USB cards and even with that, problems still persist. this post is great and I hope people will report behaviour with bios / agesa 1.2.0.2 to confirm if it definitely squashed USB issues with reverb g2 as this headset is the most recommended for simulation. 

or I will finally choose a quest 2.

 

thanks in advance for feedback and to the devs for this great sim....?

 

 

I have a b550 MB with 5600x CPU ,a GTX 1080TI GPU and 32 GB 3600 mhz gskill trident RAM. I have the G2 since late last year and haven't had the slightest issue. I had only one issue with my mobo with a powered USB hub I use for my flight sim peripherals. I had to switch it to a different port on the MB and that's all. No other issues.

[AFsparrow1968]

Thanks For you reply bottes more and more I think I will go to the quest 2. there is less clarity but more versatile, far less expensive and easy to set. hope agesa 1.2.0.2 will solve USB issues. I had a good second hand reverb g2 for 500 euros but afraid to be disappointed for my first VR experience and my gpu is not really the latest one....

see you great il2 community! 

[Jurinko]

5 hours ago, HunDread said:

 

I have a b550 MB with 5600x CPU ,a GTX 1080TI GPU and 32 GB 3600 mhz gskill trident RAM. I have the G2 since late last year and haven't had the slightest issue.

Looks like graphics card series 30X0 in combo with AMD chipset are the problem, related to PCIE Gen4 tech.

[SCG_Fenris_Wolf]

Were the problem. People don't keep their software up-to-date   I am guilty of this too sometimes  

[SakerVVS]

On 4/13/2021 at 3:05 PM, Jurinko said:

Looks like graphics card series 30X0 in combo with AMD chipset are the problem, related to PCIE Gen4 tech.

Yes, the 1080ti should be fine, and I still have not noticed any USB issues since the bios update.

[ktriggerk0ld]

I had an older Dell XPS 8910 that I used to play IL-2 but wanted to upgrade.

I followed the hardware recommendations on this forum and built a brand new system.

 

I have a b550 MB with 5600x CPU, RTX 2080 Super GPU and 32 GB 3600 mhz gskill trident RAM. Almost exactly like Jurinko above.

The USB issues were there from day 1. As soon as I powered up the system for the first time 2 weeks ago, I noticed lag in USB response to keyboard and mouse input.

 

Installed IL-2 and tried to play. NO GO!!! My HOTAS would not work AT ALL. I can change keyboard assignments in-game, but as soon as I start the mission, there is NO response to my inputs, only the ESC button works. I just updated my BIOS with the AGESA 1.2.0.2 beta from ASUS, and while in regular use I haven't experienced any lag (yet), in-game it's the same bloody thing. It is actually worse. I can assign some functions like throttle axis, but then mixture would not respond at all. And after starting the mission, it's like I have no controls at all.

 

I am extremely disappointed that after investing $2.5k into a new rig, I can't use it. Now I have a $2.5k paperweight.

 

What is also disappointing is I went by the recommendations from this forum (Tier 1 and Tier 2 PC components for VR). And nothing there suggested that the B550 and x570 MB's are having these issues. I bought almost all available DLC's for IL-2 and what a waste.

 

SO, Mr. SCG_Fenris_Wolf, it's still IS a problem even for people who DO keep their software up-to-date.

 

When AMD makes a sh1tty product, they have to own it and not pass the responsibility on to the consumers.

Edited April 16, 2021 by ktriggerk0ld

[SCG_Fenris_Wolf]

First: Congratulations on your new system. But like any system, it needs to get set up properly.

 

Second: Your tone is not something that you would want to use if you asked for help and a solution to these issues.

 

Third: USB latency issues of keyboard, mouse, your joystick, and IL-2 not receiving any input are not what this USB issue is or was about. Hence you're barking at the wrong tree.

 

 

 

You should rather check your software stack. Any Razer Synapse in there? Or RGB Fusion 2.0 by any chance? Are you one of these running any third party antivirus programs while using VR? Did your device IDs flip (no fresh installation of IL-2 but a copy&paste job?)... many things it could be.

 

I already have gotten a few ideas how to check out what went wrong in your software stack. But with this tone, honestly, I'm rather hesitant to help you out.

Edited April 16, 2021 by SCG_Fenris_Wolf

[ktriggerk0ld]

Dear Wolf (Волк)

 

Not sure what you foud so offensive in my tone, but whatever.

I specificaly upgraded my rig to improve my IL-2 VR experience, so pardon my language if I sounded a bit miffed that I couldn't source a decent GPU from a retail store (I know, me and 100M other people like me). And then after buying a second hand GPU only to realize that I bought a MB that was listed on this forum as recommended but actually has a well known issue.

 

My rig is brand new. I've been in IT for over 20 years and this is not my first build. I would appreciate if you checked your own tone first which is quite condescending.

You don't want to help, fine. Help someone you like. With that out of the way, back on topic.

 

I only stated the facts that the motherboards recommended on this forum had USB issues that were only resolved in the last few days. And I didn't find that kosher. I am not blaming anyone in particular, but I think if you were in my shoes you wouldn't be very happy either (given how easily you got triggered by my post).

 

I am not running any antivirus software, no bloatware, and IL-2 was the first piece of software installed on the system after Steam and Oculus. 

It was a fresh Windows 10 download from Microsoft, and fully licensed. No other software is installed on my build, none. The build is as clean as it gets with minimum required to run IL-2 (Steam and Oculus). Not even OTT yet. I never use any 3rd party antivirus software other than what's shipped with Windows.

 

I did a fresh install of IL-2. I copied the career folder to the new installation because I have 1000 career hours that I didn't want to waste.

The key mappinng was from scratch, not copied from the old system. While I was able to assign most functions to the HOTAS (X56 with rudder pedals) and keaybord, as soon as I started the game, NONE of the controls would respond, period.

 

That's when I uninstalled the game, cleaned up the folder and installed again. I have a good 1Gb internet so that's not a huge issue for me. I tried again, same failure. Then I tried copyinng my old "input" folder into the new one. When the game started, I got a prompt that my devices were picked up and whether I wanted to transfer the assignment. But that didn't work either because the device ID's were all different and trying to edit them manually in Notepad didn't help (probably because those ID's are cross-referenced elsewhere). So I quit for the day.

 

That's when I started researching USB issues online and stumbled upon a reddit thread that said that AMD sccrewed up and their B550 and X570 MB chipsets have the PCIe-4 conflicting with USB. And that made sense becase from the get-go my keyboard and mouse inputs were laggy.

 

After I applied the AGESA fix to my MB, the USB latency issue was fixed. Most of my IL-2 key mapping was fixed, too! Yey! But not all.

At least now I can take off and land. I still can't assign a curve to the throttle control (I can reverse it but clicking on the curve button pops up the curve window but it doesn't respond to input and the only option is to Cancel). It works though and I am fine with that.

None of the F keys work. I mostly use F2, F3 ad F4 for external view, and while I can assign them, they don't work in-game. Assigning them to 7,8,9 on NUMPAD makes no difference, they still don't work in-game.

 

I was able to fly 2 missions last night, so I have to correct myself and say that the AGESA fix actually worked, or at least partially worked. I just need to figure out why some key bindings still don't work.

 

Happy flying everyone (including you, Волк) Cheers :)