Grodin

Just don't do it or spend a few hours training for it, jeez, its not hard. Devs have much more important things to do. If you want to pretend its WT just turn on unlimited fuel and go full afterburner everywhere.

ASW causes ghosting in external views (its motion reprojection) try unchecking that from the VD options. Disabling it will lower fps tho because it essentially creates fake frames, thats why you noticed such a huge performance jump.

But for VD you connect headset to router with wifi and router to your computer with a cable. Quest 3 cable support seems pretty much abandoned, doesnt work very well for many people compared to VD. You can't use virtual desktop with a cable, only by wifi to the router.

Because the headset is recommended to connect to the router with Wifi 6.

You can do augmented reality with openkneeboard and VD to see the real world on part of the screen yes. It works by creating a blank page that is pink or some other good greenscreen colour, open that in openkneeboard and then put the same color to VD passthrough settings, then when you open that pink page on your kneeboard VD will use passthrough camera over that pink page. Switch to a router will propably work yes but the recommended setup is computer directly to a wifi6 router via cable.

Not sure i understand your question but the way i do it is i press com 1 -> 1 -> ENTR on mission start and then i can just cycle through all the channels with the up/down arrows (have them bound to a rotary on my hotas). I've never had to enter a manual freq, all the needed channels are on preset channels.

I find all reprojection methods unbearable, but give the latest update a try, they made it so much better few weeks ago than it was with VD. Gauges, hud and ground objects dont ghost anymore. I mean yeah AH64 is still unplayable because of the reprojection cant deal with the rotor and hmd and fast moving planes in external views still ghost, but other than that it is now quite good - no more ghosting on HUD, gauges or radar screen and flying low the ground objects dont ghost anymore either, they seem to have completely revamped it.

Virtual Desktop works fine so if you are itching to fly thats a solution, pretty good one actually, thats all i use anymore with q3.

It's not a performance issue, it's a maintenance issue. The plane can do 9G just fine, land based air forces have their hornets rated for 9G because they don't have to endure the stress of carrier landings so using a paddle is fine if you operate from an airfield and pretend it's a swiss, finnish or some other land based air force.

Yeah this bug has been around pretty much since the burble was implemented, it's impossible to keep the nose up with it turned on, even full aft stick wont do - so just keep the burble off until its fixed :)

Not aware of such websites but ive seen most people avarage around 60-65 when they start to get a hang of it, say around 100 landings or so - it's easy to get 75 every now and then but the occational 60 drops the avarage. More active players with thousands of landings seem to avarage around 70. I have 814 carrier landings (F14 and F18 combined) and last 20 landings i wrote down avaraged 66 with F14 and 69 with F18. Really depends on the squadrons you fly with, some take landings quite seriously and avarage much higher than some more relaxed squadrons. Also taking a break seems to hurt the scores, if i dont fly for a month i will struggle to get even 60 on the first 2-3 landings.

I strongly recommend to make sure it won't come off accidentally, because when DCS thinks you took off your headset your flight will be done, the game will freeze and you have to restart. Once you get all the settings dialed in the only advantage G2 has is the center spot is ever so slightly more clear - i'd say like 10% or so. However with quest 3 you have that same clarity for all of your FOV, i don't have to turn my head at all or zoom in to read the texts in F16 MFD, all text is clearly visible from default head position for example (unless you use DLSS/DLAA which makes everything a blurry mess). FPS is same or better with Q3. Tracking is very much better on Q3. I'm on RTX 4080, 13900KS and 64gb DDR4 4400mhz CL18. Both - i max the settings in Oculus but also increase PD in DCS, because i can't use 2x MSAA, costs too much performance, but 1.2 PD is a good middle ground for image quality/performance. I didn't notice much difference in jitters or quality on Wireless desktop AV1 vs Oculus link on cable, but few random crashes on VD made me go back to cable - nothing like losing your progress after landing on 3 hour mission..

Any news on DCS MT OpenXR with Reshade? Is it working?

Thank you so much, you totally made me enjoy VR again! By default i felt like flying in a snow storm on my Quest 3, everything was blinding white from the ridiculous amount of haze. Now it is perfect, i think i'm going with 0.3 or 0.4. This should absolutely be a slider in the options!

Can anyone confirm if current drivers fixed the vr issues and increased fps to 4080 levels where it should be?

You can just tick the option from settings to override mission settings with your own i think.

Considering that the landings work perfectly fine for the rest of us the only logical conclusion is that either a) Something wrong with the technique or b) something wrong with the game. I'm unable to reproduce a situation where the nose wont stay up no matter how heavy i load the plane if i have the correct AoA and glide path.

Unlikely because any weight you can take off with you can also land with, there is no seperate landing weight limitation.

I like how it feels now, it is better, however the well documented 60-80ms input lag (nothing to do with curves) still remains, anyone can confirm this by recording the gameplay at high fps and calculating how many frames it takes for the plane to respond to inputs - it takes a lot longer than other planes. I'm not debating if it is correct or not, but the input delay is there.

They go long if you set the bomb settings for too high altitude, for example i had my bombs at the default 1500 ft and tried to drop them at 500 feet so they went long. After having correct altitude for the bomb settings they hit where they were supposed to.

Could some quest 3 owner vefiry if F16 OSB button texts (HSD, TGP, WPN, SMS etc etc) are easily and clearly readable from the default head position or do you have to move closer to see them well? Trying to figure out how much clarity i would be losing if changing from G2 to Q3.

Did disabling the toolkit give any benefits? Before 2.9 i never got reprojection working well, lots of ghosting and apache rotor causing issues etc - is motion reprojection better with dlss?

With Reverb G2 i find DLSS unusable even with "Quality" preset, cockpits go so blurry i can't read labels, can't read F16 MFD texts and all fast moving things ghost horribly. Increasing pixel density helps for the clarity but whats the point because then i lose all the performance i gained to begin with.

In this track you seem to use a keybind to open "intercom" which is a keybind called "open communications menu", that does not work unless you use easy comms options i guess? Try using keybind for "Transmit switch" there is one for UHF and one for VHF. You need to select which radio you want to use - all i can think of is that you are used to the "easy comms" option and either they are phasing it out or it is bugged, i can't really help you with that as i don't know how it is supposed to work.

Only thing i could think of is that maybe you are already slow enough when touching down that the nose wont stay up? Sure it does fall down a bit sooner with heavy weight, but i can always keep the nose up atleast for a while even if landing with max load, but i land at 11 AoA instead of the 13 so i might be coming in a bit faster than you.