blowfish

There's a separate thread for CKAN support. Don't bother ferram with it @ferram4 The .version file in the download appears to be the old one. This would explain the CKAN woes, would probably cause some other trouble with AVC as well.

Install KSPWheel. The landing gear only work with that plugin installed.

Well, as I said then I highly doubt B9 Part Switch has anything to do with it. I think the issue you're describing is a known Procedural Parts issue.

@Canis Dirus Leidy Okay, you're totally right, thanks for being patient with this issue. I think that the issue is in GameData/RealFuels/zFuelTanks.cfg . If you go in there and delete this line: !RESOURCE[MonoPropellant] {} It should work. Could you try that and let me know what happens?

I seem to be having some trouble with B9's MFD - it has a page that's supposed to show the vessel description, but only the overlay shows (not the actual vessel description text). Is there anything obviously wrong with this configuration?

Hmm, you seem to be right. Unfortunately debugging this goes way beyond my knowledge of RPM. I don't even know how to tell if it's a bug in RPM or in B9's configuration.

Well I can try to investigate, but I'm seeing a lot of incomplete and/or conflicting information here. If you could post the log, ModuleManager.ConfigCache, and exact versions of KSP, RF, and TAC in each case, and reiterate exactly what you expected the behavior to be and what it actually was, that would be helpful.

Wait, but in your previous post you said that RF v12.2.4 worked correctly

RealFuels v12.3.1 for KSP 1.3 Actually fix the bug with tanks not getting their contents correctly (not fixed in v12.3.0) DO NOT INSTALL THIS VERSION IF YOU ARE RUNNING KSP 1.2.2. IT WILL NOT WORK

Ugh, OK, definitely reproduced the issue with the solids. Turns out I didn't actually revert those commits on the 1.3 branch. This is why I really hate having two branches right now. Will have a fix shortly. As for the issue with command pods not being able to accept RCS fuel, I think that TAC and RF Stockalike aren't cooperating - they are getting the LifeSupportAll tank type but should be getting ServiceModule. Not sure which side the fix needs to go on but it isn't a pure RF issue per se.

@Canis Dirus Leidy @Gordon Dry Well, I just tried with v12.3.0 and the latest TAC LS and the resources are doing what they're supposed to (i.e. command pods pre-populate with life support resources). So not sure what to say...

So I was developing an alternative GUI for switching in flight and it occurred to me that it might be helpful in the editor too. Thoughts? It would be activated by clicking a button in the part action window. I have no plans to get rid of the existing GUI, this would be in addition to it.

@toric5 That's because all the values are processed before all the nodes, so you're trying to access the LH2 resource when it's still LiquidFuel. There's nothing ModuleManager can do about this, it's a consequence of how KSP stores the nodes. Split the bottom bit into its own patch and it should work.

Are you talking about the patches that come with RF Stockalike or some custom ones? If it's custom, could you check whether the default ones in RF Stockalike are working as expected with no custom stuff? I'm at work right now and can't look myself.

The transforms can come from any model, but they're the name of transforms within the model, not the name of the model itself. I'd recommend Sarbian's DebugStuff plugin for inspecting the hierarchy in-game. But there's also a trick you can use. If you have say MODEL { model = Path/To/Model }, when KSP instantiates it it ends up with a name of Path/To/Model(Clone) in the hierarchy so to make it switchable you would have transform = Path/To/Model(Clone)have Oh, and welcome to the forums!

B9 Part Switch can't currently interact with other modules (e.g. engines), so that option is out for the foreseeable future.

Am I interpreting correctly that you want to have nukes on vessels already in flight use LF, but have newly launched ones use LH2? I think this could be done via a part upgrade.

RealFuels v12.2.4 and v12.3.0 are released which should fix the resource bug Please make sure you have the correct version of RealFuels for your version of KSP. They are not cross-compatible v12.2.4 is for KSP 1.2.2 only and can be downloaded here v12.3.0 is for KSP 1.3 only and can be downloaded here Sorry about having multiple versions out at the same time, having to keep supporting 1.2.2 while 1.3 is out is proving to be rather complicated

Yes, they called it RealFuels

Sadly, there are not HX crew parts. It would be cool though.

@Gordon Dry I think that belongs in RF stockalike, not the base RF. Remember that RF is used by Realism Overhaul too, and auto-balancing doesn't really make sense there. Also I think RF stockalike already has life support patches, but with tank autofill broken they aren't doing their job.

The resource density is defined here. It's 0.001 t/L = 1 kg/L which is correct. The only thing RF defines is the mass of the tank itself (not its contents).

The resource densities are defined in Community Resource Pack and were realistic the last time I checked. RF defines a tank mass which is different.

@taniwha Could you have a look at this? It seems like after your change, tanks can't be filled by default except by putting resources on the part. For example, this patch in RF Stockalike should be putting EC and MonoPropellant in the tanks by default but is not (setting maxAmount is not working). Confirmed that it was working on the previous commit. @Gordon Dry it does seem there is an issue here, but as a word of future advice, can I suggest that you narrow down what you think isn't working instead of posting a large number of configs? In this particular case, you're setting maxAmount = something and amount = filled and expecting the tanks to be filled by default but the were not. That is the info I needed, the rest is just noise.

You need to create color masks for each texture you use and assign the custom shader. In this specific case Nertea would need to do some extra work to make that functional.