ED Team Raptor9 Posted April 19, 2019 ED Team Posted April 19, 2019 Hi all. I recently upgraded to a new gaming rig since my last one couldn't run DCS since moving to 2.5. Yeah, it was a potato. I had been using a non-pro X-52 with DCS since 2009 when Black Shark 1 first came out, with no problems mapping all the buttons and axes for all the time I've been playing DCS. My standard zoom axis for any of my modules had always been the smaller rotary knob on the throttle, indicated in the attached image. However, since installing DCS on my latest computer, DCS will not recognize the axis when I try to program it in the options. All the other axes work, including the larger rotary and the slider. I know the rotary itself is functional because it works fine in the game controller settings in Windows. Does anyone have any insight into why DCS wouldn't recognize this particular axis, even though I know it is functional? As a side note, the Pinkie switch on the stick experienced the same behavior, in that DCS wouldn't recognize it when I tried to map it. However, DCS does recognize it if I leave the Windows game controller settings window open when I start DCS. Really bizarre behavior that I never experienced in the ten years I've been playing DCS and mapping controls. Afterburners are for wussies...hang around the battlefield and dodge tracers like a man. DCS Rotor-Head
Sokol1_br Posted April 20, 2019 Posted April 20, 2019 Sometimes an axes don't have "sensitivity" to be recognized by DCS controls, try assign this rotary selecting by axis name (look in Windows Games Controller) in the drop down menu in DCS assignment window.
ED Team Raptor9 Posted April 20, 2019 Author ED Team Posted April 20, 2019 Sometimes an axes don't have "sensitivity" to be recognized by DCS controls, try assign this rotary selecting by axis name (look in Windows Games Controller) in the drop down menu in DCS assignment window. Thanks for that suggestion Sokol. :) I manually selected the axis in the drop-down window in DCS Controls, and it indeed detects it. Unfortunately, it detects the rotary as either centered, or fully saturated to one side. The Saitek software isn't running, I've never programmed the rotary to behave this way, and the Windows Game Controllers window shows a smooth saturation through the entire axis of movement. I just don't think DCS likes this particular rotary anymore. :( Afterburners are for wussies...hang around the battlefield and dodge tracers like a man. DCS Rotor-Head
Holbeach Posted April 20, 2019 Posted April 20, 2019 Thanks for that suggestion Sokol. :) I manually selected the axis in the drop-down window in DCS Controls, and it indeed detects it. Unfortunately, it detects the rotary as either centered, or fully saturated to one side. The Saitek software isn't running, I've never programmed the rotary to behave this way, and the Windows Game Controllers window shows a smooth saturation through the entire axis of movement. I just don't think DCS likes this particular rotary anymore. :( My rotaries, sliders etc all work perfectly well and have done for many years in DCS. So the problem is not at that end. .. ASUS 2600K 3.8. P8Z68-V. ASUS ROG Strix RTX 2080Ti, RAM 16gb Corsair. M2 NVME 2gb. 2 SSD. 3 HDD. 1 kW ps. X-52. Saitek pedals. ..
ED Team Raptor9 Posted April 21, 2019 Author ED Team Posted April 21, 2019 My rotaries, sliders etc all work perfectly well and have done for many years in DCS. So the problem is not at that end. .. Indeed, as I also stated in my posts above; my Saitek hardware is working fine, so it is a DCS interface problem. Afterburners are for wussies...hang around the battlefield and dodge tracers like a man. DCS Rotor-Head
Recommended Posts