Jump to content

futrtrubl

Members
  • Posts

    673
  • Joined

  • Last visited

Everything posted by futrtrubl

  1. That's just it, there is no prograde to the node. Prograde is facing your direction of travel, the open green circle. The node's facing is the blue marker. They sometimes happen to face the same way when raising peri/apoapsis, but they are distinct and different directions.
  2. I'm sorry I have nothing to add to help your issue, though I know it has been brought up before. But that sentence of yours that I quoted.... that gave me a good laugh. Incompatibilities abound and CKAN really can't do anything about it, except sometimes keeping things up to date. Quite often a bug is reported and it's because CKAN didn't.
  3. Known issue. He needs logs. Logs are a good thing to attach to any bug report.
  4. The stock temperature colors may just by looking at the part temperature not skin temperature. And after the plasma stops you will continue to have conduction from skin to internal.
  5. I'd say that's more a new feature than a fix.
  6. Just to be sure; You are using KAS struts right, not the stock struts?
  7. Different efficiencies. The 25% is how much supplies you get back from a certain quantity of mulch. The 50% is how fast the module is working at doing that conversion, this depends on so many things you will need to look at the FAQ.
  8. Yes, I dislike docking ports if you can do without. Why have 2 extra wobbly parts?
  9. I meant tweaking certain engine parts not the engine modules. But I see that the Finals have now been removed. The only issue there is if someone adds an engine module in an MM pass after engine lights pass. Actually, since this doesn't use FOR[EngineLight] it defaults to FIRST, so any engines added or modified by MM may have incorrect or no lights. Also he isn't adding it if it's missing, he just adding it.So I still recommend what I said previously, using FINAL picks up all engines correctly and the !MODULE[tjs_EngineLightFX] stops you from overwriting things (actually not overwriting but adding a new module) if someone makes their own part specific change as it only adds it if it is missing.
  10. Check out the config in Community Tech Tree. That would be the best place to start.
  11. Not exactly since radially attaching things is by eye. Tying to make 2 subassemblies that are identical in the VAB/SPH is easy with symmetry. Trying to do that in the field is almost impossible. So storing or just being able to move subassemblies is not just a shortcut, it adds actual new functionality.
  12. That terminal velocity looks about right to me. You are going about mach 1 so your drag coefficient is at it's maximum and you are only getting about 1/5g (2.2m/s2) drag. Your craft is pointy so your drag coef will drop significantly after transonic so your terminal velocity (where drag =1g) should be at least 2.2x your current speed and very likely more than 5x your current speed, so >700m/s for sure and probably more than 1500m/s. Do not base your assumptions on pre-1.0 ksp.
  13. Have you tried RemoteTech XF? It allows you to deploy and point antennas even without a connection. Perfect for this situation.
  14. A minor quibble but follow node and prograde are two very different things.
  15. I wouldn't want it to activate engines. How would it know which engines I want it to use?
  16. I'd think it's because someone may have created or might create a module that starts with ModuleEngines and this would cause issues and it's just one more MM patch. Also I imagine that a wildcard match is more expensive than two exact matches for MM. Those Finals though, wish there was a better pass to put them since people may want to tweak certain engines after... ahh @PART[*]:HAS[@MODULE[ModuleEngines],!MODULE[tjs_EngineLightFX]]:Final { MODULE { name = tjs_EngineLight lightPower = 1.0 lightRange = 40.0 } } @PART[*]:HAS[@MODULE[ModuleEnginesFX],!MODULE[tjs_EngineLightFX]]:Final { MODULE { name = tjs_EngineLightFX lightPower = 1.0 lightRange = 40.0 } } would allow someone to do their own way, then yours won't stomp on them.
  17. If you are downloading things with ckan then your Modular Flight Integrator will be out of date too and will break things.
  18. You've posted this in a couple mod threads without knowing if that is the mod causing the issue. There is a forum Support (Modded Installs) precisely for this. Instead you have maybe pasted it once in the correct thread but definitely multiple times in threads it has nothing to do with.
  19. Perhaps we could cheat by having light fall off around the engine. IE having them act like a more diffuse spotlight so there is still some light behind it but not as bright as in front ("front" being the where the rocket plume goes).
  20. And stock transfer system. Not sure how many people use CLS by itself for limiting that though. I'm an SM user myself.
  21. It was changed to show all nodes in the last version. So either you are using a previous version or it's a bug, or someone is going behind CTTs back and hiding some nodes.
×
×
  • Create New...