Czar

Probably Kola and Normandy update. I don't have neither and mine got patched very quickly with 500GB of free space. Uninstall 1 of those maps if there isn't enough space then reinstall later. Patching can duplicate assets such as maps before patching.

Just reading the changelog now. Solid patch! Visors for the two awesome jets, Hornet and Viper! ...if I read it right. Good start. I hope all others receives it too.

Overexposure is not affected by lens effects, only when looking directly at the sun.

Normal. Screens have a variety of types and tech on every type of electronic. VA vs IPS for monitors are wildly different in the extreme values especially on darks, for example. Each manufacturer has also different screen calibrations. All you said is pretty normal. It would be surprising if it were the other way around. Among flat screens there are a number of different screen types, VR goggles, cellphones, tvs...etc. If you have crushed blacks on your VR goggle, consider adjusting its ''black levels'' if there is any to chose. Usually they come with ''normal'' or ''low'' on monitors. If you're using full range on ''output dynamic range'' (nVidia control panel. Whatever is called on AMD control panel) consider switching to ''limited''. It will bring the low values back up and tune down the contrast. nVidia control panel->Change resolution->Output Dynamic Range - Limited. Alternatively, bring DCS gamma up if it doesn't overblow clouds. If it does, there may have other methods on the VR hardware itself, which would be best in order not to mess with your monitor settings.

It is a universal value for digital to screens. Doesn't matter the screen. You should adjust to fit your needs. But when mastering a visual media, the artist should be at 2.2 because that's a value most electronics are around/made to be at.

I hope to see something new from Heatblur about the F-14 special effects. Those overwing/tenis court vapors and afterburner effects had already shown their age. Especially how muted down the afterburners are in dim lighting in comparison to real life. vs

@Raven (Elysian Angel) and @ThorBrasil are both right. 2.2 is the neutral gamma visual industry wise (refer to external sources), but that value in DCS is off balance with over exposure. There are much worse offenders out there, btw. DCS still looks good. All games have their look based on artistic vision, DCS just happens to be one of the few that references the industrial value being the default 2.2, which is correct. Use a lower gamma to counter over exposure and the lack of a tinted visor. ...even for calibrated monitors without any blown up whites. (we need those visors across all modern modules...)

If you have a HOTAS analog switch as a mouse you can do those with the ''F2'' external view view without editing any .lua file. Tiny inputs on the analog. There are bindings for the ''mouse look'' speeds if you want it even slower. Camera View Mouse Rate (fast,normal and slow).

Maybe something changed/got borked in the INS update. I never done this, but why would be point track only? Area track seems perfectly reasonable of a mode to do something like this, especially when point track can snap the TGP onto a moving object without the pilot consent, IIRC. Area track tends to grab the ground pretty well.

Information to identify the cause of the issue that is?

What is the storage type DCS is on? HDD, SSD? Set your pagefile to 30gb+ through windows on a fast drive (SSD). Undo any overclock made. What's the GPU usage like? If it is out of VRAM performance takes a nosedive. (DCS is heavy on the assets side). Share with us your GPU model. Problem might lie there. 10fps is not normal unless is a heavy bottleneck somewhere like VRAM or Storage, with the later making stutter seems like low fps. Check your mouse polling rate. Use the mouse of your old PC on the new one to see if it resolves. If it does, is the high polling rate issue that DCS doesn't like. (reported on the forums).

Modern HOTAS ads on a carefully crafted 1980s map intended for immersion... or a WWII one. ....or in a serious campaign during reconstruction of real life events in a war which often are tragic. Tone cannot be further away than a racing sim, which is about a sport which is hand in hand with capitalist values, which is fine. I think it is in bad taste to put ads on DCS maps in quantity to generate resources. The current ads everywhere culture kind of sucks too. There are much more efficient ways to generate resources without kneeling to the advertising world: making a good job on a module, collaborations outside the sims with related brands (already being done), Content Creators (already being done). Sorry for being too negative. Fair skies and happy flying.

