Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: TARGUT on September 26, 2007, 10:45:33 PM
-
This error has made game unplayable. I have bought not 1 but 2 new J.S.s I know this is a patch related problem as I have played for 5yrs + with out ever seeing this error. For an experiment I logged in and went to bed and got booted from tower with this error. PLEASE FIX this!!!!!!!!!!!
-
Is the stick calibrated? Have you installed everything necessary for it? Have you tried unplugging it and logging on?
Stupid questions probably, but it never hurts to ask.
-
Yes I have tried all of that, I am running Windows Vista which I suspect to be the problem. Thanks for the reply tho.
CYA Up
Targut
GHOSTS...You will believe
-
Looks like it's not the game, but your stick, machine or Vista.
I have never had this problem (except when I was moving the controls too rapidly).
What do the numbers look like in the map controllers setup screen? Are they fluctuating a bunch? If so, I have heard (and now use) a powered usb hub. My fluctuation went to nil when I added that device.
-
I moved this to tech support forum as this is not a game bug. It is localized to your computer.
Rename the 'settings' folder of the game to and see what happens. I have also witnessed erratic input on my Vista box from time to time. It even happens at the Windows desktop. No rhyme or reason for it. I just reboot and it clears up.
When it happens I usually have to re-calibrate the stick after I can get it back under control. In some ways Vista reminds me a lot of Windows 3.1 in how erratic it is.
-
I would ordinarily agree, but I did use this same PC for a couple months, and it wasn't until the patch before last that I started getting the "controls" error. Since that patch I get the error everytime I play. I had hoped the last patch would correct it, but it didn't.
I have been getting lock-ups and what looks like memory leaks eversince I upgraded the PC tho.
Anyway that was the reason I put it under the "Bugs" thread, I wanted to see if anybody else was seeing a similar problem.
Thanks for the FeedBack
Targut