x64 not using any 64bit memory?

[BoomBoom]

So, i have been using ksp since .22 with no problems. (occasional CTD- as expected when heavily modding)

Since .24.2 i cant even run x86 (verified install, clean install etc.) and x64 crashes way too often due to memory errors (see attached log)

Yes i mod heavily, yes i am using ATM, in-game textures are lowered to quarter res.

win 8 task mgr showing only 3.3gb mem usage? yet still getting memory write errors (thought it was a mem issue so i ran all required tests for memory errors - none found)

Also KSP doesnt use any VRAM (available 3gb)

Specs:

Core: i7-4700HQ (2.4ghz @ 3.6ghz/4core+8thread)

RAM: 16gb 1600

GPU: GTX 770m x2 SLi --(ran in non-SLi and SLi mode no effect)

Error Log:

Unity Player [version: Unity 4.5.2f1_9abb1b59b47c]

KSP_x64.exe caused an Access Violation (0xc0000005)

in module KSP_x64.exe at 0033:03630000.

Error occurred at 2014-09-09_173804.

F:\SteamLibrary\SteamApps\common\Kerbal Space Program\KSP_x64.exe, run by Blade.

30% memory in use.

16302 MB physical memory [11365 MB free].

24494 MB paging file [18010 MB free].

134217728 MB user address space [134215208 MB free].

Write to location 03630000 caused an access violation.

Context:

RDI: 0x164c9d32 RSI: 0x518ed3a0 RAX: 0x518ed360

RBX: 0x31c54910 RCX: 0x518ed360 RDX: 0x518ed3a0

RIP: 0x03630000 RBP: 0x14eff0d0 SegCs: 0x00000033

EFlags: 0x00010202 RSP: 0x14eff010 SegSs: 0x0000002b

R8: 0x00000800 R9: 0x00000000 R10: 0x8af4bf60

R11: 0x89740a7c R12: 0x592c3ee0 R13: 0x034c4d48

R14: 0x00000003 R15: 0x4f35b300

Bytes at CS:EIP:

?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? Module 1

C:\Windows\SYSTEM32\xinput1_3.dll

Image Base: 0x00400000 Image Size: 0x0001e000

File Size: 107368 File Time: 2007-04-04_185422

Version:

Company: Microsoft Corporation

Product: Microsoft® DirectX for Windows®

FileDesc: Microsoft Common Controller API

FileVer: 9.18.944.0

ProdVer: 9.18.944.0

== [end of error.log] ==

[vexx32]

This is a known issue, aye. From what I recall, it's an issue in Unity's own coding, something to do with the pointers it uses as memory references not working well (if at all) above ~3.5GB or so of RAM usage. Not a great deal that Squad can do except attempt to avoid running into the trouble until Unity fixes the problem.

[Azazael]

Snap exactly the same for me.

So we all switch to 64bit to allow us to have a few decent MODS and not run out of memory and now its totally nerfed ?

Unity Player [version: Unity 4.5.2f1_9abb1b59b47c]

KSP_x64.exe caused an Access Violation (0xc0000005)

in module KSP_x64.exe at 0033:03d00000.

Error occurred at 2014-09-10_173300.

F:\Games\SteamApps\Common\Kerbal Space Program\KSP_x64.exe, run by ray_000.

17% memory in use.

32713 MB physical memory [27052 MB free].

37577 MB paging file [31185 MB free].

134217728 MB user address space [134213947 MB free].

Write to location 03d00000 caused an access violation.

Context:

RDI: 0x00000024 RSI: 0xc4954bd0 RAX: 0xe3776fc0

RBX: 0xd18751a0 RCX: 0xe3776fc0 RDX: 0x4f28d400

RIP: 0x03d00000 RBP: 0x0092efb0 SegCs: 0x00000033

EFlags: 0x00010282 RSP: 0x0092ef00 SegSs: 0x0000002b

R8: 0xc4e9dd48 R9: 0x0000000b R10: 0x00000000

R11: 0xade91662 R12: 0x0092f580 R13: 0x03c04d48

R14: 0x0092f4b8 R15: 0x00000000

Bytes at CS:EIP:

?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? Module 1

C:\WINDOWS\SYSTEM32\xinput1_3.dll

Image Base: 0x00400000 Image Size: 0x0001e000

File Size: 107368 File Time: 2007-04-04_195422

Version:

Company: Microsoft Corporation

Product: Microsoft® DirectX for Windows®

