Jump to content

Errentos

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by Errentos

  1. On 4/26/2016 at 8:07 PM, Padishar said:

    It isn't really a good idea to rename the exe in the way you describe.  In fact, I'm a little surprised it would actually work without you also replacing the KSP_Data folder with the KSP_x64_Data folder too (I thought there were some native DLLs in there that wouldn't load into the wrong version and that the player generates the name of the data folder to use directly from the exe name).  You would be better off just running the KSP_x64.exe directly from explorer or creating a shortcut to it.

    Have you tried restarting your steam client or manually telling it to check for updates?

    Yeah I had to do that too.

     

    It was only a temporary fix and I have since found why steam wouldn't run the game in x64.

     

    Obiviously I changed the KSP.exe and KSP_Data folders to read KSP_32.exe ect. so that I wouldn't overwrite them.

  2. I was having major problems with this when reverting to VAB and occasionally when deselecting parts in VAB construction. I have resolved this issue. I realised that this is the same issue I was having pre 1.1 because VAB can cause a jump in memory usage taking the game over the x32 memory cap.

    I took a look at my task manager and found that the process was KSP.exe *32 so for some reason my game was still running the x32 application rather than the x64. To resolve this I went to the game files and renamed KSP_64.exe to KSP.exe. 

    This appears to be an issue stemming from my steam not giving me the option to launch in x64.

     

    Hope this helps others.

×
×
  • Create New...