Potential Stabilizer Bug on 109?

[[TWB]Pand]

I believe there may be a bug in the stabilizer control on the 109s.

 

My understanding is that on the 109, the starting position for the stabilizer is fully forward, which would be 100% forward.

 

After taking off, when in flight, if you hit the stabilizer trim in any direction it immediately jumps to 0% trim and then goes the direction you pressed.  

 

This causes a HUGE vertical pitch up, going from 100% forward to 0% and then finally to the direction you trimmed.

 

I can't imagine this was standard operating procedure.  Please confirm and correct

 

Regards,

 

Pand

Edited November 4, 2014 by [TWB]Pand

[LLv34_Flanker]

S!

 

 I recall the devs said stabilizer is set to cruise as default. I always move the stabilizer to get desired position before take off. And actually it is 2 or as indicated 0%.

[unreasonable]

This has been reported as a bug. The original build had the starting trim set to midrange which corresponded to the indicator. The the devs "improved" the game by starting the trim nose down, but our input buttons cannot recognize this setting, which has led to the results you describe.

[[TWB]Pand]

excellent...just wanted yo make sure it was being worked.

[avlSteve]

I usually try a snap roll as I do the first trim settings, so it's not as noticeable.

[unreasonable]

I usually try a snap roll as I do the first trim settings, so it's not as noticeable.

 

Not so easy if you do airfield starts and have no time to adjust trim before take off!

[avlSteve]

Not so easy if you do airfield starts and have no time to adjust trim before take off!

 

It was a joke!

 

If you're starting from the strip, adjust the trim before you start rolling. 

[unreasonable]

It was a joke!

 

If you're starting from the strip, adjust the trim before you start rolling. 

 

Whoops! Well you have to admit people do say some pretty odd things.

 

Of course I try to adjust trim first, the problem arises in SP campaign  with a 4 man flight, if you are in a Lagg3 doing ground attack with heavy bomb load you have to adjust trim, oil, water, mix, rpm and throttle and view zoom as well as get flaps down all before the wingman behind you crashes into you. The briefing does not even tell you how many aircraft are in the flight.  It is incredibly annoying. MP where you start at the dispersal and taxi is much better. I wish SP campaign missions started in dispersal as well, but of course people would complain that it takes too much time.

[avlSteve]

Whoops! Well you have to admit people do say some pretty odd things.

 

Of course I try to adjust trim first, the problem arises in SP campaign  with a 4 man flight, if you are in a Lagg3 doing ground attack with heavy bomb load you have to adjust trim, oil, water, mix, rpm and throttle and view zoom as well as get flaps down all before the wingman behind you crashes into you. The briefing does not even tell you how many aircraft are in the flight.  It is incredibly annoying. MP where you start at the dispersal and taxi is much better. I wish SP campaign missions started in dispersal as well, but of course people would complain that it takes too much time.

 

Interesting, the only time I've had them crash into me was when I started to roll, then hit the brakes.  I didn't realize they will hit you before you initiate the takeoff roll.

 

I also much prefer to start with the engine off at the parking area. 

Edited November 6, 2014 by avlSteve

[unreasonable]

I suppose I might be doing it wrong... if the AI is responding to just a tiny forward movement then it may be just that as the mission starts any adjustment of throttle to centre the controls could cause the plane to move unless the brakes are on. I will have to experiment with this to see if I can get your results.

 

I wish BoS was better documented.

[[TWB]Pand]

From what I've seen... on all Axes, BOS has a default setting or % that is set when you start the mission.   Lets say mixture at 0%.   Even if you have an axis assigned to mixture and it is sitting at the 100%, BOS doesn't recognize it being there until you move it.   

 

So in the above case, I would have to pull mixture back and little and return it to 100% for it to register.

 

I have noticed this on Prop Pitch, Radiators, Throttle, everything.  I wish BOS would read the position on mission start rather than waiting for a change to report the location.

Edited November 6, 2014 by [TWB]Pand

[unreasonable]

Pand, that is my experience as well, which is why it is quite hard not to make an inadvertent forward motion on the runway at mission start, thus initiating chaos. I am going to have to come up with a new checklist starting with "brakes firmly on..."

[III/JG11_Tiger]

I think ROF has the same issue, usually moving the sticks forward then back prior to start up fixes things in ROF

[[TWB]Pand]

I think ROF has the same issue, usually moving the sticks forward then back prior to start up fixes things in ROF

Eeek that doesn't sound good--- almost like it wouldn't  be fixed at the game level... :|

[Solmyr]

I though there was a little bug there, also. Happy to see I'm not fool.