Conure Posted December 20, 2010 Posted December 20, 2010 Hello everyone, for some reason whenever I trim my aircraft my joystick becomes disabled...until I press crlt T to reset it at which point it reactivates..any idea what might cause this? Thanks! Intel i7 6700k, Asus GTX1070, 16gb DDR4 @ 3200mhz, CH Fighterstick, CH Pro Throttle, CH Pro Rudder Pedals, Samsung Evo 850 SSD @ 500GB * 2, TrackIR 5 and 27" monitor running at 2560 * 1440, Windows 10.
Insanatrix Posted December 20, 2010 Posted December 20, 2010 turn off force feedback in the ka-50/config/producer.lua file I believe.
Bucic Posted December 20, 2010 Posted December 20, 2010 (edited) If disabling FFB doesn't help: Remember that in case of using stick with rudder pedals you have to center both to regain control after trimming. Check if your center is solid when you have your hand relaxed on the stick / hold your feet on your rudder pedals. The best (and simple!) tool to test it is DIView. If the center is not right then you should re-calibrate the controls. Recalibrating Saitek controls usually involves registry editing so let us know if you really need to proceed that way. ... Recentering in the windows callibrration utility usually does nothing. Besides, if you have the Saitek drivers installed you should not have axes to calibration at all. Manual re-calibration of Saitek self centering joysticks: - disconnect the controllers - navigate to HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput - back it up just in case - delete all the VID_* keys, unless you use JoyID application to determine which key is for affected controller - re-connect your controller and do some full range motions Edited December 20, 2010 by Bucic F-5E simpit cockpit dimensions and flight controls Kill the Bloom - shader glow mod Poor audio Doppler effect in DCS [bug] Trees - huge performance hit especially up close
Insanatrix Posted December 20, 2010 Posted December 20, 2010 I've had his problem before. It usually happens if you plug in a force feedback device and load up black shark. I left my FF racing wheel plugged in then couldn't figure out why my stick wouldn't trim and it enabled FF in black shark.
Conure Posted December 20, 2010 Author Posted December 20, 2010 Cheers guys, though ti make it work I had to reinstall! Thanks again Intel i7 6700k, Asus GTX1070, 16gb DDR4 @ 3200mhz, CH Fighterstick, CH Pro Throttle, CH Pro Rudder Pedals, Samsung Evo 850 SSD @ 500GB * 2, TrackIR 5 and 27" monitor running at 2560 * 1440, Windows 10.
talisman Posted December 20, 2010 Posted December 20, 2010 try changing the trim method in the options page. [sIGPIC][/sIGPIC] Is it a bird? Is it a plane? No - Its a Stinger - Damn....... My Pit - http://forums.eagle.ru/showthread.php?t=42253
deltahawk2008 Posted December 21, 2010 Posted December 21, 2010 Dont know if this helps. When I upgraded to 1.0.2 I was getting the same problem, I was in trims vicelike grip. No rudder, no stick. What the...? Checked and found that most of the missions in 1.0.2 had GAME ticked in the options setting, after opening them with the ME. Unchecked, and now all is good. Most embarrassing from an experienced simmers viewpoint. All is now good.
topdog Posted December 21, 2010 Posted December 21, 2010 You can also click the checkbox under options to say "Use these settings in all missions" so you don't have to edit them individually. Just beware that a 1.0.2 install itself will enable one of the game modes by default too, and that has caught a couple of people out. [ i7 2600k 4.6GHz :: 16GB Mushkin Blackline LV :: EVGA GTX 1080ti 11GB ] [ TM Warthog / Saitek Rudder :: Oculus Rift :: Obutto cockpit :: Acer HN274H 27" 120Hz :: 3D Vision Ready ]
Recommended Posts