linuxgurugamer Posted February 15, 2020 Share Posted February 15, 2020 (edited) @kizza42 When a mod is installed because it is needed by another mod, that column will become checked. When that other mod is removed, the dependencies are removed (if not needed forma different one). By unchecking that, you can remove it from being a dependency and it will remain on its own Edited February 15, 2020 by linuxgurugamer Link to comment Share on other sites More sharing options...
LittleBitMore Posted February 17, 2020 Share Posted February 17, 2020 I'm experiencing difficulties with CKAN. Every few mods it tosses me a 403 (Forbidden). This goes on random mods of my 1.4.5 install (it did MechJeb2 once, is doing KAS multiple times, has done the GPP Textures once). It makes installation long and painful for those things that need installing via a backup site, and for those that don't have a backup, it cancels the installation. I'm gonna install those things manually. I just wanted to let you know these mods were being difficult in 1.4.5 installs. Link to comment Share on other sites More sharing options...
HebaruSan Posted February 17, 2020 Share Posted February 17, 2020 8 minutes ago, LittleBitMore said: I'm experiencing difficulties with CKAN. Every few mods it tosses me a 403 (Forbidden). This goes on random mods of my 1.4.5 install (it did MechJeb2 once, is doing KAS multiple times, has done the GPP Textures once). It makes installation long and painful for those things that need installing via a backup site, and for those that don't have a backup, it cancels the installation. I'm gonna install those things manually. I just wanted to let you know these mods were being difficult in 1.4.5 installs. Sounds like #2210. GitHub doesn't like it when you download many things in parallel. Usually you can just retry the same changes and it will work eventually. Link to comment Share on other sites More sharing options...
LittleBitMore Posted February 17, 2020 Share Posted February 17, 2020 (edited) 2 minutes ago, HebaruSan said: Sounds like #2210. GitHub doesn't like it when you download many things in parallel. Usually you can just retry the same changes and it will work eventually. I've looked over the bug page and the details on it. I'll try this with installing each of the troublesome mods individually. Thanks for the insight! Edit: KAS is still not installing, no matter how many times I spam retry. I'll instead install it manually. Edited February 17, 2020 by LittleBitMore Added "edit" Link to comment Share on other sites More sharing options...
zer0Kerbal Posted February 19, 2020 Share Posted February 19, 2020 just popping in to say nicely done on the DaMichel's mods. +1 more mods coming. Link to comment Share on other sites More sharing options...
Wuwuk Posted February 19, 2020 Share Posted February 19, 2020 Why in ckan does not have version 1.0.1 for KSP 1.7.x of the DE_IVA Extension - For All the Stock Pod IVAs! mod? There is only version 1.0.2. Link to comment Share on other sites More sharing options...
HebaruSan Posted February 20, 2020 Share Posted February 20, 2020 2 hours ago, Wuwuk said: Why in ckan does not have version 1.0.1 for KSP 1.7.x of the DE_IVA Extension - For All the Stock Pod IVAs! mod? There is only version 1.0.2. Just added it, try Refreshing in a couple of minutes. Note that you'll need to add KSP 1.6 as a compatible version manually because RPM v0.30.6 isn't supported on KSP 1.7 by its author. https://github.com/KSP-CKAN/CKAN/wiki/User-guide#choosing-compatible-game-versions Link to comment Share on other sites More sharing options...
EasyAce Posted February 20, 2020 Share Posted February 20, 2020 There has been some time since I used CKAN and I am unsure on how the versions and updates are working now. One place I red that the majority of mods will automatically be compatible to new versions of KSP, but experience tells me otherwise. How is it now. Should I just set the setting fpr compatible version in CKAN to 1.8.0 and go ahead download whaterver mods I prefer... or should I still wait for the metadata to be up to date? Link to comment Share on other sites More sharing options...
DasSkelett Posted February 20, 2020 Share Posted February 20, 2020 17 minutes ago, EasyAce said: One place I red that the majority of mods will automatically be compatible to new versions of KSP, but experience tells me otherwise. This differs from update to update. A lot of mods broke from KSP 1.7 to 1.8 because of a Unity update and thus the old DLLs didn't work anymore. KSP 1.8 to KSP 1.9 only broke a few visual mods, most others are working fine. 20 minutes ago, EasyAce said: Should I just set the setting fpr compatible version in CKAN to 1.8.0 and go ahead download whaterver mods I prefer... or should I still wait for the metadata to be up to date? I'd suggest to take a quick look at the last page of the forum thread for each mod you want to install that isn't shown as 1.9 compatible yet. You'll likely find either the author stating something about the compatibility, and/or others who tried it out. Additionally, if install the mods in small groups and start + test KSP in between, it'll be easier to catch possibly malfunctioning mods. Link to comment Share on other sites More sharing options...
miklkit Posted February 21, 2020 Share Posted February 21, 2020 I just tried to run CKAN to see if any mods had been updated and got an "unhandled exception" error stating "InvalidArgument=Value of "2" is not valid for "index"". It worked fine this morning when it installed Mechjeb2 into a clean new KSP v1.9 install. Since then I manually installed KAS/KIS which seems to not cause any issues. I deleted CKAN then DLed and installed it again with the same result. I'm guessing it is something on my end causing this. Any idea what it might be? Link to comment Share on other sites More sharing options...
Wuwuk Posted February 21, 2020 Share Posted February 21, 2020 (edited) On 2/20/2020 at 2:28 AM, HebaruSan said: Just added it, try Refreshing in a couple of minutes. Note that you'll need to add KSP 1.6 as a compatible version manually because RPM v0.30.6 isn't supported on KSP 1.7 by its author. https://github.com/KSP-CKAN/CKAN/wiki/User-guide#choosing-compatible-game-versions I understand ,thank you. Edited February 21, 2020 by Wuwuk Link to comment Share on other sites More sharing options...
zer0Kerbal Posted February 22, 2020 Share Posted February 22, 2020 @HebaruSan how would I put together a CKAN mod pack? for DaMichel's parts? thank you in advance! Link to comment Share on other sites More sharing options...
HebaruSan Posted February 22, 2020 Share Posted February 22, 2020 16 minutes ago, zer0Kerbal said: @HebaruSan how would I put together a CKAN mod pack? for DaMichel's parts? thank you in advance! There's a wiki for that: https://github.com/KSP-CKAN/CKAN/wiki/Sharing-a-modlist-(metapackages) Link to comment Share on other sites More sharing options...
Hoddd9000 Posted February 24, 2020 Share Posted February 24, 2020 Clean 1.9 install, trying to install mods from a ckan mod file. Worked previously with the exact same mods and game version. Getting this error: Spoiler Unhandled exception (etc.). InvalidArgument=Value of '2' is not valid for "index". Parameter name: index. ************** Exception Text ************** System.ArgumentOutOfRangeException: InvalidArgument=Value of '2' is not valid for 'index'. Parameter name: index at System.Windows.Forms.TabControl.GetTabPage(Int32 index) at System.Windows.Forms.TabControl.TabPageCollection.get_Item(Int32 index) at CKAN.ThemedTabControl.OnDrawItem(DrawItemEventArgs e) at System.Windows.Forms.TabControl.WmReflectDrawItem(Message& m) at System.Windows.Forms.TabControl.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) Link to comment Share on other sites More sharing options...
Cryptoxic Posted March 1, 2020 Share Posted March 1, 2020 Hi guys, I'm trying to build CKAN from source and when I open the solution in my Visual Studio, it just hangs on opening ckan-core. Any solutions? Link to comment Share on other sites More sharing options...
HebaruSan Posted March 2, 2020 Share Posted March 2, 2020 (edited) Supposedly, an astounding 1.3 billion people can read simplified Chinese. If that group includes you, you're invited to test a translation of CKAN generously submitted by GitHub user 050644zf! Say hello here to receive a test build: https://github.com/KSP-CKAN/CKAN/pull/3014#issuecomment-593601521 We're interested in anything that: Doesn't make sense Doesn't fit in the available space Could be phrased more clearly Is formatted poorly, etc. The active CKAN team members do not speak Chinese (as far as I know), so we can't evaluate this translation fairly, and we'd like additional sets of eyes to check it out. Thanks in advance! Edited March 2, 2020 by HebaruSan Link to comment Share on other sites More sharing options...
zer0Kerbal Posted March 13, 2020 Share Posted March 13, 2020 (edited) @HebaruSan just a quick heads up-ScrapYard OhScrap! just hit SpaceDock - and probably sent a CKAN submission. Would you kindly just update the existing one to point at the new one? I just adopted it from @severedsolo; along with ScrapYard. Thank you in advance! Edited March 13, 2020 by zer0Kerbal Link to comment Share on other sites More sharing options...
severedsolo Posted March 13, 2020 Share Posted March 13, 2020 36 minutes ago, zer0Kerbal said: @HebaruSan just a quick heads up-ScrapYard just hit SpaceDock - and probably sent a CKAN submission. Would you kindly just update the existing one to point at the new one? I just adopted it from @severedsolo; along with ScrapYard. Thank you in advance! You shouldn't need to worry about that, the nice thing about space Dock is that it allows you to just keep pushing releases with no changes to CKAN needed. Link to comment Share on other sites More sharing options...
zer0Kerbal Posted March 13, 2020 Share Posted March 13, 2020 32 minutes ago, severedsolo said: You shouldn't need to worry about that, the nice thing about space Dock is that it allows you to just keep pushing releases with no changes to CKAN needed. oops - meant OhScrap! Link to comment Share on other sites More sharing options...
VoidCosmos Posted March 24, 2020 Share Posted March 24, 2020 @HebaruSan could you please update the license of my mod Intake Air-Drain it! To GPLv3.0 ? It is currently having the MIT license Link to comment Share on other sites More sharing options...
HebaruSan Posted March 24, 2020 Share Posted March 24, 2020 7 hours ago, VoidCosmos said: @HebaruSan could you please update the license of my mod Intake Air-Drain it! To GPLv3.0 ? It is currently having the MIT license Done. Link to comment Share on other sites More sharing options...
VoidCosmos Posted March 24, 2020 Share Posted March 24, 2020 22 minutes ago, HebaruSan said: Done. Thanks a lot! Link to comment Share on other sites More sharing options...
HebaruSan Posted April 2, 2020 Share Posted April 2, 2020 https://www.githubstatus.com/ says that GitHub is having some problems right now, which will probably have a big impact on CKAN. Watch that page for the current status, consider waiting to use CKAN, and wish our friends on the GitHub server teams the best as they work on whatever it is. Link to comment Share on other sites More sharing options...
zer0Kerbal Posted April 7, 2020 Share Posted April 7, 2020 (edited) @HebaruSan - query: what can be improved on my end to help ease your efforts? how can improve readme? etc? Edited April 7, 2020 by zer0Kerbal Link to comment Share on other sites More sharing options...
Krzeszny Posted April 7, 2020 Share Posted April 7, 2020 (edited) CKAN lists Firespitter Core as a dependency for Lithobrake Exploration Technologies, while it's not a dependency - it couldn't be found in the configs and there is no information about the dependency in LET's thread. Also, the mod Fuel Tanks Plus is marked as 1.9.1 compatible in CKAN but it's not. Many users complain about its radial tanks causing major problems and the mod is officially marked as 1.4.1-compatible, not 1.9.1. I wanted to report metadata problems on GitHub by clicking on "report an issue with mod metadata" but the link leads to the same page as CKAN-related bug reports and there's nowhere I can report metadata problems there. Edited April 7, 2020 by Krzeszny 2nd&3rd paragraph Link to comment Share on other sites More sharing options...
Recommended Posts