Would these large memory patches work on 32bit KSP?

[Galane]

This is an application that assists in making applications large address aware. When a 32-bit application is large address aware, it can access up to 4 GiB on x64 operating systems and all memory that isn't used by the operating system and other applications on x86. 64-bit versions of Windows require no modifications to the operating system to benefit from this application; however, in 32-bit versions of Windows, you must increase the user memory setting. Instructions how to do this are in spoiler below. It is not advised to use this application if you have less than 3 GiB of RAM.

This application may not work on older executables (predating 2000).

http://www.techpowerup.com/forums/threads/large-address-aware.112556/

I originally wrote this tool for a friend of mine who needed it. This very little tool patches x86 executables in order to let them have 4GB (instead of only 2) of virtual memory on x64 platforms. This tool comes very handy for applications which need a great amount of virtual memory like games, 3D renderization, multimedia etc. To gain these 2GB, you just have to use this tool to patch the executable (*.exe file) of the software you want to have these additional GBs of virtual memory. It can be used by clicking on it and choosing the file or through command line (e.g.: "4gb_patch file.exe"). It automatically creates a backup copy of the original executable.

Why things are this way on x64 is easy to explain. On x86 applications have 2GB of virtual memory out of 4GB (the other 2GB are reserved for the system). On x64 these two other GB can now be accessed by 32bit applications. In order to achieve this, a flag has to be set in the file's internal format. This is, of course, very easy for insiders who do it every day with the CFF Explorer. This tool was written because not everybody is an insider, and most probably a lot of people don't even know that this can be achieved. Even I wouldn't have written this tool if someone didn't explicitly ask me to.

http://www.ntcore.com/4gb_patch.php

[Harry Rhodan]

No. KSP can already access 4GB.

[Xyphos]

KSP can already access 4gb, as it is run by a High-Level Managed programming language which handles the memory allocation and garbage collection.

the problem with KSP is the 4gb boundary itself. in order to break the 4gb limit, KSP needs to become natively 64bit.

I'm not sure as to why KSP isn't natively 64 bits, but I suspect it's because of Unity, which raises another question as to why Unity isn't 64bit

[Umlüx]

I'm not sure as to why KSP isn't natively 64 bits, but I suspect it's because on Unity...

KSP uses Unity4 and the Windows x64 Unity build is and always was a disaster. thank god, squad is already working on porting it to Unity5, which should run definitely better (or so we hope at last)

[eddiew]

I'm not sure as to why KSP isn't natively 64 bits, but I suspect it's because on Unity...

Unity 4, primarily; seems to have issues with 64 bit that are hard to pinpoint and reproduce. Reached the point where modders started disabling their mods in x64 so's to stop getting reports about problems that weren't their fault.

Unity 5 on the other hand... there will be no excuse, and I deeply hope that all the dev work so far has been done in 64 bit. My game yearns for more visual fancies AND parts packs

[Brofessional]

Unity is 64-bit. There's some incompatibility with Windows 64-bit Unity and KSP that they haven't been able to solve.

Linux 64-bit KSP works fine, but the game runs significantly worse on OpenGL.

It's imperative that they get Win x64 working in Unity 5. By this point even the stock game is getting close to the memory limit, and it's still missing a lot of features.

Edited July 28, 2015 by Brofessional

[steve_v]

Yup, all of the above^.

Here's hoping they also do something about the lack-luster OpenGL performance and lack of x64 on OSX.

Not that I'm crazy enough to own a Mac , but everyone deserves a fair go - it's not all about Windows.

[Broax]

I just upgraded my PC and decided to give the x64 hack a go and, to be honest, I couldn't be more pleased. Aside from some minor bugs (the buildings sometimes switch between tiers) the game runs at a stable framerate with all settings maxed out (1440x900 which is the native res of my screen) using a couple of visual enhancement mods and while using over 5GB of memory.

If I were you I'd give Win64 a try. Some people report a lot of instability but others say it runs smoothly so I guess it depends on luck.

[steve_v]

Some people report a lot of instability but others say it runs smoothly so I guess it depends on luck.

Such is the crux of the problem, it's still too unpredictable for an official release. It appears the force is with you.

[luizopiloto]

virtual memory... not RAM... virtual memory reads and writes from HDD cache... ¬¬"

[Red Iron Crown]

virtual memory... not RAM... virtual memory reads and writes from HDD cache... ¬¬"

Not in this case. "Virtual memory" is Windows-speak for "virtual address space", which is the private addressing each process receives; the OS's memory manager maps these to physical RAM locations or disk-backed pages. The memory locations the process can access may be backed by RAM or disk, depending on what the OS memory manager is doing. Confusingly though, Windows also calls the pagefile management screen "virtual memory", which is likely what you are thinking of.