Acedy

I guess you mean average values, as FPS are largely situation and setting dependent. My FPS range from 10-70. Please note that there has already been a thread where Jim posted a benchmark track, maybe it would be a good idea to use that with FRAPS in order to get comparable results. See here: http://forums.eagle.ru/showthread.php?t=34194 For the track see post #7.

Just a shot in the dark, maybe automatic activation doesn't work for some reason and the window that appears asks you to do a manual activation. See here for more info: http://proactive.star-force.com/2.0/userinfo.php

I wonder if this is only true for the Russians or for the Army Aviation of other nations as well, at least to a certain degree. To me it seems that NOE flying, pop-up tactics, hovering fire at stand-off range from masked positions and the like are largely 80s/90s standard tactics of the US Army and maybe Britain (?) and Germany, as Woodstock suggested. Naturally each tactic has its preconditions, and those for pop-ups and hovering fire from stand-off range include: hilly terrain (with lots of forests) intersected by wide, woodless valleys, plus clear frontlines. I.e. German midlands in the 80s. Woodless valleys in order to use your sensors and fire weapons from maximum range. Clear frontlines because you need an absolutely safe place to hover, preferably above/behind or at least close to friendly lines, otherwise you are extremely vulnerable. The underlying idea of these tactics of course is to provide close air support against enemy tanks (which have to move through open areas), not to fly independent (long range) missions into remote territory where enemy positions are unknown. Now ask yourself if these two preconditions are still met on today's battlefields where western forces are engaged? Afghanistan: mountainous terrain, but no real frontline and no tank battles, but enemies with small arms or MANPADS that can hide anywhere along your flightpath. Iraq: I don't have a good idea about the terrain there, sure a lot of desert, dunes, but then there are also the Euphrates and Tigris valleys and the mountains in the north, so it's probably a mixed bag. Plus most of the missions are counter insurgency above urban areas, so again no clear frontlines. Conclusion: it seems that today there are quite a lot of occasions where you probably don't really want to hover, but keep moving all the time and maybe even fly high. I wouldn't think that hovering fire techniques are obsolete, but that current circumstances often demand the development and use of other tactics. An interesting question however is this: what tactics did US Army and Marines attack helicopters use during Desert Storm and OIF? How do USMC Cobras operate? Did they ever adopt the hovering fire techniques, or do they mostly stick to run and gun tactics from the Vietnam era? In regard to these questions it is also interesting to look at attack helicopter design and especially the mounting of sensors. There doesn't seem to be a clear cut decision though, as mast, roof and chin mounted sensors are equally common.

Dreamboy is right, if you use the realistic flight model it is recommended to keep the X and Y axis linear, maybe with a small deadzone in the center if required. See GUI manual page 26.

Door: RCTRL + C.

The first game I have ever bought was Gunship for C64. That tells you everything. ;) But okay, the 3rd has been F-19 Stealth Fighter...

A-10C is next in line. As to the factors that influence the decision about flyables I can only speculate, but there are a few quite obvious things to consider: 1. Demand in the entertainment market. You are probably right that a lot of people in the "western hemisphere" (cold war language ;)) would like to see the F/A-18, simply because it is an all-inclusive package, but keep in mind that Eagle are also producing for Russia/CIS and that we as forum members are only a small fraction of the actual customers, although a vocal one. Eagle have been in the business since the 90s and they have people on board who have been working on some of the best selling flights sims ever, so I think they have quite good idea of what their customers want to see. 2. Demand in the military market. Eagle are equally focussing on the military and the entertainment markets, so if they sign a contract for the military about modelling a certain aircraft and if they are allowed to modify the end-product for the entertainment market, then I guess the chance is quite high that we will see that aircraft as a DCS flyable (see A-10C for example). 3. Available information and expertise. This point has been emphasised over and over again. In order to produce high quality and fidelity simulations Eagle need tons of information, of course a simple flight manual that floats around on the net is by far not enough. You need information about all subsystems, avionics, sensors, the engine, performance characteristics, data about flight dynamics, weaponry etc. pp. As you can imagine you can only gather most of these information if you have a close relationship to the designer or user of the simulated aircraft (like Kamov in the case of the Ka-50 and the US ANG in the case of the A-10), and to mechanics and pilots as well. Which brings us back to point 2. Regarding the F-18, keep in mind that it would be a quite labour-intensive add-on, as it requires not "only" to model the plane (which alone is already quite complicated compared to others), but also the whole carrier environment, which would be a like a simulation in itself.

Happy Birthday mate, enjoy your day!!

Currently there is no built in VoIP support, but Eagle are looking into that. You have to use Teamspeak, Ventrillo etc. for the time being. Regarding the data link, you can also have a look at this: http://forums.eagle.ru/showpost.php?p=579108&postcount=40

