BigD145

That is a very old bug that happens even without RemoteTech.

Send an engineer. Send them home.

Your dropbox is a bit out of date.

Woot!

Throwing a 0.90 working folding launchpad into 1.0 makes a launchpad with attachment nodes that don't work at all. Sad day. It was worth a try.

That folding launchpad is more applicable than ever. It handles quite a bit of weight and can fit in a shroud.

The fuel tanks are actually quite heavy compared to stock tanks of equivalent fuel mass. I think one of them is about 3 times heavier. I can't check at the moment. Not an easy task to get to orbit.

Retractables are more useful than ever in 1.0.

Can we get a dollar value on these lifters, assuming default prices of parts in career mode?

Yes, I've done similar for simple landed bases with X Kerbal space needed. I didn't intend to, but I needed a ferry to ship inexperienced Kerbals to Kerbin and met the requirement after hooking them together with KAS. Minmus land bases have such low dV to orbit requirements that you might as well launch outbound traffic from the surface. The only problem is no ore/karbonite overlap if you're using karbonite.

The problem with the part is it doesn't work well with stock lights. They use different lighting code. Inline Lights had color changing before Squad did it, but did it differently.

That seemed to do it. Thanks for the fix.

Here you go: https://www.dropbox.com/sh/he8uxsohsb9tist/AADiA3WMssM6XKQwqvy3lGuHa?dl=0 Ore1 is with ore selected. Karbonite1 is with karbonite selected. Notice how ore is not in text next to "slopes" at the bottom, but karbonite is. I added the following to the Karbonite detector to save parts: MODULE { name = REGO_ModuleResourceScanner ScannerType = 0 ResourceName = Ore MaxAbundanceAltitude = 500000 } Just using the magnetometer on a satellite and cheating it into orbit over any body also does not show ore on the ScanSat map after timewarping for several days.

ScanSat 9 hasn't been showing ore on the map. It's pickable, it just doesn't show ore numbers on the map or any color patches. Any clue what's going on? I haven't been keeping track of many mods since just before 0.90 released. Kethane is not installed so I'm running sorta blind. The orbital scanner is showing percentages, I'm just not getting a map of it.

I was flying a mission from Kerbin to the Mun and back to gather science and level up a couple Kerbals. My save only has a single alarm set about 150 days in the future on a vessel I didn't touch at all between bootup and shutdown of ksp.exe. Recently ksp has been suffering from a memory leak and I don't know where. I'm running close to 40 mods. I'm trying to think of which might hook into AlarmClock or vice versa. Trying to repeat it now.

My ksp.log is 80-90% this: [EXC 12:41:33.628] NullReferenceException: Object reference not set to an instance of an object KerbalAlarmClock.MuMech_OrbitExtensions.SwappedOrbitNormal (.Orbit o) KerbalAlarmClock.MuMech_OrbitExtensions.AscendingNodeTrueAnomaly (.Orbit a, .Orbit KerbalAlarmClock.MuMech_OrbitExtensions.AscendingNodeExists (.Orbit a, .Orbit KerbalAlarmClock.KerbalAlarmClock.DrawNodeButtons () KerbalAlarmClock.KerbalAlarmClock.DrawGUI () RenderingManager.OnGUI () Almost an hour of playtime is full of that, over and over, every fraction of a second. v3.2.0.0 https://www.dropbox.com/sh/2d2b3yno5f0iu72/AAC1o58-jgbokrTt67byPbrDa?dl=0

Not everything scales in a linear fashion. Not many things actually do.

b and n rotate

I prefer github.

That is a setting in KAC.

Liquid fuel in a plasma thruster gives very low thrust. It's in the description.

Love the parts but I had to remove this. The base parts and bubble were taking up 300MB of RAM. I was approaching the limit before KSP would just crash, which it often would. My bases will have to look ugly for awhile.

Hmm. Lilleman's utility is supposed to do that by default and I did not check to make sure. Perhaps I'll try it again and see.

Just converting mbmm's from the Squad folder, with ATM installed, I went from 3.06GB RAM usage mbmm's on the title screen to 3.2GB with dds's from Lilleman's exe using all defaults. I think I'll stick with mbmm's as they seem to have a smaller RAM footprint.

So is this dropped into KSP root and it just goes through everything?