bfr

Equally flying based on feel/"seat of your pants" IRL rather than looking at speed/alt gauges is probably much more doable because the seat of your pants is actually getting some feedback. And as you note, an awful lot of things in the cockpit are between quite and incredibly hard to read. I'm reminded of doing the cold start training mission and struggling to make out (even on full zoom) with certainty the markings of the position on the BIT dial on the RH console. Although i'll try an earlier suggestion someone made of sticking the console lighting on to see if it improves things.

Isn't it just pressing the ACM button on the radar page of whichever MFD you have it up on? This should toggle it back to RWS. Not sure if there is an equivalent way to do it via HOTAS mappings though.

Yes, the 18 can be "on rails" as you put it. Although I find it can also be like driving a big truck sometimes and other times like being a bee. So its rewarding when you can get the very best out of it. I definitely don't think it lacks character, its just where the extremes of its character lies that may not appeal to some. By comparison I had a love/hate thing with the SU27 in FC3 especially because sometimes it was an absolute joy to fly and then suddenly it'd basically be hellbent on killing you. Then you have the good old dependable SU-25 which is just looking for an excuse to kill you as soon as you try and push it.

You could well be right. As the panels froze then the only failure indicators available to tell me what was broke were the warning lights on the RH vertical panel.

Indeed! I expect its not a tough fix (i've flown planes in P3D/FSX that successfully factor in altitude to whether the pilot can breathe without oxygen systems available or not) but also probably just down near the bottom of priorities. On a similar note, the same flight I had the breathing on the ground issue i'd previously lost one of the generators to ground fire. The effect of this was all the MFDs and HUD totally froze (no buttons worked, the displays were stuck on what they showed at point of failure). No idea how realistic this is as I would've expected them just to go blank rather than fail in the manner that they did. Got down OK with a mix of the analogue backup instruments and the seat of my pants.

I wasn't aware of that. I shall have a look later. Cheers.

I suspect the whole obogs thing is a bit buggy anyway. I completed a mission the other day, landed in Dubai taxied off the runway and started sitting things down. After killing the engines and opening the canopy I switched the oxygen systems off. I then proceeded to start blacking out until I quickly turned the oxygen systems back on.

Also make sure you're not hitting responses whilst the JTAC is still talking. There's a point around the 9 line being read out where you can prematurely declare IP Inbound but it sends you down a dead end in terms of the radio interaction logic (the correct response doesn't come up on the list until it's finished talking and will never come up if you cut it off).

That's my experience of it too. The test scenario I had involved using a Predator as FAC and then flying in the rough direction of the target and releasing when I guesstimated it'd be about close enough for the bombs to reach. Run this same scenario numerous times now with all the GBU variants and my hit rate is pretty much 100%.

I'd agree. Whilst this ought to work OK with the setup I have currently (I haven't as yet tried it but in theory I should be OK), it does seem a bit mean to force a multi-press on everyone when they might not have the controller hardware to easily support it.

If you mean the Yas Marina circuit then it is in there now (I tried to land on part of it the other day :music_whistling:)

I tried it myself last night for kicks with GBU-16s, and observed the same as you that it almost works.