Starwaster

Abort to Island Runway. From angels 10. Thank you, MechJeb.

Good catch, didn't see that. He's also only running 1.0.4.1, but so was I and my paradocks worked fine.

Not seeing anything glaringly obvious. Not a lot of errors. A few but nothing that's a smoking gun. But you do have a lot of MM configs that are adding things to the paradocks. Including something that alters the action groups? Clarification request: Does this happen as soon as the rocket loads in or when you're trying to launch? If the latter, make sure nothing is adding the chutes to the staging action group. Line 1616: [ModuleManager] Applying node AdaptiveDockingNode/AdaptiveDockingNode/@PART[*]:HAS[!MODULE[ModuleAdaptiveDockingNode],@MODULE[ModuleDockingNode]:HAS[#nodeType[size1]]] to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 1616: [ModuleManager] Applying node AdaptiveDockingNode/AdaptiveDockingNode/@PART[*]:HAS[!MODULE[ModuleAdaptiveDockingNode],@MODULE[ModuleDockingNode]:HAS[#nodeType[size1]]] to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 1644: [ModuleManager] Applying node ConnectedLivingSpace/Plugins/CLSDumSumHeavyIndustries/@PART[SDHI_ParaDock_1_ClampOTron]:HAS[!MODULE[ModuleConnectedLivingSpace]] to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 1644: [ModuleManager] Applying node ConnectedLivingSpace/Plugins/CLSDumSumHeavyIndustries/@PART[SDHI_ParaDock_1_ClampOTron]:HAS[!MODULE[ModuleConnectedLivingSpace]] to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 1644: [ModuleManager] Applying node ConnectedLivingSpace/Plugins/CLSDumSumHeavyIndustries/@PART[SDHI_ParaDock_1_ClampOTron]:HAS[!MODULE[ModuleConnectedLivingSpace]] to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 1648: [ModuleManager] Applying node ConnectedLivingSpace/Plugins/CLSDumSumHeavyIndustries/@PART[SDHI_ParaDock_2_IACBM]:HAS[!MODULE[ModuleConnectedLivingSpace]] to SDHI/Service Module System/Parts/SDHI_ParaDock_2_IACBM/part/SDHI_ParaDock_2_IACBM Line 1648: [ModuleManager] Applying node ConnectedLivingSpace/Plugins/CLSDumSumHeavyIndustries/@PART[SDHI_ParaDock_2_IACBM]:HAS[!MODULE[ModuleConnectedLivingSpace]] to SDHI/Service Module System/Parts/SDHI_ParaDock_2_IACBM/part/SDHI_ParaDock_2_IACBM Line 1648: [ModuleManager] Applying node ConnectedLivingSpace/Plugins/CLSDumSumHeavyIndustries/@PART[SDHI_ParaDock_2_IACBM]:HAS[!MODULE[ModuleConnectedLivingSpace]] to SDHI/Service Module System/Parts/SDHI_ParaDock_2_IACBM/part/SDHI_ParaDock_2_IACBM Line 2456: [ModuleManager] Applying node DockingNodeController/Config/@PART[*]:HAS[@MODULE[ModuleDockingNode]] to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 2456: [ModuleManager] Applying node DockingNodeController/Config/@PART[*]:HAS[@MODULE[ModuleDockingNode]] to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 2460: [ModuleManager] Applying node DockingNodeController/Config/@PART[*]:HAS[@MODULE[ModuleDockingNode]] to SDHI/Service Module System/Parts/SDHI_ParaDock_2_IACBM/part/SDHI_ParaDock_2_IACBM Line 2460: [ModuleManager] Applying node DockingNodeController/Config/@PART[*]:HAS[@MODULE[ModuleDockingNode]] to SDHI/Service Module System/Parts/SDHI_ParaDock_2_IACBM/part/SDHI_ParaDock_2_IACBM Line 3228: [ModuleManager] Applying node TweakableEverything/TweakableDockingNode/@PART[*]:HAS[@MODULE[ModuleDockingNode]] to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 3228: [ModuleManager] Applying node TweakableEverything/TweakableDockingNode/@PART[*]:HAS[@MODULE[ModuleDockingNode]] to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 3232: [ModuleManager] Applying node TweakableEverything/TweakableDockingNode/@PART[*]:HAS[@MODULE[ModuleDockingNode]] to SDHI/Service Module System/Parts/SDHI_ParaDock_2_IACBM/part/SDHI_ParaDock_2_IACBM Line 3232: [ModuleManager] Applying node TweakableEverything/TweakableDockingNode/@PART[*]:HAS[@MODULE[ModuleDockingNode]] to SDHI/Service Module System/Parts/SDHI_ParaDock_2_IACBM/part/SDHI_ParaDock_2_IACBM Line 4132: [ModuleManager] Applying node DeadlyReentry/DeadlyReentry-RealChutes/@PART[*]:HAS[@MODULE[RealChuteModule]]:Final to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 4132: [ModuleManager] Applying node DeadlyReentry/DeadlyReentry-RealChutes/@PART[*]:HAS[@MODULE[RealChuteModule]]:Final to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 4136: [ModuleManager] Applying node DeadlyReentry/DeadlyReentry-RealChutes/@PART[*]:HAS[@MODULE[RealChuteModule]]:Final to SDHI/Service Module System/Parts/SDHI_ParaDock_2_IACBM/part/SDHI_ParaDock_2_IACBM Line 4136: [ModuleManager] Applying node DeadlyReentry/DeadlyReentry-RealChutes/@PART[*]:HAS[@MODULE[RealChuteModule]]:Final to SDHI/Service Module System/Parts/SDHI_ParaDock_2_IACBM/part/SDHI_ParaDock_2_IACBM Line 6344: [ModuleManager] Applying node Diazo/AGExt/part/@PART[*]:Final to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 6344: [ModuleManager] Applying node Diazo/AGExt/part/@PART[*]:Final to SDHI/Service Module System/Parts/SDHI_ParaDock_1_ClampOTron/part/SDHI_ParaDock_1_ClampOTron Line 6348: [ModuleManager] Applying node Diazo/AGExt/part/@PART[*]:Final to SDHI/Service Module System/Parts/SDHI_ParaDock_2_IACBM/part/SDHI_ParaDock_2_IACBM Line 6348: [ModuleManager] Applying node Diazo/AGExt/part/@PART[*]:Final to SDHI/Service Module System/Parts/SDHI_ParaDock_2_IACBM/part/SDHI_ParaDock_2_IACBM

Bah, it wasn't funny when I made that joke It's for when your spaceplane touches down on the runway; the drag chute deploys

a) is possible is not. conditional math is not checked for by any version of ModuleManager @PART[*]:HAS[~breakingForce[]] { breakingForce = 1000 } @PART[*]:HAS[~breakingTorque[]] { breakingTorque = 1000 }

Sadly, I've had such a hard time tonight with getting to orbit that I've gotten proficient at aborting to runway. Actually MechJeb guided me in through Spaceplane Guidance. Which is interesting considering how people have said it doesn't work... I think even in this thread for its interaction with KSO...

Take out the <> I put those there to signify that the text between was variable.

You'd have to replace any 'mesh =' lines with MODEL{} nodes. Something like.... @PART[somePartID] { !mesh MODEL { model = <path to the Squad model for that part> scale = 1.0, 1.0, 1.0 texture = <path to your texture for this model> } } I think that's the right way to use MODEL but it's up to you to do proper research and verify. (actually everything up to texture is correct.... just not sure about texture) If you use non .mbm though, like .png you can just stick it in that part's folder and it overrides it. With the obvious caveat that to uninstall it, people have to go in and delete those textures.

Only white spaces. And nobody should be using those anyway. There are long standing issues with white spaces and not just in Module Manager. Later versions of MM try to strip them out so they don't cause problems which is basically just another way of saying that it tries to compensate for people writing configs incorrectly. I suspect 2.0.1 started from an earlier point on the branch and once the changes Ialdabaoth made in his branch are merged with Sarbian's branch then it will become whitespace tolerant once again. Or people can learn to write their configs correctly without whitespaces. Edit: Perhaps I should amend that to say 'whitespaces in unexpected locations'. Obviously expressions like 'description = This is a part description.' are ok. There are other places where whitespaces cause parsing problems, or in the case of names, URL locator problems.

With RO you'd want 10-75 KWe

Why would it produce negative wattage? It neither consumes electricity nor would it stop producing it. Even at full thrust there's an awful lot of heat and it's got to go somewhere. The whole point of bimodals is to put that excess heat to use rather than just radiate it away. Edit: In fact, the only time it might not produce electricity is prior to its first firing.

By definition, burning up on reentry doesn't sound like the launchpad bug to me... Did you change anything in the config file such as shockwave exponent / multiplier? (especially if you upped the difficulty, you need RSS compatible heat shields) Or start playing with RSS and not use RSS heat shields?

Thanks, except for the genius move where I forgot the braces and the @PART bit. I updated my post with THIS. (use this instead) @PART[TriStrutDouble] { !node_stack_top01 !node_stack_bottom node_stack_top01 = 0.0, 1.491, 0.0, 0.0, 1.0, 0.0, 1 node_stack_bottom = 0.0, -1.491, 0.0, 0.0, 1.0, 0.0, 1 }

There's no coding. It's a parts pack. Not a plugin. Edit: Well I guess one might consider the part config file 'coding' but that's not correct. Whatever. I just took a look at the part.cfg file for the 201. AND OH. MY. GOD. No damned WONDER it's coming apart. To rehash: In 0.23.5 attach node size now determines connection strength. Just as parts have breakingForce and breakingTorque, attachment nodes cause the creation of attachment joints which also have similar properties: breakForce and breakTorque. You cannot set those, they are created automagically based on attach node size. And the 201 has attachment nodes of size -1. So it's not just that it has no strength. It has NEGATIVE strength. It might hold together when you first spawn (launch) it but when you dock it, the game likely goes through every part and resets its joints, gets to the 201 and..... instant unplanned disassembly event. Solution: In your GameData folder, create a THSS_Tweaks folder. (name it whatever you want, just make a folder dedicated to THSS Module Manager tweaks because eventually more THSS tweaks are likely going to be needed so let's consolidate them) Create a file in there named THSS.201.tweak.cfg Edit that file and insert the following code in it. @PART[TriStrutDouble] { !node_stack_top01 !node_stack_bottom node_stack_top01 = 0.0, 1.491, 0.0, 0.0, 1.0, 0.0, 1 node_stack_bottom = 0.0, -1.491, 0.0, 0.0, 1.0, 0.0, 1 } I may release another fix in the near future that supersedes this

