triffid_hunter

Actually there is - Maneuver nodes! First get into LKO, then set up a maneuver node that barely escapes Kerbin's SOI in the direction of kerbin's travel (for outer planets) or in reverse direction (for inner planets). Then create a second node in Kerbol's SOI to intercept the target's orbit, and drag it around to find your intercept. DO NOT EXECUTE THESE NODES - instead, wait until *kerbin itself* is at the position of the second node, then delete both nodes and construct a new one to burn straight from LKO. I made a video about it:

I think you should make a new forum thread, and let this one die

is it just me or does the download link in top post simply redirect back to this forum thread? tried in browser first, wget finds same conundrum:

From what I've seen, providing/filling fuel is implemented as an engine that consumes a negative quantity of fuel. I would expect you to no longer be able to receive fuel if you remove the engine module.

This is a bug with latest mechjeb release, seems to be fixed in mechjeb dev. If you go into attitude control you'll notice that many of the fields go to infinity when this happens. I can generally trigger it by decoupling a ship without a SAS wheel from a larger ship that does have a SAS wheel somewhere.

This mod is very understated, I'm surprised it's not more popular any chance we could optionally add RocketParts to the list of supplied resources?

excellent, glad to know it's not just me just a heads up, I did manage to trigger this in the VAB today, same sequence- holding a part for radial attach, then shift+c to go no_snap -> 90

