Amram

https://books.google.ca/books?id=-LGZETtVCiAC&pg=PA220#v=onepage&q&f=false ~20 minutes. remember, you can orbit in 90 minutes, which means you can cover 180° in lat/lon in 45 minutes, yet targets will generally be closer than your antipode, often considerably so, and in the case of slbm's, they could be close enough that the missile never actually goes suborbital.

speed is definitely the most powerful factor. ½mv². Note the v². assuming "medium" sand, from the third reference, assuming spherical at 0.25mm radius, it has a volume of 6.54498E-05cm³, aluminum oxide has a density of 3.95g/cm³, so the fleck is around 2.585E-04 grams. at the lower 10km/sec they mention, and assuming their spec masses about the same as a grain of sand..., 2.585E-06kg * 0.5 * 1E5²m/s = 12925 joules By comparison, that is 3.7 times the punch of a single round from one of these

composed of what? I hope you weren't thinking steel..... The problem is both strength and mass. Whatever material is used, it must be strong enough to support its own weight, which necessitates very low mass at very high strength of you are never going to have a "cable" reach GSO, let alone beyond it. Important note: your anchor mass must be beyond GSO. If its in GSO, it contributes no counter-mass at all, and all of the mass below GSO will be suborbital and will fall and take the anchor with it. This eliminates trying to have a short length untethered that periodically lowers some cable to raise other bits, you'd leave orbit(one way or another...) if you tried, unless we aren't talking a pure space elevator but some unusual hybrid with active thrust to keep it up there..... If so, i hope you have a trick to get more fuel up there than the elevator burns trying to lift that fuel up there. If you don't have active thrust, your anchor must be beyond GSO, and if it is, but is not constantly tethered, then it will not remain in GSO as its center of mass is moving too quickly for the orbit its in, and it will enter an elliptical and otherwise useless orbit. Go here, look at breaking strength: https://en.wikipedia.org/wiki/Specific_strength Breaking strength is the length, in kilometers, of which you can have a vertical column that will be able to carry its own weight, we can't do it yet, even with nanotubes, we can't make them strong enough, yet. Of course that is compounded with us being unable to even adequately produce them, let alone sufficient quality. Off the top of my head with no google-fu to back it: Kevlar would be better than steel I think, its light and has great tensile properties, which are necessary, but its still far too massive for a space elevator. Now remember, that's just the breaking strength, which is, as noted the measure of how much of itself a column can hold up under earths gravity, but you need to double that when you are looking at your centerpoint, because everything below wants to fall, and everything above wants to rise, and the upward force is greater than the downward of the elevator will not be so for long. We have nothing that is remotely feasible yet, but we do have a few promising materials that may work out after some lengthy R&D.

"working" copies should not be present in a single online service, for the reasons you mention, anyone else remember megaupload? Here today, gone tomorrow. Backups are different. They are by definition not the working set, its a backup. If the backup evaporates with whatever company's collapse, you create a new one from the current state somewhere else. If your primary fails, you recover from the backup. Having a single potentially volatile backup is the bigger issue. If you rely on online, you need to distribute, 2 or more complete backups on unrelated services, the odds of losing all..... And still, the in house backup is warranted. I have important excel sheets and program code. I'd go totally mental if I ever lost the data. It exists on my primary drive, secondary drive, a thumbdrive that only ever sees use as a periodic backup of key files, and across google drive, onedrive, mega.co.nz, and copy.com. Mega might go down, as may any of the other online services. Two drives may fail the same day. The PC could take a horrendously absurd power surge and bake all hardware installed. Multiple services could go extinct simultaneously. But 2 internal drives, a thumbdrive, and 4 separate online services to vanish simultaneously? Online backups are perfectly viable, just don't rely on a single service as the sole source of backup for the data, and especially not as the working set of data.

http://forum.kerbalspaceprogram.com/threads/20451-1-0-3-Ferram-Aerospace-Research-v0-15-3-1-Garabedian-6-22-15?p=1924777&viewfull=1#post1924777 that's an itemised list I made of what far did that stock didn't at the time. Stock's aero feels a bit better now, but its still lacking in all the key areas, bubblewraps the player way too much, does some really odd stuff with its wings and cargobays, and over here we've got Ferram pulling hair out to match the strangeness we call reality that much more closely. I suppose there is one very singular advantage here over stock. All the world's literature on aero, damned near all of it applies in far in some way or other, that was the whole point of FAR, reality in ksp, can't say that about stock.

