Acedy

In the new manual only typos were corrected, there is no new content

http://forums.eagle.ru/showpost.php?p=588704&postcount=44

BS does not contain SST profiles, but there are preset button mappings ingame.

Hehe, nice URL Bone. :D

No, DCS does not have a dedicated server option yet, but that is something ED wish to implement later.

Q: I have purchased both the Russian and the English version of Black Shark. Can I use my activation key of the Russian version for the English version or vice versa? A: No, you cannot, the keys are not compatible with each other.

Normally when you just uninstall and then reinstall BS without changing hardware/reinstalling the OS you do not need to use a deactivation.

IIRC you have to pull the knob by right clicking and then rotate it counterclockwise using the mouse wheel.

A printed, extended manual will be released at a later date. In the mission editor place your 1st waypoint above an airbase and select "Takeoff from runway". If you select "Takeoff from parking" you will start in a cold & dark state. In that case you can use "LWin + Home" to perform the automatic start-up procedure.

The Ka-50's "autopilot" is actually a combination of a flight control systems and a true autopilot. It has four modes: 1. off 2. dampening of contol inputs 3. dampening + stabilization of flight parameters 4. automatic flight (or hovering) In all modes you can intefere with the autopilot's inputs, the autopilot never takes full control of the helicopter. The autopilot is off when the blue buttons on the right panel are off. The autopilot dampens your control inputs when the blue buttons are on and the flight director is activated/the trim button is pressed. The autopilot dampens your inputs and stabilizes the currently trimmed flight parameters when the buttons are on and the flight director is off/the trim button is not pressed. Automatic flight/hovering is active when the blue buttons are on and the route/hover mode is enabled. Normal procedures include that you fly with the dampening and stabilization functions on. That's why you need to trim all the time in order to tell the autopilot which flight parameters it should maintain and stabilize. Read the FAQ, there are some very helpful infos.

The reason why you are fighting the controls is because you did not retrim directly after changing direction. As long as you do not retrim the autopilot/flight control system assumes that you want to hold your original heading etc. and it takes actions to bring you back on that course. Trimming does not only fix the new position of your controls, it also tells the autopilot that you want to hold the current flight parameters. So either trim directly after changing direction, or even better, push the trim button for the duration of your maneuver and release it after you have set the new flight parameters. As long as the trim button is pressed the autopilot's stabiliziation function is disabled, and once you release the button the new flight parameters are stored.

Here is an overview over the A-10C upgrade program: http://www.globalsecurity.org/military/systems/aircraft/a-10c.htm

I merged your threads.

Did you put it behind the last quotes? I get that error if I put it in front of the quotes.

Just run the protect.exe in the bin/stable folder

The console is a diagnostics tool to show what's going on under the hood of BS, enabling it does not solve anything. When you enable it by removing the --console parameter a window will appear in the background once you start BS that logs all kinds of actions. To see it and make a screenshot you may have to alt-tab out of the game, or use window mode. Vista's rights management is different from the one XP used. Even if you are logged into an Admin account you still only have user rights unless you grant yourself or your program admin rights.

Did you place both files into the same directory?

And I merged two of your threads about this problem and deleted the 3rd. ;) I don't know what causes this issue, my guess would have been that no write permissions were set or Vista's file virtualization is causing it, but you probably checked that already. Anyway, as a temporary workaround until the solution has been found you can manually edit the options.lua file to adjust your gameplay and graphics/audio settings, just compare the entries with the options screen to find out what is what. The file can be found here: \Eagle Dynamics\Ka-50\BlackShark\data\scripts. Do not use Windows notepad to edit it, but a good editor like Notepad++. In order to map joystick buttons you will have to use your profiling software, the only issue that may remain is if BS assigns the wrong joystick axises.

Start TIR software -> Menu -> Update -> Check for game updates

http://forums.eagle.ru/showpost.php?p=587754&postcount=74

Read it here: http://www.simhq.com/_air12/air_394a.html

http://forums.eagle.ru/showpost.php?p=587510&postcount=27

No, I mean that you should try to map the TrackIR hotkeys to joystick buttons and check if they work now.

http://forums.eagle.ru/showpost.php?p=571131&postcount=6

Does the workaround fix it? @Red Tiger: yes, the problem also occurs with Numlock on.