Inconsistent Elevator Trim Mapping Results Bf-109G2 + Bf-110E2

[JG1_Lipfert]

Kameraden,

 

I am direct button mapping, no SST software profile running. I program the Bf-110E2 Pitch Trim Up Hat 2 = Nose Down and Pitch Trim Down Hat 2 = Nose up and it works perfect with good fine control.

 

Switch to Bf-109G2 and Hat 2 does not work, the only way I can get trim to work is program a Rotary Axis. I do not like this method because the in cockpit display counter does not correspond to the screen pop up indicator. Meaning 0 (cockpit indicator) does not equal 0 (screen display) [unless +2 is 0?] after use and it's really confusing. On top of that I would like it to be consistent across various aircraft with HOTAS mapping.

 

Any idea what I'm missing here? Should I be looking at Stabilizer up / down same as the 190 instead?

 

S!

Edited April 13, 2016 by II./JG1_Lipfert

[Retnek]

Sorry, I have to warm up that topic again. Re-organizing my settings I stumble into the problem Lipfert described above. Found one other message pointing on that problem,too:

 

https://forum.il2sturmovik.com/topic/27123-109-water-rad-cant-assign-any-button/?hl=stabilizer+axis+button

 

Same here now - but why? Is it just a rare problem under certain circumstances or do all the pilots in planes with "stabiliziers" (Me 109, Mc 202, Ju 52) accept there is no way to assign buttons to that function? Those legions of 109-drivers all have a slider/rotary for that function available, really?

 

I'm able to move the "stabilizer" assigning it to (any) rotary, slider or axis. But no key strokes or any peripheral buttons do work. I assigned my usual vertical trim-buttons - works additionally for the Fw-190-stabilizers, too. But not for the "stabilizer"-function. Tried extra keys and buttons not used for anything else - no joy. So is this a rare bug or do all the people accept there is no way to vertically trim some planes except assigning an axis?

[=EXPEND=Tripwire]

I currently use buttons fine for stabilizer. Just push and hold? I set it to the same buttons as trim up/down.

[Retnek]

I currently use buttons fine for stabilizer. Just push and hold? I set it to the same buttons as trim up/down.

Thanks for the feed-back! So it is possible in general and might point to a (rare) bug special for my set-up ...

[Sokol1]

Is possible use a HAT up and down for trim (nose up or down) all planes of the game.

 

The OP mistake is that he don't map  HAT Up and Down for "Stabilizer Adjust"  - command that accept keys, axis or joy buttons:

 

 

He map their HAT 2 only form "Pitch Trim", so no way to work in Bf 109, Mc 202...

 

I program the Bf-110E2 Pitch Trim Up Hat 2 = Nose Down and Pitch Trim Down Hat 2 = Nose up

Edited February 8, 2018 by Sokol1

[Retnek]

Thanks for looking into it, too, Sokol! One of your posts dealing with USB-numbering troubles gave me a direction to go - you pointed on two files:

 

...SSD\IL2BoS\data\input\current.actions

...SSD\IL2BoS\data\input\current.map

 

and there was a difference.

 

"current.actions" knew a "joy6", the new Mongoost - as "joy6" it showed up during the set-up for axis and buttons, too. But "current.map" didn't know any "joy6", but a "joy3" with exactly the same settings given in the file "current.actions" for the "joy6". "current.actions" didn't knew "joy3" at all, in the "devices.txt" the number "3" was given to the virtual joystick injecting iPad-buttons into windows (see https://forum.il2sturmovik.com/topic/31392-custom-control-pad-app-ipad/). However, those numbers were confused, it smelled wrong.

 

I did a backup and used trusty notepad to replace the expression "joy3" with "joy6" in the "current.map"-file. And here we go - I was able to move the Me109/Ju52/Mc202-stabilizer with the same buttons I use for trim and the Fw-190-stabilzer! Nice, BUT ... trying to assign new buttons to the trim-function the re-numbered "joy6" now became "joy4" in the "current.map"! Somehow this file uses other variables for the same joystick than the file "current.actions" does. And now the buttons did not work. Re-numbered them again manually - everything is fine. Sadly no trustworthy solution.

 

Looks like I finally confused Il2-BoX with all those different USB-devices ... hopefully I'm able to solve it via re-installing the current USB-devices. Would be some hours work to reset it and assign all the buttons from scratch.

 

That's the content of "devices.txt":

---------------------------

configId,guid,model|
0,%227dbaf2a0-4f84-11e6-0000545345440980%22,Mad%20Catz%20Pro%20Flight%20Rudder%20Pedals|
1,%227dc15b40-4f84-11e6-0000545345440b80%22,Pro%20Flight%20Yoke|
2,%227dc15b40-4f84-11e6-0000545345440a80%22,Mad%20Catz%20Pro%20Flight%20Throttle%20Quadrant|
3,%22ba6960b0-9fd8-11e7-0000545345440480%22,CCP%20Controller|
4,%220959f380-094a-11e8-0000545345440180%22,X52%20H.O.T.A.S.|
6,%22dec67c20-0a88-11e8-0000545345440180%22,VPC-MongoosT-50

---------------------------

 

Here's my intended setup as shown in the GUI:

 

 

 

 

[Retnek]

Hm, I think I know the reason, it was right here. Looking at the "devices.txt" there is my old Saitek-yoke with the number "1". The yoke wasn't attached for a while now, a zombie-device? Using notepad I deleted just that line and saved it. (backup before, sure)

Now my little world is in order again. I'm able to re-configure and all the joystick-designations /-numbers are consistent within all files.