steve_v

Depends on how you bought it. Squad store: Login, navigate to account, download. Steam: Who cares, steam is the devil. You still haven't posted any of the information detailed in the "How to get support" thread... You do want help, right?

Because I don't have time, and I don't like reinventing the wheel. That said, I have made some progress on this, just not enough that it is usable. Time is scarce, and porting .NET applications to C++/QT is time consuming. There's also the "good enough" effect.

Because it is an EULA. Uh huh. Ip addresses were supposed to be public, from day-one of the internet. And GeoIP is nothing new, thousands of websites know your location. It's nothing of the sort, I suggest you recheck your definitions. I was referring to those spreading unsubstantiated FUD, which was the topic of the post I replied to. People are both stupid and gullible, if they continue to believe that an application is doing something which repeatable evidence shows it is not, without testing such claims themselves. If they then spread misinformation, they are also amazing persons as horrific as this profanity filter. Trace the syscalls, cap the packets. Then you can make the case that KSP collects unreasonable user data and/or scrapes your filesystem. I have, it doesn't. But don't believe me, check it yourself. Oh, I see. Those nefarious Hackers. Do you even hack bro? Clearly, you have no idea what you're talking about. Riiight. Calm down, it's just boilerplate. Probably the same EULA they use for all their games. Oh dear, looks like they're out of stock. If you give me your postal address, I have spares. Your choice is a simple one. Agree to the silly license, or stop playing KSP. There is no legal "alternate means". They don't. It's in there to allow them to store it on their servers if you provide it to make a purchase. Boilerplate. TT are only going to get information that a) you give them by entering it into a form, willingly, or b) a product sends home, which one can trivially block. What's the big deal? ------ Oh, really?: Sure looks like that to me.

This is very, very cool. Slightly impractical, but cool. Shame KSPs terrain lacks the detail to use it on.

Granted, though most things worth doing are "work". If CKAN wasn't written with a framework I despise, in a language I have no use for, I'd do it myself.

Unity upgrade. I've pretty much lost interest in anything that doesn't contribute to "make the game not run like a three-legged gut-shot pig, even on cutting-edge hardware". That said, from my brief test run of 1.4, performance improvement is minimal. We had EVA parachutes, texture switching, and historical parts already, with perfectly serviceable mods.

Better yet would be a general "don't block the UI". Pretty much everything CKAN does can be done asynchronously, there's no reason to block the UI while resolving dependencies, downloading files, or even installing mods. The UI freezing for several seconds when selecting a mod that has dependencies is particularly irritating, I've asked about this before.

Well, if the lies are as outrageously idiotic as some mentioned here, no. I'd leave it to people to use their brains.

Depends. Depends on whether SQUAD/TT ever fixes their game engine, or choice thereof. Specifically the GC freezes. I'd pay considerably more than the going price for the DLC for this. Official multiplayer might tempt me too, but the content as currently advertised is decidedly "meh".

Indeed. And in my case I have proven to my satisfaction that it is not. 'tis not particularly difficult to find out what files an application is accessing.

Nah, unless sandboxed KSP can read all the files readable by the user executing it, so a simple text search of everything in $HOME / %USERPROFILE% would suffice. The problem is that no sane developer stores sensitive information in unencrypted files, so unless you keep your CC deets and SS# in a text file on your desktop...

