Mapping

[MoToad]

Just bought the IL2 Moscow. Excited to get into it but am having a problem mapping my new T.16000M. It's really unclear what columns are for mouse and what are for stick in the control setup. Nothing written at the top. A bit lame. So, the first column is the keyboard and the second mouse or my stick?

[BOO]

There is no specific column. You can map what you want where. 

[=TBAS=Sshadow14]

yeah you can have 3 diff joy axis in there or 3 diff keys or both mixed.

I deleted all default bindings then First column is primary action/buttons 2nd is secondaries and 3rd is for mass bindings.

Eg i have a mass key binding Ctrl+Shift+I for WoL where 1 press
Starts engine,
Opens cockpit window
Turns on all lights
Sets Altimeter to AF elevation
Resets Trims
Disables Bomb Fuse

[MoToad]

WOW! Sure do like the DCS setup a whole lot better than this one. Deleted everything and programmed what I THOUGHT was right. Eg; the stick axis. I go into a quick mission and throw the stick left and the plane goes right!. Crashed pretty quick. Did notice when I tried to input axis I pulled left on the stick and got nothing but when I shifted right I got an axis. Thought it covered both left and right. Guess not. 

Anyhoo... I set everything to default and am observing and picking carefully. 

But here's a thought ( and any imput would be appreciated). Since I bought the new T.16000M I have been wondering about my USB setup. I found inputs were barely working at first so I switched from my 3.0 port to my 2.0 port. That seemed to help a lot. The other thing I have is a 10 ft usb extension cable (3.0) going into a 3.0 hub. My computer is out of reach of the controller plugins. Would this effect anything? I am about to buy 2 more extension cables and try those for my stick and throttle, bypassing the hub.

[Sokol1]

You can invert axis response in controls be clicking in the curved arrow, when this is highlight the axis is inverted, or can test their movement, set deadzones, S courve by click in the graph icon.

 

The best way to set controls is, start a QM with plane on ground, engine off, hit ESC, goes to Keypaming and adjust, hit OK, back to game and test, if need hit ESC again and re-assign, rinse and repeat.

 

I find the delete defaults assignments and do in my the best option - but this implicates that you know every plane needs in controls, and be able to "translate" some enigmatic controls names in game GUI. 

 

Use long cable extensions is not good idea, today sticks and mobo USB ports already are problematic with default cables. 

Edited February 13, 2017 by Sokol1

[MoToad]

That's what I have been doing, So. QM, pause, adjust and so on. Have been wondering about setting the curve, deadzone, etc. Is there any generic start point?

[Sokol1]

In principle you should not use this 2 adjust, because this adjust taking from joystick control response and not adding, but in some cases is need for minimize joystick deficiencies.

 

If you feel that don't need, leave as is.