Closed BidyBiddle closed 7 years ago
I bet it's the opposite.
Windows version of legacy ioUrT always uses QWERTY so all your binds are QWERTY (eg, bind w "+forward"
rather than bind z "+forward"
).
Modern ioq3 respects the keyboard layout on all platforms (which is of course what we want) and that's why you're having this issue.
Of course this is only a problem when using ioUrT configs with the newer engine. I suppose I could try adding some legacy config detection to keep backwards compatibility. Let me know what you think!
I doubt the backwards compatibility is worth it. Thanks!
When I launch iourt, my keys are just fine. With ioq3, my AZERTY keyboard is not taken in account and it behaves as a QWERTY
suckstobefrench