A program for making KSP....almost 64 bit.(debunked)

[Tidus Klein]

HI guys so after reading the title your probably like...."wait what? SWEAT!" so hears how it goes,

I just got into this game called SPACE ENGINEERS and wanted to know if there was a way to reduce lag....so i browsed the inter webs and found this.

LINK

its a program to make 32 bit games large adress aware...COOL right? it's like fake 64 bit.

OO and before someones like (super stupid nerd voise) "but the devs said .24 would be 64 bit....) I know I thought i would just give you guys something to play with, HAVE FUN and do follow the instructions.

senceraly

TLK

NEVER MIND

Edited June 26, 2014 by Tidus Klein

[Padishar]

The 32bit version of KSP is already "large address aware" which is why it can use more than 2 GB of memory on Win64. Don't bother running any patch of this sort that simply sets "large address aware" as it will have absolutely no effect on KSP...

Also, it is *not* like fake 64 bit. It only allows the process to allocate up to approx. 3.5 GB where a real 64 bit program can allocate up to 7.5 terabytes (i.e. way more than any actual PC architecture can physically support).

Edited June 26, 2014 by Padishar

[NicoH]

I could be wrong, but isn't KSP already large address aware? AFAIK a program without this can only manage up to 2GiB of RAM, but KSP already uses up to 4GiB of RAM.

[Tidus Klein]

OOOO...... thanks for busting my bubble.....*POP*

devs lock it up

[Mr_Brain]

A way to make KSP 64-bit has already been discovered here.

[Padishar]

Also, this sort of patch program is a fairly common attack vector for various nasty malware (keylogger trojans, viruses etc). I would recommend you delete any KSP.exe you have patched using this and replace it with an original copy unless you are quite sure that the only thing it changed was this flag in the exe header (in fact, as the flag is already set on KSP.exe it should still be identical) and even then it wouldn't hurt to replace it...

Edit: though, to be fair, this particular one looks like it should be pretty safe...

Edited June 26, 2014 by Padishar

[Tidus Klein]

I have kaspersky on my laptop....It should be fine

[Spartan-S63]

The 32bit version of KSP is already "large address aware" which is why it can use more than 2 GB of memory on Win64. Don't bother running any patch of this sort that simply sets "large address aware" as it will have absolutely no effect on KSP...

Also, it is *not* like fake 64 bit. It only allows the process to allocate up to approx. 3.5 GB where a real 64 bit program can allocate up to 7.5 terabytes (i.e. way more than any actual PC architecture can physically support).

Yeah, anymore these days most applications are large address aware that are compiled for 32 bit. Also, the real theoretical maximum is 16 exabytes because 2^64 is the number of addressable bits. On Windows 7 Home Premium, it only supports 16 GB of RAM and the Professional, Enterprise, and Ultimate SKUs support 192 GB of memory. For Windows 8, the regular SKU supports 128 GB of memory and the Professional and Enterprise SKUs support 512 GB of memory.

[Tidus Klein]

Also, it is *not* like fake 64 bit. It only allows the process to allocate up to approx. 3.5 GB where a real 64 bit program can allocate up to 7.5 terabytes (i.e. way more than any actual PC architecture can physically support).

NOT the NSA computers.....

[Padishar]

Yeah, anymore these days most applications are large address aware that are compiled for 32 bit. Also, the real theoretical maximum is 16 exabytes because 2^64 is the number of addressable bits. On Windows 7 Home Premium, it only supports 16 GB of RAM and the Professional, Enterprise, and Ultimate SKUs support 192 GB of memory. For Windows 8, the regular SKU supports 128 GB of memory and the Professional and Enterprise SKUs support 512 GB of memory.

Yes the total 64 bit address space is 2^64 but this is not important. The important thing is how much of that address space windows allows the program to use for normal memory allocation and this is (IIRC) approx. 7.5 terrabytes. Just like on Win32, where the total address space is 2^32 (4 GB), Windows only lets the program use 2GB of it (or 3 with some tweaking).

Also, the amount of physical memory that is supported is not relevant. I can write a program for Win64 that allocates a terrabyte of memory and it will work on any machine that has enough disk space to allocate a terabyte in the virtual memory pagefile. I'm not saying it will be fast but it will work and is an easy way to work on very large data sets on limited hardware...

Edited June 26, 2014 by Padishar

[Fiddlestyx]

When I have to click on a link without any idea where it's going to take me, I don't click on that link. For future reference. Also, big and colorful link, I don't trust you.