FileDesc: Microsoft Common Controller API

FileVer: 9.18.944.0

ProdVer: 9.18.944.0

[LoganMalone]

This is a known issue, aye. From what I recall, it's an issue in Unity's own coding, something to do with the pointers it uses as memory references not working well (if at all) above ~3.5GB or so of RAM usage. Not a great deal that Squad can do except attempt to avoid running into the trouble until Unity fixes the problem.

Has there been even a single KSP Dev post about this issue communicated from the KSP Devs to the Unity Devs? Any forward traction to get conversation about it which could cause potential actions towards a resolution even in the near or distant future be it one, two, or three years+ ?? I'm getting weary of hearing about what the problem is and not hearing enough about actions towards a fix.

[NathanKell]

Since other Unity-based games on Windows x64 don't seem to experience issues with exception handling, if it is an issue with Unity it's one Squad can work around. And no, no Squad dev has commented on the Windows x64 issues (at least as far as I am aware).

[MartGonzo]

I never believed that 'Unity issue' thing.

I was running the x64 hack for 23.5 for over a month with no issues at all, whereas the new 64bit executable runs like crap compared to x86 and crashes all the time.

[sarbian]

Maybe if you deny it a bit more the crash will just go away ?

[IPsoFreely]

Well I don't have a memory issue like you guys as I've had ksp running 8.2gb of memory (that is only about 9% used) 96gb in machine with 6gb vram. My issue that could well be related to memory is that right clicking frustrating issue. It just took a spam off right clicks just to extend a panel. Although when i go back to space center i get a nice ksp.exe has stopped working crash.

I currently am running about 54 mods and plugins.

Unity Player [version: Unity 4.5.2f1_9abb1b59b47c]

Unknown caused an Access Violation (0xc0000005)

in module Unknown at 0033:03850000.

Error occurred at 2014-09-12_155446.

C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP_x64.exe, run by Owner.

9% memory in use.

96330 MB physical memory [89294 MB free].

82658 MB paging file [75073 MB free].

968388608 MB user address space [968383846 MB free].

Write to location 03850000 caused an access violation.

Context:

RDI: 0x0a700c38 RSI: 0x460e4500 RAX: 0xc2c80000

RBX: 0x60d4a520 RCX: 0x460e4500 RDX: 0x001bed90

RIP: 0x03850000 RBP: 0x001bf130 SegCs: 0x00000033

EFlags: 0x00010206 RSP: 0x001bf020 SegSs: 0x0000002b

R8: 0x001bed80 R9: 0x001bee50 R10: 0x001bed80

R11: 0xb55e042c R12: 0x001bf520 R13: 0x03644d48

R14: 0x00000000 R15: 0x00000000

So Unity can hold high amounts of memory but it seems only up to a certain point.

Edited September 12, 2014 by IPsoFreely

[Thanny]

The instability of the 64-bit Windows version has nothing to do with how much memory is in use. All of the crashes I've experienced were during the loading process (i.e. if you would normally see the loading graphic on the bottom right, it's a candidate crash situation). They were all random in nature, as well. Repeating the behavior as precisely as is possible (i.e. same steps from program launch) did not reproduce the crash. For example, loading the game, going straight to VAB, and loading a ship. Crashes on one attempt, doesn't crash on another.

[NathanKell]

You...understand that KSP loads all assets at the start, right? And garbage collection doesn't run until later. So during loading, your memory usage is actually maxed.

[Joshwoo70]

It is true.

My computer was like a loud whirring sound but after loading the assets the sound lowers.

If you have unity experience problems, use 32 bit executable.

It helps.

Edited September 13, 2014 by Joshwoo69
have

[Thanny]

Memory usage goes up after initial load, obviously. The game doesn't load any saves until you choose to, and those game states take up memory. The more flights you have, the more memory you need.

[LoganMalone]

Memory usage goes up after initial load, obviously. The game doesn't load any saves until you choose to, and those game states take up memory. The more flights you have, the more memory you need.

Do 'flights' include the space debris & junk from real flights of probes, stations, etc? If this is the case, then I'd recommend limiting the space junk quantity in the menu settings.

[Kaezan]

space junk is considered a 'flight' yes. it exists, it is there, it is moving, so it must be computed.

[Alshain]

The amount of RAM used by an on rails craft is miniscule. It saves a few numbers and computes their next position, it's kilobytes at best. Nothing close game assets. Killing all your debris is not going to save you much.