LC_ALL=C ./KSP.x86_64

[Daveroski]

I'm using linux and playing the game from steam.

My questions are;

Should I be using the above command line?

What does it fix?

I not currently using it and the game loads and seems to run as ok as KSP usually runs.

[StainX]

this line had fixed some language and node related (in editor) bugs for me.

if everything working without it... why use it?

[sal_vager]

If it works without, you don't need it, but it seems to fix a lot more than just nodes.

You'll need it if you use a non-English language on your operating system and use KSP.x86_64, English languages and KSP.x86 are unaffected.

To use it in Steam, edit the run options, add "LC_ALL=C %command%_64"

[Daveroski]

If it works without, you don't need it, but it seems to fix a lot more than just nodes.

You'll need it if you use a non-English language on your operating system and use KSP.x86_64, English languages and KSP.x86 are unaffected.

To use it in Steam, edit the run options, add "LC_ALL=C %command%_64"

I seem to be able to just run x86_64 directly. Of course it means my play-time doesn't get recorded this way. Are there advantages / disadvantages to playing through steam?

Could I run it through steam using just the %command%_64 part of the command? (I'm reluctant to experiment)

What exactly does the LC_ALL=C part of the command do?

[dewin]

LC_ALL is an environment variable that sets the locale used by various shared libraries -- it might, for instance, determine how certain standard libraries format dates and numbers with decimal points.

The "C" locale has a set of consistent rules that might avoid breaking other things (e.g. locale-aware code might output a decimal number, which non-locale-aware elsewhere might read and expects "one and four tenths" to always be "1.4" and not the "1,4" used in some countries.)

The only thing you get running KSP through Steam is the playtime calculations, iirc. (You might still get those running KSP directly, now that I think about it -- I still get some Steam notifications). Since I have ~5 KSP install directories on my Linux box, running the install I want through Steam is more a hassle than its worth. (I just let CKAN launch KSP)

[Daveroski]

LC_ALL is an environment variable that sets the locale used by various shared libraries -- it might, for instance, determine how certain standard libraries format dates and numbers with decimal points.

The "C" locale has a set of consistent rules that might avoid breaking other things (e.g. locale-aware code might output a decimal number, which non-locale-aware elsewhere might read and expects "one and four tenths" to always be "1.4" and not the "1,4" used in some countries.)

The only thing you get running KSP through Steam is the playtime calculations, iirc. (You might still get those running KSP directly, now that I think about it -- I still get some Steam notifications). Since I have ~5 KSP install directories on my Linux box, running the install I want through Steam is more a hassle than its worth. (I just let CKAN launch KSP)

Interesting.

I just started my game through steam. I then checked my system monitor. It seems that Steam has run the x86_64 version of KSP without input from myself. I am surprised as when I was using Macrosloth Wingers it defaulted to the 32 bit version. Do you know why it would do this?

Tell me of this CKAN.. give me your wisdom.

[sal_vager]

Yeah something like that, LC is the Unix setlocale command, ALL is for text, numbers, everything, and C is the code for Posix, EN is the code for English for example.

LC_LANG=FR would tell Linux (and OSX) to start a program using the French language.

More info here.

[dewin]

Tell me of this CKAN.. give me your wisdom.

CKAN is an open-source KSP addon manager .. you use Linux, so think of CKAN like apt-get for KSP mods. It runs under Mono, so has the same cross-platform capabilities that KSP itself has.

See https://github.com/KSP-CKAN/CKAN

[Daveroski]

CKAN is an open-source KSP addon manager .. you use Linux, so think of CKAN like apt-get for KSP mods. It runs under Mono, so has the same cross-platform capabilities that KSP itself has.

See https://github.com/KSP-CKAN/CKAN

To install CKAN I first have to install libcurl4-openssl-dev

Software Manager warns me that "The following packages would be removed: libtasn1-6, libtasn1-6:i386"

Is there a danger that something in my disro (Mint) requires these packages?

[Daveroski]

I tried CKAN but it can't see my KSP installation directory.

After reading some user reports, it seems that CKAN is broken in a couple of ways.

Perhaps when it has been fixed I'll give it a go.