So in fairness, I misspoke when I said they weren’t “seen”. What I meant was that, when plugging the X52 in and loading the game up, the game essentially said “ooh look, there‘s an X52 attached. It’s now available as an option in the dropdown menu under controls.”
Whereas when connecting any of the other devices I’ve tried - Warthog throttle, X56 throttle, and VKB stick - the only options presented are keyboard, keyboard and mouse, or blank profile. Which, looking at it, is deffo a spot of “Ahhh, why isn’t everything just plug and play?!?!”
So what I ended up doing is spending about an hour with the X52 installed and jotting down line by line what each axis, button, toggle and setting was, then started a new blank profile with the X56/VKB and recreating everything. It’s about 90% where I need it to be, coupled with relearning muscle memory (which might be the most frustrating part, reaching for a button out of habit and it not being there.)
Sort of gave up on the Warthog since ED doesn’t seem to like “traditional” switches as opposed to the spring loaded toggle ones unless the TARGET software is also running. I'd also (incorrectly) assumed that TARGET was similar to VKB or even Saitek's software, where bindings were actually written to the unit and stored. Instead it's basically an emulator that interprets the Thrustmaster product you're using, and acting as a go between between the throttle and ED. (So again, needs to be running every time for it to work)
Whereas when connecting any of the other devices I’ve tried - Warthog throttle, X56 throttle, and VKB stick - the only options presented are keyboard, keyboard and mouse, or blank profile. Which, looking at it, is deffo a spot of “Ahhh, why isn’t everything just plug and play?!?!”
So what I ended up doing is spending about an hour with the X52 installed and jotting down line by line what each axis, button, toggle and setting was, then started a new blank profile with the X56/VKB and recreating everything. It’s about 90% where I need it to be, coupled with relearning muscle memory (which might be the most frustrating part, reaching for a button out of habit and it not being there.)
Sort of gave up on the Warthog since ED doesn’t seem to like “traditional” switches as opposed to the spring loaded toggle ones unless the TARGET software is also running. I'd also (incorrectly) assumed that TARGET was similar to VKB or even Saitek's software, where bindings were actually written to the unit and stored. Instead it's basically an emulator that interprets the Thrustmaster product you're using, and acting as a go between between the throttle and ED. (So again, needs to be running every time for it to work)
Last edited: