Critter79606

Lisias, trying to update my KSP from 1.10 to 1.12 and I'm having an issue with this mod. It keeps crashing KSP on startup when switching from loading to the main menu page. I've removed all mods to make sure this was the culprit and it continues. If I remove this mod, it doesn't crash. My ksp.log is here https://drive.google.com/file/d/1QHCGCA3KUZGdwEY-wJ5v9zh3Flxz8dRB/view?usp=sharing Thanks!

Yea, I use the liquid fuel only patch as I get tired of so many fuel types to keep up with. @JadeOfMaar I also found in OPT_CryoEngine.cfg and OPT_IntakeAtm.cfg, this needs statement :NEEDS[CryoEngines|KerbalAtomics] To be compatible with the LFO patch of KerbalAtomics, I think it should be... :NEEDS[CryoEngines|KerbalAtomics,!KerbalAtomicsNTRsUseLF] I made the changes on my system and it looks like all the parts are liquid fuel now.

I'm installing a fresh ksp 1.10.1 and I'm getting a config error when I got to installing the OPT packages. Log is here. https://drive.google.com/file/d/1LPmnICBHUOoc-51yf7mRhxH7dkHMJPNg/view?usp=sharing I don't have CryoTanks installed, so it's not including it... B9_TANK_TYPE:NEEDS[CryoTanks,!ModularFuelTanks,!RealFuels] { name = OPTLH2 I added the needs to the subtype in opt_b9ps_cryo.cfg and the error went away SUBTYPE:NEEDS[CryoTanks,!ModularFuelTanks,!RealFuels] { name = LH2 tankType = OPTLH2 title = OPT LH2 }

This is a ksp problem. I've noticed it too with scansat and others. Just trigger a different tooltip and it will go way. Does anyone know why this mod won't trigger for telemetry reports?

Spawning vessels hasn't worked for KACP since 1.6 or 1.7. When it would spawn the engineering can, it would spawn under ground and blow up or get ejected into space. I don't think it has worked reliably since 1.4 or so.

Thanks much!

Works fine for me too in 1.9.1. In fact, I use a ton of the parts.

Is spaceDock down? Was in the middle of updating some mods, and everything stopped. Never mind, it's back up

Woohoo, It works! It works! Thanks guys!

@taniwha I added the following patch to mine. If you have Umbra Space Industries tools, it adds the Toggle Ground Tether to the stake, which if you set it, keeps it from moving (other than jumping up a little after a warp). @PART[ELSurveyStake]:FOR[Launchpad]:NEEDS[USITools] { MODULE { name = USI_InertialDampener } } I've yet to figure out the multiple stake thing, as whatever I build is always pointed in the same direction no matter what I do to the stakes. I've read the docs, but not had any luck. Using the least number of stakes, how do I point something in a particular direction? I know it is supposed to point toward the door of the vab/sph, but I just can't figure it out.

Man I will be so glad to have this back in game!

Thank you, I thought I was going blind!

Actually, it's more of trying to salvage being able to resize unique parts. I didn't care which (B9 or MTF) I kept, just so long as I got my TS back on several parts.

ModularFuelTanks doesn't use the B9 plugin, but competes with it when it comes to resource switching. Before the B9 author put in the disabling code, I would get tank selection both from B9 (pre-configured selections), and MFT menu (custom configurable tanks). When I accidentally used both on a part, I had to remove the part and put on a new copy, as the tanks would go crazy on the resource side. I'd get multiple copies of resources that never went away... it was a mess. Only the 2 combinations I created work, as I have a lot more #12 issue that have different combinations that I've not been able to resolve without some side affect (that you described). Since the B9 is already disabling it's side, and I can't favor it over the MFT due to the way MFT changes the config, I figured I'd at least be able to restore the TS on some of my parts, especially unique ones I don't have multiple sizes of. It's not removing variants, but the competing fuel type switch, which is covered by MFT. B9 considers the heatshield ablator a resource, so that's why there are 2 separate #moduleID masks. It in no way disables variants that aren't resource related that MFT isn't handling. This would be a lot better (especially on Lisias) if mods would only use these types of resource switches on their own parts, instead of making broad changes across the board that are almost impossible to find.

@Lisias Since I've been getting this error about ModuleB9PartSwitch and ModuleFuelTanks from B9 on several parts... and knew that tweakscale disabled it's support too, I thought I'd try to chase some of these down and disable B9PartSwitch before getting this error, and restore TS support to some of these parts. I had 80 parts that TS withdrew support for, now I have 55. This is what I came up with and thought I'd share in case anyone else wanted some of the TS on parts restored. Feel free to use it! @PART[*]:HAS[@MODULE[ModuleFuelTanks],@MODULE[ModuleB9PartSwitch]:HAS[#moduleID[Heatshield]]]:Final { // clean up B9partswitch Heatshield conflict w/ ModularFuelTanks !MODULE[ModuleB9PartSwitch]:HAS[#moduleID[Heatshield]]{} } @PART[*]:HAS[@MODULE[ModuleFuelTanks],@MODULE[ModuleB9PartSwitch]:HAS[#moduleID[fuelSwitch]]]:Final { // clean up B9partswitch fuelSwitch conflict w/ ModularFuelTanks !MODULE[ModuleB9PartSwitch]:HAS[#moduleID[fuelSwitch]]{} !MODULE[ModuleB9PartSwitch]:HAS[#moduleID[meshSwitch]]{} } This favors ModuleFuelTanks over B9, but that is what B9 is doing anyway. Hope this helps someone.