Jump to content

pjf

Members
  • Content Count

    272
  • Joined

  • Last visited

Community Reputation

496 Excellent

3 Followers

About pjf

  • Rank
    Spacecraft Engineer

Contact Methods

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. To whomever it may concern,
    Recently I have discovered the following problem. CKAN seems to think that my KSP version is 1.3.1 . However(!), my installed version of the game is 1.3.0.1, and this causes many problems with mods, which crash my game due to compatibility issues. Is there any way to convince that software of it being wrong?
    Yours sincerely,
    Alex from WolfCo. Areospace

  2. How come when I download a CKAN mod, The ships don't download?

  3. Oh dear. Is this happening with the command-line as well as for the GUI? We recently discontinued support for Mono 3.2.8, as we were hitting a bunch of bugs in it, but I'm guessing 14.04 still ships with 3.2.8 by default. You can upgrade mono by using the mono project's ppa , which cut'n'pasting is done with: And then upgrading as per normal. Having said that, I'd personally love us to keep supporting Ubuntu 14.04 as it is a long term release, so if I get a chance I'll see if I can find what the 3.2.8 bugs were that we are hitting and if we can work around them.
  4. Aww yis! CKAN v1.18.0 aka Star Tram released! Changes since v1.16.1: Bugfixes [Core] In certain cases a NullReferenceException could be produced inside error handling code when processing the registry. (#1700 by: keyspace, reviewed: dbent) [GUI] Fix typo in export options. (#1718 by: dandrestor, reviewed: plague006) [GUI] Fix unit of measure for download speed. (#1732 by: plague006, reviewed: dbent) [Linux] Better menu integration of the CKAN launcher. (#1704 by: reavertm; reviewed: pjf) Features [Core] insta
  5. This is brainstorming, so take the bits you like, and discard the bits you don't, but my big wish regarding life-support all has to do with long-term voyages. I can best explain this with some storyboards: Brett is performing a 2-day mission in space to study the effects of microwaving popcorn in microgravity. His craft needs water, food, oxygen, CO2 scrubbers, and waste disposal facilities, but isn't fitted with exercise or washing facilities. His mission is short enough they're not needed, he can always shower when he gets back. Jenna is undertaking a six month mission investiga
  6. CKAN v1.16.1 aka Plasma Window released! Changes since v1.16.0: Bugfixes [GUI] The "Not Installed" filter now has a more correct label. (#1573 by: plague006; reviewed: Postremus) [GUI] Scrolling of the mod-list no longer requires clicking on the list after start-up. (#1584 by: ChucklesTheBeard; reviewed: Olympic1) [GUI] The GUI now displays repo information as "Source Code" rather than "Github". (#1627 by: politas; reviewed: pjf) Features [GUI] The export menu now selects "favourites" as default, as that's almost alw
  7. Oh drat. That's a bug. I've opened an issue for us to track it. But with that aside, you're now able to use CKAN with your preferred install?
  8. Oh no, I've been travelling like a person who's travelling for five months per year. Have we responded to your RP-0 problems yet? (RP-0 thankfully isn't just me; I just hang around the edges these days.)
  9. That's a really good theory. The CKAN executable would work fine both under wine/.NET and mono, but those systems would present different views to the code itself. It would *also* result in registry settings being stored in different locations (~/.mono/registry under Linux, and the emulated Windows registry under wine). Wine would also present a `Z:` drive to provide a shim to your Linux filesystems. If you start the process with `mono ckan.exe` (for the GUI) or `mono ckan.exe <cmd>` (for the cmdline, with <cmd> being your command), then that should make sure it's always runni
  10. 1. The CLI and GUI both store settings in the ".NET Registry". 2. On linux the .NET registry is at ~/.mono/registry/CurrentUser/software/ckan/values.xml . You can edit them if you want 2a. You may find it easier to use `ckan.exe ksp list`, `ckan.exe ksp add <name> <path>`, and `ckan.exe ksp default <name>` to adjust the settings. These also won't have problems with any "hidden" directories. 3. That's *weird*. I don't see a 'Z:' drive at all, and I'm using mono/Linux. There's a good chance if you remove the `Z:` things will work; or at least be differently broke
  11. Thank you! Method::Signatures is an amazing module which I love very much. It's a shortened SHA-1 of the URL, which means we can easily tell if we've downloaded something already or not. The easiest way to see it is with the `ckan show` command. For example, the output below shows details for a mod I don't have installed, but which CKAN is aware of. The filename is right down the bottom: CKAN only cares about the first eight characters of the file; the rest is politeness to humans. In the future there's a good chance we'll move to more heavyweight digests of the file content
  12. KerbalStuff Recovery Update Hey everyone! Thank you all so much for your patience with me travelling! I'm writing this from a bus between New York and Boston, which conveniently has both free Wi-Fi and power. I'm very glad to say that I've finished my second round of recovery efforts by using my su-perl-powers. : ) I've managed to identity about 2,100 CKAN .meta files which were pointing to KerbalStuff, and which had licenses which permit redistribution. For all of these files, I've updated them to point to a mirror site maintained courtesy of @VITAS . Because of the huge numbers of fi
  13. There is now, and it's exactly what you've written! Olympic1 massaged the code to work today, and I merged the changes this afternoon. There'll also be a client release soon that will handle a little bit of extra "Spacedock" metadata, but the existing clients should work fine with the new files we're producing now.
  14. Update from me: I've recovered the mods which: 1. Are marked with free licenses. 2. Were in our indexer's cache where I can easily get to them. 3. Complete list of recovered mods in the spoiler below. There are still free mods from KS that have not been migrated. I'll be doing my best to do those in the next couple of days, but they're likely to be less straightforward. No CKAN client update is necessary, just update your metadata. Be aware some mods may have dependencies which aren't available, so expect there still to be some sharp edges. I'
  15. Update from me: I've recovered the mods which: 1. Are marked with free licenses. 2. Were in our indexer's cache where I can easily get to them. 3. Complete list of recovered mods in the spoiler below. There are still free mods from KS that have not been migrated. I'll be doing my best to do those in the next couple of days, but they're likely to be less straightforward. No CKAN client update is necessary, just update your metadata. Be aware some mods may have dependencies which aren't available, so expect there still to be some sharp edges. I'm out for t
×
×
  • Create New...