Martijn

There seems to be a misconception that the MiG-19's ARK-5 has some sort of feature that would require editing in the mission editor (in which case I could see value in such an alteration that lets us do it from within the game instead), but this is not the case. The ARK-5 does not have any sort of preset frequencies or whatsoever. I think some of the confusion stems from the recent video which incorrectly describes the ARK-5 as having up to 3 predefined radio frequencies, as well as older versions of the DCS: MiG-15 which also incorrectly used 3 preset frequencies in NEAR mode. The ARK-5 behaviour in the DCS: MiG-15 has since been rectified: now the only thing NEAR mode does now is override the frequency range selector on the ARK-5 panel with a frequency range selected with one of three switches. This is exactly how the ARK-5 in the MiG-19 is supposed to work as well, but instead of having three switches for our NEAR frequency range selection, we now have a much more intuitive dial just like the one on the ARK-5 panel itself. In case anyone is wondering why you would want the NEAR / FAR selector to change just the frequency range but not the tuned frequency, the frequencies on the INNER / OUTER NDBs of the airfields are spaced out in in such a way that your ARK-5 will already be tuned correctly by changing only the frequency range, so that you can use the NEAR / FAR switch to toggle between the inner and outer beacon. And with that in mind, I really cannot see a compelling reason for altering the ARK-5 behaviour. There is (to the best of my knowledge) just one and a half airfield in the Caucasus map that have two beacons where the frequencies are not set up correctly for this: Kobuleti (490.00KHz / 870.00KHz), and runway 13 of Tblisi-Lochini (923.00 KHz / 342.00 KHz) (runway 31 with 435.00 KHz / 211.00 KHz works fine). I just spent some time playing around with the ARK-5 in the MiG-15, and using the NEAR / FAR selector in a 'realistic' way works fine for most airfields. There are four airfields (Krysmk, Maykop, Mozdok and Sukhumi) where I had to tune the frequency sligthly when switching between frequency ranges. In the case of Sukhumi with the MiG-15 going from 498.00 KHz to the 640-1300 KHz range results in a frequency of 998.00 Khz which unfortunately tunes me in to Gelendzhik (1000.00 KHz) instead of Sukhumi's other beacon (995.00 KHz) despite that the Gelendzhik beacon is 300 kilometers further away. Personally I'd be much happier to see the MiG-19 have a 'realistic' implementation of the ARK-5 identical to that of the MiG-15, that instead 'fixes' these small tuning issues (i.e. have the ARK-5 select a beacon with perhaps a tiny bit more leeway in the frequency tuning, but also take distance into account to prevent the wrong beacon from being 'selected'), instead of implementing frequency memory (functionality that the real ARK-5 never had). With all that said, so long as the only difference with the added frequency memory is truely just then it shouldn't really get in the way too much either. Still, my personal preference is for keeping the system just as simple as its real-life counterpart.

The steps you described are correct and should work, but there is indeed an issue with creating new waypoints. Lets say that you are trying to create waypoint n, then your INS needs to have a waypoint n-1 first, keep this in mind as this is key. I loaded up the M02 Introduction to the INS training mission for testing purposes, where your INS already has a waypoint inserted, and ran into the same issue as you. The short explanation is that, at least in my case, it is a bug where the PCN will display garbage data when selecting a new waypoint with PREP, instead of the PCN windows going blank. In my case this garbage data in the window that is supposed to be blank, is actually valid data for a waypoint that doesn't exist. This tricks you into thinking that you have a valid waypoint n-1, so when trying to create waypoint n PREP reverts back to the previously select waypoint as you describe. In reality, there is no waypoint n-1, just this ghost data. Select waypoint n-1, modify any of the L/G, ALT or CP/PD parameters and it will actually create the waypoint (and clear out the other parameters). Now you can insert waypoint n. For the scenario with the training mission, take n=03. As a side note, I think the Mirage's INS desperately needs fixing. Within my first few hours of playing around with this module I've already come across a 5 different bugs with the INS alone.