[roaddog_665]

Having an issue with my keyboard when trying to play FS2 or FS open. I have tried my retail (cd) version, downloaded FS2 from good old games, and tried Open and  have had the same problem with all of them. When I try to create a pilot, the first letter I enter is fine, then all other letters are shown as numbers in order, ie "D1234567". If I go into a mission I have to hold the "Ctrl" key to get any other keys to function. The only keys that work correctly with out holding "Ctrl" are the Tab, Backspace, and the number pad. I have tried to rebind the keys and reinstall FS2 with no luck. The keyboard works fine for everything else, I'm using it now. It's a Logitech wireless, I am going to bring a wired keyboard home tomorrow and try that, but then I'm out of ideas. I'm running Windows XP on an older machine... as in AMD Athlon and GeForce 7800 GS old, but its worked so far. I ran some of the Open FSport missions, and other than needing three hands for the keyboard, it ran great. I'll take any help I can get. Thanks!

[MatthTheGeek]

I know FS doesn't detect your keyboard loadout (for example if you have an azerty keyboard, it will still behave as a qwerty ingame), but your keyboard must have a quite weird layout to behave like that. I'd say yes, try with another keyboard to narrow the issue down, see if it comes from this specific keyboard or from your computer itself.

Also, randomly, a log couldn't hurt.

[roaddog_665]

Thanks, its a qwerty keyboard, but somethings wierd is going on. I don't have open installed at this point, so I can't send a log, I am trying to get the issue resolved before I re-install open just in case it has something to do with the retail install. At this point I'm not sure if it is a hardware or software issue, but I've installed FS2 from Cd and download and both have the issue, so I'm leaning towards a hardware issue. It's just strange that the keyboard works fine for everything else. Thanks for the response, I will post back later today when I try the other keyboard.

[The E]

Posting an fs2_open.log is always a good idea in support cases.

Even though I have no clue at all what's going on here; This is something I haven not encountered so far.

[MatthTheGeek]

Also, keep in mind that the FSO code is much, much improved compared to retail. That issue that you're experiencing in retail so far might not happen at all on FSO. It's worth giving a try.

[roaddog_665]

Well, I tried a good old fashion wired keyboard and still have the problem.

I had FSO installed last weekend and had the same problem, I removed it thinking I had a problem with the retail install, or had something screwy happen with the download.

I just did a clean OS (XP) install last week, so I don't know if something happened then but I can't imagine it would just effect Freespace...but then again it is Windows. Keyboard works fine in Word, IE, and a few other games I've tried.

Was looking forward to playing FSO, but I am at a loss on this one...I'll keep tinkering with it and keep my fingers crossed. Thanks for the help, I'll check back later to see if anyone has any other ideas.

[jr2]

What language OS are you using?

[roaddog_665]

jr2,
English (US). XP w/ SP3.

[jr2]

Mph, run a debug build and post the <freespace directory>\data\fsopen.log in [code] tags here.

[roaddog_665]

Just an update, still haven't figured this out, but I just got a joystick with a bunch of buttons on it. I bound all the important stuff to the stick and as much other stuff to keyboard buttons that work as I could. It's not right, but it works. I'm playing, thats the important thing.

[roaddog_665]

Finally got this fixed. The problem was a security suite called Constant Guard that came from my ISP (Comcast Cable). I never used it so I removed it, when I did a popup said I needed to restart so my keyboard would work correctly. So I did, and it does.  Now I just need to get a joystick that doesn't have a center deadspot a mile wide!!!

BTW, FSOpen is awsome. Great job to all who worked/ are working on it!