I guess so, but that's beyond my ME and these items IDs knowledge. Given there is a random system failures, the values of: meantime between failures, probability for each failure point/item in the plane...etc.. are all hidden. It should be displayed and changeable from the options menu or some sort of "Hangar" sub menu like the "Special Tab" we have. The sim from Laminar has the best system and it is natively implemented.

ED modules has system failures.... just not programmed.

I had this 'aircraft armed' announcement bug too. There are no master arm switch binded to my hotas. Multiple times George is not firing the weapon after announcing 'Engaging' within constraints and steady flight. A cycle from 'No Weapon'/De Wased or from a de-slaved TADS brings him back to be able to shoot. This happens a lot. I'll try to generate a short track when able.

I don't think so. On the debrief screen you'll be able to see what has failed (able to filter out the list by 'failures' makes easier) or you'll have to diagnose it yourself. IIRC the Random System Failures is always off in multiplayer unless the mission designer has chosen to enable it, so you might never see a failure if you only play on open multiplayer lobbies and if that's governed by the mission settings. Needs a double check on that one.

There are system failures, but not preset/specific system failures by custom triggers. Turn on "Random System Failures" via Options->Misc. menu. Something somewhere might break but not cockpit lights which afaik only the F-4 does it. It might ruin a whole sortie depending on the system that failed.... or greatly enhance it depending on the mindset, ofc.

No. The missile will act like it is part of the aircraft fuselage. It is 100% fixed in position. There is no motion difference between the rail and the missile as seen in MSAA. It is just a complex scene playing chaos with the temporal algorithm. It is 100% out of the hands of ED, unless a new temporal algorithm comes along globally. It is all about contrast between pixels. Tiny details that have high contrast will either disappear with motion or be reluctant to move in scenes that has ghosting. The motion on that wingtip is of high frequency as well, a nightmare for temporal anti aliasing. Same goes to the blinking HAFU for the tomcat radar screen. At certain zooms, the blinking HAFUs appear solid, same goes for the blinking countdowns when a Phoenix has reached pitbull. This effect is also seen with a fast runway absent from the background.

Try dots at 2 pixels on the options menu. I highly discourage upscalling in DCS, which is a very pixel sensitive type of experience but it can be mitigated with the dots at 2 pixels thing.

My sim is locked at 40fps for personal preference: hardware + fps consistency across anything that's possible to occur on screen. The ghosting doesn't get in the way of my combat. I assume it will diminish with higher FPS too as it is the nature of temporal anti aliasing. Keep in mind that is FPS dependent, which is the actual render the temporal anti aliasing is acting upon previous frames to generate the next, not "Refresh Rate" dependent. The later only affects monitors if you're running with no Vsync, which is already the standard to run without. The gif is at 25 for compression sake.

The Jittering appearance is the ghosting itself. The factor is the values (color) involved. It is a bit difficult to picture it with words, I understand. Tested with DLAA and MSAA 2X. The missile is properly attached to the wingtip rail. With temporal anti aliasing it looks detached because of some details of the rail remains with stationary appearance because of ghosting. Everything should wobble but together. (F-16s loaded wingtips are very wobbly) It is just the nature of the beast (temporal anti aliasing) as of today.

Because this have small objects involved. I'll check MSAA and report back.

You have a temporal anti aliasing turned on (DLSS, DLAA, TAA, FSR...) With a temporal solution for anti aliasing, some object movements are nullified (wingtip and rails) while others are conserved (wingtip AAMRAMS). It is dependent on contrast and size. So they appear disconnected. Try to zoom right into the missile and rail to see if the rail and missile are moving together. IIRC I did that and saw them properly connected. It is been a while I don't use MSAA and always saw this discrepancy using DLAA since late 2023 when I got the Viper. There are other instances of this phenomenon happening as well, in and outside DCS.

What an horrid thing about the imgur in the UK. My quota is done on the forum, so I can't put images here. That website, regardless of its first page content, was really easy to make images shareable. @HC_Official Thanks for the heads up. An excuse can be just that, an excuse. The means to do evil in disguise.