I've gotten above 2.1 on a wheasely's in Ferri. Took some design work, but it let me get there, careful piloting becomes every bit as important - you need to find your design's optimal altitude its not always the same one. Engine optimal and design optimal don't always match. you need enough wing to stay there with low AoA to keep induced drag minimised, yet little enough wing that you keep drag under control. that particular design was plagued by poor rigidity, since its mostly composed of tail sections radially attached to eachother. Pull 8g and she snaps in half - the wings can take it, the fuselage can't. Though the design goal was the best speed I could manage, everything else secondary. Still, hopefully that lays to rest that 2+ is totally possible. Mach 2.106 on 2 basic jets. I'm fully aware this doesn't meet submission req's, isn't intended as one.

CoL is not CoL with far, its CoP, or center of pressure. Its also a poor indicator of stability, the graphs should be used as they will tell you WAY more than anything else - not only whether or not it can fly. They will tell you if it will yaw uncontrollably, what AoA you have to pull to take off, whether you can push the nose around or have to stay right on prograde to remain in control, so much more. As to the "CoL" arrow, its not disappeared, its removed.

So what is considered to be a good ratio of cross section to wave drag? I have a twin engine fighter at 10.86 currently. I did have a turbofan fighter at similar, but I crashed KSP, and on reload....no dice, lol, much higher, possibly the voxels positioned a little differently on me or far was a touch erroneous prior to the crash. Also, how fast is considered the extreme limits of the Wheesley turbofan? Do we have a noted record on it yet? I've hit 2.105 in level flight for a twin engine aircraft. I can get to about m2.248 sustained in level flight at 9200m, but it takes finicky design work, and careful exploration of its performance to find the ideal altitude. I essentially built a missile with a mach drag of just 0.189221m²(ratio of 13.52) to see how fast i could get it going. Stability is well...its decent once your up to speed, but until then it has issues, and the first few seconds after launch are reliant on the gimbal to keep things in check. Almost entirely lifting body with only as much control surface as I could add without increasing wave drag - those tail fins reduced it quit a bit actually. Launch is vertical and gradually flattens out at around 9000m for the speed run. http://imgur.com/gallery/8v3FFN3

Replace the COL indicator with a text caution? They turn it on, and get told flat out: There is no CoL indicator. This is not a bug. Use the graphs. While I suspect a large number of people would find a way to not read it, or complain anyways, I'd wager the number would be fewer than those that currently complain its not right, or would complain if its missing.

Who cares? Is this cheating? Is that? What about x mod? What about <insert here>. Answer? Someday people will get over themselves and play however they want and not care that they or others might play differently....I suspect I'll be retired long before then.

maybe because it does many things stock doesn't even consider, and while its at it, ferram ripped its guts out for this version and replaced it with something vastly superior to both stock and previous versions.....of course its going to have issues. Its damned near a 1.0 release of a new mode this update was so significant. Thats a big part of why it took as long as it did after the update, and why it still has teething problems, find me a 1.0 release for something this complex that didn't have issues. Stock started with not even knowing how drag worked..... to still not really knowing how drag works. Far has issues because it's not running full fluid dynamics, be happy, it wouldn't be a slide show, it'd be a picture frame that might update hourly if your machine is powerful. Approximations have costs, usually in the form of things they ignore, and sometimes you have to build those things in a less intensive manner, which means improperly, but close enough, and that means more edge cases. Edge cases mean problems, and look what we have here.... And be patient, impatience doesn't get you an answer faster, we are here to post or we are not, your editing in anyone? doesn't coerce us to sign in any sooner, check this thread, and answer it. Its simply wasted, sometimes grating, at worst annoying.

yep, right click your part. if its a booster, right click the booster,and remove some/all the solid fuel, so your only hoisting an empty tube, much easier to get it up there. For fuel tanks, same thing, though when testing engines its simpler to just not attach any fuel for that engine at all, it doesn't need it for the test(an oversight imo...) btw, the pod carries 10 units of RCS, early game, when you have no thrusters, right click, remove, save weight, more dv.

