[dyn0myt3]

After 100 post of useless crap no one has mentioned how
to configure FREESPACE2 to use DVORAK.
I thought this was the source code project not the Blizz forums.
Gimme some Data!

Let's start with enabling or adding the Dvorak layout to the Source Code.

DISCUSS!

dyn0myt3

[General Battuta]

I think Zacam uses DVORAK but I'm not sure how he handles it in FreeSpace.

[The E]

1. Welcome.
2. Don't necro threads that are 5 years old
3. The support board is that way ->
4. This thread will be booted there soon
5. Go to the Options menu, control config, and rebind your keys. Done.

[Zacam]

What The_E said.
I just make _A_ pilot. I map out my key bindings, ignoring what it says on-screen to where my Dvorak Keys are.
I then archive that Pilot file.
Any new pilots I need for playing or testing various things are Cloned off the initial Pilot.
????
Profit.

[Herra Tohtori]

Yep, the core of the issue is FS2 and by extension FS2_Open only support one keyboard layout, 104-key US standard layout to be specific. Because of how the game handles keyboard inputs, OS level keyboard layout settings have no effect to how it interpretes the controls.

Thus, the only option (at least before the new pilot code makes its appearance, which should enable improvements on inputs in general) is to do what Zacam says - map the keys as you wish, and ignore what it says on the control list on the game.

[Jeff Vader]

After 100 post of useless crap

I'd recommend staying away from General Discussion.

[Zacam]

Actually, in my case if the Windows 7 Regional Settings API would properly hook the keyboard, I wouldn't have to remap anything.

This is a common failing that I don't think many people realize. It's whether the GAME or application is recognizing your Dvorak converted keyboard, it is whether or not the OS is doing it's job by interdicting the key-presses and translating them properly for you outside of just itself.