linuxgurugamer

Looks nice, but isn't it rather tall? Try putting it horizontally rather than vertically and see how it looks.

In order for this to be useful, there would be some sort of wrapper file similar to what the Blizzy toolbar uses. This adds more code to an already bloated game. I am really trying to understand what advantage there would be to having a mod do the update of the info rather than reading the information from the version file.

To confirm, this is only with the kw battery? Stockbatteries are fine?

Yes, but there is no guarantee that one runs before another. What if your mod ran before this one? Either you would have to put in code checking to see if AVC is ready, or AVC would need to be changed a bit. All in all, I personally don't see a real need for this. All of my mods have the version number baked into the DLL, but that is pulled from the .version file itself.

I would doubt it. KSP-AVC runs before the plugins are loaded, to do what you ask would require changing the way it runs. I would think it would be possible to add an API for it, though.

New release, 0.4.1: KSP 1.3.1 update

The fix is rather simple for this, it's a one line change in two files (one file for the full AVC, one for the MiniAVC) I've sent a PM to @cybutek about this. I've also submitted a PR on Github with the bug fix.

This has been bugging me, and I think I've found a real bug: It seems that when the KSP_VERSION is lower than the version of the game, it doesn't check the VERSION at all. I'm basing this on the following: AVC file in folder: { "NAME":"K2CommandPodContinued", "URL":"http://ksp-avc.cybutek.net/version.php?id=428", "VERSION": { "MAJOR":1, "MINOR":1, "PATCH":8, "BUILD":1 }, "KSP_VERSION": { "MAJOR":1, "MINOR":3, "PATCH":1 }, "KSP_VERSION_MIN": { "MAJOR":1, "MINOR":2, "PATCH":0 }, "KSP_VERSION_MAX": { "MAJOR":1, "MINOR":3, "PATCH":99 } } AVC downloaded from URL (run through a JSON formatter): { "NAME": "K2CommandPodContinued", "URL": "http://ksp-avc.cybutek.net/version.php?id=428", "VERSION": { "MAJOR": 1, "MINOR": 1, "PATCH": 8, "BUILD": 2 }, "KSP_VERSION": { "MAJOR": 1, "MINOR": 3, "PATCH": 0 }, "KSP_VERSION_MIN": { "MAJOR": 1, "MINOR": 2, "PATCH": 0 }, "KSP_VERSION_MAX": { "MAJOR": 1, "MINOR": 3, "PATCH": 99 } } In the output_log.txt: KSP-AVC -> R:\KSP_1.3.1_dev\GameData\JFJohnny5\K2.version NAME: K2CommandPodContinued URL: http://ksp-avc.cybutek.net/version.php?id=428 DOWNLOAD: NULL GITHUB: NULL VERSION: 1.1.8.1 KSP_VERSION: 1.3 KSP_VERSION_MIN: 1.2 KSP_VERSION_MAX: 1.3.99 CompatibleKspVersion: False CompatibleKspVersionMin: True CompatibleKspVersionMax: True CompatibleGitHubVersion: True (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) KSP-AVC -> http://ksp-avc.cybutek.net/version.php?id=428 NAME: K2CommandPodContinued URL: http://ksp-avc.cybutek.net/version.php?id=428 DOWNLOAD: NULL GITHUB: NULL VERSION: 1.1.8.2 KSP_VERSION: 1.3 KSP_VERSION_MIN: 1.2 KSP_VERSION_MAX: 1.3.99 CompatibleKspVersion: False CompatibleKspVersionMin: True CompatibleKspVersionMax: True CompatibleGitHubVersion: True UpdateAvailable: False You can clearly see that in the log, it specifically says that no update is available, AND in-game, it shows the mod in green when I changed the website to reflect the correct version of the game. It's obviously using the data from the website, and, IMHO, is also obviously now totally useless to verify that mods are ok after the game has updated. The specific circumstance I ran into was when checking parts mods, which have a very relaxed MIN and MAX values; but if the base KSP_VERSION is not matching the current game, it doesn't raise a flag at all.

I’ll have a more formal beta tomorrow, with greenhouses and other parts

For all interested parties: I'm reviving this mod, I have it working in 1.3.1, download here: https://www.dropbox.com/s/eqe4cixmdxgtvsa/IFI_LS.zip?dl=0 I'll be adding one or two greenhouses (using zzz's public domain model), and have asked @Akinesis if I could include his parts in the mod. Please send me feedback, it's the only way I'll know if things are working properly.

Ok, thanks.

@Sandworm Would you mind if I include this patch with the revival of the mod I'm doing?

toolbar icon missing where? It's odd because I do see it, and I am seeing consumption. I see the toolbar icon in the space center, tracking station and in flight. Are you in a sandbox or career game? Make sure that all traces of any previous install of this mod have been deleted.

I'm working on reviving the IFI LS mod, which has the following resource defined: RESOURCE_DEFINITION { name = LifeSupport density = 0.0045 unitCost = 40.0 flowMode = ALL_VESSEL transfer = PUMP isTweakable = true } Is there any resource which is in the CRP which would be equivalent?

Well, it is possible to add modules to parts on the fly, but it's much easier to let MM do it.

Ok, I see. I compiled it in DEBUG mode, he changes things depending on whether it's debug or not. Also, he said he removed the need for ModuleManager, and apparently disabled the MM patch, which was needed to install the LS into the command podsl Here is another build, non-debug and with the MM patch. You will need ModuleManager 2.8.1 https://www.dropbox.com/s/eqe4cixmdxgtvsa/IFI_LS.zip?dl=0

Question, I see from the mod thread that when right-clicking on a command pod, there should be several lines from the mod in the PAW menu. Is that old, because I dont see it in my testing on 1.3.1

@Akinesis Looks like I'm going to be adopting the IFI LS mod, I have what appears to be a working version for 1.3.1 Would you like me to include these part in the main mod?

I need feedback to know whether this is working or not. Since I do not use this mud, or I should say, have not use this mod before, I don't know what's working and what's not working. I am relying on feedback from the users to bring me up to speed on the usage of this mod.

@Synthesis I spent a few minutes, try this out, it's compiled for 1.3.1: https://www.dropbox.com/s/xpjmt7hajg10fxb/IFILS.zip?dl=0

Very minor update, 0.0.2.1: Fixed version file

Minor update, 0.1.15.1 fixed missing icoins

Minor update, 0.0.4.1: Updated version file

Very nice. Ok, I just looked at your download, you have a couple of small problems Could you remove the space from the path name (ie: change the name to : LCA_Project), makes things easier Please add a .version file, that way CKAN and AVC can know about updates Move the VAB folder out of the GameData folder, it needs to be in Ships/VAB Here is a simple .version file, just save it in the LCA folder in a file called: LCA.version All you will need to do is update the version numbers every time you release an update. { "NAME": "LCA_Project", "VERSION": { "MAJOR": 0, "MINOR": 1, "PATCH": 0, "BUILD": 0 }, "KSP_VERSION": { "MAJOR": 1, "MINOR": 3, "PATCH": 1 } }

New release, 0.0.4: Updated for KSP 1.3.1