MscG

Uninstall TACLS using CKAN, than refresh the list and re-install it. It worked for me.

I have the same problem and signaled it some time (and some versions) ago but it's still there.

The last ckan metadata for TACLS has this snippet: "install": [ { "find": "GameData/ThunderAerospace", "install_to": "GameData", "filter_regexp": "PluginData/TacLifeSupport/LifeSupport\\.cfg$" } ] But the LifeSupport.cfg location has been move and the regexp doesn't match anymore. This means that, by installing the core plugin, the config file is installed as well and RO won't have any chance to overwrite it. I don't know who should take care of it (if on the CKAN end or the mod end), but some refactor in the metadata is now needed for this mod.

The mod is on CKAN but the the version name "V0.12.3" (with the capital V) is not considered newer than the version "v0.12.2" (with the small v)

Hi everyone, the update UI of the mission control that comes with the latest version of Contract Configurator highlitghted a problem with the mod in my installation: the "Build your first airplane" doesn't detect parts with control surfaces, by I have them (I almost maxed out the tech tree) and I already have built and flown aircrafts. What I see in the mission control screen is this. Any idea on how to solve the problem?

The CKAN issue has been fixed, now the 2.0.5 version is correctly marked as compatible with 1.1.3.

Ok, I'll do it! Thanks! Edit: I opened a NetKAN issue https://github.com/KSP-CKAN/NetKAN/issues/4379 . I hope it can help!

Hi, I just checked the metadata on CKAN for the 2.0.5 release ( https://github.com/KSP-CKAN/CKAN-meta/blob/master/InfernalRobotics/InfernalRobotics-v2.0.5.ckan ) and it still says that the mod is 1.1.2 compatible. Is it an error? If yes, is it up to you to manage the CKAN metadata or do I have to contact the CKAN team to fix the issue?

Obviously I never meant to be accusatory, expecially toward you, who took over your shoulders the burden of maintaining the mod. The "Talking about moot points" in my previous post was just a playful reference to the drama the spread out between mod developers and CKAN ones and I just meant to use it to introduce a question: I just wanted to know if you decided to join the CKAN-diaspora. Now, as a software developer who works everyday with dependency tracking systems, let me say that I support you in your decision to control the metadata for CKAN listing: I think it's the best and the most efficient way to avoid problems coming from random people/software trying to do the job in your place. It may take some time, it may be hard at the beginning, but the result will help you and the people using your mod.

Dear sir, what kind of tone are you referring to? I already knew that the @danfarnsy was relying on automatic CKAN discovery since he had the same problem in the previous release. I read about the "developers vs. CKAN" drama story, so I was just asking if it was a developer choice not to publsh the metadata. Then I checked more deeply, spot the problem and signaled it. My only fault is that I posted BEFORE checking the CKAN-meta commits.

Talking about moot points... Is there a reason why the new version is not on CKAN yet? Ok... just checked the commits on the CKAN-meta repository and I've seen that the new metadata are there... but the version v0.12.1 (with the starting "v") is considered newer than 0.12.2 (withouth the starting "v")

Ok, I found the solution: CKAN has just banned ModuleManager, so I had to install ModuleManger in an alternative way ( https://github.com/KSP-CKAN/CKAN/issues/1796 )

I have a problem installing this mod from CKAN. More specifically, in a fresh KSP/CKAN installation the mod doesn't show up in the list of mods even if the CKAN registry.json contains the correct entries. In another installation, where I installed Docking Port Alignment through CKAN some months ago, the mod shows up only in the "Installed" and "All" filters but not in the "Compatible" nor in the "Incompatible" ones. Anyone has an idea on how to solve it? KSP is version 1.1.3 and CKAN is v1.18.0

Hi all, i have a problem when using the offset tool on parts that are attached to a procedural tank. More exactly, I have a procedural battery and a stock structural fusalage on top of it. Using the offset tool to slide the fuselage down (in order to hide the battery inside it), this part will start to snap to strange positions and I can't center it back in anyway. Using the offset tool to slide the battery inside the fuselage works fine, but I can't use this solution for rocket design problems. Any help with this problem?

You just missed the "v" in front of the version number when you created the 0.12.1. CRP fixed the NRE when clicking on the VAB, but it has no connection with the versioning problem.

The new artifact on CKAN has version "0.12.1" while the previous one has "v0.12.0". It seems that CKAN is confused by this and it thinks that "v0.12.0" is newer than "0.12.1" and won't install the new version. I forked the CKAN-metadata project and updated the new artifact to have version "v0.12.1" and now the application suggests me this as an update. I think that you must fix the version history on CKAN to solve this problem.

I suppose that the config file is not changed... yet! As a programmer, I think that this will lead to nasty bugs at the first future change which involves the config file, if you forget to update the configuration module entry on CKAN. Mine is just a suggestion: keeping things synchronized will help you a lot!

I saw that the mod just spawned an hour ago in the CKAN-meta repository but it depends on the TACLS-Config module, which is still outdated and points to an older .zip file

Any plan to put this new version on CKAN?

I'm on Windows. The order of the sounds is correct, but it's like it's using default values for file names, ignoring what you've typed into the settings

The volume sliders work after switching between ships, but changing the values in the sound files textboxes does nothing and it always plays the fuel pump sound.

I don't know if this has been already asked, but I have a problem with the crew transfer sounds. The problem is that... the plugin always plays the pump sounds, even when I'm transferring crew! I checked the settings and they seem ok. Currently, the settings in the SMSettings.dat file are the following ones: PumpSoundStart = ShipManifest/Sounds/59328-1 PumpSoundRun = ShipManifest/Sounds/59328-2 PumpSoundStop = ShipManifest/Sounds/59328-3 CrewSoundStart = ShipManifest/Sounds/14214-1 CrewSoundRun = ShipManifest/Sounds/14214-2 CrewSoundStop = ShipManifest/Sounds/14214-3 PumpSoundVol = 1 CrewSoundVol = 1 I tried to switch the values between the pump and crew transfer groups using the textboxes in the settings window, I hit the save button and nothing changed. The problem arose a couple of updates ago, but still persists today, with the latest one (the one released today). Can anybody help me?