leatherneck6017

Members
  • Content Count

    429
  • Joined

  • Last visited

Community Reputation

235 Excellent

1 Follower

About leatherneck6017

  • Rank
    Tinkerer

Recent Profile Visitors

1,999 profile views
  1. I've had zero time for KSP the last couple of months . I do remember writing some of the code before my hiatus. Hopefully my schedule will clear up a bit this summer so I can get back to KSP in general, and the code for this.
  2. Then don't use them. Or modify them with a MM patch.
  3. I see that. I'm thinking a config file will be the way to go. It's on my to-do list.
  4. It's a Module Manager patch. Here's one I had created for Near Future Exploration antennae: @PART[*]:HAS[@MODULE[ModuleDataTransmitterFeedeable]]:NEEDS[NEARFUTUREEXPLORATION]:FOR[ZZZZCOMMNETCONSTELLATION] { MODULE { name = CNConstellationAntennaModule } }
  5. That's a good feature request. Raise an issue on GitHub and I'll look into it. You're welcome. I've always enjoyed the extra immersion from these visuals, glad to maintain it.
  6. You may need to create a patch to add the modules manually.
  7. This sounds pretty cool and well thought out. Congrats on the release!
  8. I'm no C# pro, but I'll dive in deeper and see if I can't send a PR your way.
  9. I briefly looked at your code but couldn't find where this occurs. Thanks for your time.
  10. I'm surprised I'm the first. For some reason I built a KPBS base with 2 launchpads and I face this every time I build something. No big deal, just thought I'd ask. Thanks for the reply.
  11. I can confirm. This is indeed strange. Looking at the code, it seems like some method other than bulkhead size is used to filter. Perhaps @linuxgurugamer can shed some light.