winghunter

Its such a shame we cant totally disable WMR home, even SteamVR allows this. @nikoelreplacing WMR home with an empty room in above video should be part of the guide

The HUD is usually textures and bitmap fonts afaik. These can vary greatly from module to module regarding resolution, aliasing, sharpness/contrast, mipmap levels etc. The Tomcat is another example which has very sharp aliasing on the ACM panel in the cockpit, while the HUD looks ok. In the F-15 on the other hand, the HUD looks the worst.

I think the A10 HUD is more forgiving, looks like they used bitmap fonts. But otherwise you also seem to get the jagged hill lines against the clouds, the frame edges and the jagged roads.

Thats how openXR looks for me with MSAA disabled. Notice the blocky horizon colors and jagged HUD lines. It gets amplified when you twist your head, like some orchestra of shimmering and artifacts. Thats on a G2 at 100% I dont know how folks can live without MSAA

I have installed 0.6.3 and it works fine. I disabled MR to see if my performance dips come from MR rather than openXR itself. Some mission i posted earlier was unplayable with openXR and MR, while it ran totally smooth in SteamVR.

Very strange, I am seeing the opposite: much more aliasing and shimmer with 80% openXR than with 80% steamVR

very nice, thanks ED

Found it, I forgot to switch to NAV ILS mode as in the previous mission it happened automatically. So I assumed it would be the same in this mission.

on second thought, could also be that WMR is NOT set as your active runtime

If thats set as your firewall, then yes. You need to allow openXR tools internet access, wether you have norton or windows firewall.

looks like a firewall issue, openXR is checking if its up to date and cant connect to remote host.

Thanks for these ! I really struggled with the ILS night mission. I could follow the cross and it would suddenly jump to some very different place. Not the small jumps from turbulence but really large jumps with completely different direction and altitude. It may have been that ive overflown the airport, need to try again. But in any case the airport did not come in sight.

After getting better performance with openXR, I am once again back to square one. Performance tanked for some unknown reason, i didnt change any settings. I was flying the F15 standard / default mission attached. It still has the old cloud setting but i dont think this should make the difference. For some reason openXR is having terrible performance at times. I fixed this previously, or i thought i fixed it by reinstalling openXR dev tools. Switching back to SteamVR everything is butter smooth in this mission. Can someone else confirm ? F-15C - Caucasus - Clean Sweep.miz

From this post, it looks like the 45 fps stutters could be an issue of the G2 headset (software), rather than a problem with DCS.

RTX 3070, i7 10750

The developer, gotta love M$ Windows

Unless you have an Aero and the GPU to drive it at full resolution, you wont get enough pixels to spot aircraft from a distance. On my reverb G2 I always fly with labels, otherwise its too hard to spot anything > 3 miles. For realism, fun and immersion, you cant beat VR. I dont care about unrealistic competitions. If there were VR-only competitions then it would make more sense.

@nikoelcan you note that MSFS users need to re-install OpenXR Developer Tools ? They likely have a beta version that wasnt properly updated by MS, even though it shows latest release. Reinstalling fixed the framerate dips for several people.

Adjust scaling on OpenXR Developer Tools, not in game

would be a good idea to split threads for Quest vs G2 users, as they have very different issues it seems

no steam, no steamVR, works with standalone DCS

uh_1_blade.dds I dont own the apache but it looks like you could just copy over and rename the blade texture

try reinstalling openXR developer tools

reinstalling openXR developer tools improved this a lot

Can you try re-installing OpenXR Developer Tools ? That fixed this issue for me, now my frame rate doesnt get tanked any more. I had installed it for MSFS months ago, and it was supposedly up to date. But reinstalling fixed this issue so something must have gone wrong with the updates.