I have written a step-by-step gameworks optimisation guide for AMD

[Goatsecks]

I think it is fairly obvious now that AMD's driver team are struggling to optimise their drivers. I decided to a compile a detailed and thorough step-by-step list of instructions that their team could follow to help stream line the process. What follows is the fruits of my labour:

1. Set the default tessellation level to a value less than x64.

I think that covers the most salient issues. I know this is a little verbose in places, sorry. I wonder if I should include a few diagrams to help elucidate some of the more technical points?

Feedback welcome.

Infraction issued for trolling.
-- stahlhart

 

[Erenhardt]

Perfect.
But I guess it is not all. Nvidia architecture is more serial in how it works, GCN is more parallel. I'm guessing nvidia tries to make their GW code as serial as it can be. Their architecture is fine with that, while GCN can't reach its full potential and have problem with underutilized GPU resources. I'm basing this on 600Hz pcars physx calculations shananigans. Sadly, people with actual knowledge are forbidden to bring the issue and talk about it in daylight. Shame.

 

[3DVagabond]

That would be labeled as cheating. What they need to do is get sites to actually use the tessellation slider feature. They would if it was on an nVidia card. Maybe AMD isn't paying them enough?

 

[stahlhart]

Thread closed.
-- stahlhart