Sr.

Seems unnecessarily tedious... I mean it's not like a dude walks over to do this.

Look in your Saved games folder, DCS/Config for autoexec.bat (if not there create the file), edit and add the following force_cross_eye_recovery_tool = false Or the next time you see the tool, click save. This will write a file in the Saved Games/Dcs(root dir) name HP Reverb Virtual Reality Headset G20.lua, at that point the tool will not reappear unless that file gets deleted.

For me, with 22.7.1 I was getting flicker at any rate, fixed with 22.8.1. And based on what I saw last night using the OXR toolkit counter I've gained a minimum of 4-6 fps GPU side.

Roger that! Looks more incredible now.

I've always thought it was the sheer number of cars... I can be flying along ok until I look 6 or 9 and see several parking lots full.

22.8.1 fixes this

Maybe my eyes got old enough to not notice

I run about the same only with WMR at 60Hz, and it glorious. But I think I maybe won the silicon lottery equivalent of flicker free 60Hz. I have only experienced that after AMD launched driver version 22.7.2 (I think). It was horrible and had to roll back to 21.5ish Yesterday they released 22.8.1 and fixed the flicker problem. Welcome aboard. You left out one of my favorite "improvements", eliminating the epilepsy inducing flashing during the loading screens.

I've had that issue intermittently ... never able to nail down what caused it. Currently not having the issue.

Make sure you have write/change/modify etc permissions to wherever the config file is stored.

reboot?

Honestly, I would consider rolling back off of 22.5.x which worsened with 22.7 I had a myriad of issues crop up after "upgrading". I am running 21.6.1 and plan to stay there until there is definitive proof AMD has gotten their driver **** together. Our systems specs are similar enough that you should be able to run the OXR stuff pretty much bone stock, and FSR enabled. I would start by setting the tool kit back to defaults, enable FSR then tweak contrast, colors etc to your liking. And give 60Hz a try if you haven't already.

Got mine working again, but I have to re-run the PS script between game sessions..

No change with 22.7.1 https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1?utm_source=pardot&utm_content=&utm_campaign=2022-07-26_Driver_Alert-Radeon_Software-Release22.7.1-jul-en_US-email&utm_medium=email&utm_term=

I've been meaning to follow up. A few days prior, I had been playing around with iUFC (I think it's called). App that let's you use an iPad as UFC... It dawned on me that beside updating DCS and OC, I had imported a lua file for that to work... After removing those changes, my OpenBeta is working as before.

Not yet for AMD GPU

Still working for anyone? I haven't been able to get it to work again since a couple OpenComposite updates back.

I saw the same. That shimmer... ew.

Yep, first thing I do after a repair install. It's crazy how much difference there is between my OB and stable installs. My OB must be really jacked up.

Yep... even after 3 times running DCS repair/remove extra file found.

I turned on the OXRTK developer counters and noted while in openbeta, the CPU counter would immediately flip to "CPU bound..." and it was in high 20's Even checked it via SteamVR mode using fpsVR and the CPU counter looked like a red picket fence, same frametime numbers in the high 20's. Having only ever seen the "CPU bound" for a split second while DCS was loading a mission etc. Now I don't see it at all, and CPU frame times are back to between 5-7.

Upon further review... It appears the issue I'm having is with the latest DCS OpenBeta update. I just did a new install of the previous stable version 2.7.14.25228 and everything is back to normal. BTW, not a fan of the new, sparkly FA-18 gun fire. Just seems cartoonish.

I dunno... seems something happened with the latest release. I've always ran my G2 at 60Hz, which required no need for motion reprojection. Now it's as jittery as 90Hz without MR. Or I could run 90Hz and lock the frame rate in Radeon software to using Rivatuner, no motion repro and it was fine. But I can't get jitter free with anything unless I use motion repro.

Having the same issue since the last update. Though it will only happen in a cockpit, opens fine at the in game menu.

Is there a process for "uninstalling" opencomposite? I think I need a do-over. I've always run 60Hz,high DCS, and 100%, no MR & was butter smooth. Now I'm getting tons of jitter even at 30fps