drag is a square function, the basic point of that is that going 10% faster, from 100%, to 110%, will cost you 21%(1.1²-1² = .21) more drag. The faster you go, the worse it gets and the faster it gets worse with increases. The faster you go in thicker air, the more you will lose to that air. Go too slow and you lose too much to gravity. Of course, thats nitpicking, too fast is well, crazy fast before atmo losses outweight the savings in gravity loss reduction. Don't worry about it, it'll be a rare thing to see someone lose more to aero on the way up than they gained from reducing gravity losses. Giant post, but you did ask why, its hard to do why without explaining, and explaining tends to get big.....so..... 10k hours on stock atmo? You know how all of us far players detested stock aero so much, and couldn't find enough bad things to say about it? There's a reason. Forget everything you know about KSP's aero that you learned prior to 1.0, none of it will help you now in any way, and nearly all of it will hinder you. It was that bad. Everything you think should launch fine based on past experience? Don't bet on it. What stock really should show the player is Q. Q is the dynamic pressure your rocket is experiencing, and is a damned good indicator of just how much the atmosphere is resisting. Those very same effects you get down low will also happen at high altitudes, if your moving fast enough. Less air doesn't mean they can't happen, just that the forces are lower so they are easier to keep controlled, but raise your speed and they WILL occur despite lower densities. Stock should beat everyone over the head with this concept with a non skip-able tutorial, the headaches understanding this would solve.... If your losing it at ~mach 1 at 6km, then assuming mach 1 as 340m/s, density at 6km of of 0.369kg/m³, Q is 21326, pretty low, which means your really draggy, or deviating too much, or lack control authority for your piloting, pick your answer, they'll all solve it. first we need density of the air. iirc, that is calculated as e^(-alt/5000), so e^(-6000/5000) = .301194, that gives us the ratio, sea level is 1.225, so at 6km its 0.301194*1.225 = 0.369kg/m³. Next we need velocity, you said mach 1 is when you lose it, and afaik KSP doesn't moderate mach with altitude, so its 340 all the way up. Q is 0.5 * density * velocity squared. so 0.5 * 0.369 * 340^2 = 21326.06 228m/s @ 2km 278m/s @ 4km 340m/s @ 6km 415m/s @ 8km 507m/s @ 10km 620m/s @ 12km 757m/s @ 14km 924m/s @ 16km 1130m/s @ 18km 1379m/s @ 20km 2273m/s @ 25km 3748m/s @ 30km 6179m/s @ 35km ... Still, same forces doesn't mean loss of control, your mass distribution is very different as your burning fuel the whole way up, so the proportions change, the centroids move, your ability to control those forces changes. Its almost impossible to compare. To finally answer the question though, how bad is breaking mach 1 at 6km? NaN......or 10, depending on your flavour. Seriously, it doesn't have an actual answer, especially not in a 1 to 10 form. Although your launch is failing, clearly a 10 for that combination of design, piloting, and launch profile. How bad is it for a given design, with a given piloting skill, with a given launch profile? That has an answer, but its troublesome to figure out, and any changes to the design, piloting, or flight profile invalidate the answer and you have to figure it all out again....much easier to just launch it, and adjust if necessary. Piloting and launch profile are both player skill, and widen the margin for design variety. Pre-1.0 piloting will not help you here, pre-1.0 launch profiles will terminate every launch for you. Its a whole new game. What is bad is generating more force(Q times drag coefficient) than you can control, and then putting it where you can't control it. The torque the nose is going to impose on you depends entirely on how far from prograde it is, increased by the leverage you give it by placing the nose far from the center of mass. if its 100% perfectly aligned with zero error, the net torque is zero, and you'll fly just fine. As long as you stay dead straight, try to move, and the force offsets, produces torque, and if you can't control it, you lose it. If you reduce your drag, you reduce the force on the rocket, and that means you could go faster for the same controllability and drag losses, reducing gravity losses. Or you might maintain control of a launch you couldn't control before. Don't underestimate how draggy something can be, and for a change, stock is more punishing than far is(both because it doesn't occlude when you think it will, and it does nothing to inform you of such control problems and far does) The more you deviate, the more leverage you give that force. This is why you can't do the old "up 10 over 45" routine anymore. This is made worse by exposing the side of the rocket to these forces as well. Ever try to hold something large and flat on a windy day? Your rocket behaves the same. Once you deviate, it pushes on your entire length on the exposed side. If everything were equal, as it was in the old aero, it wouldn't matter, but its not. Heavy engines in the rear, huge drag force on the nose. The engines want to come forward and take the lead, the nose wants to fall back and slow down, and together they'll win every time with every rocket if the pilot and engineer let it happen. Whether the pilot even has a chance is up to the engineer. Rule one: Keep the forces control-able. Slow down if your design isn't aerodynamic enough. Improve the design if you want to go faster - more control authority and/or reduce drag. Rule two: Keep the forces under control. Put them too far out of alignment, while they are too large to handle, and your screwed. Don't deviate from prograde unless the forces are small, which means either low velocity, or little/no air density. Violate either rule and aero will violate your launch. Violate neither and you can do massive launches on nothing but engine gimbal and pod torque, no dead weight reaction wheels or fins. Reaction wheels and fins just widen the margin for error by increasing control authority, they don't make the problem go away, nothing does that. The short answer is this: Fly as fast as you can reasonably control it, and yes, that means slow down if you can't. But understand that the faster you go, and the more draggy it is, and the more you deviate from prograde, the harder it will be to keep under control. Less deviation, or more aerodynamic, or less speed, and the forces will remain lower, and you are more likely to keep it controlled. If everything goes perfectly, you could keep it flying straight on 100g's of accel right up until drag crushes it, good luck with that, you WILL deviate, you WILL lose it, but theoretically possible. There is no hard fast rule anymore, and there never should have been. Stock taught you a broken system, left you with it far too long, and then pulled the rug out from under you, your a 10,000 hour newbie......can't say I've ever played a game where that was the case before.

