Jump to content

JPLRepo

KSP Team
  • Content Count

    3,031
  • Joined

Community Reputation

4,587 Excellent

About JPLRepo

  • Rank
    Lead Engineer

Contact Methods

  • Twitter
    @JPLRepo

Profile Information

  • Location
    Australia

Recent Profile Visitors

28,192 profile views
  1. Sorry due to KSP 1.11.2 being released... i haven't been able to get the update out for this mod yet. Hopefully this week - (Fingers crossed).
  2. Just an update here. I've worked through and made fixes for all the following issues. I just need to complete testing before I can release the update, shouldn't be too much longer (day or two). *Fix issue where CBs were becomming visible when they shouldn't be. *Fix issue where CB visibility was not being reset when loading different save games in the same game session. *Fix issue where errors would occur and game stuck when entering the SOI of a CB that hadn't been discovered before. *Fix issue where Asteroids entering CBs were making them discovered. *Fix issue with bumpmap
  3. a) Sorry. b) Not currently. c) Litres.
  4. Sorry. No this hasn't made it. This was fixed in 1.11.1 by way of adding new static public method to do this.
  5. V1.13 published. V1.13 * Added KSP 1.11 stock inventories. * Fixed issues with Kerbalism: * FusionPellets don't appear on crewed parts. * Ranger VTOL engine guzzles ElectricCharge (due to install with incompatible WBI Classic Stock). * Moved storage cuboid to Cargo category. Many thanks to @JadeOfMaar for this update.
  6. I've been through the changes. Will look to get out an update sometime in the next week.
  7. yes it should. and if used together it will trigger a discovery of that celestial body if not already found before. They will also appear foggy initially, and gradually become clearer as you research them more in the research bodies mod.
  8. Thanks everyone for raising known issues of late. I'll see if I can assign some time to give this mod some love and try to address the CB visibility issues and bring it up to date in the next week or two. Thanks again.
  9. it may or may not. if it doesn't let me know and I'll release a new version.
  10. Vessel.GroupOverride is the index of (Vessel.OverrideActionControl) the currently set action group. Vessel.OverrideActionControl is an array of the action groups for the vessel. Vessel.SetGroupOverride(int newGroup) - sets the action group.
  11. Changing the vesselId would create other issues, hence there is no public method for doing that. You can remove and add a vessel/vesselId but that also will create unwanted issues for you as that fires events and other processing.. as removing it - means it's being removed. You could try that. but I can't say that you won't have other side effects. Feels to me you should be tracking your data based on the command pod/root part persistentId and then sharing the data between them if they are part of the same vessel.
  12. Correct. Unity only uses Vector3. Vector3d is a construct used in KSP - but is outside of Unity. Raycasts are a functionality of Unity, and as such only work with Vector3.
  13. I can recreate the error in various KSP versions. Don't believe it's new to KSP 1.11.
  14. That's because when I replied there were no links. The original post was edited to add links to some of the issues that were in the post after my post and the subsequent follow on comments in the thread.
  15. It never ceases to amaze me what you, the amazing KSP Community, can come up with. Not in 1,000,000 years would I have thought of using the flag parts in this way when we dreamt them up as a thing in the game. Well done.
×
×
  • Create New...