Ziptie

When you land, your previous mark points still exist from the previous flight(s). When you land, you get a RECALC - which updates your "new home plate" - but doesn't clear your existing mark points. That being said, you can cycle all the way through the alphabet and once this happens - you will start to overwrite your existing mark points. Cheers, Ziptie

Yes, I fired the laser at least 100 time today doing numerous different tests. Works as normal. With the new update, 'latch' is enabled by default (found within the CNTL OSB setting of the TGP), but has zero effect on the laser firing - just whether you have to hold NWS or not. Double bind possibly? Check in the UI layer for a rogue binding, or possibly the general tab. Cheers, Ziptie

Wouldn't be the first time, unfortunately. It also won't be the last time either. Things slip through, and things happen - but I'm not sure how this could be missed, if it indeed isn't 'realistic' behavior - and most people find the target via FLIR, designate, TDC priority to maverick, confirm lock - weapon release (either twice to start firing laser and then fire missile or once after already firing the laser from the FLIR before switching TDC priority to the MAV). Odd indeed. For the record - I replied to your thread as well, in an attempt (possibly futile) to get more notice to this issue - which is quite a massive issue indeed. Cheers, Ziptie

18 was released much earlier than the 16 - while balance is important, the Hornet has been overdue for quite a long time. Be patient, as other Hornet drivers have been (or not so much sometimes), the Viper drivers will get some love soon enough. Cheers, Ziptie

Thank you for making it so the FLIR does not have to be cycled to OFF and then back to STBY after rearming/refueling (you can simply go wheels up, move the FLIR switch forward from STBY to ON and the FLIR is ready to go - no more waiting for a few minutes). Also, thank you for allowing the LTD/R switch to be in the ARM position, with the master arm switch still being in safe. A very simple thank you, for both of these changes (and the other features just released) Newest Open Beta version (released 11/18/2020 xxxxxxxxxx949) Cheers, Ziptie

I found the HUD designation to be simple, as well as the HMD designation - however I found that slewing that designation (via HUD or HMD) was incredibly sensitive and easily can go to 100nm out. Compared to the RDR ATTK TDC slew or the FLIR TDC slew, which is fluid and predictable. Just my .02, seems we have vastly different experiences. Using newest update/patch version of Open Beta (released 11/18/2020 xxxxxxxxx949) Cheers, Ziptie

In SP (self protect) mode, they will loft (apparently it is not considered lofting even though they climb in altitude upon release, my mistake). If you haven't used them in SP mode, you need to have EW repeated on HUD: 1. EW page on DDI, box HUD (now you can remove EW from being displayed on a DDI) 2. AG mode 3. HARM display on DDI 4. Ensure SP mode is boxed 5. RAID/FLIR/FOV will cycle RWR emission, indicated by emitter being 'boxed' on HUD display 6. Master ARM on 7. Call magnum and release weapon (watch it loft away) If you're lucky, the HARM will somehow get passed the incoming missile that is wanting to shoot it down more than the dog wants to attack the mail man. They can cover 30-40nm at FL300 with the aircraft being 0.80-1.0 mach, I've done it several times and even did it today with the most recent update/patch (released 11/18/2020 OB xxxxxxxxxx949). Cheers, Ziptie

I do not get these messages via text, when betty is barking at me. I have subtitles enabled as well, via the main menu options tab - so not sure why you are getting them.... Cheers, Ziptie

+1 A welcomed return for me. Cheers, Ziptie

+1 @Snoopy . I am experiencing the same behavior as you have listed, and also agree that this would and should be implemented. Cheers, Ziptie

Negative - I am building a cockpit for the A10C and one for the F/A-18C. Space is not an issue for me thankfully. A perk of being single and 'young' I suppose (for sure the first one). Cheers, Ziptie

+1 Feel free to close thread @BIGNEWY or @NineLine Thanks Eagle Dynamics! Cheers, ​​​​​​​Ziptie

Odd indeed. I tested today (with update released today, 11/18/2020) - and was able to successfully undesignate with no issues. Hope it is sorted for you as well. Cheers, Ziptie

What's ironic about the lack of ATC being displayed in the HMD - is it used to be permanently displayed in the HMD in the very early days of the Hornet. :megalol: +1 on the requests (really doesn't seem like this thread should be in the wish list section as they are items that are there in real life.......) Cheers, Ziptie

Video was helpful to see what you are talking about. Certainly seems like a bug to me. I realize why I haven't experienced the same issue you have shown here - because I only use program 1 and program 5, one of which is set to chaff on and the other which is set to flare only. This way when I press dispense switch forward it expends chaff, for radar threat evasion - and when I press aft on the dispense switch it expends flare, for IR threat evasion. Cheers, Ziptie

