Jump to content

CKAN (The Comprehensive Kerbal Archive Network) - v1.33.2 Laplace - KSP 2 support!


DasSkelett

Recommended Posts

9 hours ago, HebaruSan said:

What's interesting is that the version file says 1.10 or greater, which means the clearest expression we have of the author's intent says that it is still expected to work on 1.12:

  "KSP_VERSION_MIN": {
    "MAJOR": 1,
    "MINOR": 10,
    "PATCH": 0
  }

However, that version file wasn't actually included in the last two release ZIPs, so it got indexed without any compatibility info at all.

@EnzoMeertens, are you still here? If so, can you clarify whether this mod should be listed as compatible with KSP 1.12?
@linuxgurugamer, did you end up adopting this mod as per the last page of its forum thread?

No, he contacted me back and requested that I not adopt it.  It does work in 1.12, I use it in my games

Edited by linuxgurugamer
Link to comment
Share on other sites

The CKAN client v1.34.0 "Minkowski" is released!

This is a big one!

  • .NET Framework 4.8 is now required on Windows (and the build system multi-targets .NET 7 for a much more pleasant developer experience in VSCode), but Windows Update should have given you that ages ago
  • We can now track multiple download hosts per mod in case of downtime of specific hosts, and users can prioritize hosts according to their preferences:
    qSguMGN.png
    Note that additional hosts must be added by metadata wranglers, one mod at a time, so it will take a while to roll this out!
  • Repo metadata is independent of game instance, eliminating redundant downloads for users with multiple instances and shrinking registry.json
  • New Dutch translation and continued improvements to other translations
  • Many significant performance improvements
  • Carefully limited ability to delete certain specific game-generated files at uninstall
  • Usability improvements to the main toolbar, mod list, search dropdown, settings, directory deletion prompt, providing mod selection prompt, and various installation errors

... and much more; click the release link for the full changeset!

Link to comment
Share on other sites

(That's the last time you'll see a Windows 7 screenshot from me; I have finally upgraded my Windows partition to 10.)

Special thanks to (user names without "@" are from GitHub or CrowdIn):

  • @JonnyOThanfor finding and reporting several important bugs in the dev builds so they could be fixed before release, and for becoming the newest KSP1 metadata wrangler
  • irasponsible and erkinalp for some improvements to Linux packaging
  • Fierce-Cat, Nikita, Вячеслав Бучин, @vinix, WujekFoliarz, idrkwhattoput for helping with translation
    https://crowdin.com/project/ckan
  • Everyone else who made this release better by reporting a bug or requesting a feature!
Link to comment
Share on other sites

The CKAN client v1.34.2 "Minkowski²" is released!

This is a small one! Just a few critical hotfixes based on feedback in the past 2 days and one small enhancement for @JonnyOThan. Many thanks to everyone who reported issues with v1.34.0!

Full changelog available in the release notes:

Edited by HebaruSan
Link to comment
Share on other sites

