It shouldn't be a problem for the devs when they haven't access to a 69xx card. A game is programmed for a system, not for a specific card. A video card is nothing more than a calculation device and often a D/A converter and/or matrix. For every DX11 card the same input in should be the same output out. And because there is a difference in output between 68xx en 69xx cards while the input is the same, it means work for ATI/AMD. The program that displays the difference in output shouldn't matter because it's just the deliverer of a message. At least that's at least my opinion.

It will be a combination of more optimisation from the devs and the need for a unique CAP profile from AMD. Unfortunatley with the devs still optimising and fixing graphical problems any CAP profiles released now would be rendered almost worthless in the future.

I tend to agree – the Cayman GPU is the only one with the new VLIW4 architecture, and the only one that has the problem. This makes it AMD’s problem, rather than 1C’s – they should at least ensure that the new ones work as well as all of their other GPU’s. I haven’t heard back from them in a while, but have sent a reminder so will hopefully hear something soon

If Maddox Games didn't program or test on new architecture would that be AMDs fault? The fact that the 69XX cards were available since December for purchase and Maddox Games decided not to bother is again not AMDs problem. Yes AMD have a responsibility to ensure their stuff works as advertised but not for pre beta software. Like it or not CoD is not optimised or close to finished and that is purely the devs fault, not AMDs or Nvidias. Or maybe we should bombard Nividia and AMD with requests to fix the lack of FSAA, purple land tiles, lines on the coasts and flickering trees and building shadows in CoD. Taken as a whole the number of issues that CoD has points to the fact that the graphics engine (and indeed the entire game) is still a WiP.

I have logged two support tickets with AMD for this issue but deep down I know CoD is the most likely culprit. This all reminds me of the fact that when the new Nvidia 8800GTX series GPUs were released, FSX did not show self shadows on the aircraft. Myself and a whole bunch of others bombarded Nvidia forums and support with requests to fix the problem. Every single one of those requests were ignored. Eventually FSX SP1 was released and the issue was fixed by the developers. The moral, sometimes we are barking up the wrong tree :)

Here is a link to just one of those forum threads, I made a few posts in anger over that issue! Sorry for going slighty OT on this.

http://forums.nvidia.com/index.php?showtopic=22798

No,that's completely on topic. I have again requested a response from AMD as I would like them to confirm that it's not driver-related (if they will). From what you have said, it seems unlikely. If we know that it's a fault in the game we can possibly nag luthier for a fix, or fiddle with settings ourselves.

It just worries me that the only GPU that seems to be affected is the Cayman, which has a different basic shader architecture to all other current Ati chips. It may be that the way the game has been written doesn't agree with this, and unless AMD can provide a driver 'fix', we'll have to live with it permanently :(

Whats really annoying about the blue lines, is that it wouldnt take luthier 2 minutes to post on here and tell us wether it is game related or not
At least that way we would no?
I said it befor and il say it again
Ati user are getting shafted, with this game:rolleyes:

I think we need to keep asking both the devs and AMD for a fix to this issue, eventually I would hope one of them would listen. Unfortunately my experience is that neither AMD or Nvidia listen to niche gamers playing niche games, especially when those niche games are in a beta state.

It irks me really bad to see that utter crap games like Lost Planet 2 get many CAP/SLI profiles or even dedicated driver sets to increase their performance. They even get special attention months after release while sims get ignored completely. LoL for example the AMD 11.5 CAP 3 profiles include a fix for Garshasp The Monster Slayer. Nope I have never heard of it either.

I agree it would be nice if Luthier would make some comments on this one because for now we can only speculate where to go with this problem.

seems fixed

YES!!!!! The blue lines are gone since the latest update!!! :grin::grin::grin: Thank you!!! Maybe it would be better PR to make a notice of it in the update readme. This will surely limit the complains of people that the serious problems are not dealt with. I'm happy!!!