![]() |
|
Technical threads All discussions about technical issues |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
||||
|
||||
![]() Quote:
![]() ![]()
__________________
i7 2600k @ 4.5 | GTX580 1.5GB (latest drivers) | P8Z77-V Pro MB | 8GB DDR3 1600 Mhz | SSD (OS) + Raptor 150 (Games) + 1TB WD (Extra) | X-Fi Fatality Pro (PCI) | Windows 7 x64 | TrackIR 4 | G940 Hotas |
#2
|
|||
|
|||
![]()
S!
I use the 7970HD and NO stripes. Catalyst 12.1 RC or something for me. Other series could try 12.2 previews or 12.1 WHQL..And seems the 7950HD kicked 580GTX in the nuts too at launch, reviews popping up. |
#3
|
|||
|
|||
![]()
I got the stripes on my old 4850 setup as well as my new 6950. However, I distinctly remember reading that someone with an nvidia card (I think it was a 560ti) was also getting the lines, so it may not be an AMD only issue.
And like Mazex said, they mentioned that with the "major rewrite of the graphics code" many of our issues would be cured; flickering shadows, horizontal stripes, memory leaks, crashing etc. But I must say, it's very distracting ![]() |
#4
|
|||
|
|||
![]() Quote:
Wait and see! |
#5
|
|||
|
|||
![]()
The ‘blue stripes’ are the apparent result of a compatibility issue between the current graphics engine and ‘Cayman’ gpu’s, which include the HD6950, HD6970 and dual HD6990. Only these gpu’s utilise the VLIW4 architecture, all others prior to the new HD7XXX cards use VLIW5. The issue was ‘fixed’ by 1c previously, but reintroduced with the last update. I had communicated with AMD extensively the first time around without any success, but as others have intimated, it would make little sense for them to provide a solution at this stage.
I also find them sufficiently irritating to warrant not having flown Clod since their re-appearance, and hope like hell that the planned graphics engine update resolves the issue (along with the myriad of other less annoying ones) ![]()
__________________
I'd rather be flying ... Gigabyte 990FXA-UD5 | AMD FX-8350 | MSI HD7970 TFOC-BE | 8GB Corsair DDR-III 1866 | Win8.1 Pro 64-bit
|
#6
|
|||
|
|||
![]()
Another thing to consider is the market share of this Sim and that ATI has in High-End Computer gaming. This is a nice product, in a niche genre, on a niche platform. From a business point of view it wouldn't be worth ATI's time to do anything to resolve this issues since this game is less than a drop in the bucket and is only affected by on line of their products (69XX cards).
Now if there was a problem with Battlefield III, World of Warcraft, Fallout3/Skyrim or any other A+++ title, you could bet your house that they would make any issue a top priority. Considering the alleged poor sales of this game, they probably wouldn't even recoup their losses in assigning someone to fix the issue even if a new graphics engine wasn't on the way. In short, why bother when it really doesn't benefit you? Even if Clod sales were two or three times what they were, it's hard to say if they'd deem it necessary to fix. It's all about the $'s with these people, because that's what they're in the business for. |
#7
|
|||
|
|||
![]()
S!
Part of the truth Speculum Jockey. But also the devs need to be in contact with the brand, keep them informed and co-operate. It is a fact that AMD or nVidia are not the ones that should beg for info, devs have to provide it and establish communication for best results. |
#8
|
|||
|
|||
![]() Quote:
|
#9
|
|||
|
|||
![]()
S!
Well at least the driver teams would KNOW how the GFX engine works. It took AMD 10 years to fix original IL-2 issues, but they did it even IL-2 is not an AAA game ![]() ![]() |
#10
|
||||
|
||||
![]() Quote:
|
![]() |
|
|