RSharpe

But.... Kate said: Basically, none of the 4 new features promised for last patch was delivered to any level of satisfaction.

This makes me wonder... Considering we now know that we got a Spanish Litening TGP, and ED have confirmed they have been using Spanish sources. Could this mean that this "no TGP symbology in the HUD based on our documentation" thing is not accurate to US Hornets armed with Litening?

I really don't understand why ED resists giving us the ability to read off lat-long coordinates from the Litening pod. It's one of the most important features of a FLIR pod to enable it to do FAC(A) properly... one of the primary roles of USMC F/A-18s. But I guess we have to accept it was never the goal to replicate USMC Hornets to begin with.

All of these things would be mean more work for ED. ED only uses the "accuracy" argument when it means less, good-enough work from them.

Sounds familiar. Considering Litening was only ever a stop-gap measure because ATFLIR was so far away, and a TGP was needed to make the Hornet useful, I wonder if ED now thinks the effort to get things right is beyond what they anticipated. It's clearly more difficult to implement than they bargained for.

I hope they're not going to come back and tell us that they have no documentation showing lat/long coordinates on the Litening pod. USMC use it as for FAC(A) on their F/A-18D, so I would find it unbelievable if there is no way for them to get coordinate readings from a target point to pass on to other jets.

Well, I think you can try using it, but it still flies you right into the water

I posted about this last June and got no response. Someone else posted a couple months later and it was acknowledged and I don't think it was ever fixed https://forums.eagle.ru/showthread.php?t=248542

Haha. It will be delivered as expected.... like everything DCS. Late, incomplete, and probably buggy A F

You guys have to remember that shipping is very hefty from Winwing. Remember that when looking at the prices. It's probably around $100-160 depending on your location in North America. Mine was on the high end.

A lot of people started with a TH Warthog HOTAS set. Although it was a good starter, over time wear-and-tear, and the need for greater precision and control lead many to upgrade the stick base to something like Virpil, which is directly compatible, allowing them to keep using the grip. But options for better throttles are few, and many are not ideal. The Warthog throttles were fine for a time, but they really need replacing for many. Few of us would abandon our stick setups since they're already really good. But many of us are desperately eager to upgrade the throttle.

I already have a good base and grip that I'm happy with, but I would really like to replace my Warthog throttle.

First of all, what exactly is the purpose of bringing the Hornet out of "early access" in 2020 when the module will not be feature complete, with many features being pushed off into 2021 and beyond in some sort of indefinite sustainment status? Just to redefine early access and full release, and revise the feature list? As a customer, I'm afraid that ED has moved the goalposts, re-written its promises, and cut off key features and putting them on indefinite life-support, with not plans to actually finish them. Unless the true goal is to to offer "Hornet 2.0" down the line so similar to A-10C 2 and Blackshark 3 in order that they can monetize us further in order to collect the resources necessary to finally finish the Hornet. I surely hope this is not the plan, and ED makes this a clear promise.

Welcome to the DCS game "pass-the-buck" between ED and third party devs.

Encountering this in multiplayer. CVN launch in a Hornet armed with 4 GBU-31(V)3/B. DCS client crashes immediately at time of first weapon release. Host edited the mission and removed the carrier and based the Hornet at land bases, and weapons releases of the GBU-31(V)3/B worked again. Track https://www.dropbox.com/s/kjcokpopiqcb6ln/Operation%20Hydra%20v1.3b%20NOMODS-20200307-222119.trk?dl=0 Log https://www.dropbox.com/s/romld9zsix50ao9/dcs.log-20200308-033314.zip?dl=0

How do I undo this? I run your .reg file, and now I can't get back into my fullscreen DCS after ALT-TABing. The game is still running, but but the display no longer updates the video.

So this hasn't actually been fixed?

Wait a second. Sensor Up and Sensor Down will slew the TGP up and down, but will not zoom in and out. What is the bindable command for zooming in and out? T6_Antenna axis works, but there's no equivalent button bind? EDIT: Never mind. The correct binding for zoom is FOV Increase/Decrease. As always, DCS binding names, confusing as hell.

Thanks for all of the info RedKite. Especially those laser guided rockets.

I'm OK with giving up pilot LANTIRN control if Jester turns out to work well. Looking forward to seeing how this will be implemented, and using it. The single player MP experience really needs Jester to work well.

However ED spins this, the fact is that the Viper has become the overwhelming priority, and the Hornet has been prioritized to the state of progress coming to a crawl. You say this "needs to happen", but did it? The explanation is that the two projects will feed each other, but from the customer's perspective, the Hornet is now the red headed stepchild (or perhaps a foster child after the cheque from Social Services has been cashed) that may eventually get the favoured child's hand-me-downs. The Viper received TWS and TGP slew to waypoints very quickly, while Hornet owners have waited months for both features. It doesn't feel like the two are getting equal treatment in a two way sharing relationship. It's Viper first all the way... and maybe new features eventually trickle down to the Hornet. EA buyer beware.

Still a problem with me. I am no longer able to get the autopilot to engage with the AP Ref button Sent from my ONEPLUS A6003 using Tapatalk

I really hope the player won't be giving up the same amount of control over the LANTIRN with Jester implementation. It would be very disappointing if a single-player plane would no longer be able to do the FAC (A) job because Jester just isn't flexible enough, AND the pilot controlled LANTIRN was disabled at the same time.

Have they ever acknowledged the issue? I've brought it up in the Discord server and the mods weren't even aware of this problem. This has been going on for a long time and it is surely eating into MP server and client resources and hurting everyone's performance.

Are all waypoints set by Jester broken, not just those designated on the F10 map? I've been trying to enter waypoints in manually through the Jester menu. In every case, Jester will only allow me to enter the first 5 digits. It won't allow me to enter the 6th digit, so instead of N 42 55 19, I would get N 42 55 1. Jester simply stops inputting after the 5th digit, and moves on. I think this is the same problem as the F10 map. Unfortunately, ED chose not to roll out a beta update this week, so I'm not sure if this has been internally addressed.