Cherenkov

Just logged in just to say the same thing. Ideally the fairing should be able to end in an open aperture, fitting around or connecting to a part such as a fuel tank, so that you could make a rocket with a "bulge" in the middle holding your ugly lem /rover etc and still have the command module sticking out. (or mount the fairing up side down for additional coolness) If this could be made to work like the struts, but with a procedural+structurally connecting fairing i think i'll be in nerdvana. /C Edit: had a follow on thought.

Posted this in the general support thread but was referred here by moderator: I tried to use mechjeb\'s ability to 'keep alive' the debris to make deployable 'landing probes' that piggyback onto my main vessel i but got some problems: even if i have an SAS on my probe i cannot alter the course without using the engines. there is no response at all to wasd when engines off. I can throttle and engage SAS ok, and steer when the engines are running (although with some strange limits, as sometimes not able to turn left etc.) when i add RCS i can use those with wasd, but their behavior is also strange, as in mirrored effects etc. (turn occurs in direction of plume, not all RCS ports venting etc. ) i can operate landing gear just fine. I have tried this with the probe constructed above and below the command module, but the error occurs in both cases. Initially i did not think this was due to mechjeb, it seems like there is a bug with how the axises of the child vessel is set up when it detaches, but i was referred here. Could it be an issue with mj? I\'ve attached a ship to demonstrate, requires mechjeb 1.8.4 and novapunch 1.2 beta, but the bug can be recreated with stock parts as well. (+ mechjeb o.c.)

CRAFT: Mun Mobile VI MISSION:Land On Mun, dispatch independent lunar rover for unmanned exploration, return crew to Kerbin. CREW: [suppressed by thoughty police] LAUNCH DATE: v015 Telemetry: t-3: Ignition sequence start. t-3: SAS system nominal t-2: All 7 quad LF-engines of stage 1 successfully achieved ignition. t-1: Throttle ramp initated t-0: All 6 SRB Of stage 1.5 ignited sucsessfully t+1: Pad clerance reported. t+10: Flight stable, All systems nominal t+80: SRB flamout t+81: SRB stage separation succesful t+100: retrograde gravity turn initated t+120: stage 1 flameout t+121: stage 1 separation t+122: Warning: stage 2 ullage engine failure t+125: stage 2 main engine started t+130: retrograde TMI initated t+150: TMI compete t+151:stage 2 main engine shutdown. t+3000: retrograde Munar orbit curcularization burn initated. t+3005: burn ended. t+3010: stage 2 separation t+3011: Warning z axis rotation outside of mission and craft parameters. t+3011: Warning impact detected [engineers comments] crew reports that the craft spun violently in the positive pitch direction for 180 and then shuddered as if impacting analysis of the craft design indicate that the change of stage decoupler ejection force and placement from mission V may have introduced an torque impulse during decoupling It is hypothesized that the impact felt was self impact on the separated second stage this and the very high torque forces experienced may have contributed to subsequent events. ] t+3030 spin nominal t+4000 munar parabolic orbit indicated by OFPS t+4010 munar synchronization burn initiated. t+4020 Munar syncronization complete. t+5030 Munar periphasis reached t+5033 Munar curcularization burn initated t+5045 Munar curcularization burn complete [Flight log: all systems and diagnostics appear nominal. initiating reentry burn. Lander out] t+6245 Munar decent burn initated. t+6260 phase 1 Munar decent burn complete. target locked in. t+6265 Payload decoupler activated t+6265 Warning: Payload not detected t+6268 Warning: stage 3 Engines not responding [flight log: We have lost payload and landing engines. trying to resume engine function] t+6341 Warning: Descent path critical [Flight log: Abort abort abort activating return stage ] t+6355 stage 3 decoupled t+6360 Warning: stage 4 ullage engine not responding t+6360 Warning: stage 4 main engine not responding [Flight log: Mayday! Mayday! Mayday! ] t+6365 Warning: Descent path critical [Flight log: AaaaaaaaaAAaaaAAA aaaaaaaaaaaaaaaaaaaaaaa!] t+6395 Warning: Low altitude t+6401 Error: Telemetry lost [analysis: It cannot be ruled out that crew incompetence contributed to the mission failure. The raw data stream indicates that the crew mistakenly dispatched the payload when playing a game of pocket ping pong during the descent phase. this practice should be discouraged. However, the true cause of the deaths and Embarrassment rests solely with the engineering department. A recent design review indicates not only the above mentioned issue with a badly placed second stage decoupler but also that the fuel tank of the forth stage was not connected to any of the engines. To encourage a more thorough design process going forward, volunteers for subsequent missions will be assigned from the engineering staff.] FLIGHT DURATION: MISSION OUTCOME: Tragic loss of life and vital mission materiel.

Hmm, your chosen site seems to be on the edge of a crater. Might explain the pile of debris downhill, tricky to put a phallic suitably impressive rocket there. This shure makes the game laggy, even on my i7950... but fun.