Are you experiment that the game dont save the key preferences? I set another key for chat mission and when I close the game I'm lossing my setting.

If I understand correctly, you are saying that you have set a different key for the Mission Chat, but when you close the game and return, your keys are set back to the defaults?

I can't replicate that one. My key changes are saving even if I don't hit "Apply". Please tell us what operating system you are using, and maybe some detail about how you went about changing your key settings (there is more than one way).

I also changed the key for mission chat, i have a german keyboard and wanted the chat on the same key as on a us keyboard (shift-2), but this is a " on my keyboard and it seems that VO can't save this binding, so i use now 1 and 2 for general and mission chat.

The game only saves the key bindings correctly when you log out, hit cancel on the login box, and then click the quit button. It will not save anything if you command-q out of it.

Or maybe it's your german keyboard...

Try this.
Open your wgaf.cfg file (in your Vendetta bundle - Mac users, control+ click on Vendetta) and alter the keys in that file. Save your changes and go in-game.

To check in-game for your key assignments and binds, type "/print all" (without quotes) in the console.

I'll try your suggestion today night. My problem is the same that Ambush. I'm on XPpro (for now) and here the shift+2 key is " too ! May be is a path to search the problem. Tks RelayeR

Yeah, it won'r handle the " key properly when it saves/loads it.

Basically it's our parser that get confused:

/bind """ +zoom

I'll need to save it as '"' instead and I think that will fix the problem with quotes.

I am now unable to alter the key bindings in my wgaf.cfg file.

I have full access permissions to the .app (mac) and the wgaf.cfg file, but all I get when I open it is a blank document.

When I go to re-write my bindings, I am unable to save in the .app folder. This is very frustrating, because I'm able to do this on my older mac (running X.2.8, this one is on X.3.5) without any problems, and this is the first time I have had this problem. Anyone know why?