Jump to content

Recommended Posts

Posted

Hi, while using my real simulator force sensing stick and base in the F16 recently, I suddenly stopped getting a response to pitch inputs. 

I have checked within the Real simulator software and in windows and the hardware is working perfectly, also, in the DCS controls GUI, it fully detects the pitch and roll inputs and I can assign these no problem. However, nothing in the jet ( or jets, as this happens no matter which airframe) . I have another stick center mounted for the Hornet etc and this works fine if I assign to the Viper, so I can switch between grips in a flight and it works fine on the centre stick and not on the side stick.

Yesterday, to test the hardware, I installed DCS on my sim racing rig and attached the stick and base. It works perfectly in the other PC.

So the above leads me by process of elimination to the fact that something software related within DCS is preventing the pitch axis inputs from that device only being detected and acted upon within DCS....

What the hell could that be anyone? I have checked carefully to make sure there are no conflicting spurious axis assignments ( although if there were, this should not cancel out the effect of one axis  on the joystick, it would all still work , I would just be getting double inputs....) 

I am really at a loss with this one and while I am sure a complete re install would sort it, I cant face that doing that. Also, seeing as all the controls bindings are in my saved games anyway, these would not be affected.

I am hoping someone who knows the deeper workings of the inputs in DCS might be able to point me somewhere? 

 

Thank you

 

 

 

System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.

CVW-17 Profile Background VFA-34.png

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...