kdfw

you need to assign 'trim control command' keypress "T" to your cyclic button for the early access 'CD Release (trim release)' function, see pp.57 in the manual.

and so an allegation was made of ip 'violation' and ed went nuclear--no more payment to the vendor--and the outcome should've been obvious. by not paying the supplier a token/reasonable maintenance payment for products that require perpetual patching (patching due to core platform changes and bug fixes) and by not paying for the popular f15 module would result in the vendor terminating ongoing support (who da f wants to work for free?). simply, ed should've separated the 'ip issue' from the ongoing product maintenance requirements in dealing with rb. but instead it overplayed its hand and damaged its own brand and reputation.

there ain't going to be any courtroom battles here, look where these 2 companies are located, not different countries, different continents! how can any judgement get enforced? by the world police? fantasy talk. i still have not seen any rb product that supposedly violated ed ip on the market or mentioned anywhere on the web. if there's no tangible product and nothing ever went on sale, then there is no economic damage and all this is ed overplaying its hand in some dispute and ruining the ed brand. an ego thing, poor cashflow management, and/or just insanity.

i hope it will be made stable as the kw and implement fade in/out force trim release as the kw to prevent unnatural upsets.

ed accusing rb of ip misappropriation and resolving it behind the scene is one thing , not paying rb at least a nominal maintenance fee for upkeep of existing modules--on this ever evolving platform--is same as going nuclear on rb. there's nothing to indicate ed actually suffered tangible damages from the alleged ip misappropriation and so what could've been quietly resolved without harming the dcs brand is now a pr disaster. essentially cutting your nose off to spite your face. this also raises questions about how ed is dealing with other 3rd party devs: who's going next? sad state of affairs all around. ed, fix it.

this kw is a fantastic model. flies well, system details are good, and vr performance is same as others. one thing that bothered me: the cockpit textures had too much shine for flat black surfaces, looked like the surfaces had glazed coating on them like a wet candy, which is probably more pronounced in vr. and the chrome airbag valves 'glowing' in the shade just took away from the realism. i reworked many of the textures and roughmet files to clean up the shine and inconsistencies in color and it looks good. pilot skin textures also need to be de-saturated as they looked awfully pink... love the fade in/out cyclic trim and ai implementation.

old issue, for spring centering stick/peds, the ah64 force trim options either cause aircraft upset (instant trim) or controls running away (central position). the new kiowa model has the "Fade In/Fade Out" trim option that works wonders with spring centering stick/peds. just like the instant trim but without the instant jolt. much smoother, dare say more realistic. came here to beg the ah64 developers to include this trim mode option for the ah64. please.

i'm finding the kiowa's Fade In/Fade Out trim is much better/smoother than what was done on the ah64. on the ah i use instant trim mode and the control throw double the instant the force trim is pressed which upsets the helicopter (alternative central position trim is not good). i guess i'll beg ah devs to implement the kiowa scheme...

repair install was my next option...

thank you all for the help. just assumed it worked as before, i must rtfm.

trying to find out why the f16 AG radar isn't working anymore, stock f16, instant action/caucases/free flight. press A-G and get the radar screen but it's blank. the mfd range keys are 10 or 5 only. AGR works for the f18. appreciate any suggestions.

using dcs beta and hp reverb g2 and had problems with xrnecksafer beta5a so gave up on it a year ago. problem was the yaw origin was messed up going left or right, even though in-game center button was pressed. just tried it again and figured out that the g2 has to be placed on the head or oriented near the head pointing in the 'reset' position when dcs is started. it apparently uses position at dcs launch as the initial reference for the yaw axis instead of the in-game centering position (maybe the in-game centering doesn't update the hmd init yaw position?). so now it works perfectly as it did before the multithread beta. must first launch xrnecksafer before launching dcs.

many repaints hosted by dcs are License: Freeware - Free version, Unlimited distribution so guess one can take the repaints and distribute for the msfs f14 and credit the original repainter as curtesy for the work well done.

Thanks for the comments! I'm using a vkb stick with 4" extension and my wrist is resting on my leg for my sim setup. Also using cyclic saturation at 50% to take advantage of the dynamic range of the stick. With this setup, the AH is pretty stable to control with two fingers on the grip but I'm sitting on a stationary chair. What with the real AH in flight making tactical takeoff/landings with the wind buffeting the aircraft, controlling the stick with finger tips would be pretty much impossible with this kind of control sensitivity? For this model, it seems mass of the aircraft and gyroscopic stability are not quite there. Control response shouldn't be instantaneous to the touch as the rotor blades flex with change to control input. I guess I don't like the twitchiness of the cyclic for such a heavy double turbine 4-blade beast of a helicopter--a mellower AFCS modulated control is what I was expecting. Whining aside, it's still a blast to fly though.

the cyclic is very sensitive to the touch, you barely move it and the helicopter moves about. so, in the real thing, how does one fly it with turbulence and g-forces without losing control? maybe the controls are way too sensitive? the mass of the aircraft and the large 4 blade rotating disk should offer inertia and gyroscopic stability...