CrimsonGhost

As the title says, I am curious what procedure is typically used to decelerate quickly from cruise to get into position for hover? I have been pitching up and lowering the collective but it seems to take forever to bleed off airspeed. This typically works with standard configuration helicopters, but does the coaxial rotor system change this at all? Some pro tips would be greatly appreciated. Thanks.

I have been having a problem lately on the Open Conflict Server and am curious if anyone else has encountered the same issue. The problem is that shortly after takeoff I am unable to open the comms window at all. The command does not work at all. Also, I dont know if its related or not, but the other day I was cruising around in the KA-50, unable to get target reports due to the above issue. After about 30 min cruising around the conflict zone I stumbled across some red smoke, but could not find anything in the area. And to make things more confusing, pairs of flares were shooting out of ground all over the area marked by the red smoke. Anyone else seen this, or is this something wrong on my end?

Sorry to necro an older thread, but has anyone heard an update on this? Ive been trying to learn the KA-50 using the 476th vfg training range, but still have not been able to enter coords in the PVI.

I really enjoy this server. It's my go to server for learning new aircraft in a populated environment. Been practicing CSAR in my recently acquired Mi-8 in preparation for the next round of blue flag. I would love to see a similar server setup for the NTTR, and the scenario is ideally suited for that map as well. I would definitely be willing to contribute to make that happen. There is not a lot of options yet for MP NTTR.

Damn, its over. Just as I was getting up the nerve to hop in a chopper and do some delivery runs. Oh well. Round 6 it is. Gives me time to practice in my recently acquired Mi-8.

Hello all. Long time lurker, fairly new poster here. I have long admired DCS, and in particular the A-10C. I have purchased most of the modules over time during sales, knowing I would one day get involved. With the release of NTTR and 1.5/2.0 with it, I am slowly starting to get more and more into DCS. Onto the topic at hand. I lost my lower right leg in a work related accident in 2009, and have got around this ever sense by using HOTAS setups with a twist grip for the yaw axis. I currently use an X-55 and it meets most of my needs. However, a coworker recently "long term loaned" me his TM warthog and Saitek combat pedals as he no longer has any interest in flight simulators of any flavor. So now I have the set up I could never afford, and could really use some advice from folks on how to set this up as obviously the pedals present a challenge. I have a few basic ideas on how to proceed. Try and make it all work, just use the HOTAS and control yaw with the keyboard, or just stay with the X-55 and make it work. I really want to get in depth with the A-10C in particular but need to get the controls sorted out first. And for some reason the X55 leaves a bit to be desired for me with the A-10. I love it for Prepar3D, but it just doesn't fit my hands right for all the functionality that the A-10C requires. Big hands and little switches/hats on the throttle don't mix. Alright, sorry for the wall of text. Any thoughts or ideas would be appreciated. Especially input from anyone in a similar physical situation. Thank you all.

I was thinking it may be a terrain following mode for low level penetration missions, but like everyone else, I cannot find any references in the manual. If it is, this could be a neat feature.

Yes please!!! The language barrier is tough to overcome.

I relaunched DCS a few times and the updater finally kicked in and installed a patch, then the aircraft. Hope this helps.

I to am getting the same error.