Shimmergloom667

It's implemented for ages now, but was somewhat buggy a long while. It's working pretty perfectly nowadays, though, including the AACQ cue, that has been added a while ago.

And it will automatically turn off with the APU turning off, later.

Also that would be an excellent time to look at the Mission Editor. Setting up a refuel training takes all of 5 minutes.

"Dark aspect", lol, calm down. Your TGP is in ATRK or PTRK, which are both modes that are not slewable. What you CAN slew in those modes is the offset cursor (your small crosshair). Make sure to be in standard inertial track (OPR) and you can slew. As per Wags' videos: https://www.youtube.com/watch?v=xvzxfqymFq0 and https://www.youtube.com/watch?v=Cr7--PXczpM Nothing in that is weird, nor is it weird that stuff changes during development. Hate to be that guy, but: things will change during Early Access (and this got implemented *6 months* ago) Also: my F-mavs still work as usual. Bring up MAV display, assign TDC to Mav display, uncage, slew, fire. Do you have ANY mods installed? Remove, repair, try again.

IIRC laser designator range in DCS is hardcoded to 8nm, so at Angels 30 your slant range indeed might have been to high

Afaik 20 degree bank until 20 degrees off carrier heading, then reverse is correct

He means Jf-17s

Wait, you are seriously whining about your spending money because one type of ordnance isn't displayed correctly in a 3rd party program? Wow. Whenever I thought the entitlement issues of DCS players has reached a limit someone easily knocks down that goalpost.

It is the Acquisition Point Cue: the ACQ Point cue indicates the highest priority MSI trackfile if the HAFU for that track is not currently displayed (e.g. it is not the L&S or DT2). This cue will indicate the acquisition point if AACQ is commanded at that instant. This cue also represents where the L&S target will step to if the Undesignate button is depressed. Slewing the TDC cursor over the ACQ Point cue will remove the cue in favor of a HAFU if the LTWS option is selected. The ACQ Point cue is also removed when the cursor is positioned over any MSI trackfile. The ACQ Point cue is not displayed when a higher priority target is already displayed (typically the L&S or DT2).

It's called "Push to test switch" in the controls (just mouse over whatever control you want to get it's name). You can't bind it to an axis, though.

Deactivate the timescale filter

You need two sources of information together to form a hostile contact, unless you set it to hostile through PPLI. So for you alone: negative IFF response (which only ever is "unknown" by itself) and NCTR combined (NCTR only works in STT). Or offboard donors.

Nice, you are suggesting for them to code a better re-arm, menu - I like that ;)

But we have other stuff that is not used by USN / USMC. Why remove this, specifically? Like I said, my Fin or Aussie Hornet may want green bombs and you can pry them from my cold, dead hands. :P

But V1 / V3 and V2 / V4 are different weapons IRL (V1 / V2 being regular without and with thermal coating, V3 / V4 being penetrator without and with thermal coating). So why should they be removed ingame? Even if they as of this point have the same effect on targets, that might well change in the future with updated damage models so we might actually have to use one over the others. Or is it you only want to have the ones without coating removed? But why? Because not being used by USN / USMC? Fair enough, but between our spanish LITENING interface and other items, I don't see that as an issue. Hey, someone may be flying an Australian Hornet with regular old green bombs.

Thanks for confirming that work is ongoing, I'll keep my fingers crossed! :)

Hey @BIGNEWY , I hope you are doing well! Do you think you could ask the team how far along they are in adding the relevant MJU-8 flares for the Hornet, so we can arrive at the correct space requirements and thusly being able to load a 60/60 chaff/flare loadout? You confirmed that this change would come in this thread (from 2019): https://forums.eagle.ru/forum/englis...18-flare-count This thread here goes into the matter as well (and there are still more): https://forums.eagle.ru/forum/englis...haff-and-flare The last official reply on this matter is over a year ago and this seems like a change that would not be too extensive, honestly, so I'd highly welcome some update! Thanks a lot! :)

Negative. After either full align or std hdg you have to then enter IFA, which is the coupled INS/GPS mode of the Hornet. If you pick NAV it's INS only. Either way: after aligning set IFA and you are good to go (with mission in GPS era, obvsly)

It is the Acquisition Point Cue: the ACQ Point cue indicates the highest priority MSI trackfile if the HAFU for that track is not currently displayed (e.g. it is not the L&S or DT2). This cue will indicate the acquisition point if AACQ is commanded at that instant. This cue also represents where the L&S target will step to if the Undesignate button is depressed. Slewing the TDC cursor over the ACQ Point cue will remove the cue in favor of a HAFU if the LTWS option is selected. The ACQ Point cue is also removed when the cursor is positioned over any MSI trackfile. The ACQ Point cue is not displayed when a higher priority target is already displayed (typically the L&S or DT2).

That sounds like a not too compicated addition that would be fantastic for me as a mission maker! Definitely second that!

No big loss if they do :D Basically just ranting in reply to that guy talking about BMS' heritage earlier. Yes, it has a long heritage. Doesn't help when it's hopelessly outdated. Anyway, enough with that and back to DCS. :)

Yeah, I cannot, for very specifically I can't invert an important axis and buttons that are just in the right place to emulate the necessary functions of a real F-16 can't be used due to that old-ass Direct Input limitation. And come on, who was talking about BMS arriving at DX11 at a proper time? DX 11 got released 11 years ago, all that stuff is just hopelessly outdated and there's only so much longer that the Falcon codebase of BMS can be supported into the future.

Less than that, but that doesn't help me really: my stick has over 32, my throttle has over 50 buttons, and too many axis. Since BMS still uses Direct Input, the game wont natively recognize all of them. Unfortunately, that means that I simply cannot use some of my buttons without 3rd party software to remap shit (for example the 4-way-plus-press that is in the position to emulate the TMS on an F-16 stick is partly above the 32 limit, so a few of it's presses are not recognized), and this is even worse once you start taking the axis into account.

Wake me up whenever they move from Direct Input and we can natively use modern controllers with more that 32 buttons.

Well, according to one of Wags' last update news we will finally get grid entry for the Hornet with the next patch. That will make my squad's human JTAC / FAC(a) duties that much better and work with the MGRS coords of the AI JTAC