Starwaster

Yeah, try the NEW heat shield and then decide whether to suggest tweaking it..... just a suggestion

Did you see my line item note about actionAvailable? If it's set to true, then you can bind the toggle action and still be able to toggle the umbilical on and off in flight mode.

Ah ok, that's apparently because I forgot how to Github. Should be there now

Hmmmm. I didn't do it as a pull request; rather as a file edit... Anyway, question: How do you feel about starting with the LES RCS starting in the disabled state? Downside is that an action group needs to be set up to toggle them, presumably the abort key. On the other hand, the downside of leaving them enabled by default (as they are now) is that they could be used up by the time the player actually has to abort, if his RCS is on.

I already pushed the part changes to Sumghai on Github

Hrmmm very last change I submitted was to aerodynamics. Last thermodynamics change I did was back in June. KSP shield behavior changed in either 1.0.4 or 1.0.5 (I forget which) which is why the shield is depleting so fast I guess. The question is, why am I only just now seeing it? Might be because I'm testing in a mostly stock environment. No DRE so no patches being applied. Anyway, I'll push some changes to you to make it behave more like it used to.

@sumghai not when it started but the heat shield completely depletes its ablator you might want to compare configs with stock shields which (now) behave more like SDHI used to

@sumghai CoMOffset sounds good if that works. That was next on my list of things to try but busy at the cat sanctuary On another note, does anyone else here have trouble with the new forum and Chrome where you quote someone, reply to them, and then later, try to quote something else and the previously quoted message shows up instead plus a draft of anything you might have posted previously in response to said old quote??? It's driving me up the wall

I don't think that bottom set of RCS is helping though What pack are those RCS parts from?

For proper balancing, the service module (total assembly SM + engine, etc) needs 50% more mass than the CM assembly (port + CM + shield) . By that criteria, currently, the CM is 1.7 tons overweight with the added mass of port + shield. So it either needs that mass shaved off of CM or the SM needs additional mass added ... I don't think moving its CoM back further would help.... I'll play with it some and maybe wheN Kerbas reads this maybe he'll think of something else....?

@sumghai @Kerbas_ad_astra @StevieC My first, gut reaction was that StevieC is right and that slashing the service module's mass was a bad move. But before I said anything I wanted to be able to suggest an alternative so I started looking at numbers and... 1.1 tons isn't too unreasonable. Might even be a tad more than it should be. I was looking at Apollo numbers and and Orion's service module is actually about the same diameter until it widens at the front to accommodate the larger crew module. And it's about half the length of the Apollo SM which is about twice as heavy. (not including engine mass, the basic cylinder with partitions and shelves was a little under two tons) That still leaves us in the position of having a final vehicle that's too top heavy. Maybe instead (or in addition to?) we should think about cutting the mass of the Mark 1-2 Pod?

You will need a set of engine configs. See second post of this thread. If you have any MFT specific engine / non RF configs then those may need to be removed. (if they're properly written it won't matter because they shouldn't take effect if Real Fuels is installed) Doing it with an existing save file will result in stock resources (LiquidFuel, Oxidizer) being left in the tank parts and would require editing of the save file to get rid of them. Not a showstopper, but since you can't dump them in-game, it effectively increases their dry mass, affective DV.

I think you should resist the urge to change them very much. Maybe some texture work, but otherwise, don't play around with them too much. That's what I think.

I'll just leave this here...

No Those RCS on the Orion CM are for reentry only. Just like Apollo

Yeah, I understand that it's translucent and red. Thin parts like that do have a tendency to behave like that and that's a core issue with the game. Whether it works or not is not random though, just keep practicing with it until you can attach it properly at will consistently. There's nothing else that can be done about it, not mod-side.

You guys are overcomplicating things. @StarStryder, thin parts like that are often hard to snap properly. You just need to be very careful with your mouse control. Move the mouse cursor VERY slooooowly downwards until shield turns green. It WILL SNAP. There's nothing wrong with the node config and you don't need to go to the cheat menu. (As to whether it survives or is destroyed as Nathan indicates is another matter entirely and I make no warranty one way or the other)

The best use of that part is for creating something like Saturn S-IVB LM Adapter. (see below)

Fixed the missing download. Fixed the dll in the repository too, though honestly that wasn't supposed to be there to begin with so it might go away in the future.

Animated Decouplers update https://github.com/Starwaster/AnimatedDecouplers/releases/latest

Not enough information here; need logs. If you don't know where your logs are, see below: (and, FYI, it doesn't matter if you did or did not crash. KSP produces logs when you play regardless of whether it crashes or not) Make sure that your log is from a time when you played and experienced the problem you described. Then post it to a reputable reliable site. I use Dropbox. If you don't have a dropbox account, get one. Thank me later.

That is exactly what it is.

That last one got away from you, didn't it?

My cousin's science teacher fell for the DHMO thing... after I printed it out and got her good with it, she decided to test her science teacher. He failed.

This mod wouldn't be doing that (not directly though it could happen indirectly, more in a bit). Either those parts were already mis-categorized or they specified a deprecated category called Propulsion. As Propulsion no longer exists, KSP reroutes those parts according to whether they have the stock engine module or not. This is where the indirect part comes in: the mod changes the engine module to a Real Fuels module (ModuleEngineRF) which is not recognized by KSP as an engine so it assumes it must be a fuel tank. StockalikeRF tries to switch categories to Engine itself. So make sure you have the very latest version: Delete whatever you have and download from here: https://github.com/Raptor831/RFStockalike/releases/latest If it still happens, be specific about what engines are affected. Edit: Ninja'ed