4x4cheesecake

Members
  • Content Count

    1,666
  • Joined

  • Last visited

Everything posted by 4x4cheesecake

  1. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    So, I have a new (hopefully last) beta versions for you guys Some highlights of this version: I've reworked the UI to be cleaner and more intuitive. There is also a "Help" window available now, explaining the main features (tried my best^^). You can now type in a single version number, it will be set to be compatible with the current game version. In this case, you can use a wildcard/asterisk on the patch number, for example: 1.4.* This will set every KSP 1.4.x version to be compatible with your current game version As suggested by @Stone Blue: You can prevent AVC from writing into the KSP.log/output_log by adding the command line parameter "-AVC-log-only". AVC still writes it's own AVC.log within the mod folder. (Thanks @blowfish for sugegsting the command line parameter ) https://github.com/4x4cheesecake/KSPAddonVersionChecker/releases/tag/1.2.0.8_beta_2.3 This beta does no longer contain a config file, it will be created a game launch instead. By default, the compatibility override is disabled and need to be enabled (preferable via GUI)
  2. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    I haven't changed the internal assembly version but the one in the "KSP-AVC.xml" file because AFAIK, LGG runs a script to do these things. If I accidentally push a changed version to github, it may end in the pull request and AVC would skip a version. That's fine, it's one of the debug lines I've added to track down the reason for the gibberish characters which appear in some logs. The "{" is supposed to be the very first character in every .version file and if it is not the case, some code will run to clean it up. Just to be sure it is working properly, I've added an output of this line. There is actually quiet a lot debug code still in there, so if anyone reports an issue, it may helps me to find the culprit, but I'll remove as soon as I'm done Probably yes but I would actually prefer to not remove the log entries from the KSP.log. If a bug related to AVC occurs and someone is going to ask for help in the support subforum, everyone will ask for a KSP.log or output_log but definitly not for a AVC.log. I have to look at the logger code, maybe I can make it optional but no promises.
  3. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    Thanks Now, I know that it is not an issue with the .version file or the json parser...that's kinda good news because it would be quiet a mess to fix something in the parser but I also didn't found the log entry I was hoping for... This one is going to be tricky... edit: Ok, now it happend once for me but it was gone on the next launch. I'll put it on the bottom of my todo list since it seem to be just a messed up debug message which will not be in the release version.
  4. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    Glad to hear Found this one ~40min as well and fixed it already. The override GUI becomes available as soon as all mods have been checked for updates but the button in the dropdown list didn't know about this fact^^ That also means, that it will never become available, if AVC is skipped. Strange...I wasn't able to replicate the issue so far, which makes it hard to track it down. Would you mind to upload your log as well? There is already some code to remove gibberish characters which may appear while getting the online .version file, so that doesn't seem to be the case here... I've build a new .dll which will create some additional log entries which hopefully help to get closer to the culprit of the issue: https://www.dropbox.com/s/znattje7x3d5t5k/KSP-AVC.zip?dl=0 Until I can replicate the issue, I would kindly ask if someone who got this issue can run this version und upload the log for me to check (This version includes a new cool feature for the ignore list buttons , feedback about invalid version input, clearing the input field after versions are added and the fix for the NRE^^) Oh yeah, that would be an issue as well
  5. 4x4cheesecake

    Ask the Mods questions about the Forums!

    Yep, I saw the new thread, that's why I'm asking (As long as you guys know what happend there and it can be fixed, that's fine I guess^^)
  6. 4x4cheesecake

    Ask the Mods questions about the Forums!

    Looks like the old Forum Test Thread cannot be repaired? Do you guys know what happend to the old thread and can we get an explanation of the issue? Do we need to worry that it can happen to other threads as well? Yep, I'm a bit curious
  7. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    Thank you very much I see... well, that's a part of AVC I haven't touched but I'll take a look at it Ahhh, that's the window which usually shows the updates and/or compatibility issues. It shouldn't be there if there is nothing to display, i'll fix it Yep, unfortunately this would cause MM to rebuild the ConfigCache everytime a mod is added/removed from override feature and/or a new timestamp is created for the update frequency, so the config is placed in the PluginData folder on purpose. Thanks for your feedback
  8. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    Fair point, I'll change it. There are still a lot of debug messages I've left in the code but I cannot find actual garbage in my log. Does it happen on every game start? Maybe the "you have successfully installed/updated AVC" window is borked for you but it should only show up on the first launch. The Override window cannot be created while the update checker progress window is still visible, so that's probably not related. That would be kind of you Your log would be helpful to find out which window isn't displayed properly
  9. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    Not sure if this is a serious question but just in case: https://wiki.kerbalspaceprogram.com/wiki/Key_bindings#Modifier_key
  10. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    I've changed the key combination to "modkey + 2" as well. I guess, nobody plays KSP without a modkey, so this should work on every machine Also, a little update in general: Had to fix two major bugs which took me more time than expected but now, I can finally release a beta version for you guys to try I already know a few issues and they are listed on github but it's more about details, nothing really bad Pinging @linuxgurugamer @MOARdV @Stone Blue @Tonka Crash I would love to get some feedback on the new features (detailed description above). Three more thing about the update frequency: 1) So far, it is just part of KSP-AVC, not MiniAVC (the beta version doesn't contain MiniAvc anyway. Want to test it "in the wild" before I implement it in MiniAvc as well. ) 2) If you already have set an interval but decide to change it, it will take effect after a) the previous time interval was exceeded or b) you remove the previous timestamp completely and AVC will create a new one for you. 3) Need to be set in the config file (GameData/KSP-AVC/PluginData/AVC.cfg) https://github.com/4x4cheesecake/KSPAddonVersionChecker/releases/tag/1.2.0.8_beta_2 edit: Totally forgot to mention the proper format to enter version numbers for the version override: The first version number will be the one which is going to be replaced, any other version number after that will be the "target version number", each version number must be separated by a comma. for example: 1.4.2, 1.5.1, 1.6.1 will set every mod which is compatible for 1.4.2, to be compatible with 1.5.1 and 1.6.1. You need to enter at least 2 version numbers. If you want to configure the version override via config file instead of using the GUI, the format is still the same. Also, here is an example config file: KSP-AVC { OVERRIDE_PRIORITY = none SIMPLE_PRIORITY = none DISABLE_COMPATIBLE_VERSION_OVERRIDE = False OVERRIDE_NAME { OverrideEnabled = ShipManifest OverrideEnabled = PicoPort } OVERRIDE_VERSION { OverrideEnabled = 1.4.2, 1.6.1 } OVERRIDE_IGNORE { IgnoreOverride = PicoPort IgnoreOverride = ShipManifest } INTERVAL { MinTimeBetweenAvcRuns = 0 //Timespan between AVC runs in hours AvcRunsNext = 2/28/2019 3:25:54 PM } } (the first two *_PRIORITY values don't do anything :P)
  11. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    So far, it is "alt + insert" and hard coded. If you can present me good idea where to place this button: maybe^^ It cannot be in the "update available / compatibility issue" window since it will not pop up everytime, especially if you use the override feature. edit: when I think about it: I guess I can sneak in a button into the dropdown addon list since it will always be there How about this @DStaal ? (btw: the blue colored mod name indicates an active compatibility override )
  12. Well, I guess I'll write my own PBS patch in the meantime. Thanks to inform us and have fun in Civ @_Zee
  13. Nope, and when my "mirror patch" got integrated, is was explicite mentioned in the patch notes that there is still no support for any KSP prior to KSP 1.6::
  14. 4x4cheesecake

    [1.5.1+] Click Through Blocker

    You can be sure, your work is much appreciated
  15. 4x4cheesecake

    [1.5.1+] Click Through Blocker

    There is no KSP_VERSION_MIN in the 1.4.5 release (same applies for the 1.5.1 version): { "NAME": "ClickThroughBlocker", "URL": "http://ksp.spacetux.net/avc/ClickThroughBlocker", "DOWNLOAD": "https://github.com/linuxgurugamer/ClickThroughBlocker/releases", "GITHUB": { "USERNAME": "linuxgurugamer", "REPOSITORY": "ClickThroughBlocker" }, "VERSION": { "MAJOR": 0, "MINOR": 1, "PATCH": 7, "BUILD": 0 }, "KSP_VERSION": { "MAJOR": 1, "MINOR": 4, "PATCH": 5 } } So, when CKAN installs the 1.4.5 version, it will only be compatible for KSP 1.4.5.
  16. 4x4cheesecake

    [1.5.1+] Click Through Blocker

    Hm...CKAN just lists the version compiled for 1.4.5 so the version file also says it is for KSP 1.4.5 CTB isn't even listed anymore if you don't have 1.4 set to be a compatible KSP version.
  17. I was about to write this here but you figured it out already^^ CKAN should list the CTB update as soon as linuxgurugamer switches the status from pre-release to a full release, I've notified him already in the CTB thread
  18. 4x4cheesecake

    [1.5.1+] Click Through Blocker

    It is mentioned the toolbar thread...red and bold...right above the reports about the disappearing toolbars. Maybe it's just me but I thought it might be worth to check the CTB thread before reporting any issues.
  19. 4x4cheesecake

    [1.5.1+] Click Through Blocker

    Is this intended to be a pre-release? At least AVC ignores a pre-release (if it is not explicite allowed in the .version file) and CKAN probably as well, that's why everyone in the toolbar thread is complaining about their toolbars disappearing on the latest release and apparently no one checked the CTB thread for an update
  20. 4x4cheesecake

    If I ever make it back from Eve

    Your're welcome But look at all the sweet numbers and graphics you have created...it's beautiful!
  21. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    I'm almost done with my work on the AVC update and I would love to get some feedback, especially for the UI I've created What's done so far: Added "Compatibility Override" Added possible time interval between runs of AVC "Compatibility Override" allows to oppress the "Compatibility Issues" window. Since many mods are not updated to the latest version of KSP but they still run fine, many players will install "incompatible" mods anyway. Well, AVC doesn't care about whether a mods runs fine or not, it will complain about compatibility issues as soon as the numbers don't fit. If you are annoyed by AVC complaining, the "Compatibility Override" feature got your back Override by version Define a KSP version to be compatible with a different KSP version. This allows you to set many mods at once to be compatible. For example: You can set any mod, which is compatible with KSP 1.4.1 to be compatible with KSP 1.6.1. Individual mods can be removed from the version range by putting them on the "ignore version override". These mods can still use the "override by name" feature. Override by name If you don't want to define many mods at once to be compatible, you can also set a single mod (-name) to be compatible with the KSP version, you're running. Ignore version override Mods on this list will ignore the "Override by version" settings. "Override by name" is still possible (intended)! Disable override at all / for a single mod The features can be disabled at all or for a single mod by adding an entry to the .version file. If a mod creator want's to prevent any compatibility override for his mod, this is the way to got *stares at kopernicus* The first 4 options can be set by config file or in the UI (I'll probably add the ability to enable/disable the compatibility override via UI as well) Update notifications are not affected! GUI so far: This window will not replace the "update available / compatibility issue" window. It can be opend with a key combination after the mods were checked for updates. Upper left box: Here you can see all the mods with compatibility issues, for which KSP versions they are meant to be compatible, see which override option may affects this mod right now (version, name, none), if the compatibility override is enabled and a button to put it on the "Ignore version override" list. The "ENABLED" button will only control the "override by name", not the "override by version" but is highlighted if any of both modes is enabled! Upper right box: This is the list of version overrides. It's not functional yet but it will display which KSP version will be set to be compatible with another KSP version, for example: 1.4.2 => 1.6.1 This means, that all mods which are compatible with KSP 1.4.2 are now set to be compatible with KSP 1.6.1 as well. Lower left box: A list of mods which are put on the ignore list for the version override. Can be removed via the "REMOVE" button. Lower right box: List of mods which don't allow any compatibility override Time interval between AVC runs You can set a integer number of hours for AVC to wait before it will check for updates again. Takes effect after a second game start (on the first start, AVC will calculate when it is supposed to run the next time and creates a timestamp in the config file). It is also possible to disable AVC at all by setting the config entry to "-1", use "0" if you want AVC to run at every game start. If I can get the UI to work properly with the version override, I'll release a beta version tomorrow, but if you already have any suggestions or critic on the features/UI so far, I would love to hear it
  22. 4x4cheesecake

    [1.5.*] RCS Build Aid Continued - New Dependencies

    It is still there but not flagged as compatible with KSP 1.6.1 so you need to 'trick' CKAN to show it in your list of compatible mods. Don't worry, it works fine on 1.6.1 it's just a technical formality. Open CKAN, go to Settings -> Compatible KSP Version and select 1.6 (should be the very first entry in the list). Apply the changes and CKAN should show RCS Build Aid (and a couple of other mods with the same 'issue') again
  23. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    Oh, I missunderstood you the first time, I got it now
  24. 4x4cheesecake

    [1.5.x] KSP-AVC Add-on Version Checker Plugin - MiniAVC

    Sounds reasonable to me and I have an idea how this can be added easily (and it would be much more fun than creating an UI ). Since I'm already working on some changes for AVC I could add this feature as well but I'll wait for a response from @linuxgurugamer ZeroMiniAVC just affects MiniAVC, right? MiniAVC doesn't have a config file, it doesn't even include the code to read the config from AVC. So, adding this feature to MiniAVC, would make it less mini and more AVC. I didn't add the "Override Compatibility" feature in MiniAVC so far for the same reason. I think, it is supposed to be "mini" and just perform a simple version check, nothing else.
  25. 4x4cheesecake

    Science Lab Not Transmitting

    Uff, there are a lot of exceptions regarding the science lab: NullReferenceException: Object reference not set to an instance of an object at ModuleScienceLab.updateModuleUI () [0x00000] in <filename unknown>:0 at ModuleScienceLab.onPartActionUI (.Part p) [0x00000] in <filename unknown>:0 at EventData`1[Part].Fire (.Part data) [0x00000] in <filename unknown>:0 UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object) UnityEngine.DebugLogHandler:LogException(Exception, Object) UnityEngine.Logger:LogException(Exception, Object) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(Part) UIPartActionWindow:CreatePartList(Boolean) UIPartActionWindow:UpdateWindow() UIPartActionController:UpdateActiveWindows() UIPartActionController:UpdateFlight() UIPartActionController:Update() This message appears ~360 times. I thought this happens due a mod incompatibility since "LonesomeRobots Aerospace: Station Parts" is released for 1.3.1 but the mod doesn't contain a .dll file, just a bunch of models, textures and configs. I've checked the config for the science lab and it looks fine though. Kinda puzzled here...