iueras

Even though KSP complains about it being for 1.2.1, it seems to work fine. I have been able to change the contents of my fuel tanks without issue.

I think I may have found a bug... I made a testbed ship with the particle bed reactor as the root part. Did not scale it, left it default size. placed fuel tanks and such, with one thermal rocket nozzle and 2 thermal turbojets for initial takeoff and climb to altitude where thermal rocket TWR goes > 1. I will launch with the thermal turbojets and climb to around 18-20km. About 2/3 of the time, when I toggle off the turbojets and turn on the thermal rocket, the rocket nozzle produces a whopping 8kn of thrust instead of the 400+ it should be making. I'm not sure if this is related, but when this happens, if I revert to launch, the reactor is model scaled down to 1.25m and everything attached to it is just kind of "floating" there, but still attached to something (nothing falls apart, can still launch using the turbojets). Once this happens, I cannot make the thermal rocket produce more than 8kN until I revert to assembly and relaunch, even though I CAN still launch with the thermal turbojets.

Awesome, thanks for all the fixes, Boris! Happy holidays!

Hey Boris, I just added your build to an existing 0.90 save game, and now my tech tree is completely blank after selecting the KSPI tree. Started a new game, selected the tree, and the nodes are visible like they should be. I had an unupgraded research facility in both the existing and the new testing game. Anyone else run into this or have a workaround? I was a decent ways into the new 0.90 career mode and I really don't want to start over. EDIT: I had restarted KSP already, thinking that might fix it. That didn't work. But after loading the new test career mode game, then exiting to the main menu and loading my existing 0.90 career, the tree is now visible again. Not sure what to make of that, but it seems to work now. LOL Thanks so much for making this build! KSP without KSPI just isn't the same for me anymore.

I've been using Jefferson's fixed dll on the surface of Minmus and it has worked well for me, no glitches or anything. Haven't tried it in orbit, though.

Do you use modular fuel tanks? I was having a problem where everything mounted above any sort of fuel tank would fall through on launch. Removing MFT until an update comes out fixed the problem for me.

It goes in the MechJeb2\Plugins directory, yes. Just to be clear, all I did was recompile the dll so it would stop throwing errors about missing FAR versions when using the latest FAR.

I have recompiled using ragzilla's source for the latest FAR 14.1.1 and ksp 24.2. DLL is uploaded to dropbox.

Wavefunction's KSPI version is updated, and if you use both Karbonite and KSPI, you should use Wavefunction's KSPI ORS dll.

It's a bit of both, and it is not KAS. It is a change Squad made to the way PartModules are added to Parts. What happens is old craft (both those launched AND those saved as .craft files) get their PartModules overwritten by repeated references to (in my case, anyways) ModuleAeroReentry and FarBasicDragModel. It could be anything, mine did those specifically because of the specific mods I have. Once the PartModules are all screwed up by the KSP bug, you get NullRefs all over the place. This causes CTD, and also gets saved in your persistence file. So it does crash, and it does "corrupt" your save file (or .craft file, if in the VAB or SPH). Once this has happened, the only way to fix it is to rebuild the craft in question and save a new .craft, or launch it, save the persistence file, and edit the ship throwing NullRefs PartModules to match the one you lauched (which will have the correct PartModules). This is the gamebreaking bug they fixed in .24.1 supposedly (haven't tested it myself). I know it is a PITA. I spent 2 days after updating mods to .24 editing my save file to save my existing ships.

Is there a specific problem that Wave's version fixes? I am using the stock 0.11 in 64 bit 0.24, and have been from the time the update hit. Is there something in it failing invisibly that I should move to Wave's version instead?

Thanks so much for the update Taniwha!

I'm so glad you and Sirkut came up with a good solution to the versioning problems. Great work, both of you!

Awesome work, sirkut! I'm really glad you and Biotronic got the versioning issues worked out.

Oh, gotcha. IR works fine now as well.

I went through and edited my persistence file, replacing the occurrences of tweakScale = 100 and currentScale = 100 on existing craft with the correct numbers -- 1.25 for radial xenon, radial monoprop, and a B9 RCS thruster block also affected. No other parts on existing ships were affected by the incorrect scale during the upgrade, and new vessels with the affected parts are fine. I also moved the Infernal Robotics dlls as sirkut said to try here. The vessels save correctly and load fine after fixing the bad module parameters and doing the IR fix.

This did not fix the supersized radial xenon and monoprop tanks for me right off. I had to go through and edit the module parameters in the persistence file. But in my case I think the damage was already done. The parts are saved correctly after doing this and editing the file.

Alright. Can I revert to 1.22 then temporarily? Or are those new parameters going to mess things up if i do so? I'm particularly worried about the scale being 100, LOL.

I am having a similar problem as Smurfalot in my game. In my case there are 6 radial Xenon tanks that have been supersized. Maybe other things, too, but I can't see anything except the xenon tanks. I have no NullRefs at all while this is happening, so I didn't save my output.log. This is the tweakscale off of one of the affected tanks out of the save file. I see a few new parameters compared to 1.22. Do these look alright? The part is supposed to be stock size. Is there possibly a problem with the scale.dll in IR overriding this one or something? Going by the changed module to 1.24 parameters, it seems that the new dll is indeed loading and running. MODULE { name = TweakScale isEnabled = True tweakScale = 100 currentScale = 100 defaultScale = 1.25 defaultName = -1 isFreeScale = False version = 1.24.0.0 defaultTransformScale = (1, 1, 1) tweakScale_UIEditor { controlEnabled = True minValue = 25 maxValue = 400 incrementLarge = 37.5 incrementSmall = 3.75 incrementSlide = 0.001 } EVENTS { } ACTIONS { } }

I got it done, at least the ships I needed to. Had to launch a newly built vessel and copy the module data from it. Dunno if it is this problem specifically causing it, but I can confirm that adding mods that add modules to existing parts, even to an already modded install, does bad bad things to your .craft files AND already launched vessels, in some cases.

Is this what has gone through and replaced all the LifeSupport, ModuleEngines, and FXModuleAnimateThrottle modules my capsule and engines need with multiple copies of "FarBasicDragModel" and "ModuleAeroReentry"? It nuked the engines and pods on almost every craft I have... including some that were built in .23.5 with the exact same mods (but usually different versions) that I am using in .24. Is it possible to fix this in the persistence file by putting the modules back like they should be?

Sorry if this is a dumb question, but how many .cfg files should I have in BoulderCo\Clouds? Right now I have cloudlayers.cfg, cloudlayers-betteratmopsheres.cfg, and cloudlayers-planetfactory.cfg. Should I delete the others besides the better atmospheres one?

So when I update this to 1.23 (or in the future) should I replace the scale.dll in IR with the newest version I download from here? Or is the IR scale.dll different internally (other than version number) than the scale.dll distributed here?

Works fine for me on Win 64. Just saved Jeb's little green hiney a few minutes ago.

Thanks SO much for this update! Love KW parts!