lodestar

There seems to be some incompatibility with the RealChute mod. I just started a new game with the mod and I couldn't get my first manned ship into orbit. By the time I decoupled the first stage, almost 2000m/s dv spent, I was still below 100m/s. I looked into Mechjeb's ascent stats and drag losses were over 1000m/s. I tried again with the aerodynamic overlay on, and the packed MK-16 chute on top of the Mk1 pod was dragging during the whole ascent. The same problem happened with the radial chute. The problem is gone after removing the RealChute mod. Is anyone else experiencing this?

I looked into the log and found out all parts with white textures have an error like this: [ERR 19:22:47.010] PartCompiler: Cannot replace texture 'Nerva003' as cannot find texture 'Squad/Parts/Engine/liquidEngineLV-N/model000' to replace with It works when I whitelist that. Thanks. For linux players, I used this command line to generate a whitelist from the KSP.log file: <KSP.log grep "to replace with" | cut -d"'" -f4 | rev | cut -d"/" -f2- | rev | sort | uniq | sed -e 's/$/\//'

What an amazing job you guys did. It's a really great mod. I would have paid for this, and would be more satisfied than when I paid for the making history expansion. I have a few modded parts appearing without textures, and I'm trying to come up with the whitelist for them, but I think I'm doing something wrong. For example, the two mass drivers from the Stockalike Mining Extension mod are rendered with some white parts, which I assume are stock textures missing, even though the part directory seems to have copies of the stock textures. MODEL { model = MiningExpansion/Parts/Size1Driver/Model texture = Mainsail2, Squad/Parts/Engine/liquidEngineMainsail/model002 texture = Size3AdvancedEngineDiffuse, Squad/Parts/Engine/Size3AdvancedEngine/Size3AdvancedEngineDiffuse texture = ksp_s_processorSmall_diff, Squad/Parts/Resources/MiniISRU/ksp_s_processorSmall_diff texture = TriBitDrill, Squad/Parts/Resources/RadialDrill/TriBitDrill } I created a MiningExpansion.restockwhitelist file like this: Squad/Parts/Engine/liquidEngineMainsail/ Squad/Parts/Engine/Size3AdvancedEngine/ Squad/Parts/Resources/MiniISRU/ Squad/Parts/Resources/RadialDrill/ But it doesn't seem to have any effect.

Thanks! Just one minor thing. The entry for the PPD-24 has a misplaced closing brace, so the config wasn't being applied at all. //PPD-24 Itinerant Service Container @PART[utility-pod-25]:NEEDS[USILifeSupport] } {

I'm experiencing a strange glitch whenever I place the 4 bay core between other parts. When under thrust, the core is compressed like a spring, and oscillates non-stop when thrust is cut-off. The whole ship is tore apart by the oscillations. KSP 1.5.1, US2 1.6.0.9

Is anyone else experiencing this problem where no other stack decouplers appear in the VAB or SPH when the procedural decoupler is loaded? They appear in the R&D center when I research the nodes, but they are missing from the parts list in the VAB or SPH. After I deleted the cfg for the procedural decoupler, they appear correctly.

The "Land at target" seems to be broken. What I usually do is: 1. Pick the target 2. Enable the "Land at target" 3. Let it run the deorbit burn and wait until it goes into warp or goes jittery. 4. If there's no atmosphere and you have TWR>2, at this point you can just disable the "Land at target", enable the "Land at somewhere" and it should get you very close to the desired location. 5. If there's an atmosphere, or you have low TWR, disable the "Land at target" and set Smart A.S.S. to SVEL-. Every few seconds, enable the "Land at target" function again and check if it's in the braking phase, with a target speed. If it is, let it run. If not, disable, wait and try again. I just landed a dozen containers on Duna within a 100m radius using this method.

Looking great. My video card fried and I'm waiting for the new one, but I'll check the new version next week.

That's really nice. You just made my day. I've wanted something like that for a while.

Well... this is what I'm talking about: http://www.projectrho.com/public_html/rocket/surfaceorbit.php#plugnozzle Or this: http://www.projectrho.com/public_html/rocket/surfaceorbit.php#rombus And the bottom left engine here is the one from RLA-SA I mentioned. Obviously, the nozzles are much larger on this one, but it's the same idea.

That would be great with a truncated aerospike engine doubling as a heatshield. I think KSPX or RLA Stockalike had one like that, but it was 2.5m and doesn't scale well.

So, I just captured an asteroid that has weird pink lines, like scratches, all over the surface. Is that a glitch, an easter egg, a feature, or what?

You don't really need that. There's a new version of the XT Landertron that uses the BD models with generic animations. I think it's this one. Take a look: https://github.com/Kerbas-ad-astra/XTLandertron

If you want to balance it by increasing mass, the engine has to be at least three hundred tons. That's how grossly unbalanced it is. By merely increasing it to 30t it would still be greatly overpowered and far above even the best engine from NFP.

AFAIK, tank units are based on volume, not mass, and Isp is impulse per unit weight of propellant, so what you're saying is to lower the Isp. That's an option too. Fitting the role and being balanced are different things. I think RoverDude doesn't care much about balance with respect to other mods. He's generous enough to make his work available, and we're free to choose how we want to play. The engine is unbalanced with respect to the stock and NF engines. That's a mathematical fact, not an opinion. Being unbalanced makes the game less fun for me. That's an opinion.