Why no SLI or Duo Core support?

[Ghost-Ryder]

I will never understand Developers.
It is really not that hard to know the basics.

Name changing if you ask 1000 gamers they will all I mean all tell you it is a must have.
Duo core has been out long enought to be supported in any new game unless you life under a rock.
SLI has been out for many years and it is very popular expensive but popular.

That is just basic stuff not rocket science.
There are many more but want to keep it short.

[theMechanic]

that would be the UT3 engine, not the game.

SLI is pretty much just a gimmick really, seeing as how vid crads are so fast on their own anymore.
The Core Duo issue is really bad, i mean, a cpu is mainstream unlike dual SLI vid crads.

[Mike Nomad]

that would be the UT3 engine, not the game.

SLI is pretty much just a gimmick really, seeing as how vid crads are so fast on their own anymore.
The Core Duo issue is really bad, i mean, a cpu is mainstream unlike dual SLI vid crads.

I have no trouble running MOH:Airborne with SLI & Core2Duo. The UT3.0 engine handles both situations flawlessly. Those folks having problems are either experiencing machine specific problems or are hitting coding obstacles in the core code of the game itself. Not the engine.

Various software packages may not state they explicitly support these variants but the fact is, SLI and C2D are not coded into the game specifically because they are inherently supported by the mere fact of their existence and automatic compatibility due to "following the basic rules of code". Those rules ensure basic hardware compatibility.

By that I mean, the rules of code established and abided by for CPU, GPU & Audio Processors. As long as those rules are followed by everyone involved, software and hardware wise, there will be no problems.

[Dirtynap]

Must agree ith Nomad. The U3 engine supports all the modern hardware, SLI, crossfire, mutli threading and ageia physics (in fact ageia have been banking on U3 for a while).
Epic have done a good job however, they just provide the raw engine its up to the game dev's to utilise the full thing.

[The_Comfy_Chair]

Some detail on the Unreal Engine and "Multicore" support for those interested.
As Mike said, Unreal3 Engine is one of the few that do provide explicit support for multicore gaming goodness.

Link goes to Anandtech; which is a well-respected Hardware review site. :salute:

http://www.anandtech.com/cpuchipsets/showdoc.aspx?i=2377&p=3

[Pendragon]

One of the guys in my clan is in a world of pain running this game. I spent four hours on Sunday trying to help him out. On paper his PC should be eating this game up, but he was getting only 15fps at best before we started. Now it's up to 35 but still not good for a Machine that cost £3500 ($6500) about a year ago.

One of the things that surprised me was the way Windows was reports the spread of load on the CPU. It's a duel core extreme 3.2, Task manager shows 4 cores. Hyper threading I guess, makes 4 out of 2. (Sorry I'm an AMD man) When the game is running the first two graphs show almost no activity, the third graph shows about one quarter capacity. The fourth graph is maxing out! The game is running at around 10fps and the AI is beaning "starved" an in the red almost constantly.

This poor guy is pulling his hair out, and he can't afford to lose any more LOL...

As I said I'm more familiar with single core AMD's so all of this hyper-threading is new to me but surely it should be handling this better than this?

I would love to know if this is normal? If people with this type of CPU are experiencing similar things. Really I just need to know is this the game or his PC...

PS all of the drivers are up to date things look just fine with Windows nothing out of the ordinary. BF:2 runs at around 100fps on the same PC.

[Ghost-Ryder]

There is a hot fix out don't know where it shuts down one core and the game runs better from what I have been hearing.Same with SLI you need to shut one down for the game to run better.

E6700 Duo Core
EVGA 680i Mobo
2 gig Dominator Mem
2 X 8800 BFG Cards

I was getting 6 FPS in the Demo running around.

[GaSplat]

If the game is not coded for multi core it will not take advantage of it. What you see is the game running on only one of the cores. Shutting down the other cores will NOT help. They are handling the other Windoze processes that are running. About the only thing you can do is go into the BIOS and turn off hyperthreading. This could produce a minor imporovement as currently you could have one physical CPU pretending to be two CPUs and it ends up doing all the work because the OS thinks it is distributing between totally separate CPUs. I forget if its a BIOS setting or windows configuration setting (doubt that since its a pretty low level hard ware function) but hyperthreading is fairly useless if you have one big single CPU task (read: most of today's games) you are trying to max performance on. Hyperthreading is better for running multiple programs at once (like twice as many game servers - assuming the CPU load is acceptable which it is for most older games and newer server rigs).

[[ELS]WRX Boy]

With regards to the SLi issue. While UT3 engine may take full advantage of it (which I have no doubt), Airborne most certainly does not as far as I can tell. The more of the critical fixes I read, the more convinced I become that this is just another console port.

As a measure of comparison, when playing COD2 (another console port), I am getting a steady 91fps and that is because that is where the game is capped by default. With alot of smoke on the screen, I drop into the 60fps range.

In Airborne, I am averaging low 30's with alot of drops into the teens. After reading the latest list of critical issue solutions, I decided to try the "disable SLi" solution. Lo and behold, my frame rates nearly doubled. Now I am averaging 50's and have even seen a few 60's. Not stupendous, but a huge improvement.

For those wondering, my PC specs:
AMD Athlon 64 x2 4200+
ASUS A8N-SLI motherboard
Dual Nvidia 7600GS 256mb cards in SLi
2 gigs ram
150gb SATA 7200 rpm HD
WinXP SP2
All drivers updated 2 weeks ago.