Time doesn't matter, fuel doesn't matter, only the method of use. Some require to you right click and test, others require you trigger them by staging -right click on the part, if it says run test, you do it that way, otherwise, stage it. I typically use a cheap booster and hoist just the engine(any test parts) high enough to do the job, and chute back down. Straight up, straight down, nearly full recovery, plus payout. Quick, easy, effective. Payout is usually meager, but you can often stack several into the same launch, and they take no effort to do. If the part is immediately useful, I typically delay contract fulfillment to continue using the part.

not the only one: http://en.wikipedia.org/wiki/Tupolev_Tu-144 in fairness though, barely half its 102 scheduled flights(55) had passengers, still, its enough that concorde isn't alone on the list of super sonic passenger aircraft.

answer

yep, and the take away to be gained from that is that you will likely never achieve a perfectly smooth line, because even when your design borders on perfect, the parts themselves may have deviations that rob you of that perfect line. The closer you get, the more far will zoom in, and the more squiggly the remaining line will look.

Better is rather....subjective. Do you have any specific gripes about how stock does things? Little annoyances, etc? Your first few ventures in far are likely to frustrate, expect that. Your used to stock, what stock does and doesn't do, but this isn't stock aero, its not changes to stock aero, and it doesn't work with bits of stock aero, its a total replacement. There's a rather disturbing amount that stock doesn't factor and far does, and these little things can all come together to bite you, and you will get bit a few times before it all really sinks in. Once you get the hang of it though, you just can't go back. its not that its too different, its that, well, okay, its too different.....and better -subjective..... The biggest caution I should give you is that you don't really know how much stock ignores to protect you from complexity until those protections aren't there, and you don't take them into account while designing/piloting, and end up shearing the wings off, or stalling, two things stock makes nearly impossible to achieve but far leaves for the player to avoid. In stock, jumble parts together, check that mass is ahead of lift, and if it is, its almost certain to fly. In far? Well, notice how I mentioned designing? Yeah, you can almost certainly make just about anything fly in far, but fly well is a whole other ball game, but when you get there, its an achievement of its own. Like getting to the mun, except, local. Best of all, far provides all the tool you will need to determine that is needed to correct any issues that are occurring, but that will take a little reading and learning on your end to interpret correctly so it can be useful to you. As to what I think makes this mod better than stock, here's my answer to that, in point form, as a reply to asking what makes far special. Perhaps it answers your question better than simply asking if far is better than stock? To answer as asked though, if you seek accuracy and realism, to not be bubble wrapped, to have flight assists and supporting data to aide you in design and flight, then yes, FAR is beyond simply better, its amazingly so.

