wilbur81

Got it. Thanks!

Hey, Bignewy and/or Nineline. Quick (annoying, I know) question: Were any changes made in today's patch to the Hornet's flight model, engine performance, parasitic drag, energy bleed, etc... or new atmospheric effects that would degrade turn performance? I'm probably imagining things, but just wanted to check for an official word.

Just out of curiosity, what specific flight model changes are you hoping to see?

No worries.

My air to air domination in the Hornet... and everything that Echo225 said above.

I'll be honest: Having fallen in love with the DCS Hornet, flight model changes at this stage make me nervous. I am all for getting closer to how the real Block 20 performs... and any steps in the direction of the Hornet's real life performance are a plus from my perspective. But it is going to be really hard to swallow if the flight model updates have a negative impact on the Hornet we've gotten used to over the past three years. Hopefully, all the anecdotal stuff from "Mover" and "Gonky" about the DCS Hornet being a little too draggy and too slow in acceleration are actually true. But we'll see. All this is to say: The current state of the Hornet FM in DCS has at least one fan in me. Here's to improvements that get the Hornet as close to reality as possible...and that that reality is HIGH PERFORMANCE. Keep up the awesome work, ED Team! This jet is out-of-control-amazing.

Agreed...that'd be a fascinating listen!

I wholeheartedly disagree with this statement.

+1,000,000,000,000,000

Watch the canopy!!

Very true...

Wags, SERIOUSLY! Watching this latest Hornet video... you and your team have created a MASTERPIECE! Well done!

I'd think so, but certainly if they could pull it off w/o a performance hit, that'd be amazing.

Nobody here wants the performance penalty of terrain rendering many, many miles out from your a/c. There have to be some compromises... and that's what we have with the current TGP, which is reasonable.

The Syria map is by far the most detailed map I own, but it isn't as well-optimized or polished as PG or Caucasus. I feel like ED's in-house maps (PG, NTTR, Caucasus, etc.) look more clean, sharp, and tidy. Syria looks a little rough around the edges in terms of textures, but many here have disagreed with my assessment. I'd still go for the Syria map over the Viper when you already own the Hornet, but that's just me.

Just take a screenshot of the info bar airspeed data on the jet in question in the f2 view and post it.

Agreed. As a full 4K res. user, I should (to Hawkeye's point) never spot a single F-16 at 18 miles away... But I SHOULD see him at 5 miles... assuming I'm looking at his sector of sky. The new spotting has made that closer range spotting more realistic at 4K... they probably just need to reign in the farther out stuff.

Agreed.

Does anyone know if, in the real BLK 20 Hornet, the AZ/EL page displays a NCTR print? It seems as of now that you only get the a/c ID on the AZ/EL page if it is already confirmed via some other friendly on Datalink. In other words, if I'm flying alone, with no AWACS or other Link 16 support, my SA page is the only Hornet display that will give me NCTR.

I'll try again as my first post was apparently deleted by Mods (I'll assume accidentally ;-)) In this track, all of the below items occurred at least once in the test mission provided: These are in no particular order: - AACQ (SMS right) failed to STT lock the '+' plus sign priority target - STEP button on SA page didn't automatically take me to STT aircraft I was locked to - Viper & Tomcat do not get a NCTR print - Radar got stuck in RST/BST multiple times, not allowing me to undesignate my STT or return to search - AZEL page did not display NCTR print when SA page did (maybe not a bug given some of the stranger real world Hornet interface properties?) NCTR Test.trk

I'm confused: this thread is now labeled "Correct as is" and has the additional comment of "30 degrees off nose or tail." In my track I'm literally about to put my nose up the Viper's tail pipe... and still no NCTR print. I'm literally dead-on nose-to-tail aspect.

Yeah, it seems like (possibly) the problem is associated with multiple 120C launches in the air. Again, this is a newer bug for me from one of the last two (I think) updates.

Certainly not for me. PG runs quite a bit smoother than Syria... but I only have a 1070 gpu and play at full 4K. Syria doesn't feel nearly as well optimized as ED's in house maps.

Understood. Happy New Year, Sir!

Thanks for testing, Flappie! I'm surprised that no one has brought this one up yet? Hopefully it will be looked at soon.