DayGlow

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.

When I got 64gb of memory I started using Primocache to use part of my memory as a super fast cache. I have 12gb for my Windows drive and 12gb for my App drive. Can't say it helps DCS directly, but it does improve overall system performance.

As a former G2 owner with a QPro now the other thing to consider with FOV is that even though the QPro didn't have a much larger FOV you do get edge to edge clarity with the QPro lenses. When I had my G2 with its small sweet-spot I kept my eyes locked in the middle of the lense and moved my head to look at everything. The QPro you can move your eyes and scan much more naturally. Looking at the HUD a quick glance down works vs bobbing your head up and down.

I loved the FOV of the 8KX, but the jankyness of the pimax software turned me off. Randomly crashing, or tracking starting to shake, etc. It was just too much. Pimax simply promises too much and continuely fails to deliver.

The most dominant headset want necessarily be the best. Meta and the Quest 2/3 will most likely dominate the field. I'm interested in the Somnium VR 1and if it materializes. The specs look great and I hope it comes out.

Sorry, I didn't expect you to fix anything, just wondering if you would have an insight on what would be going on that would affect the mod as a starting point in finding a solution. I understand that you would have no way in changing the mod.

What are you experiencing when you say "not compatible"? I'm running both and haven't noticed any detrimental effect. dots aren't visible. I uninstalled the foveated rendering and could see the dots again. doing it back to back and there is a clear difference. Very easy to see if you edit the dot size to something ridiculously large. Very easy to see when DFR is uninstalled, but disappears when I install it again. edit I've messed around a bit more and it does work somewhat. It seems to have some weird behavior. I found that any supersampling of the focus area at all makes the dots go away for the most part. By increasing the dot size to something huge I've found that the foveated area shows the huge dots, but the center area doesn't with any supersampling introduced. I was running with 1.5 for the center area, which made the dots disappear completely. When I go back to regular-sized dots they are definitely harder to see with no supersampling compared to removing the DFR layer.

@mbucchia I have found that the improved dot mod Isn't compatible with foveated rendering. Just wondering if there could be a simple solution to this. If not I probably will choose to go with the foveated rendering with dot labels, just hoping this can be fixed somehow.

Not at this time. Meta has hinted in the past they may enable it, but nothing so far.

Is there any issue using the ARC 210 for the comms instead of the UHF AM radio as requested in the missions? IE is it expecting the old VHF AM radio set to 126.000 like instructed?

do you have info on the LUA edit needed?