I'll just touch on area ruling as I understand things...I may as well lay it out there, I'm either right and I can help, or I'm not and we'll both get it from someone that does know more. Your constraining your focus too much, its not about gradual changes in the wing, its gradual changes in everything plus an avoidance in changes of the whole. More confused yet? First a visual, this is a cross section of a human, top down. Note that it starts small at the head, suddenly increases at the shoulders, then becomes three shapes when its torso and arms, then two when it is both legs, and again suddenly changes at the feet. That is the cross sectional shape of that particular human. For our purposes here, that is his cross sectional area at each point along the way and when its multiple shapes, they are combined for the total, so torso plus arms,or both legs, or just the head, etc. Avoid what happens at the shoulders and feet, as those are sudden and significant changes in area. Now imagine if you took your plane and did the same thing from nose to tail. You'd start off good, things would increase at a fairly steady rate, and then you'd hit the end of those canards, and suddenly the area drops, because its not fuselage plus canards anymore, now its just fuselage. But then things are good again, its all fuselage until the wings start, but they start slowly and things vary a bit but tolerable. Then we get to the end of the wings, and they just stop. The problem is this. We go from all this area the wings occupy, plus tail, plus fuselage, to just tail and fuselage, magnified even more by the fuselage thinning as well. That change is area is what's getting you. Give this image a view. As soon as they start their wings, they slim the fuselage, and its thinnest when the wings are thickest and nearly at their widest. As the wings begin the thin to the rear, the tail begins, and the fuselage slowly widens out again, so that the overall area remains nearly if not exactly the same. Then, rather than abruptly end their wings, they use a diamond shaped delta, tapering back into the fuselage to prevent a sudden change in area, and allow the fuselage some room to expand smoothly to account for it. Then, once the wings have ended, the tail is still getting bigger, so the fuselage again resumes shrinking, so that the area remains as close to constant as possible. Of course, they also have to slim down for the end, since ordinary drag doesn't agree with dragging around flat areas perpendicular to the flow. The T-38 really exemplifies it. The short version is that when you have to make something bigger, you make something else smaller at that same point, by that same amount. They initially increase to a certain point that is a useful minimum size and then try to stay at that point and no bigger/smaller until they have to reduce to a minimum at the end of the aircraft. So when the wings need to get wider and or thicker, the fuselage gets smaller and vice versa. The entire goal, is to do this, note that the wing in the image is thinning as it reaches the end which helps to offset the sudden change, KSP's wing panels don't. This would be worth a read, its not real long, doesn't get into math, its just area rule for the beginner. It is a bit more involved than that, but thats enough to get reasonable lines fairly consistently. Procedural parts will make designing it a whole lot simpler since you can scale to whatever you need at that spot.

