Shimmergloom667

Yes. Maverick page takes precedence over the FOV button as per real life.

Sure thing, super easy - as StevanJ says the probe light illuminates the basket nicely, and everything else you can manage well enough without seeing it.

What is your actual question there? Cloud base and visibility limits as per civilian air traffic doesn't really apply to military aircraft, and if it's a CASE I, II or III has very specific visibility limits. And yes: full flaps all the way in landings, as soon as you dirty up in all of your landings, no matter the CASE, also half flaps for takeoff, that is correct. And yes: in a CASE I waveoff or bolter you stay dirtied up with full flaps and re-enter the break, in a CASE III it is a bit more complex and sometimes you can be asked to retract flaps and/or gear to conserve fuel (to the best of my knowledge).

Always JHMCS, I see basically no need at all for NVGs in the Hornet

Even better, then there's hope to yet get a Rhino at some point and I was mistaken.

I want to replicate everything as close to RL as possible. So given that the F-18 doesn't have more controls on the stick, I don't map anything more (and the Countermeasures switch is unrealistic already, the Hornet has it on the throttle, which is why I removed it again, the picture is a bit older). In my F-16 and A-10, the "Gate/Cont"-labeled hat switch is being used as the TMS switch, so there I use it of course. You might to do it differently of course, but as TimRobertsen said: you will have to figure that out for yourself.

What exactly is your question? I just replicated the RL Hornet's buttons on my MCG Pro, with leftover buttons being a bonus. That's how I approach every bird with the MCG Pro.

That said: it's quite possible that this will never get implemented, which is a good thing. Get a grip, it's only some cursing. (also swearing is a sign of high intelligence: https://www.sciencealert.com/swearing-is-a-sign-of-more-intelligence-not-less-say-scientists )

Nope, I use it basically daily, w/o issues - is the carrier's ICLS set correctly in the mission?

IIRC, VRSim still has the exclusive rights from Boeing on the Rhino. But don't quote me on that.

I literally landed in a CASE3 with the squadron on ICLS 10 minutes ago. It's working flawlessly.

Ah of course, how could I forget??

And on what rigorous ingame testing and comparing to what is known to the public domain do you base this, oh sagely one?

9 times out of 10, whenever someone reports uncontrollable pitch up after takeoff, they are taking off with flaps in Auto. Don't do that, if you do. Flight = Flaps Auto Takeoff = Flaps Half Landing = Flaps Full

I didn't say it was HB's problem.

To be fair: then it's a bug that DCS allows the F-14 to put two AIM-7s in the front and to 54s in the back.

My pilot and me engaged 4 AI with AIM-54 at 50nm on Friday, taking out all of them (2 SU-24, 2 MiG-29) - afterwards 1 out of 2 Sparrows connected, and then 1 out of 2 Sidewinders. Same deal in a later flight. Can't really say something changed for us.

Playing on 34" 21:9 as well, I see no difference

I mean, whoever is not realizing that those Clouds are WIP probably didn't spend a minute looking at DCS so far, so - ok, I guess? Like Bignewy said, can't please everyone *shrug*

You literaly complained about them showing WIP stuff (here: clouds) because they are not included in the immediately following patch 6 posts further above. And then continue about "false advertising". That's a bit hyperbolic IMHO and I wanted to point out to Bignewy that not all people think so strictly as you seem to do. Not more. Not less.

Just to bring this out there: please keep showing stuff in progress, even if it is not coming in literally the next patch. I fully disagree to the person above me and would like to give you positive feedback on Wags' videos, just so it doesn't get swept under the rug by naysayers. Us guys that like how you do things are out here.

Had an extensive CAS evening Sunday, works like it always did for us... (10 players)

It is the Acquisition Point Cue: the ACQ Point cue indicates the highest priority MSI trackfile if the HAFU for that track is not currently displayed (e.g. it is not the L&S or DT2). This cue will indicate the acquisition point if AACQ is commanded at that instant. This cue also represents where the L&S target will step to if the Undesignate button is depressed. Slewing the TDC cursor over the ACQ Point cue will remove the cue in favor of a HAFU if the LTWS option is selected. The ACQ Point cue is also removed when the cursor is positioned over any MSI trackfile. The ACQ Point cue is not displayed when a higher priority target is already displayed (typically the L&S or DT2).

Which plan? F-18? I think you should ask that question in the F-18 bug subforum (as well).

Yes, thats how it works IRL. Mav takes precedence of the HOTAS FOV command.