Avio

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

Finally got it all done. The needed buttons are all assigned as I want them. Attaching the lua file here (and in fresh post) for whoever wants it. Feel free to modify as you wish. Thanks to aeliusg ! Enjoy. Throttle - HOTAS Warthog {F4B41430-2DF4-11e4-8001-444553540000}.diff.lua

Hi aeliusg, Thanks for that. Before getting your reply I did managed to get it to work, but with only the Safe and Armed positions, leaving out the Switch's Alt position. Not with PC now and can't recall what I did. I just played about with the "1" and "-1" values to get that. Will take another look and try out yours and see how it goes. Thanks again. Yep, let's hope the next update won't affect the lua. Only wish TM and/or DCS could make the controllers' setup a breeze for everybody. Mastering a DCS aircraft is in itself already a Huge challenge, and I'm sure most would rather spend time flying than configuring. But I must say there is satisfaction though when things work out :megalol:.

Thanks everyone for your great patient. Finally beginning to grasp it -- managed to get it to work finally! Now I tried assigning the LASTE switch to the Off/Safe/Armed functions but using the same magic didn't seem to work :- ["d3020pnilu3020cd9vd1vpnilvu0"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN27", }, }, ["name"] = "Armament Off/Safe/Armed Up", }, ["d3020pnilu3020cd9vd-1vpnilvu0"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN28", }, }, ["name"] = "Armament Off/Safe/Armed Down", }, Any idea how I could get the codes right here? This switch should start at the bottom most position, which is Off, then Safe, then Armed. But just couldn't get it right. Btw, I replaced the original data.lua file as advised. Will this affect other stuff? Also, when DCS has a new patch, will this get affected? Thanks. Edit -- Noticed in the Option setting, a double-entry was created for those switches under editing, and the hotkey once assigned couldn't be Cleared off. Is it possible to delete away the duplicate entry?

Thanks aeliusg. I cut and paste the codes you gave above into my lua but suddently the pinky switch does not work at all. Strange. Btw, what's the difference between "vu0" and "vunil"?

My apology once again, I think I got mixed up big time after staring at all those codes. It is the right switch we are talking after all ... Here's the lua part I'm looking at :- ["keyDiffs"] = { ["d3002pnilunilcd7vd-1vpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN13", }, }, ["name"] = "Nav Lights Flash", }, ["d3002pnilunilcd7vd1vpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN14", }, }, ["name"] = "Nav Lights Steady", }, How may I insert such that I can command for an OFF when this toggle switch is returned to middle position? This is what I hope to do. Thanks.

Thanks aeliusg. I'm editing from the diff.lua file. As shown in my Edit in previous post, the switch I refer to is actually the 3-way toggle switch, not the red button. What I want is to be able to let the toggle-forward to be Light-Steady, toggle-backward to be Light-Flash, and toggle-middle to be OFF. So far I see only value assignment for Up or Down, is there one for Middle? Thanks.