Hello all. I would have hoped for happier first post on here, especially since I have long enjoyed this community as a reader. Anyhow, I have become the victim of a very strange issue in both DCS A-10c and Blackshark 1. The function keys across the top of my keyboard have begun to register the incorrect keystroke when I press them. For example: F1 still registers as F1, but F2 registers as Z, F3 as X, and F4 as N. Needless to say this has made several aspects of the game unplayable. I deleted my A-10c save game files and did a fresh install but with no effect. Further, my A-10c game files are up to date. Anyway, I was curious to see if anyone here had experienced a similar problem or had any ideas/suggestions to get a couple of my favorite games working right again.

Thanks for any help you can give.

Tell us what kind of keyboard you are using. Does it use a special driver/software?

If possible, check whether the error occurs with a different keyboard as well.

You do not mention it, so I assume other applications are unaffected? If so, are any of those actually using the same method to grab the keys as DCS (which most likely uses DirectInput)?

And by the way, what happens if you press X, Z or N?

In any case, first try to eliminate the possibility of a hardware failure.

Hi Samwise,
Read the fist couple of posts in this DCS thread by Majapahit about deleting your Keyboard.lua and Joystick.lua files to 'reset' your commands.
keyboard.lua

Maybe resetting your keyboard file will get things back on track.

Wrecking Crew

Thanks for the prompt and helpful replies. That's one of the things that is so great about the community here. I'll give the suggestions above a shot and let you know how it turns out.

After a long break from Flight Simming, I have finally returned after being tempted by this excellent DCS A10C.

But reference the problem, I suffered from this and almost called it a day as I was at the end of my tether after numerous deletions and reinstallations, The only "F" key that worked was F1, but I found that the problem was caused by not having "F Lock" turned on, on my keyboard. Not all keyboards have it, I don't think, but the keyboard I have is a Microsoft Digital Media Pro. I searched online for a solution, but never found one, only what has been mentioned here, it was only by accident I twigged the F lock button and tried it, but no where did I find this solution mentioned anywhere.

After finding the solution, I have yet to find out if I can now also remap all my "F" keys to another purpose as well as the usual keybindings, one to work with F lock engaged and one to work with it disengaged