SpaceTiger

Members
  • Content count

    379
  • Joined

  • Last visited

Community Reputation

412 Excellent

2 Followers

About SpaceTiger

  • Rank
    KerboKatz CEO

Contact Methods

  • Website URL http://kerbokatz.github.io/

Recent Profile Visitors

3451 profile views
  1. [1.3.0] AutomatedScienceSampler - V1.3.3 - 04.06.2017

    This is fixed in a pre-release here.
  2. [1.3.0] CraftHistory - 2.2.0 - 04.06.2017

    @drtedastro, @linuxgurugamer you can both open up a feature request on GitHub.
  3. [1.3.0] KerboKatz - SmallUtilities - 04.06.2017

    Right-click on the RecoverAll or DestroyAll icon which will bring up the settings. There you have to select which types of craft you want to be visible. Following that you can close that window and use the main window again to recover or destroy everything that fits the specified categories. See the first post. Need your logs to be of any help.
  4. [1.3.0] CraftHistory - 2.2.0 - 04.06.2017

    When you don't have the parts unlocked through research or they aren't available in your game at all cause of a removed mod.
  5. [1.3.0] AutomatedScienceSampler - V1.3.3 - 04.06.2017

    @Gordon Dry to me it looks like this is an issue with ProceduralParts/SmartTank as this sort of exception apears all over the log file and not just for ASS. I'll add a check for this in the next version of ASS, but stock and other mods will still show the very same exception. Could you create an issue for this on GitHub?
  6. [1.3.0] KerboKatz - SmallUtilities - 04.06.2017

    The database reload isn't available in stock KSP and as such we didn't test if it's causing any issues. I added an issue on GitHub to fix this issue in the future, see here. This seems very reasonable and well thought. Could you post this as an issue on GitHub?
  7. [1.3.0] AutomatedScienceSampler - V1.3.3 - 04.06.2017

    Full logs with debug option enabled would help narrow this issue down. If possible add it to the issue in GitHub here. Its the default results window and as such i don't think that it's possible. I'll have a look at it later see here.
  8. [1.3.0] AutomatedScienceSampler - V1.3.3 - 04.06.2017

    We didn't get to test it yet fully so the pre-release is a way of us to tell you that we didn't test it fully and it may contain bugs. It should be fully stable but just in case. We dont have any eta on how long it will take to test it all.
  9. [1.3.0] CraftHistory - 2.2.0 - 04.06.2017

    Did you ever wonder which of your craft files couldn't be loaded with the option "hide unloadable" being off ? With the latest pre-release you will now know for sure! As a side note its compatible with KSP 1.3
  10. [1.3.0] KerboKatz - SmallUtilities - 04.06.2017

    Weren't sure if this worked in 1.3 ? The time of doubt is now over! We just released a new pre-release. If you encounter any issues please let us know, preferred way is over GitHub. It shouldn't increase or decrease it in any way. All it does is just increase/decrease the modifier from the stock explosions and with that being said it doesn't use SmokeScreen.
  11. [1.3.0] AutomatedScienceSampler - V1.3.3 - 04.06.2017

    We just released a pre-release. It works with KSP 1.3 and thanks to @DMagic science experiments can now be stored in any IScienceDataContainer. Please be aware that this release wasn't fully tested and may contain bugs such as throwing exceptions, lighting your Kerbals on fire or ejecting your Kerbals into space!
  12. Will KerboKatz products be updated for 1.3 soon?

  13. Lot's of Science

    For that a bug report would be nice, so we can figure out what isn't working and fix it. So please drop by in the thread and give us reproduction steps
  14. [1.3.0] KerboKatz - SmallUtilities - 04.06.2017

    The whole idea behind the toolbar was to not use too much space with all our mods so I do agree that it should be optional and not on by default. Edit: To clarify I mean that by default the KerboKatz toolbar should be used and the user can decide not to use it.
  15. [1.3.0] KerboKatz - SmallUtilities - 04.06.2017

    They are both public so I don't see why not.