EA-DICE Frostbite Titles in 2013 Will Require 64-bit Windows

[Dippyskoodlez]

How many are there in that 1/3? Quite many I imagine.

IMO, computers that are running a 32 bit OS, and do NOT meet the minimum system requirements(hardware wise) for a game are not considered part of the target market.

People just whining to whine.

If EA/DICE support a simultaneous 32 bit executable, that means they have to split their dev team up even more than they already cut all the corners they can. (while the 32 bit exe becomes used by noone except hackers that are looking for a secondary exploit.)

seems to me, like a rock solid idea, RIGHT BF3? Completely bug free!

Windows x64 has been the same product package since vista x64, there really is NO reason not to be running windows 7 x64 if you have windows 7.

 

[FordGT90Concept]

It's a series of #IFDEF in the code. It isn't very difficult to write code to support compiling both. Competent programmers have been doing this for many years.

You, maybe. Those who want to build a supercomputer with all the memory in one address-space, might find 40-bit addressing a bit of a problem.

That's 128 sticks of 8 GiB (highest density available) RAM for ONE processor. I don't know of any systems that even come close to that. Systems with >1 TB RAM are clusters. Each processor has a small pool of memory and they send requests amongst themselves to copy data between them. A processor in one node of the cluster can't directly access the RAM of another without requesting it through the target node's processor(s).

 

[librin.so.1]

It's a series of #IFDEF in the code. It isn't very difficult to write code to support compiling both. Competent programmers have been doing this for many years.

Yet it's doesn't take much for the code readability to become like this.
Thus, the less #ifdef and such needs to be used, the happier the devs are. That is a good thing for the users, if You know what I mean...

 

[eidairaman1]

its funny but there is no means of getting the 1 and 0 anymore efficient then they are lol

 

[MxPhenom 216]

8GB DDR3 Single Channel + Windows 8 Pro + 512-GB/1-TB SSD: 2013 HERE I COME!!!

single channel? Fail.

Why not dual channel for 16GB

 

[FordGT90Concept]

Yet it's doesn't take much for the code readability to become like this.
Thus, the less #ifdef and such needs to be used, the happier the devs are. That is a good thing for the users, if You know what I mean...

The only thing that really bothers developers is feature creep. It's gonna suck when EA tells DICE the number of support calls their getting and DICE has to go back to all the code they wrote specifically for 64-bit and add those IFDEFs retrospectively. It would have been wise to do it in the first place.

 

[newtekie1]

It's a series of #IFDEF in the code. It isn't very difficult to write code to support compiling both. Competent programmers have been doing this for many years.

Writing the code is probably not the issue, it isn't hard to program a game to use a DX9 rendering path either, but EA-DICE doesn't do it. Beyond just writing the code, there is testing it. Having a 32 and 64-bit exe means more QA time. Especially with the 32-bit exe, because they are obviously writing the game to be 64-bit native, and are also assuming at least 4GB of RAM(otherwise why 64-bit?). So to support 32-bit means they will have to do a lot of QA to make sure the game doesn't crash or freaks out when limited to less than 4GB.

 

[Dippyskoodlez]

It's a series of #IFDEF in the code. It isn't very difficult to write code to support compiling both. Competent programmers have been doing this for many years.

Because that is an easy fix for actually utilizing >4gb of ram. (among other possible 64 bit features.)

 

[eidairaman1]

single channel? Fail.

Why not dual channel for 16GB

because performance gains are negligible between single and dual channel, machines like bigger frame buffers, it really doesnt care about what speed they operate at since now most FSBs run at a different speed than the Ram itself

 

[Dippyskoodlez]

because performance gains are negligible between single and dual channel

No, no they are not. Where did you get this information? If you're gonna argue this, you better provide some hard benchmarks.

 

[Aquinus]

No, no they are not. Where did you get this information? If you're gonna argue this, you better provide some hard benchmarks.

because performance gains are negligible between single and dual channel, machines like bigger frame buffers, it really doesnt care about what speed they operate at since now most FSBs run at a different speed than the Ram itself

You're both right. Single threaded performance will see no benefit of memory running in unganged dual-channel mode where the channels are split in to two 64-bit memory interfaces enabling two separate memory operations per full dram read/write cycles, however applications that have long words in memory could benefit from dual-channel ganged mode (1 large 128-bit memory interface, rather than 2 smaller ones.) Dual-channel and unganged mode show their colors when you use two threads, like how quad-channel doesn't show its true colors unless you start using 3 or more threads. This is an excellent example of how the 2600k and 2700k compare to the 3820, where single-threaded memory tasks on SB takes off, but add a couple threads and the 3820 eats the 2600k alive beyond 2 threads of heavy memory usage. I've only owned AMD motherboards that have allowed me to run dual-channel memory in ganged mode, though, but I'm not sure if this is a AMD specific ability (I wouldn't be surprised if it wasn't.)

 

[de.das.dude]

Finally!!!

 

[FordGT90Concept]

Writing the code is probably not the issue, it isn't hard to program a game to use a DX9 rendering path either, but EA-DICE doesn't do it. Beyond just writing the code, there is testing it. Having a 32 and 64-bit exe means more QA time. Especially with the 32-bit exe, because they are obviously writing the game to be 64-bit native, and are also assuming at least 4GB of RAM(otherwise why 64-bit?). So to support 32-bit means they will have to do a lot of QA to make sure the game doesn't crash or freaks out when limited to less than 4GB.

The extra QA is for 64-bit (troubleshooting usage of the extra registers), not 32-bit. It is also quite simple to tell if a program ran out of memory and custom service already recommends upgrading computers frequently. It represents very little change from the current support model.

 

[Dippyskoodlez]

The extra QA is for 64-bit (troubleshooting usage of the extra registers), not 32-bit. It is also quite simple to tell if a program ran out of memory and custom service already recommends upgrading computers frequently. It represents very little change from the current support model.

If you're going to cater to a game engine crippled by 32 bit, then why even code a 64 bit version?

i.e. crysis 2. Made for xbox, plays like an xbox on PC. BF3, made for a PC, plays like a PC.