wernst

Exactly. Distance information to the field either from DME receiver or from INS NAV is a MUST. If DCS Mirage doesn’t show DME from ILS station but NAV distance only - fine. But the distance display should always stay on the HUD, especially during the final stage of an ILS approach. The waypoint display (distance, number) should not disappear from the HUD when the gear goes down, being then displayed on the HIS and INS only. Why? It doesn’t make sense at all. Distance to the field is always critical in an ILS approach. Height is redundant when being well on the glide slope; approach course is secured when following the CDI. Display of SLOPE, CDI - AND . . . DISTANCE enable a safe ILS landing in the fog.

It's o.k. with me, just want to be sure that I haven't overseen anything.

Now I know what „snap“ means and how snapping works. It’s easier than I thought. But “airport landing snapping” works for entering a landing airport in the mission editor only, or? This remains the question: How to enter a landing airport to the INS? Of course, I can enter the coordinates of the airport as WYPT to the INS. Fine. But how can I tell the INS computer that this WYPT is for landing? Only when the WYPT has been defined as "landing" the synthetic RWY overlay appears on the HUD, or?

Learning to understand wording (from a German) may not be easy, but please read carefully or try to understand the sense of an expression in the whole context. “Is the HUD obsolete” was not at all an “aggro comment based on my apparent exasperation”. No "aggro", it was a rhetoric question. Of course the HUD isn’t obsolete, the full opposite is true. To shorten this story. Why do you think many of the ILS stations with CAT II or CAT III have an additional DME transmitter system? It’s for the pilot to receive distance information during landing in IFR conditions. Being on the glide slope, watching the CDI are important guidance for ILS landings. But knowing the distance to touch down is equally important: Knowing how many "time" I have for last corrections before the RWY appears in the fog. . . . .says a real PPL pilot with IFR licence (expired)

well, folks, my question here is not whether the pilot should be looking at the HUD or better trust the “head down instruments” only. My question is: Which sense does it make that the waypoint info (distance, number) on the HUD disappears when the gear is extended? When gear down I should not trust the HUD display anymore? If so, then for what is the HUD for? What about combat, ILS landing . . .? Is HUD of help or is it lying? Is the HUD obsolete?? I assume that the HUD shows the same information in digital format what sensors have measured. The sensors give the same information to the HUD as to the head down instruments.

thanks, Maulkin, last WPT has to be set to the center of the RWY and to be defined as "landing".

Why does the waypoint information on the HUD (distance, number) disappears when extending the landing gear? Distance to the field is important especially when landing.

in ILS landing mode the synthetic RWY overly on the HUD is missing. The normal CDI display is ok. In the mission editor I have set the last INS waypoint as to the beginning of the RWY. I have followed exactly chucks guide and the detailed youtube tutorial of "creative fun". Am I missing anything?

Is it possible to have the Normandy map available as separate image file e.g. for printout? It would ease the off line flight planning without mission editor.

oouuch, that simple. Thanks. Pls don't tell it.

Su-27 in world 2.0 alpha after arriving at parking position wheel brakes are applied for full stop. (key: "wheel brakes ON") But afterwards (engine still running) release of brakes isn't possible. The brakes even hold full afterburner power, the bird doesn't move forward.

Thanks, bbrz, you're right. Taxiing too close behind the AI when getting near (not even reaching) the RWY holding point blocks the AI from taking off. After AI is airborn you may follow. No formation take off of player with an AI is possible. A pity, but no real issue.

Neither the AI nor my A-10C could get to the RWY holding point. I let the AI A-10C being no 1 taxiing to the RWY. I followed behind with my A-10C as soon as the AI began to move. The distance to the AI taxiing ahead was not less than 15 m. The AI stopped taxiing about 50 - 100 m from the RWY holding point. Why? I could understand a stop at the holding point (e.g. take off clearance) but I wonder why the AI stopped long before getting there - and didn't move further.

Thanks, Matador, starting from ramp (nearby parking position) together and behind the AI was the first try. No success. The AI (A-10C) began taxiing from ramp towards the runway, I followed behind. Fine. But because of unknown reasons the AI stopped about 100 m before the runway and didn't move on. I waited more than 5 minutes and then I gave up. What blocked the AI from taking off? Do I have to set any trigger action for the AI? Which?

Sorry for my beginner's question. Up to now I was flying solo only (no combat) in order to train flying skills, e.g. with an A10C. Now I want to start flying in formation with an AI of same type. First step is taking off in formation, e.g. with one A-10C as AI. In the mission editor I set myself as “A10C - player - take off from runway” and the AI as “A10C - good - take off from runway”. But the scene doesn’t start, the mission editor appears only, I'm stuck here. What do I wrong? Programming formation flight in the air with one AI works fine.

