Gliptal

TOT is not how long you'll stay. It's the precise point in time you'll arrive.

The aircraft as it's modelled in DCS most probably does not have a relaxed stability.

Thanks everyone for the feedback!

It's mentioned that the strike aircraft will be coming at a medium altitude. That puts it above AAAs, but not SAMs. ID the targets and send the SEAD flight against the ones that are a threat to the F117. Basically destroy the SAMs. I intentionally left it a bit vague to add some decision making and uncertainty into the mission. In any case, the F117 should still complete the strike, since it barely enters the SAMs WEZs, although it will suffer damage (it never got destroyed in my tests). At any rate, if this does happen a message will pop up informing the player; if on the other hand all you see is a strike successfull message, you made the right choice.

Yes, you did that correclty then. You are just supposed to be acting as an AFAC, directing the other flights to their targets. You do have to send the SEAD flights to the right set of targets though.

Mine are quite different now.

I'm struggling a bit with landings. Granted, I can bring her down safely, but I never feel like I did a nice landing. Hence, here are a few questions: - Correct approach AoA is 14°: what is the correct landing AoA? - Should I flare? Up to what AoA? Or should I just cushion the sink rate without pitching? - After touchdown, the nose seems to have a mind of its own. I know I should aerobrake by keeping it up, but if I pull it skyrockets up and I end up scraping the nozzle; if I keep the stick centered, the nose falls down nearly immediately. - Related, what is the correct AoA for aerobraking?

Thank you!

I've been training with the radar and this thing is driving me mad. Everything was working fine, until I jettisoned some stores. Since then, a POL warning has been flashing on my HUD and I can't lock on targets, no matter what I do with the PCA. What am I missing here?

Latest update made the DIM position functional though.

Excellent. Was wondering because it is in contrast with the AP's BIT test behaviour.

Also, switching OFF the FBW BIT test after it has passed (green light) will make the light flicker momentarily, and then turn on again until the cover is closed. Expected behaviour?

Happening to me as well. Nevermind, the issue was with the loadout missing the left tank, although it is there in the editor. Had to delete it and create a new one for it to work.

Here are the three position abstraction for the two new radar binds. {down = 3109, up = 3109, cockpit_device_id = 11, value_down = -1, value_up = 0, name = _('PRF Selector Low, else Int'), category = _('3-Pos. Switch Abstractions')}, {down = 3109, up = 3109, cockpit_device_id = 11, value_down = 1, value_up = 0, name = _('PRF Selector High, else Int'), category = _('3-Pos. Switch Abstractions')}, {down = 3710, up = 3710, cockpit_device_id = 11, value_down = 0, value_up = 1, name = _('TDC Mode S, else Z'), category = _('3-Pos. Switch Abstractions')}, Feel free to add them to the OP and give them to the devs Riaxoxo.

Awesome work!

Nice.

Got it now. :doh:

No, I mean I'm an idiot since I forgot the landing gear down.

Nevermind, I'm an idiot.

I guess some logic was added, I don't see the WP cue, nor the WP number and distance on the HUD anymore.

I'm also having problems. Cutoff switch is closed, but the engine RPM won't go past 11% when advancing the throttle. EDIT: Nevermind, it seems like VENT now prevents startup.

http://forums.eagle.ru/showthread.php?t=166601

I just released a mission for that, if you're interested.

Moreover, they will probably want to push the Gazelle on stable before updating NTTR.

Nice! :thumbup: