You just used faulty logic, as crossfire was broken for several things at the time... dur dur dur.

ATI just fixed their broken mess. The drivers themselves are the drivers...with moderate fixes to egg out 1-2 fps on older things, and to keep things running smooth on new stuff ala profiles.

Think code tightening on their threads and data wrappers. They dont make new junk up for these games, they use the specification provided by their clients to help tailor bug fixes and best performance...again, based on the work that the game programmers do...which looks a bit shoddy for this game.

Fact is, it is up to the game creators, as the video folks are vendors, not clients,...and are supposed to be used as such.

Guys this post is not intended to flame Cryptic, its to help people who need performance increases. Please put the flames in one of the other 100+ flame posts. I am sure they relize thier code is broken somehow and are trying to fix it, they dont want to lose customers i am sure.

Unfortunately, I don't have suggestions to have, though I too would like to see more, rather than the complaints already echoed in so many other threads. but on an impressed note, has anyone else noticed that if you toggle between pages one and two, Amonight's avatar cycles through all her characters? It only seems to do it if you leave the page and come back, too. I am in awe. Hoping for a tutorial thread on that, Amonight!

Well, some times it can be the drivers at fault and not the game. For example, if the game stuck specifically to the programming requirements of the graphic API they were using (OpenGL or DirectX) but the drivers used a shortcut to increase performance, and put in a hack to for specific games to get them to work properly with the shortcut. In that case it would be the drivers at fault if there were incompatibilities from the driver trying to force the hack onto the game, and it not "taking" as it were.
There have been similar instances in the past, one example being a Futuremark version where Nvidia used a shortcut to get better performance numbers. Another, if I remember right, was where Quake III (or maybe it was Doom III, but I'm pretty sure it was Quake) was found to be running so nicely on ATI cards due to graphic drivers short changing the graphic quality. This was discovered the renaming the game .exe so the drivers couldn't detect it. The performance then dropped noticeably while the graphic quality went up.

Ummm, no, I guess you never played SoE's EverQuest or Blizzard's World of Warcaft; ans BOTH these MMOs have blamed vndor drivers for nes issues and always come back with (we're working with them to get these issues resolved). And you don't need to take my word for it, just read Nvidia's 'Issue's fixed in this release notes.' - the issues resolved are do to software manufacturers informing Nvidia - "Hey, your driver does this when folks run our Application.

Thanks for the heads up, i' donwloaded it last night and passed it on to my super group and we all love it.

cheers

Oh ok, so if it doesn't cater to your needs it's the vendor's fault. But if it's something that benefits you, it's the game developer's fault.

Right...

While you may see it as faulty logic, I was making a point that hardware vendors needs to optimize drivers for certain games for said game to work properly. If you can't look passed your own nose and see this as fact ( which is easily done by looking at driver update release notes ), then you truly are computer illiterate.

You just want to argue so badly, don't you.

Don't think the hardware vendor is to blame for this one... what, BOTH critical hardware vendors have broken drivers...pfft yeah.

Where do you think the things on patch notes from video makers come from? Do they buy games and test randomly to fix things? Um no, the clients supply them with code and issues to work with. They then tweak things - like i said prior.

I never once contradicted the fact code is updated. Simply that your example about crossfire was faulty, due to it working poorly on A LOT of things, not just Crysis. They had to fix their code in general.

Broken code CAN work both ways, but in this issue, both chipsets are having issues, which points to one culprit.

So, not sure why my nose or anything else was brought into this, or why suddenly people are computer illiterate if they don't think you are right...sigh.

I think you're over looking the fact that the issues between ATI and Nvidia are totally different, and don't even affect most people that play the game. Few ATI cards have texture corruption issues on CO, Nvidia cards do not. Nvidia cards have low FPS issues, ATI cards to not. There's other inconsistencies between the two vendors with CO. It doesn't take a brain surgeon to piece it together that if it were a problem with CO's code, then these inconsistencies wouldn't be inconsistent.

Point being - you can expect odd ball issues such as these to be present with a graphic engine hot off the press. If you think that every graphic engine should be polished upon release, then you're only fooling yourself and you should probably shelf CO and not buy any new games until video card manufacturers and game developers provide better support from both fronts.