X-45 and cycling combat modes

[gustav]

Hi all. I would like to be able to cycle through all the close combat modes with one button. I know the Saitek software lets you make advanced command so you could hold the button pressed for cycling, but its not really optimal. Anyone have a tip or a workaround?

 

Another fix would be if ED could just assign a key for cycling the close combat modes. Maybe it's to late to ask for this in 1.1 but maybe for the 1.2 version.

 

Thanks!

[britgliderpilot]

Re: X-45 and cycling combat modes

 

Try this for a workaround - map the same button in the different CAC modes to do different things.

 

Lomac lets you program buttons by HUD mode - very useful feature. Go try it.

[gustav]

Hi Brit! Thanks for the reply!

 

Had not checked the input menu out much before so this insight on different inputs for different modes was great. However, i cant figure out how to fix this particular problem as when you choose a combat mode no option to change to another exists in the list.

[Dark_Sceptre]

What he means is that there are separate input mappings for each combat mode. So what you do is to set the button in Nav mode to CAC, in CAC mode you assign it to BVR, in BVR mode you assign it to GND, in GND you assign it back to NAV. That way, 4 presses will take you through Nav - CAC- BVR- GND and back to NAV again.. which presumably is what you wanted.. right?

[Brit_Radar_Dude]

That way, 4 presses will take you through Nav - CAC- BVR- GND and back to NAV again..

Genius BGP :!: I am now kicking myself for not thinking of it, D'Oh!, I have kept meaning to post this very same question myself.

[gustav]

What he means is that there are separate input mappings for each combat mode. So what you do is to set the button in Nav mode to CAC, in CAC mode you assign it to BVR, in BVR mode you assign it to GND, in GND you assign it back to NAV. That way, 4 presses will take you through Nav - CAC- BVR- GND and back to NAV again.. which presumably is what you wanted.. right?

 

Yeah, now i found them. And when i did i first tried to set it up with the joystick buttons but that made me pull my hair out because what should work just didnt. However when i assigned a keyboard key insted there were no problems so now i just assign a that key to a joy-button in the Saitek software and the cycling is a go.

 

Thanks everybody for your input, have had this question in my mind for long.

[Pilgrim]

The best way to use the x45 is to only map y,x-axis, thorttle and rudder. Eventually zoom if it works now. The rest you use saitek profiler for and map keyboard keys to it. I found that mapping in lo-mac setup menu is somewhat flawed. That's why I only have the axis' mapped there and the rest in the profiler. No conflicts :)

[bflagg]

That way, 4 presses will take you through Nav - CAC- BVR- GND and back to NAV again..

Genius BGP :!: I am now kicking myself for not thinking of it, D'Oh!, I have kept meaning to post this very same question myself.

 

AFAIK the saitek software will not allow cyclic keystrokes on one button.

(the press and hold works, but not great)....

 

so I'm confused. How did you cycle keystrokes to one button in

X45? (I use the profile editor only)

[gustav]

That way, 4 presses will take you through Nav - CAC- BVR- GND and back to NAV again..

Genius BGP :!: I am now kicking myself for not thinking of it, D'Oh!, I have kept meaning to post this very same question myself.

 

AFAIK the saitek software will not allow cyclic keystrokes on one button.

(the press and hold works, but not great)....

 

so I'm confused. How did you cycle keystrokes to one button in

X45? (I use the profile editor only)

 

you'll do it within Lomac. Choose teh keyboard and klick "flight" below "KEY COMMANDS", choose flight mode and assign one unused key to wichever mode you want. the latest to the first of course. no great explanation i know, but youll figure it out. the you assign that key ("<" in my case) to a button in your saitek software. no great explanation perhabs, but youll will figure it out. :)

 

did the press hold thing before aswell. this is good, more with 1.1 when more modes than hms will be usefull (with the new autolock).

 

:P

[Brit_Radar_Dude]

Yeah, I spoke too soon, I tried to set this up on a button on my Logitech Wingman 3D and I could only get it to partly work. What happens is that pressing the button will move me on to the next combat mode, but subsequent presses will do nothing more and it seems frozen. If however, I choose the next mode using the keyboard (1->7), then it seems to unfreeze and allow the joystick to operate (once only) again. Wierd behaviour....

[gustav]

remowed :?

[bflagg]

That way, 4 presses will take you through Nav - CAC- BVR- GND and back to NAV again..

Genius BGP :!: I am now kicking myself for not thinking of it, D'Oh!, I have kept meaning to post this very same question myself.

 

AFAIK the saitek software will not allow cyclic keystrokes on one button.

(the press and hold works, but not great)....

 

so I'm confused. How did you cycle keystrokes to one button in

X45? (I use the profile editor only)

 

you'll do it within Lomac. Choose teh keyboard and klick "flight" below "KEY COMMANDS", choose flight mode and assign one unused key to wichever mode you want. the latest to the first of course. no great explanation i know, but youll figure it out. the you assign that key ("<" in my case) to a button in your saitek software. no great explanation perhabs, but youll will figure it out. :)

 

did the press hold thing before aswell. this is good, more with 1.1 when more modes than hms will be usefull (with the new autolock).

 

:P

 

gustav,

So If I got you right, in Lock ON, under input - keyboard, I would

change 1, (nav) 2, (BVR), 3 (Bore), 4 (vscan) to a "<" (for example).

 

then in my saitek software, I would assign only one button to "<".

 

Wouldn't this cause a conflict in Lockon?

(sorry for being dense....)

[britgliderpilot]

gustav,

So If I got you right, in Lock ON, under input - keyboard, I would

change 1, (nav) 2, (BVR), 3 (Bore), 4 (vscan) to a "<" (for example).

 

then in my saitek software, I would assign only one button to "<".

 

Wouldn't this cause a conflict in Lockon?

(sorry for being dense....)

 

In nav mode you would set the command to switch to BVR to <

In BVR mode you would set the command to switch to Bore to <

In Bore mode you would set the command to switch to vscan to <

 

 

. . . . . Seeing it yet?

 

You can only do this because Lomac lets you set a command to a different keypress in different HUD modes.

 

 

I don't know why it's not working with some sticks - I'm pretty sure it works when you use the Saitek software to emulate a keypress with a joystick button.