+1 Open Beta xxxxxxxxxxxxx949 (newest version released 11/18/2020) Cheers, Ziptie

+1 for the behavior of Maverick E not being able to fire - until SOI ('TDC priority') back to FLIR. Then the missile will be able to fire. Also a fresh thread started, regarding this very topic: https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-f-a-18c-hornet/bugs-aa/7144249-agm-65e-can-t-be-fired-with-mav-page-as-soi-in-certain-conditions Using Open Beta xxxxxxxxxx949, newest version (released 11/18/2020) Cheers, Ziptie

+1 for the TGP drift issue. It is resolved for me, by FLIR SOI, then 'bumping' the TDC slew (or changing to ATRK/PTRK), after TDC depress with HMD SOI. It is very similar to the 'issue' that the A10C experienced originally with slaving the TGP to the HMCS (which was fixed by ED with today's update). Cheers, Ziptie

100% can confirm this 'behavior' as well. Took me many steps to figure out what was impeding the missile from leaving the rail. What I am unsure of, is if this is 'realistic' behavior, or whether this is a bug. I don't recall this being how the laser maverick employment procedure was earlier, in early access stages for the Hornet (as in 6 months to a year ago). If MAV is SOI(TDC priority), the weapon will not fire even though it indicated MAV LKD (as it is x'd out). Take the exact same situation, and SOI to FLIR (TDC priority) and MAV LKD has the x'd out indication removed, and will accept the weapon release command immediately. Cheers, Ziptie

I just saw this today, watching a wingman streaming his sortie on Discord. Should be there for you as well. Cheers, Ziptie

:megalol: "Oh we're the wingmen and we ain't gotta clue" Good pull @Jonnie2Bad Cheers, ​​​​​​​Ziptie

Feel free to merge this thread with the newer one that has been labeled "feature request." I've had this one in here for so long that it was buried by the time others thought/realized this feature was missing from the A10C. buuuuuuuuuuump/merge Cheers, Ziptie

Referencing the bold above, does this mean you depressed NWS/undesignate? Sorry, just a bit confused by the following HSI/TGP, etc. I just used WYPTDSG multiple times today, along with TDC depress designation via HUD/TGP/AG RDR/RDR ATTK - and was able to successfully undesignate via NWS/undesignate without any issues like you or the OP are describing. Would be great to get this sorted for you and the OP, as it seems to be an isolated issue, and a frustrating one for the both of you at that.. Cheers, Ziptie

I apologize if this isn't actually a bug. So I used the SLAM for the first time today, doing so via the PP and TOO delivery methods. I noticed that after releasing a SLAM (from any station), that station stays selected and doesn't cycle to the next weapon station, like it does for every other store type used on the aircraft (excluding rockets from an individual pod). Instead it requires you to press the STEP OSB to bring up the next station for employment. I did not have the datalink pod on the aircraft, as I was not commanding terminal guidance of the weapon. Thought that maybe it wasn't cycling due to having the possibility of commanding terminal guidance via datalink pod - but wondered if it should automatically cycle to the next weapon station without the pod fitted to the airframe? Is this normal behavior, or is this a bug? I don't have a track file to provide, as I was flying for hours doing some testing of weapons and systems ahead of any additions with the upcoming patch/release. However this is an easily repeatable situation. Cheers, Ziptie

I will send an attachment tomorrow, a copy of the .lua that I've edited - and include the directory path that you want to place it so you can have that for ease if you'd like. If you would, feel free to list out exactly what countermeasure, and quantity / interval / repeat that you would like for each program and I can quickly make it for you - then you just place a copy of the file in a known location - so when an update/fix comes out (think there is even one scheduled for tomorrow) you can just copy and paste again so you don't have to do the work again or go back to having to adjust them each time you enter the aircraft. If you don't want it, no worries - it literally takes a matter of seconds for me to do - I never did anything resembling editing .lua files before I got into DCS, but the need has allowed me to learn. It's really pretty straight forward in my opinion. Some use JGSME (or whatever it's called) - but I find that this is just as easy to do it the "old school way." To each their own I suppose. But back to your OP - I don't get the same issue you outlined, I can land - rearm/refuel, and the program 1 and program 5 both stay as I had originally had upon entering the mission. If I recall correctly, and this was back when the Hornet was "new new" to DCS, there was a caveat to what programs are available to be commanded from the HOTAS - like having program 1 as the "active program" via the ALE-47 is one of the HOTAS commands, and the other will always be program 5. Forgive me if that wasn't entirely clear on what I was trying to say, but it's been a long day for me and trying to recall something from over a year ago that I watched/heard during on of Wags' original videos. Cheers, Ziptie