HOTAS without multiplier

[Mr_Burns]

I have a Hotas Warthog, using a profile from @GrEaSeLiTeNiN (thank you).

I have a crap memory.

Its not the profile, but I get some odd behaviour with using a multiplier, are there enough buttons on the Hotas to have it operate the same as the jet without a multiplier?

I want to try without, probably also the only chance I have of remembering them all as I have a crap memory, have spare keyboards I could mark up with stickers for additional controls.

It maybe this F-15E is a beast, I couldnt learn A-10CII due to the extraordinary number of HOTAS controls so want to keep it simple.

I have a crap memory

[GrEaSeLiTeNiN]

I think for the pilot, the warthog hotas should be enough as the modifier layer was added for additional convenient commands like kneeboard or external views, which you can ignore. But for the WSO, with 4 devices in the back seat, a modifier is needed unless you have another device like a gamepad or something. Or, if you decide to not ever fly the jet when working as WSO, you can remove the WSO hotas (flight) commands and focus on mapping the warthog for just the L/R hand controllers. I think later on they will add more AI capability to the pilot.

Just to check though, are you using the old button slew in the warthog throttle as modifier like in the profile? (If so, did you unmap the axes and any other existing bindings?)

With so many modules, I often fly with a jpeg of the module's hotas layout in the background (Alt+TAB) for a quick reference if needed.   

[Lace]

I do a lot of my DCS flying when travelling overseas and use an XBox controller.  With some clever mapping you can still do a lot of what is required even with a limited number of inputs.  My approach is to not worry too much about the terminology used - this varies aircraft to aircraft, but the functionality is largely the same.  Try to have as much commonality as you can between modules and it will help you remember what you need to press and when.  For instance, all TGP have a zoom function, and designate/undesignate function.  They will probably have polarity swap and other functions which are less commonly used - consider whether you actually need these mapped to the HOTAS.   Try to keep it to the basic, essential functions only.  Normally you'll need to fly through a few different scenarios to find out what you do actually need to use regularly via the HOTAS, and what you can setup prior to the merge/attack run.

Use one modifier for non-aircraft functions, like changing views, zooming, etc, and keep it separate from the aircraft functions, and again, keep it common across all modules.  

Pre-made profiles mean you have to learn someone else's interpretation of the workflows and memorise their assignments.  Develop your own and you will find them much easier to understand and recall when needed.

 

[Mr_Burns]

23 hours ago, GrEaSeLiTeNiN said:

I think for the pilot, the warthog hotas should be enough as the modifier layer was added for additional convenient commands like kneeboard or external views, which you can ignore. But for the WSO, with 4 devices in the back seat, a modifier is needed unless you have another device like a gamepad or something. Or, if you decide to not ever fly the jet when working as WSO, you can remove the WSO hotas (flight) commands and focus on mapping the warthog for just the L/R hand controllers. I think later on they will add more AI capability to the pilot.

Just to check though, are you using the old button slew in the warthog throttle as modifier like in the profile? (If so, did you unmap the axes and any other existing bindings?)

With so many modules, I often fly with a jpeg of the module's hotas layout in the background (Alt+TAB) for a quick reference if needed.   

I changed the multiplier to the finger paddle on the stick, force of habit thats always been my multiplier and i find it pretty solid, took a bit of modifying the profile but when you change the multiplier DCS highlights everything in the control menu with an ! so you can see the ones to change.

I actually think its user error and misreading all the commands on your PDF, there is a ton of things and learning to fly whilst learning the controls is hard work. I will probably stick with it, I should probably print more versions of the control printout and mark them up for each lesson, I think I am just overwhelmed at the moment!

 

I dont know about flying wizzo, I probably would if I knew the AI pilot was good, havnt tried it.

22 hours ago, Lace said:

I do a lot of my DCS flying when travelling overseas and use an XBox controller.  With some clever mapping you can still do a lot of what is required even with a limited number of inputs.  My approach is to not worry too much about the terminology used - this varies aircraft to aircraft, but the functionality is largely the same.  Try to have as much commonality as you can between modules and it will help you remember what you need to press and when.  For instance, all TGP have a zoom function, and designate/undesignate function.  They will probably have polarity swap and other functions which are less commonly used - consider whether you actually need these mapped to the HOTAS.   Try to keep it to the basic, essential functions only.  Normally you'll need to fly through a few different scenarios to find out what you do actually need to use regularly via the HOTAS, and what you can setup prior to the merge/attack run.

Use one modifier for non-aircraft functions, like changing views, zooming, etc, and keep it separate from the aircraft functions, and again, keep it common across all modules.  

Pre-made profiles mean you have to learn someone else's interpretation of the workflows and memorise their assignments.  Develop your own and you will find them much easier to understand and recall when needed.

 

Thats a good idea, I picked up greases profile as I knew nothing about the jet and do have a few favorites from A-10C and F-18 which does confuse me, ie. the castle to select soi rather than the one under the pickle button.

 

Hrmmm, thanks guys, food for thought that I could compromise for single player from the front seat.

[Mouse_99]

Referring to your "crap memory", I generally use Google sheets to list my controls for my HOTAS (I have the Winwing F-16ex stick and Orion 2 Throttle with F-15e grips) I fly about 8 modules and I have your crap memory also. I also printed out the control diagrams to identify the different numbers for the switches and buttons, that way, I can have a print out of the Controls and diagrams in front of my keyboard (I fly 2D) if your VR, I can't help you there. Since I fly many aircraft, I do my best to make most normal controls the same for each and then it's cheat sheet time for the unique controls for the aircraft. Hope that helps a little. ;)