Coyle

Not a bug, as the Cage/Uncage button should invoke another function in the ATFLIR that we are unlikely to get. Being vague on purpose, sorry. But yep, gotta hit the LST button on the DDI.

Hello! with the new hornet model coming up, I would like to request two feature requests that can be user select-able settings (and synced in multiplayer), sort of like the Viper with the canopy bubble tint setting. The first would be the color of the flight suit. I believe it's quite common that USN pilots will wear a more brown/tan suit when operating in desert environments, and we now have four maps such a suit would be appropriate in. The other option I would love to see would be having a remodel of the old mask we currently have. The new mask shown in the recent newsletter is a good change as it's probably long been the new 'standard issue', but it has been stated that it was rather uncomfortable to wear. USN pilots were allowed to source and wear the older masks as long as they maintained them properly. I think both options would add a bit of flair when looking at the pit. Thanks!

ATC holds true air speed, not what's in the HUD. It's working as intended.

With the way TOO works now, a designation must be made each time for each weapon prior to launch. Weapon swaps will not automatically pick up a prior designation. This is so that the coordinates are saved and are not overwritten with out positive action.

This thread is meant to be in response to NineLine for added multiplayer functionalities. I will only offer a couple of suggestions, if anyone else has further ideas please feel free to post. AI Communications. While I can appreciate that a significant amount of work has been done on the Super Carrier module in terms of AI comms, sometimes they can be quite a bit lacking. In a multiplayer setting where many different scenarios may want to flown, herding 20 people into a marshal stack is not always the prettiest or fastest method when it comes to dealing with the AI. When playing with a human Marshal/Airboss/LSO, things can often be conveyed or custom tailored to any situation that arises much more rapidly over voice. It is for this reason I request that you allow us to bypass all AI communications and potentially all marshaling instructions such that we may fly our own marshal stacks, but still have basic ACLS guidance. The simplest method I can think of is adding another radio option that'll just 'check in' the jet on the back-end to the carrier but with out prompting AI communications, thus all the things that need to happen will happen, just with out having to deal with the AI. Another suggestion might be to have a "Toggle on/off AI communication" switch in the upcoming Airboss station. Prior to the ACLS update when we do this in our group with out checking in with the AI the only issue we have is that the carrier lights do not toggle for the event, requiring at least one person to radio in the carrier (usually the last person in our custom stack). This puts the burden on only one person to turn on the lights, as anyone ahead them will have the deck set to proper conditions. Since it appears that everyone would have to radio in to get any ACLS functionality, an example of how it'll probably end up going is: 1. You will radio in with a human marshal 2. Switch to a different AI frequency so that things don't step on each other 3. Call up the AI while making sure you're not stepping on some one else who is currently in the process of doing so (the AI might choke and ignore multiple people calling in) 4, 5, 6... Switch back and forth for any further human/AI interactions. Commencing, platform... etc. This can quickly become tedious over time as people fight to get into position and make their commence times while dealing with duplicate agencies... Being able to forgo the AI but still check in to receive ACLS would be very convenient. Other manned stations functionality. We are still unsure of what exactly we will be able to manually take control of while manning some of the stations on the carrier, so I will offer some suggestions. -Having the ability to add/remove/sort jets to a custom marshal stack with or without AI comms. This would give us the option us using external comms but also giving hornet pilots in-game T/C Link4 data. -Allowing the Airboss to broadcast over 5MC Could be helpful in some situations as well, perhaps via the in-game radios ED is working on? Allowing the LSOs to set the eye-to-hook function To better facilitate F-14,F/A-18C,upcoming F-4 landings, etc. Any/all carrier features that could be used in a big multiplayer setting would be a very welcome additions to DCS for those of us that practice navy missions.

Moving designation stops updating the moment TDC is taken away from the ATFLIR for any reason, and continues updating when the TDC is brought back to to ATFLIR. So yes that means if you TDC to a weapon or to the SA page, HUD etc., you've stopped the track... meaning your weapon now has stationary only data. MAV E will be the least affected weapon caused by this bug.

It absolutely does, and I would not trust a single hornet pilot that has not flown our exact model with all of the improvements it has revived over the years to make definitive statements like it's too draggy or too powerful. The engines are the massive change here obviously, but did you know the hornet has gotten several hundred pounds lighter due to internal electronics upgrades? There are many variables at play that most are not privy too, and even now ED has Apache pilots disagreeing with each other over certain things. Trust only the book numbers which, surprise, none of us have access to. Those pilots who have only flown much earlier models of the hornet have opinions that are quite frankly, as irrelevant as my own in how this hornet should handle towards the higher end of its flight envelop.

