Jump to content

politas

Members
  • Posts

    751
  • Joined

  • Last visited

Everything posted by politas

  1. What operating system are you on? Please post the details of the certificate message.
  2. You can follow the homepage link when available to read the mod's forum thread, and look at the Relationships tab to see which mods it has known conflicts with. The relationship info is often only stored in one direction, though, so the mod you're looking at may be listed as a conflict on a mod you already have installed, without having its own conflict relationship to that mod. Also, there's no metadata stored in CKAN explaining _why_ particular mods are incompatible or a particular version of a mod is not compatible for a version of KSP.
  3. Have you tried using "C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program" (with quotes around it to escape the spaces)?
  4. I think you could do it with ModuleManager files such that it will add the ability for Procedural Deuterium and Tritium tanks, but only if users have ProceduralParts installed. Then it could be added as a recommends rather than a depends.
  5. That would completely mess with the version numbering. Better to have the fork as a separate mod that conflicts with the original.
  6. As an alternative to making part models, have you considered integrating with ProceduralParts to have adjustable Deuterium/Tritium tanks? I think that would involve less work than creating models that fit perfectly and associated textures.
  7. Should be showing as compatible with 1.0.5 in CKAN soon. Hey, @pizzaoverhead, I notice that you have a github repository that you seem to be using for your code. Have you considered pushing your releases there as well as to Curse? Then CKAN could index new releases.
  8. Should be in CKAN for 1.0.5 soon.
  9. Just downloaded Crzyrndm's release zip and it certainly _seems_ like it has a part with all its files - GameData/B9_Aerospace/Parts/Aero_Wing_Procedural/ folder has four .dds files, two .mu files and four .cfg files.
  10. Hmm. Looks like someone has applied metadata for the fork to the original. We should probably just have crzyrndm's fork as a separate mod.
  11. If you want. I'm just happy that you aren't one of those modders who leaps from "I don't see the need for CKAN" to "So no one should be able to use CKAN for my mod".
  12. For anyone wanting to upgrade to the pre-release Trajectories version, I've made a file for CKAN stock aero users to upgrade to the new version that should work fine with future upgrades. File-> Install from .ckan should add the data. If you've got the previous version installed thanks to an earlier KSP, you'll need to upgrade as a second step.
  13. I've made a file for CKAN stock aero users to upgrade to the new version that should work fine with future upgrades. File-> Install from .ckan should add the data. If you've got the previous version installed thanks to an earlier KSP, you'll need to upgrade as a second step.
  14. It ought to work fine in 1.0.5. Looking at the parts, it doesn't seem like Squad have made any relevant changes. I've submitted an update for CKAN.
  15. I have no further help, I'm afraid, other than to hope that @pjf or some other CKAN coder can have a look, but have you tried running a "ckan clean" on your install?
  16. Is there a separate thread for Real Plume? The latest versions are marked as only being compatible with 1.0.4 in CKAN, so anyone installing on 1.0.5 is going to get an old version (v0.4.3).
  17. Try changing the filter to "Compatible" It appears that you can only use Low Res with KSP up to 1.0.4, and only High Res for 1.0.5. Not sure why that happened, but that's what CKAN's metadata is currently set to.
  18. CoolRockets is also incompatible with KSP1.0.5. Are you doing a .ckan import from a previous 1.0.4 install or something? I suspect that Planetshine is not important in this error. There's some underlying issue that just happens to get triggered. If the CKAN programmers are going to do anything to work out what the unhandled exception is (so that they can write some code to handle it), you're going to need to be very precise about exactly what you've done leading up to this, because simply installing Planetshine doesn't do it, and the references to KER and CoolRockets may well be diagnostic.
  19. Actually, that's not true. Fuzzy versioning has not yet been implemented. The mods that list as compatible for 1.05 but have "Max KSP" showing lower than 1.0.5 are all showing the max KSP version from an earlier version of the mod (you'll see it in the details tab). This is due to a bug in how that column is populated, where it sees the version at the bottom of an alphabetically sorted list of .ckan files as the latest version, which means any time a mod author adds a level of versioning, the order gets thrown out, because "blah.1.ckan" is sorted before "blah.ckan". When the respective mod authors release the updated versions. CKAN does not make pre-release versions available to users.
  20. Hmm. It already was, but clearly not successfully. Working on it. Have you tried turning it off and on again? Seriously though, we need more information. What OS are you on, have you followed all the instructions in the release notes, what error messages do you get when trying to run from the console?
  21. Which metadata repositories are you referring to? The main CKAN repository doesn't include pre-releases, so whoever maintains the repository you're using would have to fix it. EDIT: Ah, I see what you're referring to. Sorry. Well spotted. Patch submitted. EDIT2: Not sure that any of those repositories are actually functional, though.
  22. For not being able to launch KSP from CKAN under Linux, see this issue For the other, have you run mozroots --import --ask-remove like the release notes say?
×
×
  • Create New...