With the latest version of CKAN I am not able to "Save Installed Mod List" to a .csv file.  I am running Windows 11 and have .Net 6.0 installed (tried to install .NET 4.5 manually but it won't let me since a higher version is already installed)

 

I get the following Unhandled Exception...

Object reference not set to an instance of an object.

 

Details below...

Spoiler

 

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at CKAN.Exporters.DelimeterSeparatedValueExporter.Export(IRegistryQuerier registry, Stream stream)
   at CKAN.GUI.Main.exportModListToolStripMenuItem_Click(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9181.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
ckan
    Assembly Version: 1.34.0.0
    Win32 Version: 1.34.2
    CodeBase: file:///C:/KSP/ckan.exe
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9200.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9206.0 built by: NET481REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Anonymously Hosted DynamicMethods Assembly
    Assembly Version: 0.0.0.0
    Win32 Version: 4.8.9181.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9191.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Net.Http
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Net.Http/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Net.Http.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9181.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Transactions
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Microsoft.CSharp
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll
----------------------------------------
System.Dynamic
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Dynamic/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Dynamic.dll
----------------------------------------
System.EnterpriseServices
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

Edited by orionguy
added system info
Link to comment
Share on other sites

Hi.

I use CKAN 1.34.2 and i have 2 ksp folders (version 1.12.5)

CKAN is installed in one of them and i want the second to be the default version.

The second is marked as default instance.

Even if i delete the first one (the one which CKAN is installed) in the "Instance game" (File menu), CKAN always load it.

 

 

Link to comment
Share on other sites

hi

 

i have this error in my debian launching ckan :


1590 [Thread Pool Worker] WARN CKAN.Games.KerbalSpaceProgram.GameVersionProviders.KspBuildMap (null) - Could not retrieve latest build map from: https://raw.githubusercontent.com/KSP-CKAN/CKAN-meta/master/builds.json
1590 [Thread Pool Worker] WARN CKAN.Games.KerbalSpaceProgram.GameVersionProviders.KspBuildMap (null) - Could not refresh the build map from remote server
1670 [Thread Pool Worker] INFO CKAN.NetAsyncDownloader (null) - Error downloading https://github.com/KSP-CKAN/CKAN-meta/archive/master.tar.gz: Error: TrustFailure (Authentication failed, see inner exception.)

 

ckan version : 1.34.2

KSP 1.12.5.3190

 

already tried to sync mono's certs

Link to comment
Share on other sites

yes i do have a linux OS (debian)

$ cat /etc/debian_version 
trixie/sid

Linux debian 6.5.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.13-1 (2023-11-29) x86_64 GNU/Linux

i applied the entire guide you posted, but it still doesn't work

isn't it possible to manually download the file (in fact i already did that) and place it in the correct folder to skip the sync at all?

Link to comment
Share on other sites

24 minutes ago, bladela said:

i applied the entire guide you posted, but it still doesn't work

You may have a problem we haven't seen before, then. If you figure it out, please consider updating that wiki with your discoveries in case other users encounter the same issue.

24 minutes ago, bladela said:

isn't it possible to manually download the file (in fact i already did that) and place it in the correct folder to skip the sync at all?

No, CKAN needs to parse it into an internal format to use it.

Link to comment
Share on other sites

The CKAN client v1.34.4 "Niven" is released!

Another small, mostly-bugfix release, including:

  • Eastern hemispheric users had issues installing very recently updated mods
  • "One or more errors occurred" during repo update
  • Multi-hosted mods weren't falling back to the next URL if the first one failed
  • Compatible versions popup was doing weird things to the max game version column
  • Audit recommendations wasn't opening
  • TSV/CSV export wasn't working
  • Indicator links under the mod list to help users figure out why some mods may be hidden from view
  • ... and a few more

Many thanks to everyone who reported issues with v1.34.2!

Full changelog available in the release notes:

Link to comment
Share on other sites

  • 2 weeks later...

I have reported a bug here on GitHub.

Steam is not accurately reporting playtime when the game is run through CKAN.

This bothers me because I want the devs to have accurate metrics - frankly, KSP2 needs the PR help. Also, I want my playtime reported.

 

Link to comment
Share on other sites

12 hours ago, kerballs said:

I have reported a bug here on GitHub.

Steam is not accurately reporting playtime when the game is run through CKAN.

This bothers me because I want the devs to have accurate metrics - frankly, KSP2 needs the PR help. Also, I want my playtime reported.

 

Is that really a CKAN issue? I wouldn't expect Steam to report playtime for *anything* that wasn't launched via Steam. If they *are* hooking into my system deeply enough to be able to detect things happening outside of the Steam environment, I wanna know that about that!  =:oo

Link to comment
Share on other sites

2 hours ago, pbristow said:

Is that really a CKAN issue? I wouldn't expect Steam to report playtime for *anything* that wasn't launched via Steam. If they *are* hooking into my system deeply enough to be able to detect things happening outside of the Steam environment, I wanna know that about that!  =:oo

You are completely right. This bug report was invalid, and should be ignored. As a quality-of-life issue I believe it warrants discussion.

The issue has been closed out on GitHub and HebaruSan has provided an explanation to me:

Quote

Right, this isn't a CKAN bug. Steam counts time when you launch through Steam.

To configure CKAN to launch through steam, you can set Settings → Game command line to:

steam://run/954850

[I can see why you'd think this would not be default behavior, but] . . . it would be incorrect behavior to make this the default.
CKAN supports multiple game instances in different folders, but the steam:// URL can only launch one instance, and there's no way for CKAN to know whether it's the right instance.

This bug report stemmed from my own long-running misunderstanding of how Steam handles games based solely on my experience with Fallout 3/NV/4 Script Extender and NMM/Vortex Mod Manager. These were the only mod managers I had used prior to adopting CKAN for KSP1.

When you launch Fallout 3/NV/4 from the vanilla install folder executable, from Fallout Script Extender, or from the mod manager which points to either executable, the game is immediately launched within Steam. I still do not fully understand how this is different from other games' functionality, or why KSP behaves differently.

All my games are on Steam and I want my playtime tracked. For me, launching the game independent of Steam is both unexpected and undesirable behavior. This behavior is not disclosed on initial CKAN deployment. Disappointingly, I only noticed it after failing to track hundreds of hours of time in KSP1 and about 50 hours in KSP2.

Other users may find this to be undesirable and unexpected behavior in the same way I did. Others like @pbristow may find this to be "zero-trust", user-centric and expected behavior. In either case I think more visible documentation of this behavior could be easily added to CKAN to prime unwary users such as myself.

Link to comment
Share on other sites

31 minutes ago, kerballs said:

In either case I think more visible documentation of this behavior could be easily added to CKAN to prime unwary users such as myself.

I guess since you're saying this in front of a wider audience now, I can ask everyone else:

Does anyone else actually feel this way?

My initial reaction to the idea of a pop-up announcing some implementation details about how some third-party software (Steam) works was that it was something most users would neither care about nor understand, and they'd be annoyed that this irrelevance was being put in their face. And that how Steam works is not really CKAN's business or problem.

Edited by HebaruSan
Link to comment
Share on other sites

Thank you for putting it to the community! When I broached the topic I was not expecting to open a dialogue, but now I'm curious.

My last addition to this specific conversation is to push back on an expectation that most users will default to a rigid, dismissive framing of Steam as "some third-party software"; etc. Certainly, the KSP playerbase overlaps with GNU enthusiasts who eschew for-profit distribution channels, but I expect the opposite.

CKAN itself is third-party software, no? As a licensed distributor, Steam was a de facto second-party/publisher when Squad was still self-publishing pre-2017: a significant, possibly even pivotal role in the game's arc of commercial success. And to the vast majority of PC gamers, Steam is hardly a fringe utility.

Consider that Steam DB aggregates 2015-forward KSP1 sales estimates of between 3.5 and 6.25 million copies. If 1 in 100 buyers still actively play the game with mods, that could be 35,000+ active Steam players leveraging CKAN as their package manager today, myself included. Presumably, many enjoy the Steam platform to some degree (myself included). I like the centralization of my library, social features, and the pleasant brain-tickle of  accurately counted playtime.

In summary,

1) much of the community uses Steam;

2) integration offers potentially desirable features;

3) other popular 3P mod managers default to integration;

