Avio

Would like to know, what is the maximum Auto hovering altitude for the Ka-50? Thanks.

"You should know that the Laser is only good for 1 set of Vikhrs and will fail somewhere in your next 12-set of Vikhrs. You also cannot repair the Laser alone, you have to have some damage, or create some, so the Laser is replaced during repair. Let the laser cool down between shots if in no hurry and don't click on every bush to measure the distance just for fun, it will heat up your laser and wear it out a few rockets earlier compared to when you have an eye on it's temperature. Check Devrim's mod for the english HuD and temp gauge in HuD, it's on ED website. So you have a clue where the temp is and don't fry it too soon." BitMaster, I didn't know the Laser is good for limited use only. I fired off quite a few Vikhrs the other day and it seemed to be good for a long while. Didn't see any mention about watching the laser temp in the manual. And does the current default HUD shows the temp? Or only available in the mod? And does the mod simulate everything else on the default HUD? Thanks.

Okay thanks for the pointer.

Thank for that. But I don't seem to see that info anywhere in the manual. On one point -- you mentioned of less efficient lower rotor at <lower> speed. Shouldn't it be at higher speed? At lower speed (below 200 km/hr) the Ka flies straight within no yaw seen. It is only when going above 200 km/hr that the yaw starts showing up.

Was doing some flight practices and noticed that during straight and level flight, as the speed goes above 200 km/hr the coordinator ball starts drifting to the right (about half-ball to right), indicating there is a left yaw. And indeed the heading gradually drifts to the left over time. But this is dual-rotor and as such should fly straight and true, isn't it? Anyone else seen this?

The Huey's horizontal stabiliser deflects the same way for both cyclic forward and backward, only difference being the degree of deflection for each. Is this right? Shouldn't it deflect in opposite way?

Just keep plugging and practicing away. It really is quite possible to master the amazing Huey.

Truly liking the Huey more and more. But one thing stands out that looks like a possible bug -- when properly trimmed to fly straight and level, with hands and feet off all controllers, the chopper flies as it should, but the nose keeps bobbing left and right a little non-stop. Compare this to when the auto-pilot (co-pilot mode) is turned on, where the nose holds rock-steady. Unless the virtual co-pilot is a much better pilot, how does one explain the discrepancy. Any modelling issue here? Try it and see what I mean.

Problem solved ... sort of. This issue crops up whenever in mid-game the control setting options page is called up. Somehow when back in game the switches all get reversed.

I had my Warthog throttle switches configured, some through Lua edit. When Huey just loaded all switches work as they should. But after flying around for some time doing touch-N-go, suddenly some of the toggle switches started getting reversed. Anyone else encountered this? Is so, how can it be fixed. Thanks.

Thanks Lib. I did trim, but not during turn. Will give it a try.

Couldn't help but ask this question -- What is your favourite, Huey or Ka-50? I have both and like them a lot, and sometimes can't decide which I like better. I like the Ka-50 complexity, and lethality at long range, but while flying it is supposed to be easier, sometimes it feels like fighting against the computer (flight director ON). Example -- doing level turn seems quite a challenge. Whereas the Huey, while feels rather slippery at first, is actually a pretty awesome machine to fly in. At least level turn feels just that -- Level ! Control feels more precise, other than wobbly stability sensitivity. And of course, that awesome, awesome sound of rotor chopping through the air. Feels a lot more alive ! What do you think?

Yep I thought it could be parallax error, but from the pilot seat, any such error should show up as SMALLER value, NOT bigger! Something didn't seem right here ..... And the hard-to-decode morse code just didn't help identify whether the right station is tuned in.

Thanks Bucic. While I have my C drive as SSD and my D drive using normal HDD, not sure how each may affect another. Read the article but that one is to do with running apps on HDD.

Am afraid got to take back some of these words! While there didn't appear to be any more stuttering during explosions and such, strangely sometimes (not often though) stuttering would happen, with some pauses lasting like half a second or so, with a series of pauses happening around the same time period (stretch of less than 10 secs), and then suddenly it would all be smooth again. Wonder what could be the cause?

What should the sound audio settings be for the Huey to sound like it should be in the real Huey, with headset on?

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.