Nooch

If it's only a 1.5.7 issue then it shouldn't remain for too long as it will probably be fixed with the new Caucasus map.

It seems there are some issue with the current ILS system. Sometimes it behaves weirdly. Edit: I am only talking for 1.5.7 as I have not tested 2.1 yet.

I'm happy you finally made it as I can definitely understand your frustration. Be aware though that it wasn't your fault. The mission designers are here to blame because the A-10 does not use QFE.

I am talking about my own experience. That's all. I don't know what you find funny about it. :huh:

You mean this switch? If you did then that's correct, you need to unstow the steering bars. It's a tiny switch and it's quite easy to forget.

Funny thing is, that's what I did, most of the time. And I never ever had to use QFE. Always used QNH.

It also depends on which resolution you're intending to play at. If you're going for the 4k experience then a gtx 1080 would probably be the minimum.

I don't understand how QFE would be any useful in VFR since the runway should be visible and as you mentionned, altitudes are given in MSL on airdrome and regional charts. When flying IRL, I have never used QFE and the tower never gave me any QFE setting. That said, I only have 11 hours of flight under my belt as PIC so I'm not pretending I'm the guru of aviation either... :)

I would much rather have the Tiger than the Ka-27.

Actually I now recall that I did encounter the same problem. The FE told me I was off altitude but it got quickly fixed by setting the altimeter setting to 2889 I think it was. The QFE for your departure airport should be displayed at the bottom of your briefing window along with the frequencies. Hope this helps.

It is weird indeed... I did the same mission about a week ago and nothing went wrong like that so I don't understand why you're having this problem.

Please report.

That's right, the FE is quite unpredictable in these missions. Sometimes he gives you warnings at the appropriate time and sometimes not.

That's what I suspected... Why make it simple and standardized after all...? :D

To succeed the mission you need to stay aligned with the flight plan on your TAD. With the crosswind, your nose will deviate and the FE will start yelling at you but feel free to just ignore him. As far as speed is concerned, it's totally normal if you fail when you go 20 kts above the requested speed. 20 kts is a lot in professional aviation standards. You won't even pass your CPL if you go 280 when the FE asks for 260. Try to stay within 10 kts of the target speed.

It's pretty simple. If you are under 10k feet you use QNH (or QFE in some rare cases). If you go above 10k feet you switch to QNE. Please correct me if I'm wrong but as far as I know, this is how it works.

That's exactly right. I've seen a video where they had refueled a F-18, Rafale, Typhoon and Harrier all in one flight.

Gorgeous pics! :thumbup:

It's nice to see a new addition to the AI lineup. It would also be great to see ED add the drogue adaptator to the KC-135 as they are currently used on a regular basis to refuel coalition fighters in the middle east.

The A-10C isn't necessarily more realistic than the others. It just has a different set of capabilities.

Weird... The sun isn't shining bright in my rift. I have shadows turned off, I don't know if it makes a difference.

My guess is that QFE is only used when performing IFR landings. Is this correct?

Generally speaking you really don't have to worry about it. The course information is already programmed in your CDU as it links waypoints together. 95% of the time, you don't have to touch the course set knob of your HSI. It's only there in case you decided you want to arrive at waypoint with a specific heading. The mission tells you to turn the course knob just so that you learn something about the HSI but it's not something you are required to do in practice.

The rockets running time is already pretty good. It's more a matter of giving enough punch but you can't give too much of it either because it could hurt the pilot. I've seen several successful ejections where the pilot ejected right before hitting the ground and while the plane was diving. The big problem is that it is actually pretty easy to forget you have an ejection seat. The ground is coming at you fast and you're suddenly dedicating 100% of your attention to pull out of the dive... Sometimes it's obvious you're not gonna make it and thus you pull the ejection lever. Other times it's a close call, a matter of meters, and you think you're gonna make it when in fact you won't. Anyway, whatever the cause of the incident may be, it's a very sad event. R.I.P to Captain Gabriele Orlandi and my condolences to his family and friends.

There is currently an issue with the Num5 key. It will always keep recentering the view no matter what, even if you bind it to something else. I reassigned Num5 to keypad 5 on the Warthog's CDU and in addition to pressing CDU keypad 5, the view gets recentered. I tried with the Ka-50, same problem. It looks like the issue isn't module specific. Also please note that I fly in VR. The problem might not be present in non VR mode.