zildac

Curious, did you get this sorted?

The 192 address should be the target of the port forward. Your friends need to connext to the 164 address.

And that's using a JTAC lasing? Can you confirm your process for LSS?

It's unlikely, more likely that value is related to the source address or addresses allowed to connect. Try with it disabled see if they can then connect. If they can then consider using their public IP in that field. Again, if they don't have a static it may change and you'll have to update the rule to reflect.

Looks fine. One point, the “Originating IP” this presumably is the IP of your friend that you wish to join your server? If so, this may change (unless they have a Static IP). Try without this enabled, but bear in mind it likely means anyone can find your server, so you may want to add a password to the server. The second thing to consider is Windows Firewall, check if it is actually allowing traffic sourced from a Public IP to access TCP/UDP 10308 on the hosting machine.

Interesting, been forever since I used the DMT with LSS, but as you say it did use to work. I hope it's not the first "breakage" as a result of the lack of updates

Not at my PC at the minute, but I'm assuming you have designated a spot using TDC prior to trying to pick up the lase from the JTAC? I recall having a similar issue, but it's been a long time since I tried.

This looks great, many thanks for your work! I couldn't get it to work using the "saved games" location but using OVGME and dropping the relevant files in *dcs*\mods\aircraft\AV8BNA\liveries works a treat.

Or you export the config and reapply it after the update.

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.

I haven't noticed any (exclusively in VR) and it's hard to make out in your pic as it's quite small.