Luigi Gorgonzola

Possibly something like that? Apart from the different languages, the russian letters are very blurry. Of course, this varies with the ATI driver settings, but as the latin letters do particpate from the graphics driver as well, the difference remains.

Found this today:

FT = "Free-Turbine" switch. It tells the Governor what RPM to maintain. By switching from "Nominal" to "Low" you're lowering the target RPM percentage value, if I understood correctly.

Not really ;) In case of a single engine loss, all you do is to move the throttle lever of the working engine to its FULL position, close the failed engine's cut-off valve and (usually) RTB while maintaining Rotor RPM at no lower than 85% using Collective. There is usually no need to "waste" a Joysstick/Controller button or slider with the Throttles. They remain untouched during flight (except in cases of emergency).

The Ka-50 is equipped with a so called Governor, a device that eliminates the need of the pilot taking care of the throttle. In consequence, you place the throttle levers in AUTO position and the Governor device does the work on the throttle. All you have to take care of is Cyclic and Collective. And that's already pretty much. ;)

Nice one, had to smile when the sound came up ;)

:shocking: Quite interesting way to loose altitude... ;)

To edit the ADF frequencies simply have a look at Scripts\Aircrafts\Ka-50\Cockpit\ARK\ARK.lua. A list of available beacons can be found in Scripts\World\Radio\Beacons.lua and a list of known airdromes is available in Scripts\World\Airdromes.lua. And all this is written on page 6-73 of the BS 2 Flight Manual, along with an instruction to check the ADF system.

Ah, thanks :) Found them in "Ins Cyclic" :)

*bumpedibump* Hmm, maybe I just encountered the very same (BS2 1.1.1.1). Track attached. I was at the ramp and played a bit with the different camera views. In doing so I intentionally used my arrows keys. This must have b0rked something as I just saw in my track (the important part are, as usual, the fery last minutes). The visual hickups are caused by my TrackIR "Center" key mapping - it's the Up arrow key as I usually don't need it ;) When returning to the F1 view, I found my Cyclic being stuck in an extreme position (down right iirc). Utilising my joystick wouldn't do anything and using the arrow keys would simply make the Cycling going mad, moving to the end position of the direction the arrow key I used was pointing to. No way to convince the Cyclic to return somewhere close to neutral and stay there... It's the first time I see this. In the past, whenever I touched the arrow keys, the Cyclic would move a bit into the corresponding direction but would stop moving and keep its position once the key was released. It was also always no problem to use the joystick to "fix" the issue... EDIT: Just realised that I have absolutely no keyboard keys mapped to any of the axis commands?! Is that by default? CrazyKBD.trk

Strange, I always was able to return the HUD to normal by resetting the system.

Regarding the second pic (target symbology) - did you do a reset? For me, this usually helps.

Communication seems a bit weird in UK, I learned. Especially in rural areas it seems pretty common to have no landline available (Carmathenshire, Summer '08 ). However, no reason for finger pointing, others don't even have beer... ;)

Wich is labelled "INT.COM". It's the leftmost switch in the row of radio switches. I always turn on all radio switches once there's enough power available (i.e. either by ground power or the generators). To check the audio system in general, there is a pushbutton on the upper part of the left front panel (next to the G-Meter, above the Zebra Light). Push this to check your warning lights and the audio system.

I wouldn't take it a s abug, you probably forgot to remove the corresponding keybinging(s)... Happened to me the other day, too. Was pretty funny until I realised, what had happened ... :D

BS1 und BS2 gehen problemlos nebeneinander. Ich habe sowohl BS1 als auch BS2 installiert und kann keinerlei Probleme mit dieser Konstellation bemerken. Einzig wichtig ist die Entscheidung zwischen BS2 als Upgrade oder als Vollversion. Das Upgrade benötigt für die Installation ein funktionierendes BS1, danach nicht mehr. Das bedeutet bei einer eventuellen Neuinstallation von BS2 natürlich auch eine Installation von BS1. Weil das irgendwann einmal unangenehm werden könnte, hatte ich mir einfach die Vollversion von BS2 gekauft.

Please keep in mind that you're actually dealing with two systems when hitting the trim button: Trim -- removes all forces on cyclic and rudder, thus easing a pilot's life (that's the clicking sound you hear) Attitude Hold -- determines the helicopters current attitude in space and stores the resulting values in the flight control system which is then (within certain limits) modifying the pilot's input to match the attitude determined when the trim button was hit. Result: If the helicopter's attitude does not match the pilot's intention, the helicopter wins. This is often described as "strange behaviour" or "trim is broken". As you can switch off the Attitude Hold system by engaging the Flight Director Mode, it seems advisable to do so in training situation when the intention is to actively control the aircraft. IRL, most definately every pilot would use "Auto Hover" (or "Hover Hold" in our case) to keep a hover attitude. It doesn't make any sense -- again, except of training situations -- to "waste" precious pilot attention to maintain a desired attitude if there's a system doing the job at least as good as the pilot, usually even better. ;)

At first glance it seems fine. Once I figured out that I downloaded the wrong patch (the patch for the patch instead of the patch for the full version :wacko:) the installation just did what it's supposed to do. Startup, new option "Shadow Tree" (hmpf?) checked as I'm still hunting FPS, quick instant action to check the ADF thingy (all fine here) - nice :) Strange, it still is a 'copter... ;)

Just 324 MB? That's nice :)

ModMan is a highly recommendable tool to install modifications/add ons (not only) to the DCS series, FC2 and more. If you don't want to bother about ModMan, you can also unzip the file somewhere you remember. In both SP ad MP mission select screens you can switch drives, folders, etc...

Nate, sorry for editing my post ;) - could you please check the second track? Anyway, if it doesn't happen in 1.1.1.1 it would be good news :) EDIT: Airborne in 1.1.1.1 all fine :) Anyone got a spare "1" key? Mine is pretty much worn out and I guess there will be quite some more 1s to type... ;)

Here you go, just switch the ADF channel and it crashes. EDIT: Weird. Using my own track, I couldn't reproduce the issue? However, I managed to save a track (ADFCrash2) that displays the actions taken. About a second or so before the end of the track, I saw the windows error message. N.B.: Also tried to produce the crash by switching the TLF/TLG button. All fine there as far as I'm concerned. ADFCrash.trk ADFCrash2.trk

Also crashes airborne. DIY: Instant Action -> Shooting Range. I doubt it's specific to an airport but a general issue, instead.

Not sure about that. Reproduced the issue in Maykop, "takeoff from runway". Easily done. Now: Maykop, "takeoff from ramp", to lazy to switch on everything, so I just powered the communications equipment and the NAV stuff (INT.COM on, VHF-2 on, NAV on, nothing else). No crash, I can play with the switches and still live ;) However, every time I switch the ADF channel now, I see something like the Morse code of the station being displayed in the upper left corner (see screenshots). No idea if this is related to the issue, though.