SeeYouAtTheMerge

The mission editor and new DTC function incorrectly label the COMM 2 as the ARC-222. The F-16 does not use the ARC-222, it uses the ARC-186 or ARC-210 as the comm 2. I believe ED does not intend to implement the ARC-210 so it would nice to get it corrected in the menu to ARC-186. Thanks

4.2+ Sniper can show frag rings

In the new tactical employment chapter the description of one vs two circle BFM is not quite correct. Both the one circle and two circle labeled images are actually a 2 circle. The image attached below is a one circle fight, notice the turns of both fighters in the one circle fight go together to create the single circle vs each fighter making their own full circle (aligned or not) in the 2 circle fightnull

RF Silent and Quiet should make L-16 receive only

Its a bug, the bomb should have a CEP of 5m but BOC isn't simulated properly so the bombs miss when dropped in BOC

It doesn’t, the way it currently works is basically hacking it so all the sams that aren’t set to hidden are “loaded into the dtc when you spawn as threats” and that’s how they appear on the HSD

Unfortunately that one isnt apart of M4.2+

He mentioned that we are missing an entire radar mode that is specific to the F-16, ULS. That most certainly belongs on the list as it is a viper feature. DTS is definitely not a waste of time, there are many things the DTS provides. The first thing is PGCAS which I don't recall if we have currently. The second is Database Terrain Cueing which is similar-ish to TFR but instead of it using radar it uses the terrain database to cue you to stay X feet above the terrain model, its not as accurate as TFR because your relying on the quality of terrain model loaded so you should only use it in VMC but it still a great feature. In addition, DTS provides obstacle warnings if the system determines your not going to overly an obstacle by at least 500ft by default. And I highly disagree with the notion that introducing error-correcting systems is useless, if you want to simulate the viper's navigation system as realistic as possible you have to model the ENTIRE THING, including the parts that degrade and upgrade the navigation quality, not just the degradations or else you have an incomplete simulation. Also, to your comment about the JDAM threads, the problem that was being discussed in the JDAM thread is that BOC isn't working properly so what should be the most accurate mode is actually the LEAST accurate in dcs. In the case of Expanded DL, this isn't a DCS ecosystem limitation. We should be able to HSD or FCR cursor over L-16 tracks and see more info about them which the hornet can already do so its NOT a dcs limitation Here are some very useful hotas commands that we are missing; Cursor Enable should switch between POS/HAS/DL delivery mode, Cage/Uncage button should cycle target isolate modes but those arent implemented for the HARM, in POS submode the pinkey switch should rotate between PB, EOM, RUK submodes, TMS Right while In POS or DL should steps the threats in the threat table.

You guys said after you guys release the sniper you are going to fix the lantirn and make it accurate but in the roadmap the LANTIRN is marked complete even though it isn't

Yes, it should

I dont think the green emitters should fade, they should stay so if a emitter goes offline you can still hook it and shoot it with a harm from the HAD or find it with the TGP

For the bombs without the FMU-152, the cockpit options for arming delay doesn't actually change the arming delay of the bomb, its just telling the jet what the arming delay of the bomb is to compute when to show the LOW symbology

This isnt working correctly, the 3 seconds lase shouldn't matter for a BOC attack. The point of the lase before the drop is to provide valid ranging to the TGP to generate good coordinates. With BOC the bomb is loading the coordinates directly from the STPT so you don't need a laser to make the coords more accurate because you have perfect coords.