Key Assignment Hopes, among others.

[Afterburn]

A few of my wishes:

 

1. For any rotary dial (e.g. CMSP OFF, STBY, MAN, SEMI, & AUTO), I would propose adding two mappable commands, one to increment and the other to decrement the rotary control. This would allow someone to map two buttons on an input device and control a 5-way rotary switch (usually requiring 4 rotary inputs or 5 momentaries to work).

 

2. Add a button to the key assignment dialog box so you can clear the existing assignment AFTER you open the assignment dialog. Can't tell you how many times I've opened the assign dialog only to remember I didn't clear the old command... :mad:

 

3. Modelling of the open/hold/close canopy switch in controller assignment. I was greatly disappointed when I purchased an (on)-off-on toggle, drilled my enclosure, wired it up, and found I could only assign a single canopy open/close button. It became a L/G toggle :doh:.

 

4. Adding the functionality to assign a key assignment as a toggle switch, as opposed to momentary, within the UI. I'm capable of editing the LUA as much as the next guy (or gal) but a simple check-box that has the software do it behind the scenes would be AMAZING.

 

5. Maybe this is already done. I only got DCS:BS recently and haven't had a chance to try it. But...I want to be able to buy the modules for the aircraft and be able to select which one I fly within a single UI (like load A10 and select the KA-50 as my machine of choice).

 

6. AT-802U :music_whistling:

 

All joking aside, I'd buy it. Esp if I can control it in SP (I'm not much of a MP pilot...yet). I love my FSX GA planes. This would obviously be different (as it can be armed) but I see no reason I would like it any less than GA. Crop dusting will be the least of my enemy's worries:joystick:

 

It's been great! Keep up the good work, ED!

Edited September 13, 2011 by Afterburn
Got my numbering scheme wrong...

[Burnett]

Hi ED

 

I really need to be able to assign the logitech g940 stick POV hat axis to the trim function of the dcs a-10c.

I've heard the "its not there because the real aircraft blabla.."

I did not design this stick, but I want the option to map it as close to the real stick as possible.

just like the "hotas slew" function axis, a trim axis would be great.

[cichlidfan]

Hi ED

 

I really need to be able to assign the logitech g940 stick POV hat axis to the trim function of the dcs a-10c.

I've heard the "its not there because the real aircraft blabla.."

I did not design this stick, but I want the option to map it as close to the real stick as possible.

just like the "hotas slew" function axis, a trim axis would be great.

 

I may be way off here but I do not believe trim is an axis in the RL aircraft. Four distinct switches is the way it seems to act for me. Either way though, why would you need it to be an axis to assign it to four points on an eight way hat. I don't have that stick but I can't imagine not being able to do what is needed to map the four trim commands to it.:)

[159th_Viper]

I may be way off here but I do not believe trim is an axis in the RL aircraft....

 

Nope - you are quite correct.

[Burnett]

The G940 stick POV hat is not an 8-way hat. its an axis or slider, which cannot be assigned to trim in the current state of dcs a-10.

DCS A-10c is not a real aircraft, but a simulator.

there is no Pause in the real aircraft, but there is in the sim.

 

What I would like in this sim is the ability to map this axis to the trim function.

[cichlidfan]

DCS A-10c is not a real aircraft, but a simulator.

there is no Pause in the real aircraft, but there is in the sim.

 

What I would like in this sim is the ability to map this axis to the trim function.

 

Very true, and this is a wish list.

 

I was just confused by this part.

 

...but I want the option to map it as close to the real stick as possible.

Disregard previous post.:D

[Dimebag]

If you really want to use the Ministick as a trim pad, why not assign zone function commands for the x and y axis of the Ministick with elevator trim nose down as +y, nose down as -y, trim left as -x and trim right as +x? There is no reason why that shouldn't work. The only problem then is you need to move the axis everytime you want to trim, can't NSF click a button. Don't forget to add atleast 15% deadzone for the Ministick (I do it in game) because the Ministick is very touchy. All you sacrifice that way is an analogue trim function, which I can tell you from experience, sucks ass anyway.