My opinion stated below is based on 1.5 decades of tech support experience including years with one of the Fortune 5 companies.
The problem is not ATI per se but how SD attempts to interface with the instructions made available to them by ATI. The software is either making a bad call under specific circumstances or it is not getting the expected response. I can only speculate on that front without getting my hands on data that I’m sure SD won’t release (and I don’t blame them). I am sure that they are working with ATI to the best of their ability to resolve the issue but they still haven’t found the root cause yet. I suspect that it is somethey they have overlooked or dismissed. Something simple that seems too easy or unrelated.
ATI has already stated that they don’t see a problem and the latest driver release seems to have made the problem worse for Brink players. It doesn’t absolve ATI of doubt but the majority of the evidence is leaning toward SD’s code and how they are trying to interact with ATI instructions.
If I had a hand in the situation I’d have 3 programmers (alternating shifts) from each of the companies to sit in a room and pour over the code line by line until the problem is found. From my experience, having the devs and the vendor physically in the same room helps in ways that phone or online support couldn’t possibly. Body language or a subtle “huh” can clue others in to what may be what they’re looking for.
