fjacobsen

My preferred setting is DLAA without DLSS. MSAA causes too much shimmering using 2x, but 4x only helps a tiny bit with worse performance. DLAA is more blurred looking at the distance, but I prefer this over shimmering with MSAA. I tell myself that it is haze, since IRL this also causes a kind of blurriness. I have not tried DLSS with the new DLSS version, since I get good performance already with DLAA.

In 15-20 years maybe, when / if they can get hands on documents for it´s sensor and weapons systems on the present Block version. Note that for all the present "modern" combat Aircraft in DCS, the Mark / Block numbers simulated are all more than 15 years old.

It´s weird... I have both V63 on my Quest 3 and in the Oculus PC App and everything works as it always did. I´m not sure if I still use then openvr.api.dll from the Open Composite Github site and if it makes any difference to the issue. Here is the link: https://gitlab.com/znixian/OpenOVR (look under pre-game install and download the 64bit version)

As posted before - I have both my Quest 3 and the Oculus Link app updated to V63 and has no problems running DCS in OpenXR mode. Oculus Link app is set to use Oculus as OpenXR runtime. OpenXR Toolkit works with no issues.

Strange... I have V63 in both the Oculus app and my Quest 3 headset, running DCS in OpenXR with the OpenXR Toolkit and does not have or had any issues. Oculus is set as the OpenXR runtime.

I got my T-shirt with a Parcel service today (Denmark).

I feel the same. In one of my self made missions (AH-64D in Syria) I got ~53 FPS before, but now see ~60 FPS.

I mainly use the Link cable, but also has VD installed. Apart from the velcro strap that comes with the Meta Link cable I have attached the cable with an additional Velcro strap to the Quest 3 headstrap (not using the original headstrap). I don´t see much difference between Link or VD connection, so most often I use the link cable. BTW: look forward going from the Quest 2 to the Quest 3, the clarity is way better with slightly better performance.

Try it in the dark on a supercarrier with rain.

Yeehaa If You can manage to get it ready for today, You certainly deserves a great Holiday

Wow.. I hope to see the AH-64D FCR this evening then - right Bignewy ?

I´m not sure, since I haven´t really experimented with it that much. But I guess that a target designated with the AG Radar will override the position loaded into the JDAM, thus You need to undesignate the AG Radar target. Regarding the TPOD, this might work a bit different depending on whether the TPOD CDES is boxed or not. Theoretically designating a target with the TPOD and CDES unboxed, will only designate at the moment You press designate and keep that spot as the designated target point also if You start moving the TPOD around. With CDES boxed in will continually designate the position where the TPOD is looking Question is just if there is a need to undesignate the TPOD before dropping JDAM's with positions ,oaded into weapon memory. Until now I have undesignated both AG radar and / or TPOD before dropping JDAM's with good result.

I cannot get the WSO Ground Radar to Freeze / Unfreeze. Using the Laser Fire button does not work, also not in RBM mode.

Yes but don´t forget to undesignat the radar or TGP (Boat switch aft) before releasing the JDAM's

Seems You have to undesignate the Air to ground radar before releasing the JDAM's Kind of makes sense.