Bug report! Problem: hard crash (Floating Point Exception) 1) go to SPH (doesn't seem to happen in VAB) 2) place command pod 3) select a radially mountable part 4) hover over command pod for radial placement 5) press shift+C a few times 6) at the transition from 'no snap' to '90°', KSP bombs, printing "Floating Point Exception" to terminal using linux 64 bit binary This behaviour isn't new in 0.23, but 0.23's massively faster load time has allowed me the patience to find a way to reliably reproduce it Other than this, works perfect in 0.23. may want to update thread title

GLC works great for me, that's what I've been using to record my videos. ps: congrats on inheriting EL, I'll grab this ver and test it soon

http://bugs.kerbalspaceprogram.com/issues/1230

I have, you want SURFACE_VELOCITY, BACK. would really love a couple of buttons for easy access to surface pro/retrograde While I'm at it, any chance of moving the aerobrake prediction out of landing autopilot? I think it makes sense to separate those and make aerobrake prediction available maybe one tier earlier in the tech tree

Keosync is at 2868km, a bit beyond the range of the starter omni antenna. Instead, put 6+ sats in a ring at at half-sync (1585km) so there's always one or two within range of KSC, and they're also within range of each other so signals can pass around the whole ring. Then you get no more blackouts in space near Kerbin. Then you can put something with an omni and a dish or two up at keosync (2868.7km). the omni will hit your half-sync ring, and the dish can point at Mun or Minmus maybe put a matching pair opposite KSC to keep Mun/Minmus online 24/7 (or is it 6/7 since Kerbin's day is 6 hours?) highly elliptical polar orbits become pretty useful around this point see my half-sync ring + two keosync sats - I set the pictured craft in an orbit with apo at 1585km and orbital period of 7/8 * 3h (2:37:30, peri about 1219km), then dropped off a sat every time I got to apo, then circularised the sat targeting an orbital period of exactly 3h (can see reading of 2:59:60.0 pictured) Yes, I placed every last one manually using only the orbital period readout from KER. MJ was used just for orientation and ascent autopilot, but not injection orbits or circularising since it's frankly not accurate enough. With a range of 2.5Mm you need >5.5 sats at half-sync for an unbroken, zero blackout ring. I went with 8 for redundancy and because I didn't know how accurately I could position them.

Bug report: If I radially attach things, then I can only attach the welded part to my rocket by the nodes that appear at the radial attachment points. Example (5x X200-16 tanks arranged in a 4-pointed star using I-beams): PART { name = Station-Core-4 module = Part author = UbioZurWeldingLtd rescaleFactor = 1 PhysicsSignificance = -1 node_stack_top4294427884 = 2.086163E-07,0.4687508,2.086163E-07,0,1,0,2 node_stack_bottom4294427884 = 2.086163E-07,-0.4687492,2.086163E-07,0,1,0,2 node_stack_top4294426714 = -3.13744,-8.813257E-07,-3.137441,0.7071068,4.768372E-07,0.7071069,0 node_stack_bottom4294426714 = -0.8771394,6.429071E-07,-0.8771399,-0.7071068,-4.768372E-07,-0.7071069,0 node_stack_top4294423812 = -3.987281,0.4687499,-3.987282,-7.787723E-08,1,3.225779E-08,2 node_stack_bottom4294423812 = -3.987281,-0.4687501,-3.987282,-7.787723E-08,1,3.225779E-08,2 node_stack_top4294426620 = -3.137441,-5.002676E-07,3.13744,0.7071068,2.384186E-07,-0.7071067,0 node_stack_bottom4294426620 = -0.8771402,2.618489E-07,0.8771398,-0.7071068,-2.384186E-07,0.7071067,0 node_stack_top4294423614 = -3.987282,0.4687499,3.987281,-5.034347E-08,1,-4.366267E-08,2 node_stack_bottom4294423614 = -3.987282,-0.4687501,3.987281,-5.034347E-08,1,-4.366267E-08,2 node_stack_top4294426596 = 3.137441,-8.813257E-07,3.137441,-0.7071069,4.768372E-07,-0.7071069,0 node_stack_bottom4294426596 = 0.87714,6.429071E-07,0.8771403,0.7071069,-4.768372E-07,0.7071069,0 node_stack_top4294423582 = 3.987281,0.4687499,3.987282,-5.506751E-08,1,-2.280971E-08,2 node_stack_bottom4294423582 = 3.987281,-0.4687501,3.987282,-5.506751E-08,1,-2.280971E-08,2 node_stack_top4294426572 = 3.137441,-5.002676E-07,-3.13744,-0.7071068,2.384186E-07,0.7071067,0 node_stack_bottom4294426572 = 0.8771402,2.618489E-07,-0.8771396,0.7071068,-2.384186E-07,-0.7071067,0 node_stack_top4294423550 = 3.987282,0.4687499,-3.98728,5.506752E-08,1,-2.280971E-08,2 node_stack_bottom4294423550 = 3.987282,-0.4687501,-3.98728,5.506752E-08,1,-2.280971E-08,2 node_attach = 1.25,0,0,1,0,0,1 cost = 4900 category = Structural subcategory = 0 title = Station Core:4way manufacturer = UbioZur Welding Ltd description = Warranty void during re-entry. attachRules = 1,1,1,1,0,0,0 mass = 4 dragModelType = default maximum_drag = 1.8 minimum_drag = 2.3 angularDrag = 14 crashTolerance = 6 breakingForce = 200 breakingTorque = 200 maxTemp = 2900 fuelCrossFeed = True MODEL { model = Squad/Parts/FuelTank/fuelTank4-2/model position = 2.086163E-07,8.34465E-07,2.086163E-07 scale = 1,1,1 rotation = 0,0,0 } MODEL { model = Squad/Parts/Structural/structuralIBeam2/model position = -2.00729,-1.192093E-07,-2.007291 scale = 1,1,1 rotation = 90,225,0 } MODEL { model = Squad/Parts/FuelTank/fuelTank4-2/model position = -3.987281,-1.192093E-07,-3.987282 scale = 1,1,1 rotation = 4.462037E-06,315,1.848235E-06 } MODEL { model = Squad/Parts/Structural/structuralIBeam2/model position = -2.007291,-1.192093E-07,2.00729 scale = 1,1,1 rotation = 90,315,0 } MODEL { model = Squad/Parts/FuelTank/fuelTank4-2/model position = -3.987282,-1.192093E-07,3.987281 scale = 1,1,1 rotation = 360,44.99999,2.706683E-07 } MODEL { model = Squad/Parts/Structural/structuralIBeam2/model position = 2.007291,-1.192093E-07,2.007291 scale = 1,1,1 rotation = 90,45,0 } MODEL { model = Squad/Parts/FuelTank/fuelTank4-2/model position = 3.987281,-1.192093E-07,3.987282 scale = 1,1,1 rotation = 360,135,-3.155136E-06 } MODEL { model = Squad/Parts/Structural/structuralIBeam2/model position = 2.007291,-1.192093E-07,-2.00729 scale = 1,1,1 rotation = 90,135,0 } MODEL { model = Squad/Parts/FuelTank/fuelTank4-2/model position = 3.987282,-1.192093E-07,-3.98728 scale = 1,1,1 rotation = 360,225,3.155136E-06 } RESOURCE { name = LiquidFuel amount = 1800 maxAmount = 1800 } RESOURCE { name = Oxidizer amount = 2200 maxAmount = 2200 } } I'm not familiar enough with KSP's part system to derive what's wrong with this, but it simply refuses to attach as a vertical stack.. it'll snap to a node, but when I click the part remains semi-transparent and red-tinged meaning it's placed but not attached... I can successfully radially attach it though. Also, if I summon one as the root (first) part, I can successfully attach other parts to it.

+1 for Douglas Adams reference I like the rest of your idea too, ie a highly expanded tech tree with some random variations thrown in, like a 1 in 1e7 chance of discovering quantum physics shortly after the telescope, balanced to roughly follow our historical pace of development

I can't for the life of me remember where I saw this idea and so can't credit its original author, but it's the most sensible one I've seen yet: (not quoted verbatim, just my own wording of the idea itself)