AmimalMother

Hey so after some more experimentation that issue is probably hardware, I am not gonna lie, ever since I got this stick (new) it has always been finicky. For example back in the day when I got it I could never get it to install the drivers on AMD based chipsets, no issues with Intel chipset though. The issue I am seeing is that when I change the axis in CCP to the guide settings (or any other change I make) and select "User Mode" the axis are indeed changed although sometimes the stick becomes unresponsive and I have to reconnect the stick. When it works though and I go to the "Viewer" in CCP I can see the axis switch but the stick behaves really strangely. I guess the best way to describe it is that it loses resolution, with only moving the axis to there maximum will actually register from what I can see in the Viewer. The same happens if I run your script with Target and check the axis through there. (same behavior in game) Have you ever heard of an issue like this? I also tried saving the axis to a profile and make CCP change the settings at startup but the same weird behavior happens. When I said your script never worked with microstick is simply because the stick wasn't in User Mode in CCP, and if I do apply the changes and run User Mode the above behavior happens. Anyways, I am back using Foxy with the axis at defaults so I don't run into the strange issue. I can set the microstick for mouse or key emulation no problems. Back to the Foxy manual it is.

Hi HF, Yeah, I do have CCP installed and it is setup like the guide, see attachment. I dont have rudder pedals attached so axis 6 is disabled. I have also attached a screen shot of the Device Analyzer while moving all the axis. Which should the microstick be here? (combined) In the picture axis Z is the throttle Rx is ANT ELEV, and Slider0 is MAN RNG. I am also holding the microstick button. Ry, Rz and Throttle never move. What should the name of the microstick axis be inside the game? On joy.cpl when the script is running I see the exact same behavior as the Device Analyzer. Without the script running viewing the axis in joy.cpl opens the Thrustmaster tool (I have CCP installed), and you can't see the microstick axis there as far as I know. Thanks for the help.

Hi Home Fries, first of all many thanks for these wonderful profiles. I have been using your profiles for quite some time now, well ever since I upgraded to a Win10 machine. I have a HOTAS Cougar and well I opted to drop Foxy for Target. I am a newbie when it comes to Target. I have set your profiles successfully but there is one thing that I can never get to work, the MICROSTICK on the Cougar to control the TDC. I was able to do it in the Foxy days and I know the stick works but I can never get it to work. (I have set the axis as suggested in the guide) I have seen these two posts regarding the Cougar's Microstick with TDC: https://forums.eagle.ru/showthread.php?t=168075&highlight=hotas+cougar+microstick https://forums.eagle.ru/showthread.php?t=134867 I was wondering if you had any more input with regards to this, since you mention you are Cougar user. Different axis setups are suggested but I can't get either to work. Where should I place the Target code in the posts? When I open the Target script editor axis tester the microstick never works and cant set the axis on DCS either. Hope you or somebody else with this issue is able to help.

MSI GTX 760, I'm planning on getting a 970 soon.

Thanks Charly_Owl! This is proving to be indispensable!

Can anyone point me to a Hotas Cougar foxy profile for the Mig-21?