Possible to use NTCore 4 GB patch???

[Bandy]

Posted this elsewhere, more newb questions.

Does the CoD exe exist on our hard drives or the Steam 'cloud'? If so, one could patch the game's 32 bit exe to use up to 4 GB (leaving overflow for the system) if you run a 64 bit OS with lots of RAM.

I've patch all my 32 bit exe's this way with NTCore's patch:http://www.ntcore.com/4gb_patch.php

Of course, it would be nice if the developers simply already have the exe patched for x64 OS, as Rise of Flight is patched this way and there are no online issues.

Please let me know.

[Heliocon]

Posted this elsewhere, more newb questions.

Does the CoD exe exist on our hard drives or the Steam 'cloud'? If so, one could patch the game's 32 bit exe to use up to 4 GB (leaving overflow for the system) if you run a 64 bit OS with lots of RAM.

I've patch all my 32 bit exe's this way with NTCore's patch:http://www.ntcore.com/4gb_patch.php

Of course, it would be nice if the developers simply already have the exe patched for x64 OS, as Rise of Flight is patched this way and there are no online issues.

Please let me know.

If the game is a 32bit exe it can use up to 4gb of ram as long as it has LAA (large address aware) capability. Cant C/D if the current exe does, although I would tend to say no as it keeps making my win 7 switch to classic from aero and I have 12gb of ram...

[Bandy]

Well, I experimented and patched the Launcher.exe with NTCore's 4 GB patch. This has worked on all my other 32 bit apps running on Win7 x64.

Just looking at 'Resource Monitor' and 'Task Manager', and I see no difference in system utilization between patched and unpatched Launcher.exe (same mission 'Manston airfield attack', reboot between tests, playing 'Offline' such as that is...).

Essentially the same:
Unpatched Launcher.exe committed 1,392,112 kB RAM
Patched Launcher.exe committed 1,378,152 kB RAM

This could mean two things, the Launcher.exe is already patched for x64 operating systems (as Heliocon mentioned, but says unlikely...), or that the Launcher.exe is not the executable that needs to be patched.

The one thing I did notice in this simple challenge, that despite experiencing really low FPS as the bombs were dropping all around me when taking off and about a dozen+ bombers in the air, my CPU (2.66 GH x 4) was no where near being challenged, in fact it was only around 50% utilization. Network activity was also high (no other network apps running), so I wonder if Steam is part of the problem...

I already have most texture choices turned down, grass off, etc. so I'm surprised to find out CoD is not as CPU bound as I thought, but mostly gpu bound. Likely not news to anyone, just thinking out loud, and makes sense that they're rewriting the graphics...