[CORRECT AS IS] Badly designed system integration.

[=4c=Nikola]

The fact I need to undesignate target to be able to slew AGM-65 is just stupid. It resets all sensors for no reason other than to prevent you confirming target destruction. A-10C has much more streamlined workflow, and additionally it automatically creates markpoint so you can easily snap back to it even if you lose TGP sight.

[Swift.]

Im sure Boeing read these forums for design suggestions

[dorianR666]

Im sure Boeing read these forums for design suggestions

dcs manual describes different behaviour than is in the game (page 185). doesnt sound like boeing caused this.

[=4c=Nikola]

They should read these forums.

[BarTzi]

Slew the TGP instead and designate a new target?

[MacEwan]

Slew the TGP instead and designate a new target?

 

I didn't think you could slew the TGP when the AGM-65 is selected

[=4c=Nikola]

Slew the TGP instead and designate a new target?

 

Will try, but MAVs really struggle to snap onto a designated target without a little bit of nudging.

[Shimmergloom667]

I didn't think you could slew the TGP when the AGM-65 is selected

 

You absolutely can. MAV takes priority for FOV change on Hotas, though.

[FoxxyTrotty]

you can slew the TGP - you just need to "sensor select" the side of the cockpit you have TGP on and/or Mav (back and forth).

 

It does work, you don't need to totally undesignate, and I agree with you and look forward to the markpoints - the A10c has a much better "workflow" when it comes to blowing stuff up

[GrEaSeLiTeNiN]

My friend who flew both F-16s and F-15s said the F-16 logic (hotas) is more intuitive and easier to get reacquainted with than Boeing's.

[MacEwan]

You absolutely can. MAV takes priority for FOV change on Hotas, though.

 

Ah yes thank you, that's what I was thinking of.

[Noluck]

You absolutely can. MAV takes priority for FOV change on Hotas, though.

 

Prior to latest OB, it depended on which DDI the SOI was located. Either the MAV or TPOD/FLIR. The "RAID/FLIR FOV select button" affected that SOI selected display. Now it only affects the MAV, no matter the SOI. I do not think this is correct.

 

Why would the NATOPS call the button on the throttle as mentioned in quotes above? Now I have to take my hands off of HOTAS and and manually press an OSB to change the FLIR FOV? Makes no sense and I believe it is now in error?

 

---

[rob10]

Prior to latest OB, it depended on which DDI the SOI was located. Either the MAV or TPOD/FLIR. The "RAID/FLIR FOV select button" affected that SOI selected display. Now it only affects the MAV, no matter the SOI. I do not think this is correct.

 

Why would the NATOPS call the button on the throttle as mentioned in quotes above? Now I have to take my hands off of HOTAS and and manually press an OSB to change the FLIR FOV? Makes no sense and I believe it is now in error?

 

---

 

 

The FOV switch only affecting MAV when MAV is on a DDI change was made a bunch of OB updates ago (not in the last one). It's been confirmed multiple times since then that it is correct behaviour.

[Bunny Clark]

I rarely have any trouble with this, usually the Mav's gate closes by itself without a problem shortly after it is within range. You can uncage the Mav seeker, switch TDC back to the FLIR, and then slew both around together using the FLIR. Once the TD passes close enough to an object, the Mav will automatically lock on and track. Honestly, I prefer this control system over the A-10, it's simpler and fewer buttons presses. It's super easy to get 4 Mavs off in a single pass very quickly using the FLIR in the Hornet. When using the Mav slaved to the FLIR, it is actually advantageous to be able to toggle the Mav FOV without needing to switch my TDC away from the FLIR page.

 

Prior to latest OB, it depended on which DDI the SOI was located. Either the MAV or TPOD/FLIR. The "RAID/FLIR FOV select button" affected that SOI selected display. Now it only affects the MAV, no matter the SOI. I do not think this is correct.

 

Why would the NATOPS call the button on the throttle as mentioned in quotes above? Now I have to take my hands off of HOTAS and and manually press an OSB to change the FLIR FOV? Makes no sense and I believe it is now in error?

It's definitely worked this way for longer than just the last OB. It works that way on current Stable, and I'm pretty sure it did on Stable before that as well. Mavs only take control of the FOV button when they're selected as the active weapon, so most of the time the button works on the FLIR pod as advertised, even when you have a Mav onboard.

 