YES! Parachutes that go off on impact!

I'd do the opposite. Just copy your entire KSP folder (copy/paste) and then go in and delete planet factory. Then start it up, start a new game and see if chutes still have problems. [IMGUR]nz1kT[/IMGUR]

In Photoshop, Image -> Mode -> RGB It's that easy. Now your grayscale image is an RGB image. That just happens to still look grayscale. I used the add height and average RGB (as height) options. You should also check wrap mode which is for textures that wrap seamlessly. Otherwise weird things might happen at the edges. And... omg is Levi related to Mikasa???? Holy crap.

Normal Map is done but it's 113 mb so it's still uploading. (ADSL so upload is slower) If you want to try it in the future, you need a normal map filter for photoshop. I use NVidia's which is downloadable from their site I presume. I don't remember where I got it exactly; I've had it for years. Re: the color map.... ugh, it's got a lot of shadowing and stitch lines... but also what looks like scan lines... I'm not sure how to get rid of all that except slowly going over it section by section. I wonder if we could superimpose the height map over it and... use that as a reference or filter..... Edit: PMed you the link

I think that's Carl Sagan. Also, why do you keep stealing zoacrystals, Apollyon?!??

Ok still working on this. You. SHOULD be able to download it already but that gawdawfully huge image is intent on strangling the life out of my computer and its puny 4 gb. Photoshop just crashed shutting off non essentials and trying again. Question: does the normal map have to be same size? I'm assuming that's what you want but it would go a long ways to not-killing my computer if it were not. Edit: Done. Uploading it. There were some VERY tense moments when I tried to save and the PC seemed to hang for a few minutes.

If you're happy with that height map I should be able to produce a normal map from it.

Good job. Remember, a programmer converts caffeine directly into computer code so have lots of coffee!!! I think 1 fl ounce of coffee is equivalent to 10-75 lines of computer code. (declaring new classes however depletes a full cup right off the bat and I'm not talking those little wussy 8 fl oz cups)

Source Code gets a free surprise round to act.

There's a switch in the internals that you have to click. I forget where exactly...

Where are those roundish RCS thrusters from?