Grodin

Sold

Just a heads up. I had constant stuttering (frametimes spiked every 2 seconds all the time everywhere) very noticeable in VR. I did _everything_ people suggested here, in reddit, anywhere i could find. All the CPU parking registery hacks, nvidia control panel settings, affinity tweaks, process lasso, deleting shaders, increase page file, exclude stuff in windows defender etc etc all of it. The one thing that cured my constant stutter was turning HAGS on. Confirmed by turning it off and back on again. Also credit to the core parking tips, that cured all the menu and mission editor stutters, for processors that have E- and P-Cores. So in some cases HAGS on is a very very good thing. This was on W11, 13900KS and RTX4080.

But V72 did. https://www.pcmag.com/news/meta-replacing-quest-headsets-bricked-by-buggy-software-update Yeah learned my lesson, disabled updates and will keep it like that.

Let's start with adjustable winds before going all crazy with the features heh

You mean like the previous stable channel patch that bricked headsets? No matter which way you go can't win with these.

Just your avarage Quest update breaking 2 things to fix 1. Luckily this time the update doesn't permanently brick the headset like the previous one did.

Quest 3 audio quality is horrid, G2 audio is better by far, not even a comparison. All high pitched sounds like RWR make my ears bleed with q3. Also a new update just rolled out yet again breaking things, just your avarage quest 3 experience. Im so done with this headset lol.

The MFD numbers issue is also very evident in F16 when adjusting radar up/down the numbes next to TDC become unreadable for many seconds.

Can't helmet designate with F-16 unless you have a VIS mode capable A-G weapon loaded. Other functions like snowplow should work even without A-G weapons afaik as long as you are in A-G master mode.

F-16 is by far easier and simpler to use. Partly because it is designed like that and partly because most of the stuff is still missing in DCS where F18 has a bit more systems modeled. 16 has much less weapons, much less different kinds of mfd pages, hotas is more user friendly and datalink is missing so many things, barely any failures modeled etc etc. No flaps or trim to worry about either on the 16. I find it quite boring after a while even i do enjoy how easy it is to do things with it. Thats why i prefer f18 in dcs and f16 in the other sim.

Got to testing things now. It is less blurry and there is less ghosting - so much that i feel like now its usable. I mean yeah the image quality still does suffer and there absolutely still is ghosting especially with MFD cursors, but not enough to be a dealbreaker anymore. This is great!

Just got an idea how to sort of make this work. - If all the units are inside the safety zone i will cycle the ship ai and/or alert state on/off preventing it from shooting at all - If some units are outside the safety zone but inside the ship wez then the ship will shoot at everyone and the guardian angel script will destroy the missiles sent for the units inside the safety zone. This way the ship wont always keep spamming missiles, only when there are some targets it is supposed to attack. It is likely to hit the planes that are outside the safety zone making the mission pretty much a failure before it runs out of missiles. Is there better way to stop the missiles as soon as they are fired than increasing guardianAngel.minMissileDist?

Very happy to hear that, until now i've found DLSS to be unbearable but i'll give this a try!

In single player using invisibility command works well enough because the wingman stays close to the player but in multiplayer you can get in to a situation where one player of the group is inside the safezone and the whole group becomes invisible and then the other players can fly anywhere on the map and stay invisible to the ai as long as one of them is inside the safezone. Or if the trigger requires whole group present then nobody is protected if even one player is somewhere else. I could just make every client the only member of the group but then TDOA and some other datalink things might not work correctly.

While getting rid of the MFD ghosting is a huge deal, looking at the switch labels in your picture it still looks like the same blurry mess DLSS always was - can anyone confirm if the image quality in VR still takes a huge hit like it did with the previous versions? I just can't stand the blurry labels and MFDs in VR.