Avio

Now I could finally get them tuned correctly after trying at Batumi. However the tuning for NDB seems always to have to intentionally tune beyond the actual frequency on the dial. Example at Batumi NDB is 433 but from the pilot's seat it looks like one has to tune it to nearly 500 before getting the correct station. Trying to set to 433 gets a wrong station that points elsewhere.

Thanks Flagrum. That makes it work.

Have been trying hard to tune in to a NDB station but with the analog read-out it is hard to tell if I got the right station. Also the audio volume is too soft to make out the morse code, even though the gain has been maxed out. And even if I could hear it somewhat, most time it didn't seem to be tuned to the right morse code. Is there an easier way ? As for the VOR, no matter how I tune the frequency it just didn't seem to receive anything. I was trying these out at Kutasi. Any advice most appreciated.

After the most recent patch, pressing the Huey auto-pilot key no longer gets it to work. It used to be okay. Anyone else seen this?

Yes the pinky was set up as a Modifier in game. Is there another "official" way that I may not be aware of? Would like to know.

Pretty strange cos I'm just merely trying to map pinky and combo switch to a normal 4-way hat switch such as TMS. Example TMS UP for one function, and Pinky+TMS UP for another. Somehow sometimes after switching around the switching just wouldn't update. But after a few more presses, they function again.

Not sure if it turning on HT would affect the overclock speed. Will give it a try. Thanks.

I mapped the TM Warthog's joystick pinky switch to use in combo with another switch for the Ka-50 but noticed that the combo key command doesn't always work. A check using device property confirms that both the pinky and other buttons are all working perfectly. Anyone else notices this? Thanks.

Getting quite confused here ... My PC runs on ASUS i7 Quad-Core OC to 4.5, and I would like to know should I run it on hyperthread or single core for DCS world? Read somewhere that turning on hyperthread may actually bring down the clock speed of each core. Advice please. Thanks.

Just the very thing I have been looking for ... Thanks a bunch !

Thanks Flagrum. What I meant was to display 2 sets of control points display (in 2 diff colors) within the same control box. That way when I move the physical stick I could see its real position in the box in relation to where the virtual stick was at. Anyway not a real important thing there. Will check out the non-rudder trim mod you mentioned of. Thanks.

Wonder if it is possible to implement another set of control position points into the control box view -- meaning there is one current set of points to show where the virtual sticks currently are in-game, and another set (of different color) showing in real time the exact locations of where the physical control positions are. This way I would know how much I need to reposition the physical controls to match up with the virtual ones when I decide to reset the trims. Currently reset trims result in some rather embarrassing jerking all over before control could be regained back. Hope to hear how you do trim reset (elegantly) while in mid flight. I particularly prefer to have the rudder always not affected by trim, an option present in the Huey but not in the Ka.

Thanks a lot BitMaster for your illuminating notes. Indeed perfect symmetry can't be expected, just wondering if the imperfection is randomly modelled for each flight or if it is scripted to behave the same way each time. One thing for sure -- the Kamov is truly a dream helo to fly (and fight in). Great.

Okay will check that out. Thanks.

With dual-rotor, I would expect that the Ka should maintain nose straight upon vertical lift-off into a stable hover, unlike in the Huey with left rudder is needed. But strangely, I noticed the Ka tends to want to rotate clockwise on its own. I left it on its own and it could turn through several rounds, therefore it can't be due to wind, otherwise it would have just weather-vaned into the wind and stop there. Hope someone could help shed some light here. Thanks.

Been trying to locate where this Ejection System Test button is on the wall panel but just couldn't locate it. Anyone knows? Thanks.

Very strangely, my encounter is exactly the opposite. Maybe we're really flying diff DCS. I had mine patched to latest.

I CAN CONFIRM IT ALL, FOLKS ! Started this thread while on HDD encountering occasional stuttering in DCS for years. Just made the switch to SSD, and voila ! The stuttering is gone!! While it makes no diff to the FPS as expected, eliminating the stuttering truly makes a world of diff here. Silk-smooth FPS now most of the time. Hope this thread helps point the way for those facing similar issue. It really helps.

Is it better to do pop-up attack directly or from an offset path? Offset pop-up seems to make better sense as it presents a crossing and moving target to any ground fire. But it also seems to create problem of stabilising the chopper when swooping down on final attack run. This is especially so in a Huey, unlike in a plane where it's all steady. Anyone has a good idea of how better to stabilise the Huey when coming out of a turn? Tried using rudders, but not easy preventing gunsight from rocking all over.

Yes I did. Exact same scenario.

Was trying to take out a few BMP using cannon and was surprised to find the Ka-50 acting like jelly under fire --- it seems too easily destroyed by the armour fire. In comparison, the Huey seems just the opposite --- it is able to take tremendous amount of hits everywhere and anywhere and still fly. Even hits through and all over the cockpit windscreen didn't seem to cause a dent in the pilot's body. Now which is the more correctly modelled one here, the Ka-50 or the Huey?

Alternative method -- Get used to where the rockets usually land when firing from those distances you tend to prefer firing from, do the necessary offsets, and you're on target most time. No need for fiddling with adjustment in the heat of battle.

Is there any guideline on how to do the correct setting? And I have been wondering, how does one judge the slant distance to a point on ground ahead? Any rule of thumb?

Not sure if we're talking the same thing here -- but I similarly noticed that rockets seem to fire out above where the aiming reticle is. As a result, I always have to intentionally put the aiming sight below the target in order to hit it. The reticle seems accurate only when firing from a further distance away.

With the wonderful help from user "aeliusg", and much trial and error, finally got a lua done for the Warthog Throttle. Most switches assigned for those needed in startup as well as armament. Hope you like it. See attachment file here :- http://forums.eagle.ru/showthread.php?t=130018&page=2