The single greatest imo is the voxel model, which among other things, lets far determine when you have "built" a fairing or cargo bay. If the parts shield it, its shielded, end of story now. Clipped parts are shielded, unlike stock. area ruling, now that FAR takes the actual shape into account, the shape now actually matters. Aerodynamic mach effects. Stock has none, it has visual effects, I'm talking aerodynamic effects: mach tuck, transonic instability, you can and probably will stall. In stock this is nearly impossible to do, far doesn't bubblewrap the player, you will fail when you should. advanced options for control surfaces, allowing you to specify their response to commands from 0 to ±200%, as well as optional automatic response to AoA enabling unstable aircraft to be controllable, and leading edge slats, and so much more. The result is relative ease in creating and controlling super maneuverable aircraft with CoM behind CoL. while stock can do flaps now, they are all or nothing. In far they are deployed/retracted in steps, with the deflection set by you. variable wing strength, everything from light weight but fragile to virtually unbreakable but heavier. the atmosphere isn't screwy and strange. stock is still a soupmosphere, it just behaves a bit better than stock used to, FAR yields as close to real as can be done on a kerbin without adjusting atmo height - in RSS you get as close to reality as KSP can get. stability diagnostic tools. no more guessing and finding out mid flight that it yaws uncontrollably, FAR will tell you that while your building it if you ask it to. It will tell you the altitude you can reach, the AoA you need to fly at, the speed you'll stall at, so much more. What does stock tell you? a chute implementation(essentially a variant of real chutes integrated into FAR) that permits braking chutes that stay deployed on landing, and more. Stock is better than it was, but comparatively it falls rather short still. flight stability assists that ease keyboard flight by helping damp out rolling, yawing, pitching, high AoA, and dimming control authority to keep you from ripping the wings off. Flight just works better in FAR. very detailed readout in flight of your aircraft's performance, to further aide you in optimising if you are so inclined. last, FAR doesn't dumb down for the average player like stock has, it is what it really is. What works in reality stands a damn good shot at working in far, and best of all, most of the worlds info on aero applies to FAR's aero. What better documentation could there be? The opposite is of course true, what shouldn't work, won't work, though with proper design just about anything is still possible. and I'm sure I have forgotten things worth mentioning. couple that with stock not doing hardly any of what far does, and what little it sort of does, it does in a hacky sort of "fake it til you make it" kind of way, and there really is no comparison. Really, in all fairness, the only thing stock aero does right is disconnecting the forces from the center of mass, finally acknowledging that these forces produce torque, and so stability matters.

