Controls and modifier, not working as before.
- Thread starter fennster
- Start date
Which HOTAS?
Were you setting something up in the HOTAS' software? Maybe you just accidentally disabled the "shift" button, making it a normal button.
Were you setting something up in the HOTAS' software? Maybe you just accidentally disabled the "shift" button, making it a normal button.
Just the bog standard T-Flight HOTAS X Thrustmaster. There is no external software. The modifier is when defining the controls within Elite, i.e. Hold 2 buttons to create an alternate control.
I have one modifier button which works fine for duel functionality for the rest of it, just not this particular set. Nothing has changed with hardware or software, apart from Elite.
Maybe, I'll just have to try redefining to something different, just that's what I played with for over a year now.
Hmm, sorry. No ideas, then.
My beloved HOTAS broke down ages ago [before i even bought Elite], so i am on a DS4..
However, i experience some troubles with modifiers as well... and also found a temporary solution to this..
I have set "O + digipad up" as "enable FSD" - but sometimes when first leaving a station upon entering the game, the "O + up" combo enables 'headlights' - which isn't even set on my pad anymore but just the "H" key on my keybord..
However, i remember an older, less fine tuned ds4 config i was rocking in which "O+up" actually represented the headlight function..
Solution for me:
Go to settings, check if everything is set in there as you want it to be [as for me, it shows "h" = headlights / O+up = FSD] - it probably will be set to your likings allready, just not working the way it's displayed under 'controls'.
Click apply [even though you changed nothing] - should be fine and working now.
Works out for me every time this happens..
Also, when you experience this, does "module priority" gets reset/bugged for you as well?
Happens to me, too, and i feel the 2 problems are somehow related to each other...
However, i experience some troubles with modifiers as well... and also found a temporary solution to this..
I have set "O + digipad up" as "enable FSD" - but sometimes when first leaving a station upon entering the game, the "O + up" combo enables 'headlights' - which isn't even set on my pad anymore but just the "H" key on my keybord..
However, i remember an older, less fine tuned ds4 config i was rocking in which "O+up" actually represented the headlight function..
Solution for me:
Go to settings, check if everything is set in there as you want it to be [as for me, it shows "h" = headlights / O+up = FSD] - it probably will be set to your likings allready, just not working the way it's displayed under 'controls'.
Click apply [even though you changed nothing] - should be fine and working now.
Works out for me every time this happens..
Also, when you experience this, does "module priority" gets reset/bugged for you as well?
Happens to me, too, and i feel the 2 problems are somehow related to each other...
The problem I have is that when i try to define one, it will tell me the [Joy U-Axis] is already in use, do I want to change it? Confirm. So it will delete the previous entry, even with modifier. I'm pretty sure it started after 2.1, but have not been doing combat for a while, so hasn't bothered me.
I think I might support/bug report this one.
It might have something to do with whether you've set the U-Axis as analogue or digital. See this thread for details: You're Doing It Wrong: Analogue Vs Digital Settings in ED. it seems that when you have set the rudder correctly as analogue, as per that thread's suggestion, then you can no longer use it in combination with the modifier. I also used to use the rudder+modifier for targeting subsystems, but once I've fixed the rudder so that it's analogue (for yaw), I had to change the bindings for targeting subsystems.
Yep, that's it. Setting vertical thrust to digital, allows me to apply modifiers elsewhere, well that sucks.
- - - - - Additional Content Posted / Auto Merge - - - - -
Oh well, finally the perfect excuse to get around to configuring VA......