Thrustmaster Hotas Warthog mapping not working

[operatorone]

Hi there,

 

 

I use a Thrustmaster Hotas Warthog and mapped all keys from the joystick, throttle and keyboard for the F/A-18 sim. When I start a mission only the axes of the joystick and throttle are working. No key bindings are working at all. I can click in the cockpit, but nothing more. Is it an issue of the open beta 2.5.2 or can somebody explain me what's going on and may be has a hint for me to get the controllers and keyboard work properly.

 

 

Cheers,

operatorone

[majapahit]

Mapped to the correct page / aircraft / gameplay .. ?

(chk the dropdown)

[Grodin]

AFAIK there are no default binds for the F-18 yet, it's not yet a final product. You have to map it yourself. See the other topics on the forum for help with mapping :thumbup:

[operatorone]

AFAIK there are no default binds for the F-18 yet, it's not yet a final product. You have to map it yourself. See the other topics on the forum for help with mapping :thumbup:

 

Hi, thanks for your replies. I mapped all my desired key to the right plane F/A-18 arcade and sim on my joystick, throttle and rudder, but can't get any button to work exceptionally the axes. When I want to map the left and right wheel break to the rudders X and Y axis, the axis does not appear when I kick it with my foot. Wired!

 

Well what I recognized is that the arcade profile has a lot less keybindings than the sim of course, but I mapped both, just to be sure I have the right key in place.

 

Cheers.

[bradleyjs]

I have the Warthog Throttle and Stick all works as designed. However, I had some issues initially and had to un-bind all mappings that were interfering with the proper operation. Ie., the F-16 MFDs and Saitek rudder pedals were also bound to some of the controls. Once unbound all worked perfectly.

Edited June 5, 2018 by bradleyjs

[cwarre9]

Hi, thanks for your replies. I mapped all my desired key to the right plane F/A-18 arcade and sim on my joystick, throttle and rudder, but can't get any button to work exceptionally the axes. When I want to map the left and right wheel break to the rudders X and Y axis, the axis does not appear when I kick it with my foot. Wired!

 

Well what I recognized is that the arcade profile has a lot less keybindings than the sim of course, but I mapped both, just to be sure I have the right key in place.

 

Cheers.

 

Check the settings of the axis. I had to reverse mine to get the breaks to work. If you press on the toe breaks, look at your rudder pedals in the cockpit and see if they deflect down like they should.

[BIGNEWY]

Long shot

 

Do you have steam turned on and use a steam controller?

 

I've seen this happen for some, it can be turned off in the big picture in steam and allows other controllers to be used.

[MrReynolds]

I've been slowly making up my target profile and have had some weird issues.

Usually a PULSE for a keypress works (and it does).

However, for some functions I've had to program a press, then release command for the key to work in game. It seems like the button is broken. I think the default pulse is 25ms - setting a release after 100ms works.

 

Totally weird as some pulses work, and others....don't.

[majapahit]

I've been slowly making up my target profile and have had some weird issues.

Usually a PULSE for a keypress works (and it does).

However, for some functions I've had to program a press, then release command for the key to work in game. It seems like the button is broken. I think the default pulse is 25ms - setting a release after 100ms works.

 

Totally weird as some pulses work, and others....don't.

 

I was experiencing the same ‘slow buttons’. ‘Buttons’ are not so much broken, but this is the way F/A-18C interface is coded.

 

F.i. TMWH AP 3-way switch Up, I programmed as A/P ATTH,

 

When simply using TARGET MapKey:

 

CHAIN “Pulse A/P button” (needs extra key binding), “Pulse ATTH button”

 

this gives unpredictable results. Sometimes catches, lot of times not.

 

Then again if one codes a Target CHAIN like actual button pushing. e.g.

the TMWH flip AP 3-way Up ‘PATH’ does:

 

// TMWH 3-way AP - "A/P","ATTH" - (L_CTL+'1',L_ALT+'1')

MapKey(&Throttle,APPAT,CHAIN(

DOWN+L_CTL+'1', // A/P

D(111),

UP+L_CTL+'1',

D(111),

DOWN+L_ALT+'1', // ATTH

D(111),

UP+L_ALT+'1'

));

 

which does

‘UFC A/P’ down, 111msec, ‘UFC A/P’ up, 111ms, ‘UFC Options button 1 Down’,111ms,‘UFC Options button 1 Up’

 

This works properly (as good as one manually pushing the buttons in the A/C)

 

BTW. The actual A/P sequence would also involve UFC "On/Off" but this appears to be either broken or not implemented in the present F18 pre-release