metalpoetza

Members
  • Content count

    94
  • Joined

  • Last visited

Community Reputation

13 Good

About metalpoetza

  • Rank
    Rocketry Enthusiast

Profile Information

  • Location Cape Town
  1. I have found the bug in pyKAN, and just pushed a fix. The latest commit in git contains it. I will release a new official version with the fix once @minecraft2048 finishes his current work so it can all go into one release. In the meantime you can get the (small) fix by using the master-branch git code directly.
  2. Possibly, but I suspect not -since I wouldn't be writing any new functionality into the GUI at all - the GUI would just do the exact same thing the CLI does, call out to the underlying libPyKAN to do the work, while presenting it all in a nice a frontend. There is a stub pykanqt file in the repo, but I haven't had time to actually work on the GUI due to work-load getting insane this year, was planning to do so on my last holiday but ended up spending it all househunting. Hopefully sometime soon.
  3. Version 0.1.2 is now available. A new version of PyKAN with multiple bug features and some new features including a revamped commandline interface with support for multiple modules in a single command. My thanks to Feanor for his wonderful contributions to this release. https://github.com/ajventer/pyKAN/releases/tag/0.1.2
  4. Heh, well I was working on it mostly because it was ruining my playthrough so I'll be starting over now that it's fixed because I am in the final tier of CTT... and only NOW do I do manned missions again ? I'd end up with no use for the science from most of them. But I believe I have correct values for the missing ones now - I was able to do a test playthrough up to the end of the year-in-space mission. So I'm preparing a P.R. - and in case anybody was wondering, the KerbalAcademy pack works great with this.
  5. I probably could, but I'm still experimenting a bit with the fix - looks like it needs a bit more tweaking to work for everything - GROUP_ALL worked for first crew but not for the next ones. Once I have it working properly I will do a P.R.
  6. I believe I found the cause of the bug. Found this in the log file: NotSupportedException: The SelectUnique method can only be used in DATA nodes with the uniquenessCheck attribute set. So I added: uniquenessCheck = true To the DATA node in the SSFirstCrew mission - that did not help. So I instead I removed the SelectUnique() call from the targetVessel line. That made the contract not show up in the All listing even - suggesting it broke it entirely. Next thing I tried was to open my save file, get the hash for my station vessel - and replace that entire line with one that read targetVessel1 = <hash code> Hoping this would match what SelectUnique was meant to return. No luck. I googled the error message, it's actually defined in the ContractConfigurator code - so this may well be a version incompatibility with C.C. perhaps @nightingale has some insights ? Update: I found it, my very first hunch was right - it did need a uniquenessCheck line added, I just had to look up valid values for it. Based on my understanding of the documentation, and what I think the contracts want to do: adding uniquenessCheck = GROUP_ALL to every one of the targetVessel data nodes is the fix for the bug.
  7. The only other contracts I have active is CactEye so I doubt it.
  8. I seem to have encountered a bug. I launched a space station when I got the contract, completed it successfully. But the next contract never appeared. After a while I got concerned and looked. The first crew contract show "Get your space station" as unmet. I am playing with SSRSS and all other contracts seem to to work fine. Since I cannot get this contract, I also cannot progress with any other crewed missions. Is there a work-around, perhaps a save-file hack I could use for right now ? Or a fix suggestion to get it to appear ?
  9. Those are all implemented - I've not had a mod fail to install correctly through it in a long time - I use PyKAN as my own client for day to day stuff -and my current playthrough is on SSRSS, with a whole slew of other mods, and working well. The main reason I didn't do it that way at the start was to avoid the risk that bugs in my then, still new, project could corrupt people's CKAN systems. Right now the CKAN registry is treated as a read-only access - so pyKAN knows what CKAN has installed, but not vice versa. But the code has been quite stable at the library level for some time now - so it's probably safe to add that feature now. The main place I want to evolve the code hence-forth is on the frontend side, it really could use a GUI.
  10. Heh, I had no idea the CKAN guys even noticed or cared about my little project. As it happened I wasn't able to work on it last week - we are in the process of moving house and it ended up taking all my time, so the next version is yet again delayed a bit by real life, but thanks for that information - having the full spec to refer to could be very helpful. Are there any particular deficiencies I should prioritise ?
  11. SSRSS detection seems to be broken. First sounding rock mission is wanting me to hist 92000m - which is the RSS height, but for SSRSS it should be around 63000m so it seems the RSS detection is overriding the SSRSS flags.
  12. Hi, No pyKAN uses it's own installation registry - but it does *read* the CKAN registry and knows what CKAN has installed, just not the other way around. I am hoping to start serious work on the next version next week - I'll look into the possibility of doing this as a feature.
  13. Here's how to fix the problem - I'm not sure what causes the bug but this makes it work. ./pyKAN change_setting --key=minKSPversion --value=1.2.1 ./pyKAN change_setting --key=maxKSPversion --value=1.2.1 ./pyKAN update Afterwards it works normally. It seems it has trouble parsing the version number in 1.2.1 for some reason. I will investigate further but in the meantime manually setting the version flags in the settings file works.
  14. Seems like something is breaking the version checks in the 1.2.1 repo - I will have a look and try to reproduce it when I can.
  15. Oh - I must have misread the document, I was looking for the data to go up, never checked for science to review. I'll try that, thanks.