Airhunter

What was the OAT on that MP mission? Field elevation and DA?

Lift AND drag. Said vanes also sit way ahead of the CG and center of lift, which pretty much should deminish pitch rates as they are non-moving surfaces. To my understnding the glove vanes were intended for mostly supersonic maneuvering and more stability in that regime. Why they would be out during a 300-400KIAS regime, I honestly don't know. My only guess would be to negate some trim drag with the wings at 68.

There was an AFC for the 14A and B that allowed low RPM X-Bleed starts. Prior to that You have to advance the throttle to 87% RPM. So yes, either HB did not model said AFC or the physics behind it are simply all wrong and not implemented, even though it was common procedure on the boat. I have used said 87% technique and never gotten close to 18% RPM, however, was able to start successfully.

Yeah true lol. But even just spectating someone, your own missiles as well as seeing grey C's on an early and later IRIAF Tomcat is rather odd and breaks the overall immersion.

Hopefully the next "big" patch changes that. It's really important for the A models and general visual ID.

These are so good that HB really should include them officially for the Forrestal release.

I guess this is just a current bug with the Hornet's lookdown capability. Hornet has insane SA and if you have good radar mech (proper scan techniques) you should be picking up most low flying targets even in valleys if you are high enough. It becomes a geometry problem. Also, when actively scanning, avoid having the radar scan in one spot and at one elevation for say longer than 10 secods. Your MSI (datalink feed) is great but it also won't see absolutely everything and this is where your own radar scan becomes so much more important.

Yes, it will be put on the new API and HB are looking into making the 54C better than the A in some aspects as far as the game and its API allow.

That is a good point. Wings being swept back does indeed act differently aerodynamically speaking as it pretty much behaves like a delta wing at this point. Sadly there is no performance data with wings swept back (other than the one from flight tests which aren't anywhere public).Swept wings should technically also help with the wing loading and bending motion as the arm is simply shorter. One thing is for sure, with wings at 68 DEG you WILL bleed energy much faster at those speeds, resulting in a fast tightening turn radius and decreasing load factor, but more likely will also have more momentary lift at a higher AOA given the geometry. Nothing can be said for certain however without knowing the flow distribution or having any perf. data for that configuration really. But it is nontheless something one can consider when it comes to INST rates.

@maxsin72 I have actually discussed this and analysed this video with a buddy who is a fast jet pilot and we both agree that this pretty much matches the available charts (best case being 5k feet, 53k lbs GW and 4x4 loadout), if you ignore the unknown environmental variables. It in fact is more or less 23-25 (if you really want to be generous 30 DPS if you go out of your way and consider that the aircraft is clean, has low fuel and the DA is low as well as air being humid, helping with thrust). Whether you like it or not, this is what professionals had to say about it who udnerstand nose position, rate and BFM geometry. It's up to you to think that this is more INST rate than it is and that is fine, you have no frame of reference and believe that, just be aware that people on here will disagree with that. If anything is certain is that Snort was a hell of a pilot and knew how to demo the Tomcat, often times also ignoring the 6.5 G limit.

Impressive for sure. EDIT: After further review that is more like 23-25 DPS INST, which is roughly mathching the charts (estimated for SL). If anything it's 30 at most. We also dont know the DA for that video and it does look quite humid.

So much this. There are words being put in our mouths that were never even remotely said or implied.

Just to make a point on what is still missing and was advertised over a year ago to be included during the EA phase. Not to mention some outstanding bugs which are crucial for flight ops. No knock or shade thrown here just facts. What are the items planned for after Early Access release? • Ready Room • Air Boss Station (?) • Interactive LSO Controls like manual control of hook touch down location, hook to ramp height, wave off lights, and cut lights (partially implemented) • Plane directors to guide aircraft to catapults and off the landing area • Three additional ships of the sub-class (The new Stennis is still missing and is only mentioned on the product page) o CVN-75 Harry S. Truman • Rendered hangar deck (I guess this is in but not operational?) • Emergency barrier net (controlled for Air Boss station) • Deck crew (not static deck crew) that move to avoid collisions with aircraft • Deck crew glow sticks for night operations • Pilot animations like the salute and right hand on grab bar. And from the homepage: Combined Arms integration. "Burble" effect. Wave off and bolter return to pattern radio messages.

Our Viper still has HPRF which it shouldn't have in RWS and TWS as far as I'm aware. The radar is still a lot more believable and realistic now especially if you do some rough math with the radar range equation. It will also never be accurate to real life or precise in detection by 1-5nm increments. Even in real life these values are simulated and calculated as you wont have or know the exact RCS value of a contact you are picking up during testing. No one is going to go up and fly against a precisely 1sqm, 2sqm, and so on up until 100sqm target to build an exact detection table for those conditions. It is now mostly good enough as far as DCS goes, maybe even still a bit too good. But it's mostly in line with estimates, physical attributes and what some SME's say.

Make that a before.

With any STT it will simply look at the track and be active off the rail. Again, this is all for the A, the C might have very well had different functionality we dont know about. No reason it shouldn't given pretty much the same WGU as in the AMRAAM.

It should literally be Tomcat level.

Any proof for that? Might be related to the 54C if anything.

So is this in right now since that post is from August?

I'll send em your way tomorrow.

We do have those.

Excuse me but is someone disregarding the work? People were pretty happy with the continuous progress over the past year and more and no one was complaining. It's the simple fact that things have seemingly slowed down and moved over to the Viper. We understand that it all takes time but it would take less time if you didn't move people around all the time. I think 4 years of EA is more than enough time, especially considering that highly voted for items like the FM/FCS improvements and ACLS still weren't addressed. It's also pretty disrespectful to tell your customers "if early access is not your thing" after they have bought two EA modules and supported you over the years and have some legitimate concerns moving forward. Pretty sure your business model is built around early access and these practices will surely make old customers hesitant to buy into yet another early access project in the future. We saw it time and time again. So please spare us with this copy pasta, political answer and please do talk to the team / management instead and see if we can at least get a short term roadmap or status update on what is in the works right now. I saw the FM being mentioned in a past newsletter and stated that news on this front would follow shortly - since then pretty much radio silence. Because given the monthly patch-schedule there are what maybe 4 major patches left this year if all goes well?

Actions always speak louder than words, yes.

Agreed - there is still a lot of unfinished and simply missing stuff in the Hornet. When was the last time ED or Wags teased a new major Hornet feature or improvement? Quite a long time ago. There are now 3 months left in this year and given the current pace I don't really see how the Hornet is going to leave EA this year. In the same fashion of other devs why should customers of the Hornet who have been patient for many years now suffer because of a rushed and terrible Viper release and EA plan? The F16 peeps can now wait and that's not their or the user's fault.

Yup, the new API application will either make or break the Phoenix.