Help -Slew control on the throttle
-
Hello friends,
the slew control on the throttle is hard to use…slewing the cursor is very difficult and somehow inaqurate.
Is there any idea out there how to fix it?
Thanks.
-
Hello friends,
the slew control on the throttle is hard to use…slewing the cursor is very difficult and somehow inaqurate.
Is there any idea out there how to fix it?
Thanks.
Change throttle ?
-
You can change the Cursor Speed in Falcon BMS Config and some other stuff in the Advanced Options of the Controller Page (Cursor X/Y)
-
You can change the Cursor Speed in Falcon BMS Config and some other stuff in the Advanced Options of the Controller Page (Cursor X/Y)
Hm…ok i will try this. Moving the cursor with this small ball is really pain right now.
Thanks.
-
Yep Warthog cursor is worst part of this great throttle. With 4.34 U1 try add this to your “falcon bms.cfg”.
set g_nAxisExp_AXIS_CURSOR_Y 30 // Axis exponential curve. Should be in 0…100 range. 0 is disabled
set g_nAxisSat_AXIS_CURSOR_Y 0 // Axis saturation. Should be in 0…99 range. 0 is disabled
set g_nAxisExp_AXIS_CURSOR_X 30 // Axis exponential curve. Should be in 0…100 range. 0 is disabled
set g_nAxisSat_AXIS_CURSOR_X 0 // Axis saturation. Should be in 0…99 range. 0 is disabled -
Hello friends,
the slew control on the throttle is hard to use…slewing the cursor is very difficult and somehow inaqurate.
Is there any idea out there how to fix it?
Thanks.
Good Day, Pranne. Just in case, there is an alternative. I, too, couldn’t handle the Warthog’s cursor. So, I set up the WH’s “Mic Switch” as cursor using the BMS Alternate Launcher. You can also do it in the regular UI. It works off keypress ,not axis, but it does work. As a side benefit, pressing for cursor enable is very easy.
Before I set up the throttle POV2 for Comms, I had them set up as shifted functions “under” the cursor. That works, too. BTW, if you have Voice Attack, it’s actually fairly easy to set POV2 up as Comms. -
Thanks guys, i will see what works best for me.
-
Someone has felt your pain. I wish I’d had this for my X55!
https://deltasimelectronics.com/
There must be a thread about this somewhere!
-
Well i use Morphines Profile now, but whats the difference between Warthog_BMS_Full_4_434 and Warthog_BMS_Full_5_434?
Too many switches now…i didn´t even know how to switch in AA Mode from Missiles to guns.:(
-
Well i use Morphines Profile now, but whats the difference between Warthog_BMS_Full_4_434 and Warthog_BMS_Full_5_434?
Too many switches now…i didn´t even know how to switch in AA Mode from Missiles to guns.:(
You’ll get there
-
Well i use Morphines Profile now, but whats the difference between Warthog_BMS_Full_4_434 and Warthog_BMS_Full_5_434?
Too many switches now…i didn´t even know how to switch in AA Mode from Missiles to guns.:(
There is no functional difference between the two. Full 4 is just backwards compatible with older versions of target. Going forward I’m dropping support for 4. Try the most recent version from the Dropbox. Older versions of the profile don’t work well in 4.34.
-
There is no functional difference between the two. Full 4 is just backwards compatible with older versions of target. Going forward I’m dropping support for 4. Try the most recent version from the Dropbox. Older versions of the profile don’t work well in 4.34.
Thank you. I have to apologize for my noobishness…with this new stick i have to deal with functions i never used before.
-
Good Day, Pranne. Just in case, there is an alternative. I, too, couldn’t handle the Warthog’s cursor. So, I set up the WH’s “Mic Switch” as cursor using the BMS Alternate Launcher. You can also do it in the regular UI. It works off keypress ,not axis, but it does work. As a side benefit, pressing for cursor enable is very easy.
Before I set up the throttle POV2 for Comms, I had them set up as shifted functions “under” the cursor. That works, too. BTW, if you have Voice Attack, it’s actually fairly easy to set POV2 up as Comms.Just for understanding…you use this one for cursor and for coms, shifted with this pinky switch, is that right?
Second…to i really need coms when flying alone?:-)
Thanks
-
If you have a few euros to spare Delta Sim Electronics offers a great replacement for the microstick on the WT throttle.
All the best, Uwe
-
If you have a few euros to spare Delta Sim Electronics offers a great replacement for the microstick on the WT throttle.
All the best, Uwe
I think this is best idea.
-
Just for understanding…you use this one for cursor and for coms, shifted with this pinky switch, is that right?
Second…to i really need coms when flying alone?:-)
Thanks
Yes, Pranne, that was my set up, at least until I got POV2(the throttle POV) set up for comms.
IMHO, would definately say yes to needing comms. If you fly any campaigns, even with AI wingmen, they have to be controlled. Then you have AWACS calls, approach/landing/departure, the list goes on. Also, again just MHO, but not using comms cheats you out of a fun Immersion Thing.
BTW, Hoover, I ordered the microstick. It sounds like a good thing, and instructions sound easy. At $78, my defination of a few euros may differ from yours -
Yes, Pranne, that was my set up, at least until I got POV2(the throttle POV) set up for comms.
IMHO, would definately say yes to needing comms. If you fly any campaigns, even with AI wingmen, they have to be controlled. Then you have AWACS calls, approach/landing/departure, the list goes on. Also, again just MHO, but not using comms cheats you out of a fun Immersion Thing.
BTW, Hoover, I ordered the microstick. It sounds like a good thing, and instructions sound easy. At $78, my defination of a few euros may differ from yoursI will order that too…should be the better long term solution.
About this reprogramming, iam using this TARGET software…but i have no idea how to edit that profile.
Can that alternate launcher used with TARGET?
-
Can that alternate launcher used with TARGET?
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. -
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.
-
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.
Pranne, one thing that my recent Warthog programming has reminded me of is that there is more then one way to solve an issue in BMS. Don’t be afraid to try your own approach, and the Forum is always ready to help.