I also find poking buttons on the MFDs to be pretty simple and easy. I have Cougar MFDs to make it easier for me playing DCS, but it stands to reason if it's pretty easy for me to poke a button on my MFDs it's probably easier for a pilot to do it in the real jet.

[hein22]

There are dozens of things you guys see in the DCS Hornet that are not the way the real thing works. Some are due to incomplete systems modeling and will make much more sense later in early access (like tons of HOTAS commands), some others are due to ED's misinterpretation of documents that were later corrected after a user pointed it out (JDAM logic, TGP features, etc). I strongly suspect that the whole sensors + TGT logic is wrong and that ED needs to re read the available docs. There is no way any airforce would pay more than 10 dollars to have the systems logic that the DCS Hornet has, no one would have approved that.

[Aspen_]

Be the change you want to see in the sim then. Back it up and show some documentation its wrong if you're so sure

[hein22]

Be the change you want to see in the sim then. Back it up and show some documentation its wrong if you're so sure

 

I wish I can, aspen. Welcome to the forums.

[Sting57]

I refuse to believe the US Navy and Boeing would put pilots into combat with the current implementation.

[hotrod525]

I refuse to believe the US Navy and Boeing would put pilots into combat with the current implementation.

 

 

You would be surprised to learn their is plentyfull of situation armed forces can put you in with bad gears :megalol:

[G.J.S]

Im sure Boeing read these forums for design suggestions

 

:megalol::thumbup:

[LastRifleRound]

The HOTAS functions aren't all currently implemented. There are many great commands available and ED is waiting to have all the pages and modes done before they implement (Like AZ/EL page, which many HOTAS commands interact with). It's not as intuitive in my opinion as the A10, but the A10 is the newest of the modeled HOTAS implementations and the one I have the most experience with by far. I remember on Jello's podcast an interviewed A10 pilot said they took feedback from Viper and Hornet pilots to see what they liked and didn't like with their HOTAS and made modifications.

 

As for the MAVF FOV, it's a little clumsy, but Hornets rarely employ MAVF and the MAVE implementation is outstanding. It's so easy to engage with laser guided munitions in the Hornet.

 

The MAVF workflow, being able to initiate track without having to change SOI is pretty great. You can still use the digital zoom if needed on the FLIR page.

 

In my opinion, the Hornet and Harrier HOTAS make more assumptions of what you want to do with certain pages open, whereas the Viper/A10 went with a more universal workflow. I find the Hornet implementation is great for the most often used processes, with less bouncing SOI around to do what you need to get done.

[oldcrusty]

I rarely have any trouble with this, usually the Mav's gate closes by itself without a problem shortly after it is within range. You can uncage the Mav seeker, switch TDC back to the FLIR, and then slew both around together using the FLIR. Once the TD passes close enough to an object, the Mav will automatically lock on and track. Honestly, I prefer this control system over the A-10, it's simpler and fewer buttons presses. It's super easy to get 4 Mavs off in a single pass very quickly using the FLIR in the Hornet. When using the Mav slaved to the FLIR, it is actually advantageous to be able to toggle the Mav FOV without needing to switch my TDC away from the FLIR page.

 

 

It's definitely worked this way for longer than just the last OB. It works that way on current Stable, and I'm pretty sure it did on Stable before that as well. Mavs only take control of the FOV button when they're selected as the active weapon, so most of the time the button works on the FLIR pod as advertised, even when you have a Mav onboard.

 

I also find poking buttons on the MFDs to be pretty simple and easy. I have Cougar MFDs to make it easier for me playing DCS, but it stands to reason if it's pretty easy for me to poke a button on my MFDs it's probably easier for a pilot to do it in the real jet.

 

That's pretty much what I do. Changing to narrow FOV when at max range helps with Mav seeker lock. When in close, he narrow view is not available.

 

One thing I noticed when uncaging the MAVF ahead of FLIR designation, you have to have master arm on in order to uncage the missile. Powering up by boxing the Mav on the stores page is not enough:noexpression:

[Mars Exulte]

I refuse to believe the US Navy and Boeing would put pilots into combat with the current implementation.

 

You must not have spent much time reading about the history of military aviation...

[Shimmergloom667]

You must not have spent much time reading about the history of military aviation...

 

Sounds like he didnt spend time in any military, ever, tbh :D

[Sting57]

Wrong on both accounts.

 

Not sure why you guys feel the need to personally attack me, strange community this one, says more about you then me I guess.

 

There is definitely something wrong/missing with the current implementation on the targeting system.