@SemedianIndustries Oh? Well im looking forward too it 👍

@kimfri the Japanese server just has horrible ping, take this plane and return to the American one

@demoman9 btw, you've inspired my next build

@hoontown thanks my man

@SemedianIndustries
For someone with a 21k upvote score too upvote my simple 747-500 proto engine creation it draws my attention. This massive thing barely runs on my phone XD but its amazing. Needs more weight in the rear or less mass up front though. Constantly wants too nosedive.

@demoman9 cheers mate

@SemedianIndustries Hm. Actually they all do not hold altitude too well, i understood after carefully testing most variants...

@vonhubert can you tag me in an unlisted build?

@SemedianIndustries
Well, so far nothing. I've tried 2 variants:
1) (Activate4=1)?clamp(pow((270-IAS)/270,0.5)*(atan((rate(Altitude)-smooth(Trim,0.5)*38)/5)/90+atan(-PitchRate/5)/90),-1,1):(-Trim*0.5)

2) (Activate4=1)?clamp(pow((270-IAS)/270,2)*(atan((rate(Altitude)-smooth(Trim,0.5)*38)/5)/90+atan(-PitchRate/5)/90),-1,1):(-Trim*0.5)

Both made it work much worse( the plane that did held altitude at AG4+ Trim=0 stopped that...

@SemedianIndustries thanks, i'll try and report the result

@vonhubert like, the faster you go, i'd want it to become less and less sensitive, so you do
(your function)*pow((MaxSpeed-Speed)/MaxSpeed,0.5 or 1 or 2)

@SemedianIndustries any advise how to add that? I thing something connected to the speed is more realistic...

@vonhubert each program must have speed or the center thrust in consideration in consideration.

@SemedianIndustries Well, i was trying to use your code for automatic trim and roll controll, i basically changed pitch input for trim input in your code:

(Activate4=1)?clamp(atan((rate(Altitude)-Trim*20.32)/5)/90+atan(-PitchRate/5)/90,-1,1):(-Trim*0.7)

So when AG4 is active and trim = 0 they should fly more or less level and hold altitude change rate = 0 or close.
but cant find the reason why with pretty much the same code 2 planes (for example this one !tu-104d-3 ) when trim=0 hold altitude change rate pretty close to zero (between -0.2 an -0.2 m/s) while 2 other ones (!Tu-114) cant hold altitude change rate near 0 - this one usually holds +2m/s when accelerating and -2m/s when decelerating at least a bit, and even when more or less stable - at best deviates from 0 for at least 0.8 m/s.

Any ideas how to fix that?

@13321892812 thanks m8

@Sgtk thancc

@vonhubert you may copy the ones in this aircraft if you wish

@SemedianIndustries well, i think i found a walkaround using vanilla airbrakes and smooth function so they don't pop up instantly. They do not pitch up an airplane (though it is not very realistic, real wing mounted spoilers/airbrakes do pitch up the plane, but on most planes it is compensated automatically

@MAHADI thanks man

@vonhubert it doesn't fit all but it seems you're missing some multiplication signs

@SemedianIndustries Like that?
(Activate5=1)?((Pitch=0)?((PitchAngle>0)?(sqrt(rate(PitchAngle)0.1)):(-sqrt(rate(-PitchAngle)0.1))):0):0

Apart from the ineffective code, i've just understood that the main problem is that i've trying to use that code to compensate the spoilers deployment at AG5. When i activate ag5 - spoilers (not vanila airbrakes but small wing pieces) deploy 30degrees up and that makes the plane pitch up. Code allowed the plane to at least stay at stable pitch angle after pitch up, but when AG5 is deactivated, plane pitches down violently, and spoilers take some time to get down, but any code stops working immediately making the pitch down even more violent.

@SemedianIndustries No problem, Mate!

Sure thing! I love original airplane designs.

@goboygo1 thx man

@vonhubert would you please write that function again but
using code quotes this time?