Starwaster

Woah.... inneresting

Kill it. Kill it with fire!!! (that was all caps, but it wont let me do all caps even though it would have been appropriate, so just pretend that I used all caps. Here, let me boldface it and italicize it, maybe that helps)

And, also, it has to be decoupled either through the context menu (right click the part) or through an action group item. It does not respond to staging.

It's in KSP_Data

As in reversed, you mean? It has to be reversed. In the game it comes out reverse of whatever the texture looks like.

I'll probably be working.

Please demonstrate using KSP 0.25 and the most recent stable official MechJeb release for KSP 0.25 that it can in fact properly set up a rendezvous with a target in a polar orbit using the Launch to Rendezvous and specifying only an Orbit Inclination of 0 as you say that it did. Because I tested that postulation and was not able to validate it. KSP 0.25 with latest stable official MechJeb release for KSP 0.25 behaved exactly as it does now given the setup designated in your message.

I'm not going to get ticked off for feedback on a file I told you you needed. Not sure why you'd have problems with it though. Is it not deploying at ALL? How far down did you let it go?

It is normal to experience lessened heating from steeper reentries. The danger shifts from burning up to increased g forces. I'll look at the log and get back to you.

I've felt a great disturbance in the Module Manager, as if millions of indentations cried out in terror and then were suddenly silenced...

It can only be opened in flight mode so the option only shows up in flight mode.

That's the file that is causing your problems. The version that I am directing you to download is the version that (barring any more changes) will be in the next update of Deadly Reentry. It makes fewer changes than the older file does. Doesn't touch deployment times and focuses mainly on making predeployment safer by shifting the altitude low enough that the pod should be subsonic.

Honestly, I'd just delete that post... and we can all pretend it didn't happen.

For future reference, it's not model =, it's a node. (i.e. MODEL{}) example: MODEL { model = DeadlyReentry/Parts/deadlyReentry_6.25Heatshield/model.mu //scale = 1.0, 1.0, 1.0 //texture = can't remember how to specify texture but you wouldn't have needed it anyway }

There are two types of fairings. The actual fairings which are under the Aerodynamics tab and the Fuselage pieces which do the same thing but do not decouple. You used the fuselage parts.

Read this thread, somewhere around the middle (just text search for 'player.log') it tells you how to find your logs. http://forum.kerbalspaceprogram.com/threads/92229

Hukt on rokkit siunce werkt fer mee.

You have to copy your settings to the other chutes. There's a button for that. Copying to symmetry doesn't happen automagically.

Yes it's Attitude Adjustment (Adjuster?). It's the second menu item in the main MJ menu. Look for 'Use Stock SAS'. For some reason it becomes ineffective above a certain altitude. I thought it was good up until at least 50km but it could be lower. No, it's old. There's been an option to engage it for quite awhile now. As I explained to Fellow314 above, in Attitude Adjustment. It works great, even better than MJ's PID, but only at low altitudes. In orbit, it's horrible however. Pretty much behaves as he indicated in those pictures. I have a feeling it has to do with how MJ is invoking it. Maybe something to do with the different frame of reference.

Are you adding it to the toolbar?

it was there. It's been there ever since that part was introduced. It lets you create adapters in the style of the Saturn V 3rd stage which had a payload space for the lunar lander inside and the Apollo CM/SM on top. Or a docking adapter instead of the lander. For docking with soviet craft. resize it like I said, if you're having trouble. Or move the top node up out of the way. Or just accept it being attached there. Depending on design that could be an option. That part is flexible.

He also needs roll authority. There's not enough. If there's RCS then it's not active. And no control surfaces. (Would they still be effective at that altitude? Maybe maybe not) Finally, turn off Stock SAS. MJ's interaction with Stock SAS is only effective at low altitudes.

output_log.txt, not ksp.log (or player.log if using Linux/Mac)

It would also be nice if people stopped using spaces. When it works at all it should be considered a work-around

You're getting a lot of errors from MechJebFARExt.dll (Sarbian's FAR extensions for MJ) An error at just the wrong time could prevent other functions from being called. Not sure how your new observations fit into this... But what I suggest is removing the FAR Extensions and seeing if the problem persists. Or see if there's an updated version of it. Something else I noticed was a lot of RT errors, but that's a discussion for their thread. I enclose the error below: (the log said it was version 1.5 but there was an AVC log entry indicating it downloaded 1.5.2) NullReferenceException: Object reference not set to an instance of an object at kOS.SteeringHelper.GetThrustTorque (.Part p, .Vessel vessel) [0x00000] in <filename unknown>:0 at kOS.SteeringHelper.GetTorque (.Vessel vessel, Single thrust) [0x00000] in <filename unknown>:0 at RemoteTech.FlightComputer.updatePIDParameters () [0x00000] in <filename unknown>:0 at RemoteTech.FlightComputer.OnFixedUpdate () [0x00000] in <filename unknown>:0 at RemoteTech.ModuleSPU.FixedUpdate () [0x00000] in <filename unknown>:0 (Filename: Line: -1) That's about what I would do. Launch into its plane at about 150km altitude. That will get a transfer window opening in a few hours at most, fine tune correction after the transfer and it's done. DV for the transfer is pretty negligible