DayGlow

This is the issue. Turbo mode will cause these crashes

Not sure for other airframes, but the A-10 you can change the slew rate for the TGP and MAV through settings in the aircraft.

You can navigate SteamVR with a gamepad so if you only use VR for sims you don't have to worry about VR controllers.

Cool, though it doesn't detect the eye tracking of my Qpro though.

Can't find any info on this, but it seems there are new options in the VR tab, but they are greyed out - use Quad View _ Track the eyes position Quad views is checked off for me since I have Quad Views on the Quest Pro. Are these options live or settings for a future update?

So turns out it is Taz1004's optimized textures for the aircraft somehow affect the radio even though it's only a texture mod. Once I removed it the radio worked as expected.

I don't know why but the optimized A-10CII textures mess up the ARC-186 radio (bottom FM radio in stack). With the mod activated the default channel is 130mhz and anything below 80mhz gives an out-of-range tone. Once I removed the optimized textures it performs as expected with the default channel of 30mhz

Long press works. A short press also works, but the mouse curser has to be centered in the jester wheel, which was causing my issue

Getting back into the A-10c II and flying some missions. Trying to figure out what is going on. Trying to communicate with JTAC, but I found if I use the ARC-186 at either 30 or 40mhz I just get a continuous tone. If I tune the ARC-210 to 30 or 40mhz I can communicate just fine. Write rather use the ARC-186 for JTAC as summer missions need the ARC-210 for other mission comms

I found that it's difficult to use the Jester UI with VR and head tracking to issue commands as to close the menu afterward the mouse cursor has to be centered into the UI wheel to close it. Kinda defeats the purpose of using head tracking for commands

The tacan for the ship in the instructions is set to 44x, which is the same for Kutaisi Airbase, so when you go to TACAN to land at the boat you aren't heading anywhere near it.

I was running into the same issue. I have v63 on my Quest Pro and couldn't get link to start. I switched over to IL2 and found OpenComposite was crashing. To fix that I took the Oculus App on the desktop out of PTC in the Beta tab of settings. That fixed the link issue for DCS as well.

If you want 64gb one thing to consider is using a program like Primocache. I used it create a ramdisk cache of your SSD(s). I find it makes a noticeable difference in performance loading commonly used programs

I've read there is encoder issues with the 79xx series and quest headsets. People reporting degraded image over link, but very clear over virtual desktop. No idea if it's been fixed or not, but it seems Meta had to do something, not AMD.

On the return leg I'm asked to tune to Darkstar as an enemy flight is getting close. It's set as preset 3 on the ARC-210, but the preset channel is FM, not AM. Manually tuning the radio is fine, just an FYI the preset is on the wrong band.

Personally I really like my QPro. Decent FOV, edge to edge clarity with the lenses. Eye tracking for DFR and wireless for better VR outside of sims. Pimax Crystal is king of clarity, but my experience with Pimax with my 8kx is that there is a lot of jank in their headsets and software.

Id think it makes more sense to keep pixel density at 1 and increasing it for the foveated region in QVFR You're wasting resources with upscaling the whole scene then QV to downscale the peripheral region again

I've found screen space shadows makes the foveated border much more noticeable.

I don't see any issue if it's only to make it smaller than default. Have a slider with 100% as the top so if someone thinks the dots are too big they can reduce them. No advantage is gained this way.

Yeah, haven't flown the AV-8 in awhile. Thought I'd check out how dlss works with the ehsd as it was always a very aliased display. Thanks for the amazing app by the way

I've noticed with 2.9 and DLSS enabled you can see the eye-tracking box moving while flying the AV-8B. Kinda hard to explain, you can see the shade difference as the box moves around. I believe that the AV-8B has a different glass shader used than most jets. The old VR shader performance mod modified this shader.

The 2.9 video shows DLAA had a 10+ fps improvement over MSAA X4

Would be the quad-view settings. This app makes adjustments easier https://www.digitalcombatsimulator.com/en/files/3332882/

I've noticed a few posts where people are wasting resources in upscaling while using quad-view DFR. For myself I keep the PD at 1 in the debug app and in the Quest desktop app under my headset settings I keep the res slider at x1. I know this goes against conventional thought, but I use DFR, so I increase the foveated supersampling to 1.25-1.5. This way I'm not wasting resources supersampling the whole render only to have DFR downsample it afterwards.

I'd increase the density for the center in the foveated settings file instead. No point wasting resources supersampling the foveated part.