You can lock up a position with the Shkval, then select the wingman number on the datalink panel and finally press the send/mem button. This will transmit the locked position without storing it in the ABRIS. The drawback is that the position has to be in view range. An easy way to create preplanned attacks is to set a PVI target point in the mission editor on each location that you want your wingmen to use as an ingress point. Prior to the attack you send these TPs to your wingman and order them to move there, and to hold position once they arrived at the point. Then you can initiate a coordinated attack. The problem of this method is that you have to read the contour lines on the map very carefully in order to find good IPs/holding points for your wingen, where they aren't exposed to enemy fire.

US Army FM 1-112 "Attack Helicopter Operations", freely available from fas.org: http://www.fas.org/man/dod-101/sys/ac/docs/1-112.pdf

Hey Haukka, if the problems persists, could you please start a new thread in the bugs section and provide a complete bug report, including the error message and crash logs? This way it will be easier for the devs/testers to keep track of your problem and help you.

Afaik you can only select coalitions when creating a new mission, not afterwards.

1) Base files 2) Start menu shortcuts 3) Desktop shortcuts 4) Set realistic mode on 5) Install DirectX

They will be in the printed, extended version of the manual.

The idea is to align the SAI before take-off and then keep it caged until you need it.

The safest and easiest way to lose altitude while in hover mode is by holding the ROUTE/DESCENT switch in the DESCENT position. The autopilot will continue to descent with a rate of 2 m/s as long as you hold that switch (until you reach 4m AGL). The rate may seem to be slow, but it prevents that you accidentally enter vortex ring state.

Just tried it, flying straight and level at sea level with a fully loaded heli, 200kph is okay, 250kph is okay, but kicking in right rudder at 280kph caused the blades to crash. Note, this was still within speed limits, so no overspeed warning.

A single-rotor helicopter has a roll tendency at high speed because of dissymmetry of lift, which has to be countered by cyclic inputs. Generally speaking this problem of dissymmetry is canceled by the coaxial configuration, although not completely, as far as I understand it there is still a small roll momentum because of the rotor's separation on the mast, the upper, clockwise turning rotor has a greater leverage effect than the lower, counter-clockwise turning rotor, which would explain a slight tendency to roll to the right side.

High-speed forward flight and violently kicking in right rudder.

See here, last picture. http://proactive.star-force.com/2.0/userinfo.php

Q: How do I use the Ka-50's Data Link? A: The Data Link can be used to store target positions or other points of interest (POI) that were sent to you by your wingman or that you locked up with the Shkval. You can also send these information to your wingman if you want them to move to or recon a certain location, or to attack a designated target. The following assumes that you have set up your targeting system, data link, frequency and ID according to the manual. How to store targets/POI in the ABRIS: If your wingmen send you data that you want to store, just click the send/mem (ПРД/ПАМ) button after you received the EKRAN message and the target type and wingman number buttons started to flash. You will then see the target/POI on the ABRIS map. If you want to store targets/POI using the Shkval, first lock them up, then press the corresponding target type button and after that the send/mem button. Do not press any of the wingman buttons, as you do not want to send data. Important note: after you have stored new targets/POI, reset the targeting system. Sending targets/POI to your wingmen: You can datalink targets/POI that are stored in the ABRIS. To do that, select the desired target by pressing the corresponding target type button, then press the button for the wingman number. When both buttons and ABRIS icons flash, press the send/mem button to send the data. You can also send target points (TP) stored in the PVI navigation computer. To do that press the TP (ОТ) button on the PVI and the number of the target point. The target point will be shown as a flashing square on the ABRIS. Select the wingman and press the send/mem button. Finally you can send a location although it has not been stored in the ABRIS/PVI. To do that, lock it up with the Shkval, press the respective wingman number button and then send/mem. Do not press any target type button as you do not want to select an already stored target. Important notes: In case 1 and 2 the Shkval has to be caged. When storing or selecting a target in the ABRIS, be sure that you do not have a taget point selected from the PVI and vice versa, otherwise you will get problems because the computer does not know if you want to use the PVI or the ABRIS. After sending the target location/POI, you have to tell your wingman via radio what you expect him to do, i.e, fly to the datalinked position, recon the position or attack the datalink-designated target(s). Ingress Points (IP): If you want your wingman to use an ingress point for attacking a datalinked target or flying to a POI, first transmit the ingress point, then the target position/POI and finally send your orders via radio. The wingman will then fly to the ingress point and turn to the target/POI once he reaches it. Note that ingress points can only be used in conjunction with other target points, otherwise wingmen ignore them.

See manual p. 2-101 You have to request the NVGs from the ground crew first.

http://forums.eagle.ru/showthread.php?t=34016 ;)

The core simulation part of DCS will be the same for all modules, in order to ensure MP compatibility. So if you do not want to buy each and every module you will still be able to update your DCS core to the latest version via updates/patches, only the number of flyables will depend on which module you buy.