Speed Bug at ground and in the air..

[Nedum]

There is a annoing speed bug that some people explain as "normal" behavior. I cant believe this!

I have flown the first Su27 Campaign and at the ground you can clearly see that there is a lose breaking thing @80% RPM but there is no break activated.

You have to go to 80% RPM, wether with one or two engines, then there is a "lose break" and the plane accelerates from zero to 90 kph in 1 second.

The plane holds this speed till your input is under 72% RPM. Before that the plane accelerates at the same speed even with 72% or 77% or 80%.

Under 72% RPM the plane "breaks" on own to zero.

If you hit F2 you can see the nossles act even in this range. There is NO analoge input. It's a on/off switch! 80% RPM on ~71% off!

 

The same behavior in the air with something more strange things incomming.

In a straight flight you have to go to 80% RPM to accelerate. You even accelerate if you now go under 80% till 72%. If you now go under 72% RPM there is an "Airbreak" incomming.

The effect is much more intensiv as with the real air break itself!

If I go under 72% RPM I lose every second 15 kph. If I pull the real air break I lose around 10 kph. If I am under 72% RPM the real airbreak has nearly no effect only if i try to sink then the real airbreak add a small breaking effect.

 

The speed display for AI planes on ground is wrong too. Speed is around 30 kph, shown speed is around 76 kph. @ around 10 kph 56 kph are shown.

 

@ Under 610 kph the plane begins a "rudder dance" with autopilot on (A).

The "dance" stops @615 kph. You can see this at the external view (F2) that the whole time the rudder and the ailerons are working "together".

 

Edit: Trk upload error all the time

Edited November 12, 2014 by Nedum
Trk upload was broken

[Weta43]

Please go to this thread :

 

http://forums.eagle.ru/showthread.php?t=133698

[Nedum]

Please go to this thread :

 

http://forums.eagle.ru/showthread.php?t=133698

 

Yes I know this thread but I think this is a bug and It's not working as intended.

Even with all this strange explanation, there is some physic that works even for russian planes!

Please explain the breaking effects on ground and in the air.

Please explain this "Rudder dancing" with Autopilot on and under 610 kph at every hight and without Autopilot at a hight above 2000 Meters!?

Why can the AI "drive" the plane without this strange breaking effect but the player can't?

And as I said, why is there a "digital" behavior for the engines and why is the acceleration the same with only one engine?

 

It's all about physics, even for russian planes!

 

The same discussions with the F15c PFM... was all alright said the testers and after 3 patches, all this "allright thingies" went away!

Edited November 12, 2014 by Nedum

[Weta43]

"The same discussions with the F15c PFM... was all alright said the testers and after 3 patches, all this "allright thingies" went away! "

 

LOL :)

 

Please explain the breaking effects on ground and in the air.

 

I'd say it's 2 separate issues, the first has been explained by Yo-Yo (the non-linearity of engine thrust with throttle mvt around that part of the range / % indicated RPM), & the 2nd ground thing - I'd say there's actually also a minimum rolling resistance & below some threshold amount of throttle there's not enough thrust to overcome it. That causes a 'breakout' effect as the throttle goes forward. You can see the nose drop as thrust comes on (as if a brake were applied), then release & rebound as the plane moves off.

 

Is it a bug ? I'd say it's intended, but intended and 'as it will end up' might not be the same.

You've rasied it - that's good.

 

Please explain this "Rudder dancing" with Autopilot on and under 610 kph at every hight and without Autopilot at a hight above 2000 Meters!?

 

Yes - it's a BETA, and the AP still needs work.

 

I think you've been part of a discussion of the FCS rudder / ailerons interaction already (?), but I didn't get to what the resolution was, but presumably if the FCS is on, you'd expect it, if it's there with the FCS off, it might be a bug.

 

Why can the AI "drive" the plane without this strange breaking effect but the player can't?

 

Because the AI have the SFM that you had till recently (all AI in all planes use the equivalent of a human level SFM - get yourself in an inverted spin, then ALT+J out and watch them restart their engines and recover.)

 

And as I said, why is there a "digital" behavior for the engines and why is the acceleration the same with only one engine?

 

Isn't the first part of that the same as the question above and covered in the other thread ?

 

The second part - if you can demonstrate it please leave a track.

[Thumper1606688436]

Listen to the pitch of the engines during taxing in this video.

 

[Weta43]

Increase revs till it starts to bolt, decrease revs and coast, apply power, coast.

To turn, apply power, brake through the turn, apply power, coast.

 

Seems like what we have now...

 

Edit - removed a comment

Edited November 13, 2014 by Weta43

[Lusik]

It is related to engine nozzle operation. Notice that when you increase revs beyond certain point nozzle diameter is reduced and plane accelerates rapidly. If I remember correctly one of the F-16 prototypes crashed due to inadvertent closure of its engine nozzle. It simply wouldn't land even with idle thrust.