Aces High Bulletin Board
Help and Support Forums => Aces High Bug Reports => Topic started by: sre2f on April 04, 2007, 05:29:51 PM
-
Here is a video. It is an F4U.
You can see that throttle is full up and I cycle wep off and on.
There is not keyboard or joystick mapping for brakes.
Link to video (http://mtsu.edu/~sre2f/film2.ahf)
-
all I noticed is that when the film starts that the beacon light comes on, you got hosed by the system.
-
The beacon light turns on some films, for some reason; it's probably not related.
sre2f, it looks like you've caught an actual bug.. The only other reason I can think of is that something, somewhere in your controls configuration is causing this.
Have you tried a full reinstall?
-
I wonder if this has anything to do with the removal of all brake commands as he has done.
And really, why would you want to remove all brake commands?
Just a tangental cogitation.
-
Originally posted by fuzeman
And really, why would you want to remove all brake commands?
Scientific method; eliminate all other variables that could interfere with the test. If the brakes cannot be engaged, they won't be the cause of the problem.
-
Ok, OOZ, what are all of these variables, and proof that there are no others?
Someone should try to take off in that plane with the brakes on. If it doesnt give the same result as what's seen in his film, then there's something more to it than just the brakes being on despite his unmapping them.
-
Originally posted by moot
Ok, OOZ, what are all of these variables, and proof that there are no others?
No one said they were all gone. In fact, we're trying to find the ones that are left.
-
Originally posted by fuzeman
I wonder if this has anything to do with the removal of all brake commands as he has done.
And really, why would you want to remove all brake commands?
Just a tangental cogitation.
I took them off because the first thing I assumed was that it was the brakes.
-
Also, when it happens, sometimes I can gain a little bit of speed. It wont gain anymore unless I can point the nose down. It still doestn accelerate correctly, but 1 runway lengths will get me off the ground sometimes with 25% gas and no loadout in an f4u for example.
-
What I was getting at is something like this:
If there is no setting mapped for brakes they may default to something, possible always on.
If the game knows there is a key mapped to engage brakes, it might default to them being off.
Of course, I have no idea how it's coded and I may be talking from a planet somewhere between Neptune and Pluto.
Yea yea yea I know they just reclassified and say Pluto isn't a planet now, I'm old school.
-
I can duplicate this with full brakes applied.
You've un-mapped the keyboard commands. Have you also un-mapped the controller maps for brakes (if any)?
Try this, go to option -> controls -> map controlers. Then for EVERY controller listed (stick, pedals, mouse, etc) in the drop down box click Default Map and then OK. Also, be sure you're in Mode 1 when you take off.
-
For every controller; keyboard, joystick, mouse. There is no brake mapped. It still does it though if I map them :)
-
You should try reinstalling the game, in a new directory, and refreshing your controllers too.
-
I have to ask!! Does your engine come to full power, both RPM and Manifold pressure?? Did you somehow map these controls to the joystick?
I have my Manifold set to normal throttle and RPM set with the slider on my X52 (maybe the other way around). Sometimes I forget to put the slider back to normal (full) after landing engine out or after landing on Max cruise settings. I goto take off with full throttle, but I'm not getting full power which is when I remember to return the slider back to full power settings. See if this is the cause of your problem..