Army slang: it’s when somebody says “Bravo Sierra” and it means “bullshit”. “Shitbird” - The guy in the unit everyone hates for making life harder on everyone. “cheesedick“ To do something with minimal effort. As in "He cheesedicked his way through it." “Ground Pounder” - A term used to describe a military member in the armed forces whose primary job is being an infantry member. “Wingnut” - A member of the US Air Force “FUBAR” - F***** Up Beyond All Repair: A description of many differing items and people “broke-dick” - A soldier with a medical condition that would hinder the soldier's ability to perform certain tasks You wanna learn more . . .? If you want to stick to perfect English why not run MS Flight Simulator. The Com here uses General Aviation Phraseology only. DCS is a combat simulator. In combat situations you wouldn’t use perfect Oxford English phrases while being in a situation where it’s just about saving your ass. You are working out stress when bragging with the power of words. Is it that difficult to understand? I consider these types of phrases during combat flight actions as true immersion into the f…. world of battle field.

Even as German I don’t have real issues to understand the basic sense of these teasing phrases. I assume they are a kind of military slang, meant to talk smack to you, working off stress. If one doesn’t understand the meaning it has no relevance at all for passing the campaign successfully. In short: Just ignore them. On the other hand I have some difficulties to correctly understand your phrases ”I'm cracking up at some of the phrases” or "it does slightly detract from the Immersion" but intuitively I’m guessing what is meant here.

In real flying at an ATC controlled airport you’ll NEVER get a taxi clearance INCLUDING entering the RWY. That is simply unrealistic because it’s max dangerous. A clearance “taxi to RWY XX” always means: taxi to RWY holding point only and hold there waiting for the next clearance. What if your taxiing is slow or you missed the right taxiway and you are arriving the RWY only 10 minutes later, entering the RWY while meanwhile another aircraft is approaching?

I'd wish that menu music is the only problem with this challenge. To me the Mustang engine sound is music I like. I've switched off menu music.

This video shows that passing this mission is possible. Fine. But is this really “one of the easiest mission”?! To me it’s a hard nut to teeth. Flying in dusk light, near to earth in a narrow and curvy valley, power lines on the side or across the valley, 35 minutes adrenaline pure. Don’t get me wrong, this kind of challenge is true fun. But is this an easy one? It challenges most of your flying skills, coordination, reaction, precision, system handling, all under time pressure. What can be more difficult? e.g. flying in a foggy night upside down under a low bridge with max speed in artillery fire. Mastering challenges is the nature of fun. If the mission is too easy it spoils the fun, if it is too difficult it’s frustration only.

o.k. - in the air PTT has to be used - which is, of course, used in real flight only, on the ground as well as in the air. I was assuming that the insert reads "F10 radio menu" it is the same com menu as used on the ground before. I'll try this and hope to get one step further. thanks, Dzen, for your patience.

Dzen, all DCS campaigns have challenges and they are all challenging campaigns. Flying (NOE) near of earth close to power lines in a curvy valley IS a big challenge, and mastering this challenge gives great fun. Your video was truly helpful. Meanwhile I have encountered another issue, which might be the reason why I'm stuck at WP3. When Beslan ATC asks to RESPOND over WP3 I am not able to switch to the main radio menu anymore. It was possible on the ground and at the RWY for take-off. But soon after take-off the main radio menu switch doesn't have any function. What goes wrong here?

Dzen, I wasn't asking for the level of skills (high, middle, low) I want to know which type of flying abilities are meant to be tested in this mission. The #1 mission was meant to test take-off, pattern flying, touch and go, landing skills. Which skills are meant with #2 mission? Flying NOE? Following the straight course line on the map? Following the river? I simply don't know for what I'm challenged here? Because there is no feed back how or why I failed the mission target.

Here is a summary of issues which I had so far with #2 “Airferry” first issue: engine coolant overheat before take-off manual start procedure (as done in #1 and "thousand" times before in other scenarios with no problem) when reaching the RWY coolant temp at red line, engine died soon after reason: unknown solution: CHEAT “auto start procedure” second issue: long wait or no ATC take-off clearance when at holding point RWY 27 reason: RWY holding point has not been simulated, trigger zone for ATC clearance is very close to RWY or even on the RWY solution: you may enter RWY without ATC clearance (!!) and you’ll immediately be cleared for take-off third issue: mission failed message at WP3 reason: has nothing to do with WP3 but with WP2 only, map and trigger zone do not match. If one overflies WP2 on course as shown on the kneeboard map you won’t touch the trigger zone. solution: Disregard the kneeboard map and overfly WP2 with take-off heading until the ATC confirms “outer maker” fourth issue: mission failed message after WP3 “deviation from course” reason: unkown solution: unknown I’m sorry, this mission #2 has not been designed well. On the one hand it mercifully allows cheating, disregards critical ATC clearance procedures and uses incorrect trigger points. On the other hand it tells you merciless “mission failed” but without telling and explaining, why and how. A precise briefing and a clear de-briefing is the basis of each Air-Force mission. For this campaign: Which flying skills are challenged? A clear briefing is needed, less story telling. What went wrong? A helpful de-briefing is needed. No learning curve means not to make any progress in this campaign. You are stuck. I wonder how many of you have passed this #2 mission?