It comes on a disk in the box with the x52!
Getting use out of those X52 extras (pic hvy)
- Thread starter Calaban
- Start date
Ok, question for you.
I have an X-52 (non-pro) and I've set up the three modes as 1-Land 2-Flight and 3-Combat. I set the Mode 2 "Run on Activate" to include raising the landing gear (for coming out of Land mode.)
Now, when I come out of Combat mode (3) back to Flight mode (2), it lowers the landing gear. How do you handle the landing gear?
Is there any way to run a different macro depending on which mode you're coming from?
Any and all help greatly appreciated.
Don't see an answer to that problem at this time as it not a problem with the controller software.
Its down to the fact that a lot of the games controls are single switch toggles.
IE press "L" to swap the state of the ship lights, doesn't matter what it was before just change them to the opposite state.
With the radar range you have two controls increase and decrease so with a bit of clever programing you can get this to work with the slider.
But until you get a separate on and off button for all the controls you won't be able to make a quick change mode function where your landing gear is lowered and your weapons are retracted that won't in fact do the reverse if you already have them in the state you want.
Its means double the keys needed and would be only useful to a few of us, the only other way around the problem would be to give us an API to the controls and ship state so we can see what is on or off and work from that.
Can't see either happening any time soon.
Don't do it that way. You want to toggle your gear both entering and leaving mode 1, because you can enter mode 2 from either mode 1 or mode 3 so if you toggle gear on entry to mode 2 you'll mess with it when going 3->2 as well as 1->2
Create an "advanced command" for mode 1 (landing) that has toggling the gear (plus whatever other commands you want - mine includes additional keystrokes to ensure that whenever the gear is down I have my lights on and full pips to shields) on "press", nothing in "hold" and toggling the gear (and lights and whatever) in "release". In mode 3 (combat) you'll want to toggle your hardpoints and set up a sensible default power distribution on "press" - again nothing on "hold" and toggle your hardpoints on "release". For mode 2, assume that by the time you get there your gear and hardpoints are already stowed and your lights off. Set up that mode with any extra stuff you only want to apply in mode 2 (my setup automatically sets 4 pips engines and 2 to sys when entering mode 2 and nothing else)
So, entering mode 1 drops the gear, turns the lights on and sets 4 pips shield in case I meet a drunken CMDR (or am one) in the slot. Leaving mode 1 turns off the lights and retracts the gear.
Entering mode 2 (whether from mode 1 or mode 3) sets power 4 pips engine, 2 pips sys
Entering mode 3 deploys hardpoints and sets power for rolling into a fight
Leaving mode 3 retracts the hardpoints
Nice programmers way round the problem. Doesn't overcome the problem of not knowing what state the controls are in, but if you start in the correct mode at least it will do what you expect.
Have a rep point on me
Right, and it's important to have the keystroke for any toggles be something sensible you can remember because if the stick does get out of sync with the game (eg, you got popped and didnt remember to roll the stick into "landing mode" before taking off in your replacement ship) you can reach for the keyboard and quickly stab the key(s) to get things back in sync.
Given that in any case where you want different functions in different modes at least two of them have to be keystroke-based and you can only use keystrokes, not button presses, in X52 macros I've always found when setting up a new profile for any game it's best to start with the game set for keyboard control, customize the in-game bindings so they are intuitive for me (with no consideration for ergonomics - I want to remember what key to press, not have them nicely grouped under my fingers) then create all those keystrokes as named commands in the profile, assign those to buttons (and use them as a reference in creating macros) then go into the game and add bindings for the axes only.
The 6P principle definitely applies if you want to get the most out of this stick!
Thanks, that was the bit I was missing. I hadn't realised mode switches had a "release" action that happened when switching away. I thought it was a leftover from all the other buttons. Now I can fix my stuff and feel even cleverer about splashing out on a HOTAS setup.
Another bunch of profiles, keybindings and instructions e-mailed out. let me know if anyone has any questions.
Will be updating for Beta 2 in case there are any new bindings. I will be creating 2 separate sets, one for those with energy weapons on primary, and those with kinetic... once I get the time.
Will be updating for Beta 2 in case there are any new bindings. I will be creating 2 separate sets, one for those with energy weapons on primary, and those with kinetic... once I get the time.
Thanks for this Post!
I've been thinking, ok, pinkie will not work, whatever.
But it seems you solved that. Thx.
I have Windows 7 64bit and the 7.0.27.13 Drivers and Software.
My MFD shows only "Welco" instead of "Welcome Cmdr".
If i try other Namings it will only show 2 Letters or so. "El" instead of "Elite"
Anybody have this problem too? And an fix for that?
I've been thinking, ok, pinkie will not work, whatever.
But it seems you solved that. Thx.
I have Windows 7 64bit and the 7.0.27.13 Drivers and Software.
My MFD shows only "Welco" instead of "Welcome Cmdr".
If i try other Namings it will only show 2 Letters or so. "El" instead of "Elite"
Anybody have this problem too? And an fix for that?
Last edited:
At the risk of sounding repetitive - for those that have pm'd me for copies of my profile - you have mail!
I'd be interested in feedback from anyone who has had profiles set up much as the descriptions are above and sent out by me are faring - are there any good changes that you've made?
For my own use, I've made some newer modifications. The main one has be to have two different profiles, depending on whether I've got energy or projectile weapons as my main.
I've noticed that now that we have the discovery scanner, switching to the combat mode in supercruise allows me to fire the scanner using the pinkie for 2nd fire group and then switch back to flight mode to drop out as needed.
Having the energy balance under that left wheel is working well for me to make fine adjustments to the spec, as are the reverse and faoff buttons under the left hand. the slider for the radar is working reasonably well, though not ideal.
Got the big rotaries for the cargo scoop deployment and the second hasn't got a plan yet.
All in all, my hands never need to leave the sticks (at least not until I'm in galaxy map screen - working on that one at the moment).
I'd be interested in feedback from anyone who has had profiles set up much as the descriptions are above and sent out by me are faring - are there any good changes that you've made?
For my own use, I've made some newer modifications. The main one has be to have two different profiles, depending on whether I've got energy or projectile weapons as my main.
I've noticed that now that we have the discovery scanner, switching to the combat mode in supercruise allows me to fire the scanner using the pinkie for 2nd fire group and then switch back to flight mode to drop out as needed.
Having the energy balance under that left wheel is working well for me to make fine adjustments to the spec, as are the reverse and faoff buttons under the left hand. the slider for the radar is working reasonably well, though not ideal.
Got the big rotaries for the cargo scoop deployment and the second hasn't got a plan yet.
All in all, my hands never need to leave the sticks (at least not until I'm in galaxy map screen - working on that one at the moment).
I just want to thank Vingtetun for good work and for sharing his profiles. However I can't test them properly.
The biggest problem at the moment is with mode switching. Macros seem to be stuck in a loop and in extreme situations Saitek software is causing BSOD on my system. I like the concept and I can see true potential in using external profiles but at the moment it's useless to me because of buggy software.
Anyone had similar issues?
I'm on Windows 8.1 64bit.
Saitek driver version: 7.0.34.109
Software version: 7.0.27.13
The biggest problem at the moment is with mode switching. Macros seem to be stuck in a loop and in extreme situations Saitek software is causing BSOD on my system. I like the concept and I can see true potential in using external profiles but at the moment it's useless to me because of buggy software.
Anyone had similar issues?
I'm on Windows 8.1 64bit.
Saitek driver version: 7.0.34.109
Software version: 7.0.27.13
I have had he same and ticketed it. Teamspeak interferes with it as do some other applications that poll the stick for push to talk.
Check you are not using usb3, check you have enough power and the little screen is not flickering.
I did a complete deinstall and reinstall of drivers and it is better but still occasionally flickering.
Doesn't happen in other software.... so please ticket it if it persists.
Check you are not using usb3, check you have enough power and the little screen is not flickering.
I did a complete deinstall and reinstall of drivers and it is better but still occasionally flickering.
Doesn't happen in other software.... so please ticket it if it persists.
Ok, thx for quick reply.
Well, I don't use Team Speak in PTT mode only in Voice Activation.
Do you mean ED? It doesn't matter if I'm running the game or not, it still happens.
Anyway it must be TS fault because as soon as I shut down that program problem disappears. I also tried both USB3 On and Off in BIOS including xHCI that was causing problems previously on my Windows 7.
Well, I don't use Team Speak in PTT mode only in Voice Activation.
Do you mean ED? It doesn't matter if I'm running the game or not, it still happens.
Anyway it must be TS fault because as soon as I shut down that program problem disappears. I also tried both USB3 On and Off in BIOS including xHCI that was causing problems previously on my Windows 7.