sebi.zzr

@RussianAround

And? How do you expect to get support with that information?

I had to use some "tricks",but i finally made it.

@Svm420,if you're on windows

Most certainly is.

Are you running x64.exe?If yes then read:

I think the solution is to change name="multiPartAttachNodeReinforcement">0< in ...KSP_win64\GameData\KerbalJointReinforcement\Plugin\PluginData\KerbalJointReinforcement\config.xml

@Shadowmage,thank you for response,it was my original idea to add all the modules and enable them with upgrades,but i never found how to disable MODULE[ModuleScienceExperiment]. I was trying: SetInoperable = true //and Inoperable = true with no avail. Do you know how this could be achieved?

I would like to add different science experiments to command pods when they are available in tech tree and would prefer the stock part upgrade function. This'll add icon and notification in tech tree: PARTUPGRADE { name = comandscience partIcon = sensorThermometer techRequired = engineering101 entryCost = 2500 //cost = 0 title = thermometer upgrade //basicInfo = Whatever\nblah //manufacturer = description = Adds thermometer to all command pods } no problem here,but nothing of the following is working Upgrade through "PartStatsUpgradeModule": direct upgrade: so,is there any other method to achieve that? thank you

The only thing that's missing is,either support for blizzy's toolbar or function for hiding the icon.Otherwise,everything is working as intended,is simple as it gets and that's why i like it. If you want more complicated version of automatic science gathering,you could browse the forum and find it.

You sure do have more questions than answers.There is no such thing as "scranjet",closest to what Google could find was Scramjet. R.A.P.I.E.R. is a sabre engine,but if you're looking for scramjet,you could make it yourself,with stock parts. What you need is:Whiplash,Engine Pre-cooler and Shock Cone Intake. And this is how yor "scranjet"shoud look:

Try this,is a little more user friendly.

The original thread was deleted by some unfortunate circumstances,but i think you'll find everything here: p.s.:ALG is being worked on , so don't poke the hornet's nest.

You didn't made any progress update,but how is your network connection?

And we thank you,just look at your repository.No need to explain yourself.

Ok,i'm going to drop this here. I've been using ALG with help from KSPWheel.They are not "out of the box" working,because they still need some in game adjustments,but they suit me well.These patches are for big and medium landing gears,because the little one is too bugged out. If someone would like to try it out: What you need in addition for patches to work: KSPWheel Module Manager BDAnimationModules On another note.The only dependency for AGL to work is BDAnimationModules (FSBDwheel) and while they work on their own just fine,the thing they are missing is working wheelcollider.So my question here is.I know the FSBDwheel is based from firespitters FSwheel and all FSwheels are somehow working,without model changing,wouldn't be just enough to fix the plugin,at least te FSBDwheel part?

Why not test this with without other mods and post some logs?!

https://github.com/RangeMachine/TextureReplacer/releases

I checked that yesterday and the patch don't get applied,because MM don't see "GLOBAL_RESOURCE".There is no such parameter in cache.

I see.Well if this is only for your use,you could remove "ore.cfg" from resource folder,because MM can't find "GLOBAL_RESOURCE".

@5thHorseman,why do you struggle so much,just remove resource definition.If there is no definition the resource not exist. !RESOURCE_DEFINITION[Ore] { }

ninjaed For blacklist you need to use "!" example: @PART[*]:HAS[!MODULE[name],!name[parameter]]

All radial attach capable parts have "node_attach (= x, y, z, angx, angy, angz, size)" parameter,so you must determine,if this is the only parameter you need to include radial attachable parts and no others. For the physicless part you need: PhysicsSignificance = 0

You should ask here:

You're missing: @MODULE[ModuleRCS] { @name = ModuleRCSFX runningEffectName = running } you also need to change: @PART[*]:HAS[@MODULE[ModuleRCS],!MODULE[ModuleRCSFX]]:Final so you won't patch existing modules twice.