Results 1 to 5 of 5

Thread: Keymapping bug

  1. #1
    Community Member SickCat's Avatar
    Join Date
    Oct 2009
    Posts
    150

    Default Keymapping bug

    Ok, I get it...this client is in beta. It's too bad, really, since the game, otherwise runs beautifully. I've tried getting around the keymapping bug...so, when the game loads up, it looks like it's resetting the keymap file to a default...maybe. I modified the mappings the way I wanted, then made the file read-only. Great! The game doesn't reset it to defaults anymore! But it also ignores it, and your mappings are back to default. I tried taking a copy of the modified file and inserting it while the game is running...no joy.

    Not sure what's going on with this, but it's the only real problem that's driving me nuts. Is this on the table to be fixed? Is it known? Should I bother monkeying around with it, since it's going to be addressed 'soon'? Is there a workaround...is the game looking elsewhere at a keymapping default? Maybe the default is hard coded in the game and there's nothing we can do aboot it. Would love a heads-up on this.

    UPDATE: Looks like making your keymap file read-only ruins your ability to use in game chat. I could not, for the life of me, get it to work. Then, I made myself able to read/write the keymap file again, and bam...it worked. The two seem completely unrelated...yet...there you have it. What in tarnation is going on here???
    Last edited by SickCat; 02-13-2013 at 08:42 PM.
    -Qetsil / Sickcat / Dorktastic / Belir / Peachfuzz / Fysh / Sometime / Segment / Skwash / Pyg / Swetn / Smurfingly, And 2 nameless others
    All Thelanis, all the time...FER SHIZZLE!

  2. #2
    Community Member kisnord's Avatar
    Join Date
    Jun 2012
    Posts
    36

    Default

    Quote Originally Posted by SickCat View Post
    Ok, I get it...this client is in beta. It's too bad, really, since the game, otherwise runs beautifully. I've tried getting around the keymapping bug...so, when the game loads up, it looks like it's resetting the keymap file to a default...maybe. I modified the mappings the way I wanted, then made the file read-only. Great! The game doesn't reset it to defaults anymore! But it also ignores it, and your mappings are back to default. I tried taking a copy of the modified file and inserting it while the game is running...no joy.

    Not sure what's going on with this, but it's the only real problem that's driving me nuts. Is this on the table to be fixed? Is it known? Should I bother monkeying around with it, since it's going to be addressed 'soon'? Is there a workaround...is the game looking elsewhere at a keymapping default? Maybe the default is hard coded in the game and there's nothing we can do aboot it. Would love a heads-up on this.
    I asked this 3 times minimum, becouse its a really annoying and lame bug, even if the client is in beta. No official respond, and i think we never get one. Powered by our fans...

  3. #3
    Community Member PwnHammer40K's Avatar
    Join Date
    Nov 2010
    Posts
    454

    Talking It's fixed!

    Update 17 fixed it! YAY
    Last edited by PwnHammer40K; 02-20-2013 at 09:57 AM.

  4. #4
    Community Member
    Join Date
    Oct 2009
    Posts
    1,233

    Default

    Quote Originally Posted by PwnHammer40K View Post
    Update 17 fixed it! YAY
    This is really fantastic news. I might try the Mac client again rather than constantly swapping to Boot Camp.
    The Silver Legion - Guild Medieval
    Arisan - Arisanna - Arisanto - Arisgard - Betatest
    Cannith

  5. #5
    Community Member SickCat's Avatar
    Join Date
    Oct 2009
    Posts
    150

    Default

    Nice!!!!!11!!!!!111!1!!ONEZ
    -Qetsil / Sickcat / Dorktastic / Belir / Peachfuzz / Fysh / Sometime / Segment / Skwash / Pyg / Swetn / Smurfingly, And 2 nameless others
    All Thelanis, all the time...FER SHIZZLE!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload