@ilborga70 I'm still not sure I understand you correctly, but...I don't think you understand the way the device priority is supposed to work, or what it represents. Of course different devices have different priority, that's the point.
You did increase the priority for the G27 wheel from the default 100 to 300. You've also increased the priority of generic Xinput and Dinput wheels from the default 99 to - again - 300. And you've also increased the priority for keyboard input from 2 to 200.
I don't think you have achieved anything by doing this. Well, anything positive at least.
First, the priority setting is only used to determine the device priority to be used as a steering input device if you leave this completely up to the game to decide. You can manually override it at any moment in the controls section, in which case the priority setting becomes meaningless.
Second, you've not really changed anything in regard of priority for the G27. It was at 100, which is already the highest priority. Setting this to 300 does nothing on a system with only a G27 wheel connected, as in that case, the G27 already is the preferred device for the game to use, so you can't make it *even more preferred than preferred* - there's nowhere to go from the highest tier. Raising the G27's priority to 300 would only make sense in case you had multiple wheels connected at the same time and you wanted to make absolutely sure the game prefers the G27 over any other wheel (and even then you could still just manually override it, see above).
Third, you've raised the priority of a generic Xinput or Dinput wheel from 99 to once again 300. By doing this, you are effectively breaking the whole thing, because those devices are set to a lower priority for a reason (you want them to be on a slightly lower priority than wheels the game recognizes directly, because they are generic only), and also because their 99 priority is a reserved value that should not be changed for this very reason. So the only thing you might've achieved by this is that now, the generic wheel has the exact same priority as your G27. The game will still likely prefer your G27 in its native mode over its generic mode (I'd have to test this, though, because it's hard to say how the game will actually behave once you have intentionally broken its priority settings), so either you have achieved nothing, or you have created a conflict of priorities that can have unpredictable results. And let's not forget the fact you also set the FFB multiplier for these generic devices to 10, as in every single FFB effect will now be ten times stronger than before on these devices (which means it will be clipping horribly as soon as you even look at such device). So not only you have created an unpredictable device priority situation, you have also introduced a very questionable setting into the equation. Can't see how that's a good thing in the slightest.
And finally, you have changed the priority for keyboard to 200. That means you are once again effectively breaking the whole thing, because you've changed the intended (and reserved) priority setting for keyboard controls from very low (because you likely don't want to be using keyboard as a preferred device if you have any other controller or wheel connected) to a value of 200, which is double what regular wheels are using. With the rest of your setting, you are basically saying you want the game to prefer keyboard controls over anything else, except for the G27 or a generic Xinput/Dinput wheel (because you've set the priority for those *even higher*). In effect, while this specific settings combination should probably work for you (since your only connected wheel is likely the G27), it doesn't make much sense otherwise and it's a really bad practice IMO.
So, yeah, I really can't help the feeling you have no idea what you're doing here. On the other hand, *I* have no idea how the whole thing even does anything for you, because I don't think it should. But again, you've introduced a very unpredictable element into the equation, so maybe it accidentally does something, I'd need to test that, given how bizarre the whole config is.
