Search the Community
Showing results for tags '64-bit'.
Found 6 results
-
So, I just decided to try out 64 bit KSP to see if I could get any better FPS with my large (or rather, small but high part count) base on Minmus. I found there was rather little difference in FPS anyway, with an increase of maybe about 3 fps, still below 30. Does 64 bit support CPU multi threading? What effects does 64 bit actually have on the game? From the little bit of reading I have found, it appears that it only effects ships, with each ship getting its own thread. Anyone actually use 64 bit? (I hope this is the right section for this, the Gameplay Questions area didn't seem right but idk)
-
Yesterday I wanted to launch KSP but nothing happened. Because there was no output, I tryed it from the terminal and got this output: Importing game controller configs Abgebrochen (Speicherabzug geschrieben)Set current directory to /home/tobias/.local/share/Steam/steamapps/common/Kerbal Space Program Found path: /home/tobias/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP.x86_64 Mono path[0] = '/home/tobias/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed' Mono path[1] = '/home/tobias/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono' Mono config path = '/home/tobias/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.5 client has 4 screens displaymanager screen (0)(DVI-D-0): 1600 x 1200 displaymanager screen (1)(DVI-I-0): 1280 x 1024 Using libudev for joystick management Importing game controller configs Aborted (core dumped) Please help. PS: My OS is Kubuntu 16.04 LTS 64-bit
-
After many months of not playing KSP I'm about to pick it up again. To my surprise I see I have the option of choosing between 32-bit and 64-bit. What should I choose to get the best experience possible? I play on a modern pc with 64-bit Windows 10. I thought I heared that 64-bit is advantageous when using mods, but I use no mods whatsoever. -
It's hard for me to reproduce; I thought it might have been something to do with adding parts then removing them, but if I fiddle with a vessel in the VAB for a while, it pretty reliably crashes. There's a copy of what it spat out on the console and Player.log here. This line spits out on the console before a back trace and memory dump: *** Error in `./KSP.x86_64': double free or corruption (out): 0x00007f3a1fb414d0 *** So it's probably a double free. I'm running KSP.x86_64 on Debian: 4.4.0-1-amd64 #1 SMP Debian 4.4.6-1 (2016-03-17) x86_64 GNU/Linux -
Hello, I searched for quite a while, and could not find an answer to my question. I just did a fresh install of the game on, but when I try to run ksp64 or the launcher I am taken to a black scene with "loading..." At the bottom where it stays frozen forever. -
We are all very excited for the 64-bit upgrade included in KSP v1.1! But will it last? What will happen if the 32-bit edition is seen as more stable or as less buggy? If users and modders make the mass exodus back to 32-bit, I worry that 64-bit will not get the attention it needs. Modders may drop support 64-bit. Squad may mark 64-bit as "experimental" or "unstable". The universe as we know it may collapse into a singularity. Or I might be worrying too much and none of these things will be an issue. What do you think? Either way, think about taking the 64-bit pledge: Pledge to stay on 64-bit KSP v1.1: Pledge to hang on during the rough times. Pledge to report the bugs and provide useful information to help Squad iron out the issues. Pledge to support 64-bit in your mods. Or don't take the pledge, that's up to you