regarding turbojets in 1.0, I've got a stock aircraft that can do 21000 @ 1150ish sustained, but to get up there takes forever, very shallow climb beyond 20,000, and very slow accel beyond 1100 while up there. That said, yeah, they killed air hogging and gave the rapier a niche by tying the output to altitude, add more intakes all you want, won't do anything unless the intakes your using are under-performing. You won't get much higher on jets I don't think, and good luck keeping the turbojet alive above 25000 on its own. Did a quick bit of math in excel and found the following for the turbojet: the following assumes that the engine shuts down regardless at 10% of "nominal thrust", that being the value in the cfg which is 180kN, so when it reaches 18kN, it shuts down. So I end it at 26600. I could be totally wrong on the shut down point, so take that with a grain of salt. Mind you, its pretty useless when it only yields 18kN anyways, so yeah. velocity is 1100m/s, speeds are in percentage of maximum, which is 964.787kN at 1100m/s at sea level. Because they are percentages, and based on the altitude data, they should hold for any speed, though if you are slower, then you can't get as high before the engine starves and shuts down. Its rather approximate, because I'm not trying to deal with slope smoothing, rather, I just take the upper and lower value, and interpolate the result A quick example process before the table: 2000m is a pressure of e^(-2000/5000) = 0.67032 from the turbojet cfg: 1=1, 0.5=0.6, so my upper atmos value is 1, lower is 0.5, and upper thrust is 1 and lower is 0.6 (atmo - lower_atmo)/(upper_atmo - lower_atmo) * (upper_thrust - lower_thrust) + lower_thrust (0.67032 - 0.5)/(1 - 0.5) * (1 - 0.6) + 0.6 (0.17032)/(0.5) * (0.4) + 0.6 0.34064 * (0.4) + 0.6 0.136256 + 0.6 thrust factor = 0.736256 did the same for mach number, I assume mach in KSP is a flat 340m/s? then it was just multiplying the two factors. [table] [tr][th]Altitude[/th][th]Thrust[/th][/tr] [tr][th]0m[/th][th]100.0%[/th][/tr] [tr][th]200[/th][th]96.879[/th][/tr] [tr][th]400[/th][th]93.864[/th][/tr] [tr][th]600[/th][th]90.968[/th][/tr] [tr][th]800[/th][th]88.186[/th][/tr] [tr][th]1000[/th][th]85.512[/th][/tr] [tr][th]1200[/th][th]82.943[/th][/tr] [tr][th]1400[/th][th]80.476[/th][/tr] [tr][th]1600[/th][th]78.104[/th][/tr] [tr][th]1800[/th][th]75.826[/th][/tr] [tr][th]2000[/th][th]73.637[/th][/tr] [tr][th]2200[/th][th]71.534[/th][/tr] [tr][th]2400[/th][th]69.514[/th][/tr] [tr][th]2600[/th][th]67.572[/th][/tr] [tr][th]2800[/th][th]65.707[/th][/tr] [tr][th]3000[/th][th]63.915[/th][/tr] [tr][th]3200[/th][th]62.193[/th][/tr] [tr][th]3400[/th][th]60.539[/th][/tr] [tr][th]3600[/th][th]59.62[/th][/tr] [tr][th]3800[/th][th]59.058[/th][/tr] [tr][th]4000[/th][th]58.519[/th][/tr] [tr][th]4200[/th][th]58.001[/th][/tr] [tr][th]4400[/th][th]57.503[/th][/tr] [tr][th]4600[/th][th]57.024[/th][/tr] [tr][th]4800[/th][th]56.565[/th][/tr] [tr][th]5000[/th][th]56.123[/th][/tr] [tr][th]5200[/th][th]55.699[/th][/tr] [tr][th]5400[/th][th]55.291[/th][/tr] [tr][th]5600[/th][th]54.899[/th][/tr] [tr][th]5800[/th][th]54.523[/th][/tr] [tr][th]6000[/th][th]54.161[/th][/tr] [tr][th]6200[/th][th]53.814[/th][/tr] [tr][th]6400[/th][th]53.48[/th][/tr] [tr][th]6600[/th][th]53.16[/th][/tr] [tr][th]6800[/th][th]52.851[/th][/tr] [tr][th]7000[/th][th]52.555[/th][/tr] [tr][th]7200[/th][th]52.271[/th][/tr] [tr][th]7400[/th][th]51.998[/th][/tr] [tr][th]7600[/th][th]51.735[/th][/tr] [tr][th]7800[/th][th]51.483[/th][/tr] [tr][th]8000[/th][th]51.24[/th][/tr] [tr][th]8200[/th][th]51.008[/th][/tr] [tr][th]8400[/th][th]50.784[/th][/tr] [tr][th]8600[/th][th]50.569[/th][/tr] [tr][th]8800[/th][th]50.362[/th][/tr] [tr][th]9000[/th][th]50.164[/th][/tr] [tr][th]9200[/th][th]49.664[/th][/tr] [tr][th]9400[/th][th]47.856[/th][/tr] [tr][th]9600[/th][th]46.118[/th][/tr] [tr][th]9800[/th][th]44.448[/th][/tr] [tr][th]10000[/th][th]42.843[/th][/tr] [tr][th]10200[/th][th]41.302[/th][/tr] [tr][th]10400[/th][th]39.821[/th][/tr] [tr][th]10600[/th][th]38.398[/th][/tr] [tr][th]10800[/th][th]37.031[/th][/tr] [tr][th]11000[/th][th]35.717[/th][/tr] [tr][th]11200[/th][th]34.455[/th][/tr] [tr][th]11400[/th][th]33.243[/th][/tr] [tr][th]11600[/th][th]32.078[/th][/tr] [tr][th]11800[/th][th]30.958[/th][/tr] [tr][th]12000[/th][th]29.883[/th][/tr] [tr][th]12200[/th][th]28.85[/th][/tr] [tr][th]12400[/th][th]27.857[/th][/tr] [tr][th]12600[/th][th]26.903[/th][/tr] [tr][th]12800[/th][th]25.987[/th][/tr] [tr][th]13000[/th][th]25.106[/th][/tr] [tr][th]13200[/th][th]24.26[/th][/tr] [tr][th]13400[/th][th]23.447[/th][/tr] [tr][th]13600[/th][th]22.666[/th][/tr] [tr][th]13800[/th][th]21.916[/th][/tr] [tr][th]14000[/th][th]21.195[/th][/tr] [tr][th]14200[/th][th]20.503[/th][/tr] [tr][th]14400[/th][th]19.837[/th][/tr] [tr][th]14600[/th][th]19.198[/th][/tr] [tr][th]14800[/th][th]18.583[/th][/tr] [tr][th]15000[/th][th]17.993[/th][/tr] [tr][th]15200[/th][th]17.426[/th][/tr] [tr][th]15400[/th][th]16.881[/th][/tr] [tr][th]15600[/th][th]16.292[/th][/tr] [tr][th]15800[/th][th]15.653[/th][/tr] [tr][th]16000[/th][th]15.039[/th][/tr] [tr][th]16200[/th][th]14.449[/th][/tr] [tr][th]16400[/th][th]13.883[/th][/tr] [tr][th]16600[/th][th]13.339[/th][/tr] [tr][th]16800[/th][th]12.816[/th][/tr] [tr][th]17000[/th][th]12.313[/th][/tr] [tr][th]17200[/th][th]11.83[/th][/tr] [tr][th]17400[/th][th]11.366[/th][/tr] [tr][th]17600[/th][th]10.921[/th][/tr] [tr][th]17800[/th][th]10.492[/th][/tr] [tr][th]18000[/th][th]10.081[/th][/tr] [tr][th]18200[/th][th]9.686[/th][/tr] [tr][th]18400[/th][th]9.306[/th][/tr] [tr][th]18600[/th][th]8.941[/th][/tr] [tr][th]18800[/th][th]8.59[/th][/tr] [tr][th]19000[/th][th]8.254[/th][/tr] [tr][th]19200[/th][th]7.93[/th][/tr] [tr][th]19400[/th][th]7.619[/th][/tr] [tr][th]19600[/th][th]7.32[/th][/tr] [tr][th]19800[/th][th]7.033[/th][/tr] [tr][th]20000[/th][th]6.758[/th][/tr] [tr][th]20200[/th][th]6.493[/th][/tr] [tr][th]20400[/th][th]6.238[/th][/tr] [tr][th]20600[/th][th]5.993[/th][/tr] [tr][th]20800[/th][th]5.758[/th][/tr] [tr][th]21000[/th][th]5.533[/th][/tr] [tr][th]21200[/th][th]5.316[/th][/tr] [tr][th]21400[/th][th]5.107[/th][/tr] [tr][th]21600[/th][th]4.907[/th][/tr] [tr][th]21800[/th][th]4.715[/th][/tr] [tr][th]22000[/th][th]4.53[/th][/tr] [tr][th]22200[/th][th]4.352[/th][/tr] [tr][th]22400[/th][th]4.181[/th][/tr] [tr][th]22600[/th][th]4.017[/th][/tr] [tr][th]22800[/th][th]3.86[/th][/tr] [tr][th]23000[/th][th]3.709[/th][/tr] [tr][th]23200[/th][th]3.563[/th][/tr] [tr][th]23400[/th][th]3.423[/th][/tr] [tr][th]23600[/th][th]3.289[/th][/tr] [tr][th]23800[/th][th]3.16[/th][/tr] [tr][th]24000[/th][th]3.036[/th][/tr] [tr][th]24200[/th][th]2.917[/th][/tr] [tr][th]24400[/th][th]2.803[/th][/tr] [tr][th]24600[/th][th]2.693[/th][/tr] [tr][th]24800[/th][th]2.587[/th][/tr] [tr][th]25000[/th][th]2.486[/th][/tr] [tr][th]25200[/th][th]2.388[/th][/tr] [tr][th]25400[/th][th]2.295[/th][/tr] [tr][th]25600[/th][th]2.205[/th][/tr] [tr][th]25800[/th][th]2.118[/th][/tr] [tr][th]26000[/th][th]2.035[/th][/tr] [tr][th]26200[/th][th]1.956[/th][/tr] [tr][th]26400[/th][th]1.879[/th][/tr] [tr][th]26600[/th][th]1.805[/th][/tr] [/table]

Try it in far, bet you get better results. If parts ~should~ occlude, they will, and stock doesn't have a snowballs chance on moho of matching it.

new dependency, modular flight integrator, you need it, and I bet you don't have it. ....and ninja'd

you have this? http://forum.kerbalspaceprogram.com/threads/118088-1-00-ModularFlightIntegrator-1-0-%28Apr-30%29 if you don't, that's probably the issue, dev build requires it.

Been there, done that, complete agree, being the root part will cause the motors to not drop off, simply not using them as root resolves it.