Grid 2 has exclusive Haswell GPU features
- Thread starter Davros
- Start date
I think we bump into each other for as many years that we know more or less where each and everyone of us comes from. See also my reply to nao above; I've been personally always VERY finicky with texture filtering. Those that have a strong memory might remember that I was part of NV's focus group from 2004 to 2006. The first ever thing that knocked me over when I laid hands on a GF6800 back then was the intense occassional texture shimmering. I as a layman wrote even two whole write-ups about it back then and my humble personal contribution to the attention the press and gaming community layed on to the topic after that.
The nastiest of the AF related optimisations originally were in the "underfiltering" ballpark; still today in my book if an application requests for trilinear it should receive trilinear.
Programmable blending might be a point from your side but under normal conditions I don't get eye cancer from all the dancing meanders/noise that can spread over my screen with crappy filtering.
Of course I have seen it. I tested that regularly. On my old HDD I should have Filtertester videos from HD3000. No, HD3000 never had shimmering issues nor banding issues unlike AMD. The shimmering level on HD3000 is not any different to HD4000 or Haswell. All what changed is the angle dependence. Nobody was forced to use the quality setting with the negative lod bias. That's just a software thing. A different setting than balanced never was a recommended option.
It reproduces less details in the middle setting. Together with the strong angle dependency (which was clearly visible ingame unlike nV's very slight angle dependence) it was the worst solution, even in the default setting (which was usually also slightly less shimmering than HQ in AMD's case btw.; intel's HQ was right from shimmering hell, much worse than anything else [besides point sampling]). The occasional banding and shimmering bugs of AMD's old AF algorithm don't change that (It was obviously really just a bug in the implementation using wrong weights for the interpolation of the samples. As embarassing as this is they didn't save efforts as with early implementations or intel was doing before IB). One may provoke corner cases with manually set mipmaps (not correctly filtered or not matching between the levels as it is the case with one of the filter test programs out there, iirc; but for that you can't blame the hardware imo).
As I said already, you don't need to defend something what even Andrew Lauritzen called terrible and admitted that intel was the last to move in the right direction. Intel did their homework, AMD ironed out their bugs too. Let's be happy about that.
As I said already, you don't need to defend something what even Andrew Lauritzen called terrible and admitted that intel was the last to move in the right direction. Intel did their homework, AMD ironed out their bugs too. Let's be happy about that.
Last edited by a moderator:
When it comes to shimmering and banding, AMD had the worst solution not long ago. Oh well Trinity and Richland still suffer from shimmering.
Irrelevant since balanced always was set as default from the driver. Nobody used quality.
I don't defend anything, I just correct wrong statements from you. It is funny that mostly people who never tried it in games are the biggest moaner.
Then you have to correct also quite some tests out there.
I gave you my reasoning which is backed up by facts established by tests from respected sites concluding that for overall AF quality intel sat in the last position back then. Miraculously, this appears to be also Andrew's position here in the thread. You have chosen to argue that intel's AF wasn't that bad and defend it with weaknesses of competitors. I can accept that you weigh the factors differently. Do what you want with that.
That's a nice example falsifying Paran's statement.
That's clearly a bug somewhere (app, driver, etc)... if you can see "shimmering" in a youtube-compressed video, there's something a lot more wrong than approximate LOD computation.
Anyways, we're way off topic here...
That has nothing to do with the AF from HD3000 itself. At that time I tested it and reported to Intel. What happens here is that the App didn't enforce AF. In fact AF wasn't enabled. If you disable AF on Nvidia and AMD it shimmers as well in this app (edit: not anymore on Nvidia and Intel, just checked with their newest Google Earth, probably same for AMD). This bug has been corrected from google in their next next major version. AF properly enforced and no shimmering anymore.
That's a nice example of someone who never tried Intel graphics and has no clue about it.
Back to topic. Here is a Grid 2 test with Iris Pro 47W+55W and AMDs newest APU: http://techreport.com/review/24954/amd-a10-6800k-and-a10-6700-richland-apus-reviewed/5
In Grid 2 Iris Pro does a pretty good job.
Last edited by a moderator:
As I said, I don't think that's true. If it is, it's just a judgement call on performance in that specific engine. The extensions are available on any Haswell GPU.
nAo and I both worked on this stuff (see authors for the papers I linked), hence the "insight"
You were right Andrew, it works on every Haswell. I just tried Grid 2 on a GT2 HD4600, the two Intel options are available. So it's not bound to Iris graphics only.
Cool thanks for the update Paran.
They are available on my amd 6950
Sounds like broken detection logic if so. Definitely won't work/do anything even if you are allowed to enable them.
http://www.computerbase.de/artikel/grafikkarten/2013/intel-iris-pro-5200-grafik-im-test/7/
Screenshots and a video from the Intel extensions.
Screenshots and a video from the Intel extensions.
No real technical reason, but it would probably require lowering quality settings to maintain high performance. Note that there are also screen-space AA techniques in Grid 2 which smooth out a lot of the remaining jaggies. MSAA is fairly expensive on Haswell, so OIT + post AA is probably a better trade-off.
Do Intel HD Graphics EUs increase in bit-width between generations?
Because cpu-world.com http://www.cpu-world.com/info/Intel/Features_of_integrated_Intel_HD_graphics_units.html shows that HD 4000 units can execute 8 threads; does that mean they are 256 bit wide? Why isn't Intel more clear on their GPUs specs?
Because cpu-world.com http://www.cpu-world.com/info/Intel/Features_of_integrated_Intel_HD_graphics_units.html shows that HD 4000 units can execute 8 threads; does that mean they are 256 bit wide? Why isn't Intel more clear on their GPUs specs?
