Forums » Bugs

Direction keys broken?

Oct 03, 2004 Bandor link
running xp sp1
have a logitech keyboard just using generic windows keyboard
nostromo n52

drivers (none of logitech's proprietary software)
The keys work in windows just fine. In game they do not function in flight mode, they do work on the menu's though.

So I went and changed the assinged keys in the games configuration to home, end, delete, page down. They keys still don't work in flight mode, work just fine elsewhere.

Changing various keys on the nostromo didnt help. I just can't get it to use flight direction. Any key not assigned to flight direction works just fine in game (targeting, firing missles, strafing).

The game controls worked fine last night with the latest patch (when it was lagging for everyone). I haven't changed anything since.

Anyone else having this issue? I know the server code was tweaked a bit to get rid of lag but it seems more like a pc/software issue since controls worked just fine yesterday. I'm reluctant to bother sending a bug report on something that seems to be my issue.
Oct 03, 2004 a1k0n link
First thing's first: is the control set to "keyboard/joystick mode" as opposed to "mouse mode"? You can toggle this with the apostrophe (') key in-flight, or with the radio buttons in the Controls menu.
Oct 03, 2004 paedric link
Semicolon < ; > for mouselook toggle, apostrophy < ' > for flight mode toggle. :-)

If worse comes to worse, since you made changes to some of the settings, try renaming your WGAF.CFG file to WGAF.CFG.OLD . Vendetta will recreate the default WGAF.CFG file the next time you play the game.
Oct 04, 2004 Bandor link
[10/04/04 03:56:50] gdinput.cpp(767) : or Error (DIERR_READONLY): The specified property cannot be changed.
[10/04/04 03:56:50] gdinput.cpp(761) : Error (DIERR_NOTACQUIRED): The operation cannot be performed unless the device is acquired.

With mouselook on my arrow keys work just fine for spinning the ship. I changed to keyboard/joystick - no change. But I did find I just played for a minute and generated a 237K file just of this error repeated over and over again in my dinput.log file. The log only has 20 seconds showing on its timestamps. It seems thats quite a few errors for only 20 seconds.
Oct 04, 2004 a1k0n link
Ah-ha. Yes, Ray re-enabled dinput.log errors (they were previously disabled because they make huge files, as you noticed, but they do help track down problems). Perhaps this can be fixed for the next patch if we can figure out why it did that. DirectInput seems to be quirky.

paedric: doh! you're right.