zildac

May be worth having a look at the last few posts in this thread. With the latest DCS update, you can select which preset DCS uses by editing the autoexec.cfg file.

I have two shortcuts, one for VR and one for Pancake, they still appear to work. EDIT: Just noticed my "start in" is incorrect, but it works, as the MT binary is the default these days. null

Any idea when you may be in a position to release what you've done so far

You may want to take a look at this:

I went from a 12900K to a 14900KS and I didn't notice much of an improvement in DCS. I run a 4090 and am still CPU bound in VR with a Varjo Aero. I suspect you will get far more benefit with a 9800X3D.

Ensure both of these settings are disabled and retest null

"but only on days that are divisible by prime numbers"

I have had numerous issues with the 572.x series, predominantly black screens and random system lock ups (using multi monitors). This seems to be a known issue and is all over the Nvidia forums. For now, I have rolled back to 566.36.

@BIGNEWY Can you highlight this to the devs again, please? Even if Matt is unable to implement the changes to the tools, having DCS "ready" for such an approach would likely benefit many VR users.

You are not in TPOD DES mode, merely slewing over the target then hitting TOO (number) will not set the JDAM coords to your TPOD position. You need to TDC DOWN once over the target then TOO -> Number. IF you want to just be able to slew and have it designate automatically, you need to check "Easy Mode TGP" in the Harrier special options. null Watch this vid from around 2:30 and notice the TGP bottom right change to TPOD DES.

TCP/UDP 10308 is the only port you need inbound, unless you also wish to admin the server remotely, in which case you will also need 8088 (WebGUI) also if you use the DCS voice chat you'll need to allow TCP/UDP 10309 also.

No, just using the latest DLSS dll that shipped with the CyberPunk patch.

That's interesting, and negates the need to set the profile via NVPI if you’re already using DLSSTweaks...how did you find that?

Yes, or globally if you prefer. I opted for the former.

At a guess, in VR the CPU is worked harder, hence the CPU render thread message. In 2D I am GPU bound at 249FPS. It seems normal to me. As to why you are seeing worse performance in VR with DLAA when you are not GPU limited is a bit of a mystery. I am also using Varjo Quadviews Foveated in VR.