Hive

So planned for March now?

Are you sure this is how CM works in DCS? Usually it is the other way round: 1 HEI round followed by 4 API rounds. https://man.fas.org/dod-101/sys/ac/equip/gau-8.htm

Please forgive the perhaps stupid question, but I just want to be sure and I think it may help. others, too: I use OpenComposite (system-wide) and OpenXR. What exactly do I have to do now to switch to DCS native support? Just switch back to SteamVR in OpenComposite? Delete the OpenComposite folder? Delete the openvrpaths folder? How do I now for sure wether DCS uses native support vs OpenXR via OpenComposite (despite some features do not work at the moment? Thanks!

Oh no, even worse performance in VR is what we needed... I appreciate the switch to OpenXR which surely was Intended to boost performance and it is completely fine if it has some problems at first in an open beta, but I wish ED would communicate such changes a little more transparent.

Wow, awesome find. Thanks ColinM9991. Please receive my "hero of the day" award! Looking forward to test it. And thanks BIGNEWY for mentioning it to the devs.

Today I did some testing and raising the brightness of the MFCDs does not help (for me). Then I jumped into the F/A-18 (which I own, but do not fly) and the difference is insane, like night and day. ED, please, please, please just take the Hornet as your reference and adjust the A-10's displays accordingly. The font/symbology is much heavier for the F/A-18 and I think that's the solution as thinner lines are eaten by aliasing in VR (even with MSAA 4x) while thicker ones just shimmer on the contour and keep their readability. Make it optional, if you want to keep the new look for 2D (for me it looks great in 2D).

Miles sends the HMS with the newest firmware already installed. I don't think that you have to install anything to make the AUX buttons work.

Please not too much off-topic. We know this thread will be closed otherwise. I am just happy to hear that there is progress. I am very curious how much the new radio will change gameplay. Using the old radios in VR is a pain as they are very hard to reach and I do not like the preset functions where you have no indication what frequency is behind each preset number. As far as I understand that will be better with the new display and MFCD page. On the other hand I hope it won't cause errors in campaigns where you have missions with certain presets that you need to dial in.

I suggest you visit wikipedia. These pages list the complete armament capabilities for both aircrafts and you can click on each weapon system to find more information about it: https://en.wikipedia.org/wiki/Fairchild_Republic_A-10_Thunderbolt_II https://en.wikipedia.org/wiki/Boeing_AH-64_Apache A-10C, AH-64D and UH-1H are completely different modules - you won't be bored. Mavericks and Hellfires are both Air-To-Ground missiles, but they work completely different - at least most variants. The laser guided Mavericks and Hellfires share some similarities, but otherwise it is a fire & forget, optoelectronic missile vs a laser guided missile (or radar guided, when the Apache gets the Fire Control Radar upgrade).

Not sure, but DLSS brings its own antialiasing method (DLAA), right? Since DCS is completely aliased in VR, even with MSAA 4x, DLSS may enhance the image quality.

@BIGNEWY would you be so nice to clarify if/how DLSS and VR will work togehther? It was asked several times in this thread. Thanks in advance!

Awesome newsletter! Thanks! ED, could you tell a little more about DLSS and VR, please? Will they work together?

Let's give it a try. Many things change without notification...

Well, as the title says, it is a VR problem, so I am not suprised that you do not see it without VR. But I will try turning up the brightness. I did not fly the A-10 for some weeks and when I did today I was shocked again what an aliased mess the MFCDs have become. I am happy for everyone who does not have/see this problem/change, but it still needs to be fixed for those who do. Checking out, Happy New Year everybody!

Thank you, BIGNEWY! You don't see a problem, but you see the difference, right? At least in ColinM9991's screenshot? If we can at least agree, that something has changed, it should be easier to to find a solution for those that are negatively affected by the change. For me and obviously others this is a huge deal as it is so much harder to read the MFCDs. As it worked well for years until the recent update, we know it is possible.

Exactly what I think, too. I want to support ED, but no by buying modules. Put a PayPal-Button on the homepage, receive money and do whatever you think is best, ED. It doesn't even have to be for specific features. That is risky and creates even more expectations.

+1 I would like the HUD to be in English, too. It is inconsitent with the rest of the cockpit und hard to understand.

This thread is still flagged as "cannot reproduce", but I hope it is investigated?

Thank you, ColinM9991! It is extremely obvious in your screenshot that something has changed. And while it does not look necessarily worse in the screenshot (I might like 2.8 even better in 2D), it is a completely different story in VR where it is so much harder to read.

nVidia RTX 3090: everything on standard settings in the Control Panel Reverb G2: OpenXR, 110% resolution DCS: PD 1.0, MSAA 2x

Thanks for merging. I hope this thread will move to the bug-forum and the issue is investigated?

No performance improvements with the new patch yet, right? No complaint, just a question, not every change is listed in the patch notes as we all know. But really missing FLIR-updates.

You can configure everything via the onscreen-menu, LSHIFT+F7. Description see page 1.

Have a look at the wishlist section Not that I demand anything that wasn't promised, but it would have been cool to get some of the requested features.

I recently posted it on the A-10c II forum, too. Reverb G2, 110 % resolution, PD 1.0, MSAA 2x, nVidia Control Panel standard settings, OpenXR