AH2 did not respond to commands

[Infidelz]

This is a intermittent thing that seems to set up after I played for a bit last night. I am not sure if I alt tabbed before this occurred. I had been testing new shifts states earlier for multi-engine starts/operation.

I have an X65F, Track IR, I-950, 12 Gram, Nvidia 570 and WIN7. also running win7 from a SSD PCIE Card. Except for the SSD these all seem pretty standard and representative of what many folks have in terms of Manufacturers. Also have 1k corsair power supply.

During the great hoard attack last night against A116, i went to up a goon. After take off, the landing gear would not raise. No problem must be an X65f glitch. try G on the keyboard. Nothing. no joy.

I bailed and tried again. Again nothing working.

I quit and restarted aces high and all was good again. this suggests that it is not my setup (hardware) causing the issues because I did not reset the operating system or PC, only ace high.


That is all.

Infidelz.

[Skuzzy]

If you are trying to run Aces High from the SSD, you will have problems.  The game does a lot of writes to the "settings" folder, all the time.  I have found those constant small writes are a problem with an SSD.

[Infidelz]

Hi Skuzzy!

Win7 is on the SSD and runs from there. AH is on my Velociraptor.  Any chance it is still writing there? Have win7 64 installed. It is a tricky beast. The key commands worked OK outside the game on a notepad for both the keyboard and the joystick.

Infidelz.

[Skuzzy]

Did you try using the "Fix key" button in the "Map Keys" panel?  This will tell you if the key mapping is messed up.

Are you running some odd keyboard software which uses some type of macros?  Are you running some Bluetooth software (notorious for remapping the keyboard)?

[Infidelz]

I am using the wireless 2000 thing from microsoft for mouse and keyboard. Not running macros though. What does the fix key thing do? reset in game?

infidelz

[Skuzzy]

Just follow the instructions in the "Fix Key" panel.  If the problem goes away, then it is a scan key mapping issue between DirectInput (the intput API of DirectX) and the input device.