escaner

With this week's update it seems fixed to me, thank's!

I remember some time ago someone also complaining that fuel would run out before landing. Maybe Belsimtek should consider adding 500 or 1,000 lb extra fuel, for some (foreign) people, it can take some time to understand the instructions.

"Hold short" is the instruction to stop taxiing before entering an intersection or runway. "Holding point" is where you "hold", normally marked with horizontal or vertical signs. Sometimes you can use either one. E.g.: - GND: XXXX, taxi to holding point of runway 31 by A, hold short of T - XXXX: Will taxi to holding point 31 by A and will hold short of T - XXXX: XXXX holding short of T - GND: XXXX, continue to holding point 31 - XXXX: continue, XXXX - XXXX: XXXX at holding point runway 31, ready for departure. or - XXXX: XXXX holding short runway 31, ready for departure - GND: XXXX, monitor tower 120.8 - XXXX: tower 120.8 good day, XXXX When you find either a red vertical sign or a pattern of lines with the countinuous ones on your side, the hold is compulsory until athorized. When the discontinuous are on your side, you can cross:

With the Viggen already in the open beta, I guess more work will be done in the Tomcat pretty soon. Is there any info on the current state of the F-14, or whether a release could be expected during this year or maybe 2018? Thank's a lot!

After starting the plane a few times, I must say that even needing many more pumps now, it is much quicker to pressurize with the new animation. BTW, where is that electrical pump that everybody talks about?

Good news, from the changelog, looks like it has been fixed: DCS 1.5.6.1648 Update 2017-02-03 DCS World ... Fixed bug that caused to AI wingmen not starting up in some missions ... https://forums.eagle.ru/showpost.php?p=3028651&postcount=44

It happens for other Spits different to own. AI or human Sent from my Redmi Note 4 using Tapatalk

I can confirm this one.

Thank you Belsimtek for adding the GBU-12 training mission. :thumbup: I think someone forgot to push the updated manual, because it still does not show there. :music_whistling: Now just missing the Snakeyes and the CBUs.

The relation between de altimeter readout and what the kollsman window displays is incorrect. E.g. for cold start mission in Beslan: * Beslan elevation: 1772 ft * QNH 771 mm Hg -> 1028 hPa Setting the altimeter for the airport elevation displays 1048 hPa in the kollsman window instead of 1028. See attached screenshot.

Eg. for Beslan it says 1772 m elevation and 9914 m runway length, but both figures are actually in ft.

If you don't pressurize the fuel system, the engine won't start. Just tried it both in 1.5.5 stable and 1.5.6 beta.

Yeah, and now you need to pump 20 times instead of 10... great.

LOL. As it was in capitals I though it would be an acronym. Thank's again. :)

Thank's! Do you guys remember what exactly "BIP" stands for?

It has both controls: differential brakes in the pedals for normal operation and a paddle brake in the stick for takeoff. BTW, they also added a Nose Gear Steering switch (LALT + Q). The switch flips in the left console, but I can't see any light indicating whether it is engaged or not.

BIP appear in the "Aterrissage" checklist in the real world Mirage manual (see attachment). What is is and what is its complete name in frech? Merci!

Back to the original topic, some airspeed indicators have a second scale for TAS. You calibrate by manually matching your pressure altitude with the outside air temperature using a knob in the instrument. Sent from my Redmi Note 4 using Tapatalk

Come on, guys, stop the OT. If you want to talk about the AoA indexer, start a new thread.

I haven't tried sidelisps in the DCS Spit, but what jcomm describes I have experienced in C152 and C172.

Look for a shop in the USA that sends by USPS First-Class Mail International or ask them to do so. It takes 2-3 weeks, but it is way cheaper than any other method. I have purchased there several times with that one, including charts years ago.

This has happened to me a lot of times in Caucasus too, and a friend just suffered it last Tuesday. I started a thread about it and someone pointed to this bug report: https://forums.eagle.ru/showthread.php?t=154630 I don't think ED has acknowledged it though... In my case, I cannot relate it to flying under structures. Under other aircraft, who knows...

I just flew this mission and can confirm a few problems: SPOILERS AHEAD! 1. I am not sure now whether I told my flight to anchor but lost my #3 and #4 without a warning. Perhaps the load is too heavy for the AI at such altitudes. 2. When I was leaving IP ALPHA for the run on the first target, I was notified that I had hit it, before releasing the bomb. From the log, it looked like an artillery or mortar unit hit herself and killed all. This didn't happen in the second target, which was fine. Well, with the clouds I expected the JTAC to lase my GBU-12 so I didn't and missed. But hit it with a GBU-38, so the coordinates were fine in my case. For the guy with problems with the CBU, I recommend lowering the Height of Function (HOF). It is by default at 1,900 ft, which is too disperse anyway and inaccurate with wind. It worked fine for me at 700 ft.

Mission 10.

I taxied before communicating with Defender-9, but took off after receiving the SAM footprint clearance. After the mission I noticed in the log several SA-18 launches but didn't see them, my MWLS didn't alert me and neither my flight nor Defender-9 said anything about them.