64 bit questions

[falloutaddict]

Hi guys! I'm kinda new to the forum, but I've really been enjoying KSP and I had a question about 1.0. From my understanding, Squad will not be releasing a version of 1.0 for 64bit users. I looked at my system and it says I am using 64bit. So after they update I will not be able to play 1.0? Sorry for the seemingly silly question, I just wanted to clear that up... I searched through the forums and that seems to be the consensus, please tell me I'm wrong...

[SpaceTiger]

32bit applications are able to run under 64bit windows. Chances are you are already using the 32bit version of Kerbal .

[stibbons]

You have a 64 bit operating system. It's able to run both 32 bit and 64 bit applications. You won't have any problems when 1.0 comes out.

In fact, by default you're launching the 32 bit version of KSP now. It takes some effort to switch over.

[EladDv]

You have a 64 bit operating system. It's able to run both 32 bit and 64 bit applications. You won't have any problems when 1.0 comes out.

In fact, by default you're launching the 32 bit version of KSP now. It takes some effort to switch over.

not really when i had the 64bit the launcher would launch the 64bit version unless i went into the settings menu and pressed accept (the 64bit wasnt checked in the menu i am aware of that option)

[Guest]

You'll be fine.

[falloutaddict]

Thank you all for putting my mind at ease

[NFUN]

Thank you all for putting my mind at ease

Funnily enough, Fallout 3 not only runs on 32-bit, but is unstable even using multiple cores.

[jarmund]

32bit applications run fine on 64bit OSes through a simple abrstraction layer provided automatically by most (all, maybe? I haven't found an exception) OSes. No need to do anything differently. I ran 32bit KSP on 64bit Win7 just fine. I'm now running 32bit KSP on 64bit Linux just fine too.

The most noticeable difference right away is the limit to 32 bit addressing, especially with memory-hungry applications such as KSP: An application will not be able to use more than 4Gb of RAM. With 64bit this is not an issue anymore. If you run a lot of mods you might reach the limit, but hopefully that too will not be as much of an issue once 1.0 comes out due to a lot of bugs and memory-leaks being fixed (at least as indicated by the weekly devblog).

Edited April 12, 2015 by jarmund

[NFUN]

32bit applications run fine on 64bit OSes through a simple abrstraction layer provided automatically by most (all, maybe? I haven't found an exception) OSes. No need to do anything differently. I ran 32bit KSP on 64bit Win7 just fine. I'm now running 32bit KSP on 64bit Linux just fine too.

The most noticeable difference right away is the limit to 32 bit addressing, especially with memory-hungry applications such as KSP: An application will not be able to use more than 4Gb of RAM. With 64bit this is not an issue anymore. If you run a lot of mods you might reach the limit, but hopefully that too will not be as much of an issue once 1.0 comes out due to a lot of bugs and memory-leaks being fixed (at least as indicated by the weekly devblog).

I thought 64 bit worked fine on Linux.

[jarmund]

I thought 64 bit worked fine on Linux.

Possibly. It's just that when I first installed it, it was just supposed to be a quick and dirty test for my GFX driver, so I ended up with 32bit. But alas, temporary has a tendency of becoming permanent. I haven't had any reason to reinstall, as the 4Gb limit isn't an issue for me (I don't run that many part mods).

[Padrone]

I thought 64 bit worked fine on Linux.

It works for my Ubuntu installation. I find if I add one mod at a time it seems to soothe the memory kraken. I'm currently running about 130 mods, ATM included. (That's more for the speed of loading the game than anything else). It takes up about 10 gig of memory while running.

Once in a blue moon the game just abends and I'm staring at my desktop. Other than that, it's good. I'll take that tradeoff for the ability to mod it this heavily.

YMMV

[Ignath]

Possibly. It's just that when I first installed it, it was just supposed to be a quick and dirty test for my GFX driver, so I ended up with 32bit. But alas, temporary has a tendency of becoming permanent. I haven't had any reason to reinstall, as the 4Gb limit isn't an issue for me (I don't run that many part mods).

You should not need to re-install (unless they don't pack x86 and x64 distributions together in the KSP store, I'm a STEAM user), the x64 executable should be packed in the same directory as the x86 (32 bit).