@drtbkj:
Pranne, to be completely honest, I took one look at TARGET and said “no way, Jose!”. Seriously though, my programming is 100% TARGET-free. AL is just a more comprehensive, better functionality version, of the regular BMS IU. I don’t know if TARGET would override AL, or vise versa. Since it’s sounds like you have a TARGET profile set, I can understand why you may not want to start over with AL.
If I may suggest, try this-Take something benign, like external lights toggle. Remove it from your TARGET profile, and reprogram it via AL .IF it works, then you know you can “spot program” what you want. Then , you can address your cursor issue how you want to, and the rest of your profile remains intact.
Sidenote: I have noticed that AL does override the regular UI, in things like Axis’, which makes sense. It may try to override TARGET. So, what I do is use the Launcher part of AL only after I’ve changed something. Go in one time, then exit BMS, then reenter via the regular BMS Launcher. Or, try launching from AL after checking the box in AL to “launch without override” . Either way, BMS saves the changes you had made on that first entry. The former is how I work around the one issue I’ve had with AL. When I set the throttle axis(s) via AL, they seem to lose calibration. I’ll be in the middle of a mission, and one throttle in my Hornet will be at 100%, one at another value. I had the same issue with my Saitek HOTAS, before it died.
So, my work around is to leave the AL throttles unprogrammed, go into BMS using the regular launcher, then set them via the regular UI. The “z rotation axis” is the left throttle, and the “z axis” is the other.BTW, with that set up I have no problems in the Viper, either.
Ok thanks….i have to invest some time into this.
This TARGET is somewhat…my first idea was to “modify” something in this morphine profile, but the target software let my run it, but not open and modify.
Maybe its better for a beginner like me to setup a my own style.