jlcarneiro

Even with the latest version (2.2.1.0-beta)? If it helps, I have old versions of OhScrap! and Scrapyard running fine with KSP 1.12.3 (without the improvements introduced recently, of course!): OhScrap! 2.1.1.1 ScrapYard 2.1.0.0

How does Oh Scrap compare to EVA Repairs? I mean, from two different points of view: 1. Reproduction of failures occurrence in real life (adapted to gaming experience, of course!); 2. Complexity and resource consuming

This mod seems FANTASTIC! And taking Snacks! by example it really is! Thanks! I intend to replace another failures mod with Eva Repairs but I have a few questions: 1.What classes should I use to include probe cores, batteries, tanks, antennas and such via MM patches? 2. Is 600hrs too little MTBF? What starting MTBF should I use if I intend to adopt it to so many items? 3. Do I also need to use SandCastle? Nevertheless, SHOULD I use it or tweaking the settings can save me even another mod?

Thanks for your kind (and prompt) answers! But for one of those mysteries only cell phone forum navigation can answer, I meant to post my question in RLA Reborn topic! Sorry!

This is a very fine collection of alternative parts! Thanks once again to all who contributed make it possible and to LGG for mantaining it! One question, though, does anyone know a waterfall config that works with engines added by this mod? Or how I could make configs for other engines work with those from RLA Reborn?

Does anyone know a waterfall config that works with engines added by this mod?

This mod is amazing! Thanks! I use Restock, Restock+ and RLA Reborn. I'm using Waterfall Restock config but it doesn't t work with RLA Reborn engines. How do I fix that? Should I download another config pack? If not, how do I use existing configs with MM patches? Is there a tutorial on the GUI editor?

Is it possible to implement some kind of automatic removal of old parts? I mean, those that get destroyed, for example...

Oh, yeah! Sorry I didn't update it here! BTW, his quick reaction surprised me as well!

Hello, folks! I have a little doubt: I've noticed the Micro Dawn's (IX-631) mass is the same as the stock one (IX-6315) even if its mass is one quarter smaller. Is that intended? If so, why?

Actually, I CAN'T remember when I updated US2 for the last time (sorry!)... Maybe it had that absence for a while but the update to Part Volumes "found it" (I searched older versions of Part Volume and the line MM reported didn't exist, so I suppose you started to use packedVolumeLimit just now. IDK... )

I posted an "warning" on UniversalStorage2's post. Hope this helps... Now, HOW did you find that error in those logs (there are many lines!), I mean, what did you use as seach term?

Hello, guys! Recently, due to an update to KSP Part Volume, I got an error message from ModuleManager: [ERR 18:52:27.887] Error - Cannot parse variable search when inserting new key packedVolumeLimit = #$/MODULE[ModuleInventoryPart]/packedVolumeLimit$ [ERR 18:52:27.887] Error - Cannot parse variable search when inserting new key packedVolumeLimit = #$/MODULE[ModuleInventoryPart]/packedVolumeLimit$ Then, linuxgurugamer (thank you, mister!), analysed the logs and gave me a workaround: MAYBE linuxgurugamer will implement some code that deals with this since there are so many mod parts out there. Anyway, I thought I should tell you here... Anyway, thank you all for your great work!

WOW, that was FAST, thanks!

Firstly, thanks for your attention, you must have little time! Secondly, here is the link to the logs on file.io: https://file.io/CmG8f0Ymdb8L Unfortunately, they say the file will be deleted after download. So guys, PLEASE DON'T CLICK on this link, let @linuxgurugamer download it...