FourGreenFields

Members
  • Content Count

    276
  • Joined

  • Last visited

Community Reputation

77 Excellent

1 Follower

About FourGreenFields

  • Rank
    Messerschmitt Fanboy

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Where's the CoM? Should be slightly behind your main gear, but only slightly. If that's still possible, try to reduce the drag of the main gear, and increase that of the tail wheel. And make sure the gear doesn't flex. Also worth a try to pull during takeoff run, to increase pressure on the tail wheel. That being said, are you sure the thing will lift off at 50m/s at the AoA it has when sitting on the runway? I don't consider it impossible, but AoA seems relatively low - might still be sufficient if the craft is light though.
  2. I'm quite sure it resets prior to every launch. You could just angle the control surfaces for a "saved" trim though (allthough it wouldn't change thrust vectoring). Or maybe you could write a macro to set trim at spawn (and the rest of the routine, like lowering flaps to takeoff position, etc.). Maybe it'd even be possible to save the trim settings as part of the plane file (as comment?), and have the macro read it.
  3. Or just trim the plane (iIrc alt + qweasd, and alt + x removes trim).
  4. Am I right to assume it only reaches critical AoA due to thrust vectoring? Either way, my money is on side-slip, and possibly higher speed of the outer wing. Considering you compared it to the 190, I assume that you know it's a bad idea to pull hard when using rudder, and afaIk that's because the side-slip causes asymmetric stalls. And you'll usually end up with a small amount of side-slip in turns, unless you counter with rudder. Also the outer wing has a slightly larger turn-radius (unless banked 90°), while keeping the same turn-time, with other words a higher speed. If your wings stall sooner at higher speed, it may make matters worse. PS: How stable is the dev-version of FAR?
  5. Btw: SpaceDock says that FAR is still outdated. Does the outdated version work with the latest KSP patch? Or are you using some experimental branch?
  6. Was a thing in Germany even before 1945. Wing sweep as early as the thirties. Allies should have known about wingsweep too, considering it wasn't kept a secret. They did, however, ignore any knowledge they may have had about it, until they found German blueprints and a prototype (or several prototypes?).
  7. Dihedral effect isn't limited to dihedral wings(/lifting surfaces). A vertical surface (tail fin!) will also make your plane roll when slipping, as long as it's mounted above or below the CoM. If that wasn't the case, nearly every plane would have some dihedral, because you generally want a little dihedral effect (-> roll stability)
  8. I'd guess that might be due to dihedral effect. If you roll at high AoA without using rudder with ailerons (left ailerons -> left rudder) you'll turn your AoA into slip angle, which then causes roll in the opposite direction. Not entirely sure if it's that, but worth a try I'd say.
  9. The challenge went through a redesign, and the scoring vanished at that point. I posted what it may have been at some point, may want to dig that up.
  10. That might be some weirdness with unusual characters and forum redesign. Pretty sure it's meant to say 12°.
  11. The B-2 there used artificial stability, as blowfish mentioned (I think the setting was called yaw brake). However, it is possible to make a plane yaw stable (aerodynamically, not artificial stability) without dedicated tail fins. The most kerbal way is probably to add drag on the tail (like a chute), but that kind of limits your speed. Wing sweep also increases yaw stability, although not usually to an extend that allows you to remove a tail fin. Probably the easiest way is to add an di-/anhedral angle to your wingtips, when using wing sweep - they'll work similar to a tail fin, but aren't technically tail fins. Usually a good idea to use artificial stability/fly-by-wire on top of that. And keep your CoM close to the nose, as that'll increase stability anyway.
  12. I hope I'm not too late for the flying-wing-party... date-volume limit prevented downloading stuff (playing on another PC now) before Deizel made his bomber himself, so I decided to build a cargo plane based on Mk 3 fuselages (as he said that increasing size was the problem). Testing isn't done yet, and there'll probably be some adjustments. Relies on FAR stability assists for stability (yes, pitch too. And any landing attempts without roll assist failed as well).
  13. Ok, Mk2 fuselage, blended wing-body. High speed, and some payload (judging by X-45 and X-47 a bomber/attacker, so doesn't need to be that manoeuvreable). Pilot-friendly handling. Going to try that later today. o7
  14. Aerodynamically stable (basicly translating to di-/anhedral wingtips or stuff) or artificial stability? Messed with both, mostly for the 5th Generation Fighter Challenge. Size? Payload? Speed? SSTO? Any requirements for takeoff and landing (other than being able to do that at KSC)? Existing design that you want improved?
  15. If the CoL is far behind the CoM that usually means high pitch stability. Not nessecarily bad, but means you need a powerfull elevator to pull high AoAs. Put simply, you'll want CoL and CoM close to each other for agile planes (stuntplanes, fighters) and possibly planes with high wingloading (as they may need high AoAs to fly slow). CoL further behind if the plane is meant to be easy to fly (trainers and stuff). But even "futher behind" shouldn't be overdone, or you risk not being able to pull the AoA to sustain level flight - which is probably what is happening to your plane. You can, ofcourse, build agile planes with CoL far behind CoM - a very big/powerfull elevator can overcome stability, thrust vectoring can help (especially at low speed), and some planes may have lower stability at certain speeds (one kind of layout I used had significantly lower pitch stability at exactly 0.9M for example). But it's a bit like building supersonic planes without area ruling them - possible (as the Bell X-1 proved), but there are easier ways. A better indicator for how pitch-stable a plane is are the "pretty graphs" in the FAR interface. There's a yellow (iIrc) line, and if it's going down as AoA increases, the plane is pitch-stable. Good way to see if the plane is, i.e. getting more or less stable as AoA increases. Also usefull to see if the plane will keep the AoA required for level flight without trimming (if you want that, I'd recommend adding an Angle of Incidence (AoI)), and to get the critical AoA. You can also calculate the graphs with pitch input (only elevator, not RCS/thrust vectoring iIrc) to see the maximum AoA you can pull. I'd recommend you to do that, and compare that to the AoA required for level flight (as can be claculated using the "scary numbers" section). The "scary numbers" can also help determine stability in general, but not all of them (not even all of the coloured ones) are vital, and I found it hard to figure out how stable the plane is - only if it is stable at all, or not.