Yes, in the context of our DCS hornet that has not a shred of actual MSI implemented it is a little more odd. However the feature works as intended all the same. NWS with TDC on the radar even if the page isn't up should, as in the video: invoke L&S step onto valid tracks.

Seems fine to me. https://youtu.be/KEKDSTgDR2M?t=903 Gets an L&S after landing, as you can see in the HUD repeater. Don't need radar contribution to L&S a MSI trackfile.

Disregard.

Hornet does not have towed decoy, unless you're thinking GEN-X which was removed, but is still not a towed decoy. Only the Rhinos fielded towed decoy. Viper getting VS is suspect though, since the hornet will not. At any rate... I would like to see an updated roadmap for the hornet that should also shed some clarification on a lot of other things the hornet should have but have had little/no discussion about dev wise.

When you consider the alternative was simply not having any magical symbology approximating flight positioning in an attempt to maximize SA like it used to be prior to this kind of tech, yes, I'd very much so use such a system. It's good enough, and is better than having nothing. Pilots had have to make due with out it for so long.

I'd argue this doesn't need to be fixed since the ATFLIR offset feature as it is now is incorrect and has to be reworked.

43110421 43110253 Both of these are the same LAT, just converted... Which is which? The computer doesn't know exactly, both are valid "DMS" coordinates. Now let's do a bit of formatting... 43°11.0421' 43°11'02.53" The point being, your LONG could have been within bounds of looking like DMS, but your LAT was not. In any case had you punched in an entire coordinate block in degrees minutes that was within bounds, the bomb would have missed anyways.

JDAMs/JSOWs etc can only accept degrees, minutes, seconds ( XX°XX'XX.XX" ). If you were attempting to copy a way point with out switching away from decimal minutes first (what the hornet defaults to ( XX°XX.XXXX' )) then you will have issues. You'll find that ability to switch in the A/C menu under the HSI DATA sub page.

In addition to this bug report The Radar BRAA will display inaccurate numbers based on radar scales. Going to the SA page and setting a step on top the target and changing SA page scales along with de-centering will also give wildly inaccurate bullseye numbers. If all of this is correct, how are we meant to communicate reasonable distances and azimuths between flight members and GCI/AWACS when people could have different scales set up on their screens? BRAA_BULLS_MISSINFO.trk

Part of the reason is (I think) the coordinate block is smaller than it should be, that and it uses a different font compared to the rest of the text around the screen (Note the T and 3). Luckily most things can be modified to achieve a more genuine look.

I'll also post a track for this one since it has been bothering me as well for as far back as I can remember. Works perfectly in A/G, does not work in A/A. In A/G you can see me make deliberate circles around the island, in A/A I am unable to do the same. I only get movements when I have perfect input from only 1 axis at a time (mixed inputs makes it stop/stutter as you can see). I'm using the VKB MCG Ultimate, JOY_RZ for Horizontal Axis, and JOY_SLIDER1 on the Vertical Axis. tpg_axis.trk

I believe this has to do with the ATFLIR SCENE mode. For whatever reason, it does not want to let go of the designation when you try to undesignate from other systems (HSI/SA, Radar, HUD). Try switching out of SCENE first.

Should probably be in magnetic like everything else unless TRUE is selected in the HSI.

To add to this, punching in a GRID coordinate also sets the TGT to the grid numbers you used.

Are you able to expand on this? Under what conditions or steps were you able to bring out the capture box? Assuming we're talking about the same thing...

Currently, (and only with the ATFLIR) you can SCS long to directly enter AUTO mode from INR. I wonder if this is what would activate the expanding box mechanic that isn't implemented yet?

https://forums.eagle.ru/topic/258808-azel-cit-fov-limits/?do=findComment&comment=4541719

This is because ED choose to ignore or fail to implement proper HOTAS functionality for our jet. Mind you, it's a bit of a mixed bag on this one in particular. Now from what I've gathered recently: With a target designation set, hitting NWS only once should first clear the designation - this will not move the TGP. Follow up NWS commands should then reset the TGP causing it to cycle between VVSL and snowplow. Either that or the cage/un-cage will cycle those modes from what some one else told me. Regardless, I find it hard to believe that you'd have two separate buttons with redundant actions (instantly resetting the TGP) with out some steps or logic in-between them to differentiate some use cases. We all know the F/A-18 has its quirks here and there, but even this one seems a bit far-fetched.