You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I'm testing my aircraft, a major problem that occurs is that the BDa AI pitches up too aggressively, tries to pitch up too early, or starts maneuvering before its fully taken off, usually some combination of the three.
I would like the ability to specify when it should pitch up, how much to pitch up by, and when it has gained enough speed to be completely off the ground. (Vr, takeoff pitch, and Vlof respectively) This eliminates the guesswork of trying to figure out which combination of takeoff speeds and landing gear positions prevent the engines from slamming into the ground.
Another way to not have the craft maneuver after takeoff too early would be to have some sort of minimum altitude, say 10 m, before it stops takeoff procedures and starts maneuvering. There could also be some rudimentary collision detection to prevent overly aggressive pitching from slamming parts into the ground.
The text was updated successfully, but these errors were encountered:
The "Takeoff Speed" already controls the speed at which the AI will try to take off. While below this speed and either landed or splashed, the AI doesn't steer. Once it does start trying to get airborne, the climb rate is a combination of the vessel's speed, current TWR, min altitude, default altitude, current altitude (AGL) and terrain normals, so it's not so simple as specifying preset speeds and pitch.
This is also used for determining the climb rate when trying to get back up to the min altitude after the initial take-off sequence, which is partly why it's more complicated and allows for steeper ascents for high-powered fighter jets.
The vessel is considered to be in it's initial take-off sequence until its radar altitude exceeds the terrain avoidance alert radius, which is the lower of twice the vessel's radius and the min altitude. It shouldn't be performing any manoeuvres until it's climbed to at least this altitude after take-off.
I'll make some adjustments to the climb rate for the initial take-off sequence to make it less agressive, which should help. However, planes are always going to need to tolerate at least 5° of pitch when taking off, otherwise they generally won't get enough lift to get airborne.
When I'm testing my aircraft, a major problem that occurs is that the BDa AI pitches up too aggressively, tries to pitch up too early, or starts maneuvering before its fully taken off, usually some combination of the three.
I would like the ability to specify when it should pitch up, how much to pitch up by, and when it has gained enough speed to be completely off the ground. (Vr, takeoff pitch, and Vlof respectively) This eliminates the guesswork of trying to figure out which combination of takeoff speeds and landing gear positions prevent the engines from slamming into the ground.
Another way to not have the craft maneuver after takeoff too early would be to have some sort of minimum altitude, say 10 m, before it stops takeoff procedures and starts maneuvering. There could also be some rudimentary collision detection to prevent overly aggressive pitching from slamming parts into the ground.
The text was updated successfully, but these errors were encountered: