BlackSharkAce

Hi, I ran into the same issue last night and found a fix for it with the latest firmware. See here for the details: https://forum.virpil.com/index.php?/topic/3976-mt-50cm2-warthog-stick-and-target/&tab=comments#comment-36274 Cheers !

There is another program called OBS for performance measurement that should work. Not sure about VRPerfkit. Edit: not OBS, but CapFrameX. People are using it to graph frame times and fps. https://www.capframex.com/

Yes it’s this setting ! I run it without preview mode, but that shouldn’t affect it.

Set it to « enabled » or « forced » so it will always be active (45 or 30 fps). It gives more stable results than if it’s jumping between 90+ and 45 in « automatic ». I say 90 because I have a reverb g2, might be 70 for other headsets.

You can use the motion reprojection from openXR, it allows to « upsample » from 30 or 45 fps. Or you can disable it and run 90.

Well this bypassed steamVR completely, it’s a performance gain even if not native per se :)

Check this out by amazing jabbah: https://www.assettocorsa.net/forum/index.php?threads/openxr-for-wmr.70825/ He did it for ACC, now it supports DCS !

Use the download link for manual installation, it’s on the same webpage as the installer. This will give you an archive containing the .dll file and documentation you need to update.

Yes, the .msk kept on doing a « repair » without actually updating the version.

2.5.61.1 fixes the issue. Thank you for your prompt support !

@MAXsenna Thank you for your feedback, new thread with additional info and details on Voice Attack configuration has been posed here:

Hi , I just updated to DCS OB to v2.7.7.15038, VAICOMPRO v2.5.26.0 and VA v1.8.9 and it looks like not all "exposed variables" work anymore. Flying around in Caucasus in the FA-18C (free flight solo mission) I can get {TXT:vaicompro.serverdata.currentserver.theater} to work (returns Caucasus as expected) but both {TXT:vaicompro.playerdata.currentmodule.cat} and {TXT:vaicompro.playerdata.currentmodule.name} return "Not set". In the attached picture we can see the module is detected and display in the VAICOMPRO configuration window, SRS also recognizes the module and switches to the correct profile. It's a bummer because I use different button presses for my radios depending on the plane I'm flying. Any clues ? So far I tried the following: -Running VA, VAICOMPRO, SRS, DCS as admin -Repairing SRS & VAICOMPRO -Searching for "vaicompro.playerdata.currentmodule" in the forums -Verifying the command didn't change in the VAICOMPRO manual Cheers, Here is the VoiceAttack configuration. I expect it to output the currentmodule name and category along with the theater, but I only the theater seems to be working. Here is the relevant page in the user manual.

Hi @Hollywood_315, I just updated to DCS OB to v2.7.7.15038, VAICOMPRO v2.5.26.0 and VA v1.8.9 and it looks like not all commands work anymore. Flying around in Caucasus in the FA-18C (free flight solo mission) I can get {TXT:vaicompro.serverdata.currentserver.theater} to work (returns Caucasus as expected) but both {TXT:vaicompro.playerdata.currentmodule.cat} and {TXT:vaicompro.playerdata.currentmodule.name} return "Not set". In the attached picture we can see the module is detected and display in the VAICOMPRO configuration window, SRS also recognizes the module and switches to the correct profile. It's a bummer because I use different button presses for my radios depending on the plane I'm flying. Any clues ? So far I tried the following: -Running VA, VAICOMPRO, SRS, DCS as admin -Repairing SRS & VAICOMPRO -Searching for "vaicompro.playerdata.currentmodule" in the forums -Verifying the command didn't change in the VAICOMPRO manual Cheers,

In the meantime you can get a first glance at it here: fholger - Modified OpenVR DLL with AMD FidelityFX SuperResolution Upscaler https://r.tapatalk.com/shareLink/topic?share_fid=74365&share_tid=276638&url=https%3A%2F%2Fforums%2Eeagle%2Eru%2Findex%2Ephp%3F%2Ftopic%2F276638-fholger---Modified-OpenVR-DLL-with-AMD-FidelityFX-SuperResolution-Upscaler&share_type=t&link_source=app Beware results may vary and I think it works best above rendering resolution of 1440p or higher. Up scaling from anything below yields mixed results and the performance cost is there.

Have a look at this topic: NEW: Universal VR shader https://r.tapatalk.com/shareLink/topic?share_fid=74365&share_tid=266701&url=https://forums.eagle.ru/index.php?/topic/266701-NEW%3A-Universal-VR-shader&share_type=t&link_source=app