4) thus, as CKAN is by and for the community, offering up-front transparency and an obvious path to optional integration would certainly seem to square with its mission of enabling an open management and compatibility framework atop the vanilla game.

I am new to these forums, though not to KSP. Before responding, I read some of pjf's initial 2014 CKAN release thread. It's evident that CKAN has been shaped by much discussion and occasionally passionate discourse. It's been a long time since I participated in a community software effort and it's enjoyable to dip my toes back in - I'm looking forward to being active during KSP2's development. Thanks for engaging with me on this point.

Edited by kerballs
Readability
Link to comment
Share on other sites

I purchased KSP2 via Steam.  Most of my game library is in Steam.  To tell you the truth I could care less about the play timer in Steam.  I have looked at it at times but not a big deal.  I also don't normally start KSP2 from CKAN.  I run CKAN to update and select mods.  But then I start KSP2 from a desktop shortcut (running Windows 11).  I don't think I would spend much if anytime on coding CKAN to integrate with Steam just to keep the Play Timer up to date.  I would think there are better things to spend time on.  Yep, just another opinion so that the coders and others are aware.   Your opinion may very and I can respect that.  Definitely not something worth argueing over.  My opinion is that this isn't an issue worth spending time on.  Granted, documenting that starting KSP via CKAN does not update the Play Timer is probably a good idea  and note that if that is a concern, just start KSP via Steam instead of starting it from CKAN.

Link to comment
Share on other sites

A first-time user intro window explaining that CKAN is able to manage multiple KSP installations, and recommending that users *not* use it directly with their live Steam-based installation (i.e. copy that to separate location first and use that copy for modding), might be a good idea. 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...