Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: fd ski on October 02, 2016, 06:08:04 AM
-
For my birthday ( yes, 18th :D ) I got Thurstmaster Warthog. Need some help with configuration.
I always ( Saitek x45 ) has a view system dating back to WB. Two separate sticksets, toggled using pinky on the stick. And views as follows:
Stick set 1
Hat up - look up
hat back - look back
hat left look left
hat right look right
stick set 2
hat up - up forward
hat back - back up
hat left - left up
hat right - right up
that gave me a full range of vision all around without much thinking about it.
On Warthog hat is situatied very high up, there are two other "hats" however they perform as buttons or combinations of thereof.
While AH recognizes buttons pressed at the same time ( back and left making - left back 45 angle ) and in that are it works, mixing in forward/up view screws things up.
Up ( being stright up ) and left at the same time gives left up view where i'd like to get 45 deg angle to the left view...
Any workaround ?
Also, any suggestions as to how to map all those switches and controls ? Not used to so many of them, however I'd gladly learn. Hotas users, come help newbie please !!! :)
Thanks a bunch,
-
If you want to have more complex button programs try TARGET software that is free from Thrustmaster. With TARGET, the button combinations are just about endless. There are a couple of versions. One is graphical interface that really makes it easy to use.
As you expand your AH experience you will want to try tanks and bombers. The buttons you need will become clear.
Just go through the list of functions in AH.
Here are few of my fighter uses.
auto-climb
auto level
On the p-38 engine selection
RPM
I use the slider for elevator trim
If you join a squad you will need a two radio buttons
flaps
secondary weapon fire for rockets and bombs
weapon selection
mode selection for special setups
call up the clipboard
zoom button
zoom in and out
zoom in and out on clipboard
With TARGET you can even do salvo selection or set a particular climb speed.
-
Happy Birthday! Nice gift! :aok :cheers:
-
Randy1, thanks for info. I was joking about being a newbie and all,check out my join date :)
I sent you a PM , not sure if you got it. If you could send me a config file it would be a great start. E-mail in PM.
Thanks,
Bart
-
I use a warthog and for my joystick hat i have it looking around except pushing it to the 8 position puts my head forward and up to look over the nose as much as possible.
For up/down I use a hat on my throttle.
On the throttle I also have the slider and another hat switch mapped to move pilot left/right.
The momentary toggle switches are set to Auto Climb and Auto Level in the forward position and auto angle and auto wingman in the rear position.
The bottom 3 switches I have mapped to change planes in a bomber formation.
-
Randy1, thanks for info. I was joking about being a newbie and all,check out my join date :)
I sent you a PM , not sure if you got it. If you could send me a config file it would be a great start. E-mail in PM.
Thanks,
Bart
Bart another person's config file is not a good way to start. The reason is you have to set the buttons to match your mindset's priority on your fingers. Sounds strange but my left index finger might have a higher ease of use than your left index finger as an example. Add to that once you make the set you can remember it easier.
-
(https://s22.postimg.org/alqzp7c5t/Full_STick_Map.jpg)
-
Bobo, you have a very busy thumb there! Do you use trackir?
On my CH I have it set up so my right thumb doesn't need to touch anything except the hat during combat. I want to be able to use flaps, talk on either channel, drop gear, hit wep, zoom in, and toggle trim (basically anything I need to do) all while looking any direction.
I use the other thumb switches for things I generally only need while looking forward: weapon toggle, elevator trim, etc.
By all means do what works for you, but I couldn't imagine having to take my eyes off a con to raise or lower flaps.
-
No, waiting for Oculus to drop down to the developer kit prices like they said the consumer model would cost.
Or at least less than $500
-
Bobo, thanks, that looks interesting, you inspired me a little.
As for view system, you went a different path then I did. I guess my hands are too small to use the gray switch for views, for up modifier i use sticksets, to each his own. I was hoping to use one of lower hats for views, however they are actually buttons, hence the question.
B
-
No, waiting for Oculus to drop down to the developer kit prices like they said the consumer model would cost.
Or at least less than $500
Check out Razer's HDK2 (http://www.razerzone.com/osvr). Less expensive than both the Rift and Vive, it's open source so there will much more of a 3rd party selection for peripherals and it's easy to upgrade. When an upgrade comes out, you just purchase the upgrade kit, without having to buy a new VR set. It will also work on any VR game that supports either the Rift and/or Vive.
-
Bobo, thanks, that looks interesting, you inspired me a little.
As for view system, you went a different path then I did. I guess my hands are too small to use the gray switch for views, for up modifier i use sticksets, to each his own. I was hoping to use one of lower hats for views, however they are actually buttons, hence the question.
B
Don't rest your hand on the shelf. Put it where it reaches the view hat easily. If you have trouble maintaining that position put a spacer on the shelf.
-
I would not fly without my TrackIR, it takes quite some time to get used to it, but SA gets so much better.
-
Bobo, thanks, that looks interesting, you inspired me a little.
As for view system, you went a different path then I did. I guess my hands are too small to use the gray switch for views, for up modifier i use sticksets, to each his own. I was hoping to use one of lower hats for views, however they are actually buttons, hence the question.
B
The Black hat that I use for flaps and rudder trim is 8 position so it would work for views.
-
Randy's advice is great IMO, using another player's setup will never feel as right as just setting up your own - you can use them as a general guide, but I've never once stuck with another player's profile and always made my own, or changed theirs if I grabbed it.
One thing I found with the Warthog - I use all the higher end Hotas, have quite a collection now, but typically prefer the CH Fighterstick for AH as it combines the best precision and lightest movement along with decent quality. Using the thumb hat for views, I always used the pinky switch on the bottom of the front of the stick for "look up", so I could combine hat views with look up quickly. Using the Warthog, it's very tough to do this if you have large hands, or even medium hands I'd wager. That same pinky switch isn't on the front of the stick, but angled toward the 11 oclock position making it harder to press without turning your wrist a bit, plus the larger vertical switch/paddle thing if you want to use that instead for "look up" means your pinky is floating in space instead of on the stick. So, using the WH for me meant changing how I had done things for over 10 years when it came out, so far as flying AH went.
I stuck with my CH sticks/throttle for AH as a result, and use the TM and other custom stuff for DCS and other sims where rapid SA/head movement isn't as critical I guess.
I have trackIR too, don't use it as much now that i have VR, but even in AH I always found using thumb hats/buttons faster in close combat than tIR was for me, so I would habitually flip trackIR off whenever I got into a fight. I probably should have just forced myself to stick with trackIR by disabling the view buttons on my stick, but now that VR is out it doesn't matter as much, plus with VR in AH it's back to using the hat system for faster dogfighting view switching anyway.
-
GMan - I wasn't clear enough. My intention isn't coping someone else's setup, i know it is personal. Rather looking for inspiring things one can do with all those bells and whistles that throttle has :) Script that is underneath the configuration could also display some advanced mapping techniques, that's all.
Found something i was looking for:
simhq.com/forum/ubbthreads.php/topics/3429294/New_Warthog_Here_s_the_TARGET_.html
-
FD Ski - That's a good find. However, it's still pretty much advanced for me. The truth of Randy's response rang a bell for me. It helps to have a pretty good use case for each control before you start into TARGET programming.
My Warthog was delivered yesterday. My first look at TARGET was a little daunting, I admit.
Personally, use cases keep me on point while I'm trying to learn foibles and nuances (syntax) of script language outputs.
I think I'm going to have to ratchet down my expectations of quick success and respect the learning curve more. I wish TARGET was easier to visualize. But it's not in my case.
Best of luck on your journey!
:salute
-
I just program in AH. What do you need to do that you need advanced Target programming?
-
ok, played around with target and got it working, basically switched so that DX hat is now a small hat in lower left part of the stick rather then large gray one on top right. That one i can reach easier with my thumb and it works in 45deg directions ( gray one in the middle of the stick is a 4 way not an 8 way unfortunatelly)
FOllowing code added to the script will switch those hats. Make sure not to include the throttle in the profile as to retain two devices and all those lovely DX buttons.
This script also turns old hat ( gray one ) into 4 DX buttons ( from 20 to 23 ) so that they can be mapped for trimmers and such.
script as follows:
MapKeyIOUMD(&Joystick, H2U, DXHATUP, DXHATUP, DXHATUP, DXHATUP, DXHATUP, DXHATUP);
MapKeyIOUMD(&Joystick, H2R, DXHATRIGHT, DXHATRIGHT, DXHATRIGHT, DXHATRIGHT, DXHATRIGHT, DXHATRIGHT);
MapKeyIOUMD(&Joystick, H2D, DXHATDOWN, DXHATDOWN, DXHATDOWN, DXHATDOWN, DXHATDOWN, DXHATDOWN);
MapKeyIOUMD(&Joystick, H2L, DXHATLEFT, DXHATLEFT, DXHATLEFT, DXHATLEFT, DXHATLEFT, DXHATLEFT);
MapKeyIOUMD(&Joystick, H1U, DX20, DX20, DX20, DX20, DX20, DX20);
MapKeyIOUMD(&Joystick, H1D, DX22, DX22, DX22, DX22, DX22, DX22);
MapKeyIOUMD(&Joystick, H1L, DX23, DX23, DX23, DX23, DX23, DX23);
MapKeyIOUMD(&Joystick, H1R, DX21, DX21, DX21, DX21, DX21, DX21);
-
I just program in AH. What do you need to do that you need advanced Target programming?
Teamspeak mike button is the only thing that comes to mind, to answer your question directly.
TARGET should be useful for using a single control to do multiple key strokes...like a single control to open bomb doors - jump in the nose - bring up the E6B - set salvo to 3 - reduce rpm by a notch - and enter calibration. Call the button "Pre-Bomb Checklist". That's what I meant by a use case. Landing configuration might be another one, for example.
But to your point, most folks don't need to bother with that.
I'm going to have to be real fluent in TARGET before I get that far.
:salute
-
Can't teamspeak see the Wathog DX button press?
I understand the point of programming, it's good for text macro's in VR for example, I was just curious what people were doing with it.
-
TS works just fine with DX button.
-
I just program in AH. What do you need to do that you need advanced Target programming?
I use target to buffer program .commands like salvo 6, climb speed, and bomber calibration. I also use it to set functions like wep on the throttle.
I also have hand tremors making a single button press difficult. IN TARGET I can set a delay to compensate.
BTW, the button set for team speak is set in team speak so you make no button assignment in target and or ah.
-
I just use Target to turn the lights down. :D The throttle doesn't remember settings like the MFDs.
-
I'm sure the DX button is fine for most folks. I'm not trying to convince anybody to do what I do. It's just a matter of personal preference. My X55 programs have everything in them pertaining to the HOTAS...including the TeamSpeak mike 'hot button' (which is set up in TeamSpeak) and a command for centering TrackIR.
If that screws up (it never has) I would only have two places to troubleshoot.
For whatever the reason, my early days in Aces High had a large number of stick program problems usually resulting in my sticks being spontaneously un-programmed in the game. I didn't know half of what I do now after 9 years. I know now that I should have been backing up all my settings someplace. It was easier then to solve by programming outside the game. Haven't had a problem since.
It's a personal preference and I certainly respect yours.
:salute