How exactly would they do that? ROFL, they can try... Repo man knocking on the door? Asking the NSA for a windows backdoor so they can remote delete it? I think not. EULAs like this are works of fiction. These "people" clearly do not know how to capture such activity, or they would see that there is none. Over here we call this FUD. Just for lols, (and it's slow) I just started KSP under strace. It shows nothing of the sort. Expected accesses to system libraries, that's it. Perhaps this is a problem specific to the Windows build... In which case you have bigger things to worry about - Windows 10 is spyware. People are stupid. And gullible. Incidentally, if you do want to block the analytics for some reason: echo -e '127.0.0.1 cdp.cloud.unity3d.com\n127.0.0.1 api.redshell.io' >> /etc/hosts' Or just block all outgoing traffic from the KSP executable in your firewall. Iptables has --cmd-owner, dunno about windows.

Yet another reason for the much-asked-for ability to force a version from the GUI. Yes, the metadata should be fixed, but this does not mean one should have to poke about in the registry for version strings and use the command-line to fix ones install in the interim. General users do not have the access rights to update netkans metadata. This kind of thing happens every KSP update, why do we still not have an easy way to downgrade a mod? How about a "lock version" option too? Every package manager I know of has both.

Looks appropriate to me.

Agreed, up to a point. Changes that are disruptive to mods should be limited to worthwhile releases, like fixing the shoddy game engine or a significant collection of new content. My gripe is not that there are new releases, it's that every new release is followed by 2 or 3 "hotfixes" for obvious new bugs, which often break mods all over again. And releasing new content that is a blatant rip-off of a good mod is a waste of time (commnet, eva parachutes). Thus I am not installing 1.4.x any time soon.

This is what firewalls are for, calm down and block it if it concerns you.

Here we go again... CKAN is pushing this version to 1.3.1 installs, where it is bung. Metadata needs updating.

How do you keep your CPU warm, if you don't compile everything that moves? Well then, I guess you're saying "Mono is broken". I see exactly the same if I compile mono 5.4.1.6 (just to poke at another version) by hand, straight from mono-project.com. This is upstream mono, no patches, no ricer cflags, no strange configure options. I see Debian applies some 49MB(!) of patches to their mono package... What are these "dependencies" that CKAN requires? The closest I see to a list is "mono-complete ca-certificates-mono libcurl4-openssl-dev", none of which applies to anything but Ubuntu. Is there something I need that's not in http://download.mono-project.com/sources/mono/mono-5.4.1.6.tar.bz2?

Install Gentoo GNU/Linux, amd64 v17 multilib profile. Install updated mono 5.8.0.22 from "dotnet" portage overlay (5.x req'd for tls1.2, or so it seems). Start CKAN GUI and do something that opens a filepicker, such as "Install from .ckan...". I didn't know that existed, it's much better Then again, if it's the outcome of the "shall we use GTK or QT" discussion... Still an improvement I guess. That there is one single application, of the many I have installed, 100% not following system font settings. FWIW, it doesn't even follow system font size either.

Latest CKAN on Gentoo stable, Mono 5.8.0.22. All filepicker windows crash with: Unhandled exception: System.ArgumentOutOfRangeException: Not a valid Win32 FileTime. Parameter name: fileTime at System.DateTime.FromFileTimeUtc (System.Int64 fileTime) [0x00020] in <603673beab70479cb1a2aed0074edce0>:0 at System.IO.FileSystemInfo.get_LastAccessTimeUtc () [0x00028] in <603673beab70479cb1a2aed0074edce0>:0 at System.IO.FileSystemInfo.get_LastAccessTime () [0x00000] in <603673beab70479cb1a2aed0074edce0>:0 at (wrapper remoting-invoke-with-check) System.IO.FileSystemInfo.get_LastAccessTime() at System.Windows.Forms.FileSystem.GetDirectoryFSEntry (System.IO.DirectoryInfo dirinfo, System.Windows.Forms.FSEntry topFolderFSEntry) [0x00047] in <b2178b49d04c4b05a1693a7f35e9ec31>:0 at System.Windows.Forms.FileSystem.GetNormalFolderContent (System.String from_folder, System.Collections.Specialized.StringCollection filters, System.Collections.ArrayList& directories_out, System.Collections.ArrayList& files_out) [0x00023] in <b2178b49d04c4b05a1693a7f35e9ec31>:0 at System.Windows.Forms.FileSystem.GetFolderContent (System.Collections.Specialized.StringCollection filters, System.Collections.ArrayList& directories_out, System.Collections.ArrayList& files_out) [0x00155] in <b2178b49d04c4b05a1693a7f35e9ec31>:0 at System.Windows.Forms.MWFVFS+WorkerThread.GetFolderContentThread () [0x00000] in <b2178b49d04c4b05a1693a7f35e9ec31>:0 at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <603673beab70479cb1a2aed0074edce0>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <603673beab70479cb1a2aed0074edce0>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <603673beab70479cb1a2aed0074edce0>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <603673beab70479cb1a2aed0074edce0>:0 at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <603673beab70479cb1a2aed0074edce0>:0 If it matters, the filesystem in question is ext4, mounted with noatime. What's this "Win32 FileTime" rubbish anyway? No Windows here, nor 32 bit. Shouldn't that be "Unix timestamp"? While I'm here, any progress with the previously-discussed not-incredibly-fugly-on-*nix UI? Any way to get CKAN to use system fonts like everything else, instead of the butt-ugly serif (looks like times to me) it's displaying now? Shall I just assume no, because mono and winforms? Did I mention I hate winforms?

This is what backups are for, with any drive configuration. It's statistically more likely that you'll need to restore one with RAID0, that's all. No hassle if one already has a good backup strategy.

As nobody else has (as far as I can see), I'll bring this in here: The OKEB 75 deployable solar panel (solarpanel-blanket-4) from Near Future Solar is causing serious voxelisation issues, i.e the entire screen filled with 'em, when attached to a craft (retracted or extended). @Nertea seems to think this is one is for @ferram4. I don't see any errors relating to FAR or the offending part in my log. If it's needed anyway, let me know and I'll do it in a clean install to cut down the filesize. Any idea what I can do about this? It's a showstopper for up a truly awesome craft design...

That, plus a mono upgrade, plus a cert-sync: fixed it.

@HebaruSanIs the build you posted to the github issue (ckan-tls12.zip) the current solution? Not working here:

Yes, as is WinForms in general.