Played some mp today and this game is dead in the water. So the only saving grace now is the possibility of a mod sdk. Crysis 2 had an sdk but you had have 64 bit. Total b.s move on crytek's part. With the crysis 3 sdk I would like to see a 32 bit sdk. I wish I still had my 64 bit windows but it'll be a while before I can get a new copy so 32 bit is all I have right now. it's sad how fast the mp died.

You do realise that SDK's like CE3 use a lot of resources, you want to load entire level's and edit them in real time? People expect that sort of thing to fit into less than 2Gb of ram per app are rather crazy.

less than 2gb? I have 4 installed and can use 3.5. Also Crysis 1 had a 32 bit sdk. You're an idiot.

Idiot eh? I suppose Crytek use 64bit SDK for no reason then because 32bit apps have a 2Gb memory limit.

All I'm saying is. It's possible to make a 32 bit sdk. I'm not gonna pretend to understand how it works. Tell me why I can run the free sdk on my 32 bit windows but not the mod sdk.

It's really down to how big your game assets are. The mod SDK for Crysis has to load entire levels and manipulated them in realtime, which requires lots of resources and memory, otherwise it will just crash.

If a 32bit app gets near the 2Gb memory limit it will crash.

Played some mp today and this game is dead in the water. So the only saving grace now is the possibility of a mod sdk. Crysis 2 had an sdk but you had have 64 bit. Total b.s move on crytek's part. With the crysis 3 sdk I would like to see a 32 bit sdk. I wish I still had my 64 bit windows but it'll be a while before I can get a new copy so 32 bit is all I have right now. it's sad how fast the mp died.

There's no reason to have a 32-bit *anything.* 64-bit computing has been with us in the supercomputer and RISC world since 1975 and made its debut in the x86 world in 1999.
No desktop computer system which isn't purposefully crippled ships today that supports less than 8GB of RAM. The people holding back x86 64-bit computing and holding onto the legacy that is 32-bit are people like you who either don't want to spend the extra $40 for 8GB of RAM or are still holding on to legacy 32-bit applications. It's a self sustaining cycle : people won't give up their ancient legacy applications so Microsoft and hence the PC world still has to support 32-bit computing which leads to a bloated vestige of 32-bit software and hardware still present on every PC which enables people who want to use ancient 32-bit applications etc. This is why DOS can still be run on an modern PC because of the 32-bit, nay 16-bit, vestige of legacy BIOS that even modern UEFI systems must support.

32-bit is dying ( and almost dead ). Live with it.

All I'm saying is. It's possible to make a 32 bit sdk. I'm not gonna pretend to understand how it works. Tell me why I can run the free sdk on my 32 bit windows but not the mod sdk.

Because your 32-bit version of Windows is an obsolete vestige that Microsoft has to keep supporting for the reasons mentioned in my other post.

Idiot eh? I suppose Crytek use 64bit SDK for no reason then because 32bit apps have a 2Gb memory limit.

It's actually a 3GB memory limit in Windows I believe, but you're point is still valid.

32bit has a 2Gb physical memory limit per app. You can do large address aware which will switch to 3Gb but you need a 64bit OS for that to even work.

Some games use LAA switch, otherwise they become unstable. Many people complained about this with games like Skyrim or heavy texture mods.