http://www.beyond3d.com/content/interviews/39/1
---------------------------------------------------------------------------------- quote------------------------------------------------------------------------------------------
Here's a "from the geeks wet dreams file" question: Is there any chance that there might be an interface to allow third parties (and knowledgeable enthusiasts) to write their own CFAA algorithms and run/implement them on their R6xx? Even distribute them for others to run?
It?s certainly possible, and in DX10.1, applications will have access to the fragment data themselves and they can certainly do it quickly. But the issue here is access to the compression data. I?m not sure we?d expose that; so we would be limited in offering people DX10.1 style functionality, which could be done. Again, it would be a question of making tools available and supporting users. Perhaps through CTM or OGL this will be possible too.
Lastly, as you look around the web at reaction to the R6 family. . .are there any specific aspects to the design that you feel have been particularly misunderstood or not emphasised to the degree they deserve?
I can?t help but be a little disappointed that we did not have enough time to get more optimizations into our drivers in time for the launch. I still cringe when I see poor performance (especially if it?s compared, to, say, our previous generation products), and send daily emails to the performance and driver team, begging for this or that. In fact, I do believe that they all hate me now. They should join the club.
Also, on the feature side, we weren?t able to expose the adaptive edge detect CFAA modes to the public, or even to the press, until very late in the review process. This means that most reviewers did not have a chance to look at the amazing quality this mode offers ? There is nothing comparable to it out there.
We also had some last minute performance possibilities, which is always incompatible with stability, and we did not have enough time to get those tested and integrated in time for launch. We see in the latest driver, some 2x to 3x improvement in adaptive AA performance, for example, which is great but came later than I would have liked. But, I?ll admit, there?s so much to do still, that I haven?t really spent that much time on reviews and such. The reality is that I expect things to continue to improve and be much better in a few months.
---------------------------------------------------------------------------------- quote-------------------------------------------------------------------------------------------------
If you have no idea what Eric demers is talking about or what interviewer is asking then i suggest you read up on "R600 Architecture and GPU Analysis" by beyond 3d. Also wikipedia all the terms if you don't what they are or mean.
---------------------------------------------------------------------------------- quote------------------------------------------------------------------------------------------
Here's a "from the geeks wet dreams file" question: Is there any chance that there might be an interface to allow third parties (and knowledgeable enthusiasts) to write their own CFAA algorithms and run/implement them on their R6xx? Even distribute them for others to run?
It?s certainly possible, and in DX10.1, applications will have access to the fragment data themselves and they can certainly do it quickly. But the issue here is access to the compression data. I?m not sure we?d expose that; so we would be limited in offering people DX10.1 style functionality, which could be done. Again, it would be a question of making tools available and supporting users. Perhaps through CTM or OGL this will be possible too.
Lastly, as you look around the web at reaction to the R6 family. . .are there any specific aspects to the design that you feel have been particularly misunderstood or not emphasised to the degree they deserve?
I can?t help but be a little disappointed that we did not have enough time to get more optimizations into our drivers in time for the launch. I still cringe when I see poor performance (especially if it?s compared, to, say, our previous generation products), and send daily emails to the performance and driver team, begging for this or that. In fact, I do believe that they all hate me now. They should join the club.
Also, on the feature side, we weren?t able to expose the adaptive edge detect CFAA modes to the public, or even to the press, until very late in the review process. This means that most reviewers did not have a chance to look at the amazing quality this mode offers ? There is nothing comparable to it out there.
We also had some last minute performance possibilities, which is always incompatible with stability, and we did not have enough time to get those tested and integrated in time for launch. We see in the latest driver, some 2x to 3x improvement in adaptive AA performance, for example, which is great but came later than I would have liked. But, I?ll admit, there?s so much to do still, that I haven?t really spent that much time on reviews and such. The reality is that I expect things to continue to improve and be much better in a few months.
---------------------------------------------------------------------------------- quote-------------------------------------------------------------------------------------------------
If you have no idea what Eric demers is talking about or what interviewer is asking then i suggest you read up on "R600 Architecture and GPU Analysis" by beyond 3d. Also wikipedia all the terms if you don't what they are or mean.
Facebook
Twitter