Aces High Bulletin Board
General Forums => Wishlist => Topic started by: Pollock on August 08, 2012, 07:34:24 PM
-
For those of us using the throttle having single command button mapping would be great.
This would make full use of all the cool toggle switches and levers on the throttle examples:
engine on, engine off, doors open, doors close, landing gear up, landing gear down.
While we are at it how about adding button mapping for flap controls example:
flaps fully up, flaps 25%, flaps down 50%, flaps down 75%, flaps down 100%.
With these examples it would provide button/switch mapping for virtually everything even common dot commands.
-
I don't understand why you're asking HiTech to implement something like this. You'd be better off asking Thrustmaster to update their programming software to allow this, if it's not already a function in the software.
ack-ack
-
I don't understand why you're asking HiTech to implement something like this. You'd be better off asking Thrustmaster to update their programming software to allow this, if it's not already a function in the software.
ack-ack
Well for one reason the Thrustmaster target software is absolute crap and Guilemot support is just as bad. It would be easier for it to be added in the game, and with more and more subscribers adding sophisticated controllers I don't think I am alone in wishing for this.
-
Well for one reason the Thrustmaster target software is absolute crap and Guilemot support is just as bad. It would be easier for it to be added in the game, and with more and more subscribers adding sophisticated controllers I don't think I am alone in wishing for this.
It wouldn't be easier for HiTech to do Thrustmaster's job for them as it's not HTC's problem or product. If you want that functionality for your joystick and the current programming software doesn't have the features you want, take it up with Thrustmaster.
ack-ack
-
Trolling wishlist ackack .... Classic ... Deposit your 25 cents here
-
I was going to use a piffy remark to respond to you ack ack, but I don't prefer to feed a troll.
This feature would benefit more than just thrustmaster users, anyone who is using a programmable stick or building a simulator like me. Again the topic of this category is "wish list". So this is what I wish for. Maybe I will contact Dale directly and ask him what his quote is to add this and a couple of other features that would be nice. A case of his preferred poison at a minimum.
-
Ack Ack isn't trolling. He's right. You're basically asking HTC to do thrustmaster's job in supporting their hardware. The game is VERY accomodating for almost anything you could wish for.
There are only so many buttons to go around, and having gear toggle on 1 button instead of gear up on 1 and gear down on 2, is a good thing. I have rocker buttons on my throttle quad, and I map them to different but related things. For example, gear toggle is mapped to the up-press of one rocker switch, and gear brakes is mapped to the down-press of it. Map zoom in and map zoom out are the same. Flaps up and flaps down another.
I think having HTC break up every "toggle" into the separate elements would simply lead to an unfriendly list of commands to scroll through when you're trying to set up your controls. For the most part, only a very small minority would make use of it, as well.
So, overall, outside of your VERY specific issues, it wouldn't help much if at all.
-
For those of us using the throttle having single command button mapping would be great.
This would make full use of all the cool toggle switches and levers on the throttle examples:
engine on, engine off, doors open, doors close, landing gear up, landing gear down.
While we are at it how about adding button mapping for flap controls example:
flaps fully up, flaps 25%, flaps down 50%, flaps down 75%, flaps down 100%.
With these examples it would provide button/switch mapping for virtually everything even common dot commands.
You need to learn mapping for one, I have everything listed mapped on my Warthog, simply learn to actually map it out and you will be fine. I have engines on off, doors open closed, gears up and down, flaps up and down.
Everything that's needed from engine start, gears, flaps, bomb bay doors is mapped on the throttle end, as well as wep, stick wise I have a few other things.
In all I have every button in use on the warthog mapped in game to a specific function.
Except for the Flaps, not sure where you think we need 4 buttons for flaps, but on the Warthog there is a flaps button for UP or Down, instead I have it mapped as my thumb button on the Throttle, flaps button are for bomb bay Doors.
-
First, don't lsiten to Ack and Krusty trolling in this forum, if they're not being of any help they're contradicting themselves like usual in their posts (AH is probably the most accommodating game so HTCs clearly has a history of throwing his hands up when it comes to the matter of being accommodating... :confused: :D ). Anywho...
Now, reading your post, are you aware that AH allows you to map all these function to your controller (or should)? See Butcher's post and the Help & Training forum for assistance in learning to map and configure your controller in-game. If you are using (in addition to basic drivers) any third-party software provided by the manufacturer or somebody else this may be unnecessary or causing a problem as AH usually supports most devices directly.
If not then you may have outdated drivers, your controller may not be hooked up (or defunct), or your version of AH is 5-year out of date. If those are not it then it is possible that your unit is so brand-spanking-new that AH does not support or recognize it, in which case you would ask HTCs to look into providing support for it. It's not one or single-button though, ingame you need to select the device, and then configure each button to what you want (maybe a 2-4 step process per button). It's not the easiest method I've seen (IE: where you select the function you want to assign and then click that button on your controller and it's set to it) but it's pretty easy. Aces high does have maybe the most functions one could choose from to map, so if you can't or haven't found what it is you're looking for, just ask for a little help with it.
-
Babalonian, once you open the "Map Controllers" panel and select the stick, if it is not already selected. Double-clicking on any of your stick buttons will highlight the button you pressed AND open the command list window.
Select the command, hit "Okay" and move to the next button on the stick.
-
I think Pollock is asking that in addition to the engine toggle button for example,there is also an engine on button and an engine off button. It is simpler just to map the engine toggle to 2 switches, then the on switch will start it and the off switch will stop it. The fact that the reverse is also true shouldn't be an issue.
-
Babalonian, once you open the "Map Controllers" panel and select the stick, if it is not already selected. Double-clicking on any of your stick buttons will highlight the button you pressed AND open the command list window.
Select the command, hit "Okay" and move to the next button on the stick.
New to me, Ill check it out.
Personaly I still think the process is "easier" when starting at the command you're trying to asign (after finding it on a list) and then trigering the button you want that function to be assigned to - rather than starting with the button/trigger and then scrollign through a list.
-
I think Pollock is asking that in addition to the engine toggle button for example,there is also an engine on button and an engine off button. It is simpler just to map the engine toggle to 2 switches, then the on switch will start it and the off switch will stop it. The fact that the reverse is also true shouldn't be an issue.
Possible, didn't think of it like that. Didn't one of the updates in the last year include a "flaps full up/down" option? (or maybe that was trim...)
The flaps at 25/50/75% wouldn't work with the game I think, too many differences. IE: the mustang has I think 5 or 6 positions (0/20/40/80/100%), the 190s only has 3 (0/25/50/100), spits have all or nothing (0/100).
-
Apparently people don't know what trolling is, and throw the word around inaccurately. :rolleyes:
-
I think Pollock is asking that in addition to the engine toggle button for example,there is also an engine on button and an engine off button. It is simpler just to map the engine toggle to 2 switches, then the on switch will start it and the off switch will stop it. The fact that the reverse is also true shouldn't be an issue.
Actually, you kind of have that. You can map the toggle command to two buttons, if you want to use two buttons to control the engine. You just have to know which button you pressed last. If this is for some type of cockpit, put an LED on the switch you pressed last.
Ta-Da! And BOING! Another wish fullfilled,....sort of.....in a sideways manner.
-
Problem as I see it working an AH toggle function off a toggle switch is that the toggle switch retains the output.
i.e its equivilent to holding the button down all the time.
if you can program your toggle(via game controller software) to give a fleeting out put then this can be over come.
As Skuzzy said if you then cause the toggle to give the same out put(G for gear) in the up and down position then you could use it accordingly.
However I would advise you disable auto take off as this raises the gear automatically and would leave you out of synch.
Toggle switches are very usefull for bombsight calibration where the button has to be "held down" I use a 3 pos toggle function witht he centre position left blank.
-
Actually, you kind of have that. You can map the toggle command to two buttons, if you want to use two buttons to control the engine. You just have to know which button you pressed last. If this is for some type of cockpit, put an LED on the switch you pressed last.
Ta-Da! And BOING! Another wish fullfilled,....sort of.....in a sideways manner.
Give the man a cookie! If you reread carefully you'll see I said the same thing. :aok
-
I understand what the OP is asking for, the difference is in what happens when you start flight.
A switch functions differently then a button, It must be in a correct position with start flight to work with a toggle,but it requires to different functions to work properly.
1 to start engine, one to stop engine. Other wise the switch must be in the correct position to act as a toggle.
And that functionality, can not be coded into any controller software, it must be in AH.
HiTech
-
The Warthog has four 3 position toggles switches. Two of them, marked IGN/Motor Left and Right are momentary in one direction and are ideal for selecting and starting/stopping the left and right engines. I use the APU toggle to select all engines after starting. You could also use them as gear up/down switches etc. I'm not saying it's a bad wish, just that you can already use all the buttons and switches on the Warthog without splitting toggle functions into up and down.
-
Actually, you kind of have that. You can map the toggle command to two buttons, if you want to use two buttons to control the engine. You just have to know which button you pressed last. If this is for some type of cockpit, put an LED on the switch you pressed last.
Ta-Da! And BOING! Another wish fullfilled,....sort of.....in a sideways manner.
Sorry I have not gotten back sooner to the replies of my wishlist request. Again the section is wishlist so I simply posted what I wish for. I did not know that Kristy and back back were here to contradict a wish, silly me.
Scuzzy thanks for replying. The reason I was asking for this was to have an exact command for each position, that way from feel without looking and by touch I will know what state that control is in. I have already mapped all controls to my stick and throttle.
Let me plead my case one last time. Some of the switches on thrustmaster warthog are hard positioned that lock in the up or down position. I think they call them single pole double throw. For this type of switch to have the option in mapping controllers to a definitive on and off would work.
Example for landing gear control from 1 toggle switch up position "gear up", down position "gear down". To do this in the controllers software may or may not be possible, if it is possible it would take a series of key strokes to train the switch to activate the command
(not easy). If this was possible via Aces high in the controller mapping, flick the switch, map the command,save, and close. (much easier).
That is my wish what would it take to make this possible.
-
You are asking for a function that the Saitek controller software has built in. You want Hitech to introduce key combo macros.
If I remember from a few years back this was not received well. With a key macro you can put together a bridge between complex actions that otherwise the real WW2 fighter pilot had to do one action at a time. Like engine management. With your Warthog at face value it would seem like a reasonable solution to a complex irritation. But, in an over view towards general game play, it will introduce a new world of game finessing to allow many to bridge the time between newbie and veteren hot stick.
Then again you could counter with Hitech could write a detection routine to only allows key macro mapping to the Warthog. At that point you would at least shorten the suspect list for HTC to look at when the game finessing complaints come in. Some of your system info including your controller type goes into (sytem.cfg) which I beleive is a snapshot everytime you start up the game that HTC sees when you access the game server.
-
Actually bustr, what he is asking for would require a new set of commands to be done in the game. Right now, no external software can know the state of a toggle and that is what would need to happen in order to use any external software solution to address his request.
-
Actually bustr, what he is asking for would require a new set of commands to be done in the game. Right now, no external software can know the state of a toggle and that is what would need to happen in order to use any external software solution to address his request.
It would not be necessary to know the state. Pre flight launch it would be the pilots job to set the toggles before taxi to take off.
A perfect reason would be you get shot down back in the tower. Now before start up you have to set switches to be ready, that's how
DCSA10 handles it. In DCSA10 within the virtual cockpit you can see the switches change state, which is helpful but not really necessary. I realize this is a wish that only a few would benefit, however the newer high end controllers will have more than momentary buttons and switches.
-
I cannot address that as I am not part of the development team.
My thought was to use a single command to get the state of any other assigned command so external software could be used to do exactly what you want. I cannot say it is possible or if it would be worth the effort to do.
I do not and cannot speak for the development team.
-
Just took a look out on ThrustMaster's page. I stand corrected. Toggle switches. I thought the AirForce had commited itself to fly by wire and push button. Douh...1970's vintage cockpits. At least we don't work flaps with a lever.
-
Just took a look out on ThrustMaster's page. I stand corrected. Toggle switches. I thought the AirForce had commited itself to fly by wire and push button. Douh...1970's vintage cockpits. At least we don't work flaps with a lever.
Before I started using the Warthog I used a saitek throttle quadrant using the saitek programming software I mapped the axis bands to a lever it worked well. Too bad flap control couldn't use axis directly through Aces high. Oops there I go wishing again time to really look at the Target software for thrustmaster it really has its issues even starting up without crashing.