Emmy

A-10Cs operate on a different DL and need a gateway asset (usually an AWACS) to play on the same network.

I reprogrammed my Buddy Fox A-10C UFC to cover probably 90% of the ICP functions. Works great!

I’m hoping the altimeters get right as well.

Thanks for clarifying... :thumbup:

Vipers and Hornets should, I think, be able to “talk.” For A-10Cs to play, I believe you need a gateway asset such as an AWACS. Right now, human-flown Hogs can’t see human-flown Hornets but Hogs can see AI Eagles and Vipers (and associated SPIs) on their TADs. Here’s hoping that eventually, we can all (at least) see each other!

Pretty sure DMS Right (on a Warthog Joystick) will turn it off and on.

Not every group uses the “Start Request” call... Over in the 476th, our ground ops do not require it.

Happier still if the sequenced strobes work as well.

Pave Penny Pod https://en.wikipedia.org/wiki/Pave_Penny

Exterior Lights, Too...

This won’t cure Mic Fright nor Selfishness. Those who can’t use a radio or won’t use a radio will not suddenly develop a gift of gab or a sense of teamwork.

We don’t pitch up 5° before rolling in: I’d roll in a hair sooner and make sure it’s an unloaded roll such that your velocity vector is on the target before you pull the nose down.

Not the worst effort I’ve ever seen... Keep at it!

IIRC, John Dibbs (one of the finest aviation photographers in the world) did most of the modern air to air imagery.

:thumbup:

AFAIK, its current state is a workaround and it will eventually not affect WPs as the system matures.

Correct... The red lines are 45, 30, 20 and 10 bottom to top and the yellow line denotes where the target should be when you tip in. and yes, AOD means that your actual longitudinal axis it pointing .2 miles beyond the target and nailing that comes with practice. Took me a while to figure out that you don’t want or need to put your axis directly on the target to get the proper dive angle and release.

I’d settle for seeing crew in the AI Forts...

The circles up each side...

Honestly, I don’t know. I’m really not one to sweat module development. If I have “gripes” they’re usually directed more at the overall sim experience vis a vis the core game (and the occasional “Yeah, you fixed B but you broke A, C and D”)

Are you asking about historical anecdotal operations or what constitutes a normal traffic pattern today? (Interesting diagram from Iwo. 30 to 50 feet on the “overhead?” Yikes!)

You’re asking ED to nerf one of their (for better or worse) core tenets and honestly, I don’t see that happening any time soon. I guess it’s better to have “X” and not need it than it is to need “X” and not have it? Personally, I prefer to learn all the nuts & bolts because then I can develop a flow for startup that works for me. For those who don’t want to get neck deep, there’s FCS and the upcoming MAC.

Can’t speak to the efficacy of running checklists covering every single real-world system (Lord knows I’ve skipped one or two from time to time) but as for operational realism, yes, I have flown A-10C missions of 3 to 3.5 hours and returned to base with the same ordinance I left with. We’re blessed with very talented mission makers in our group and sometimes the enemy just isn’t where they were initially reported, or you can’t reach them because they are under too dense an anti-air umbrella so you’ll need SEAD/DEAD help or red air moves in on the AO and you need to head to safety, or your lead/wingman gets zapped (requiring an RTB by regulation) So yes, there are groups that operate “by the book” and the fun lies in sharing an Op with your buddies and getting back Code 1.

Even stranger logic: An F/A-18 encountering a MiG-19 in combat...

The canopy rail and dust plugs in the canopy bow make handy references for dive angles... In rough terms: - On your canopy rail = 45° Dive - One dust plug up = 30° Dive - Two dust plugs up = 20° Dive - Three dust plugs = 10° Dive The above is applicable so long as your altitude and offset are correct for the desired delivery profile.