Pwndenburg
Member
Don't know, but I hope this does launch AMD right back into the game. Nvidia doesn't have much time to fix a lot of stuff if this data is true. That would be awesome to have competition and sane pricing again.
I remember reading in another Anandtech article that pre-Maxwell 2 HyperQ was not compatible with DirectX 12 Asynchronous Compute, though.
For the current specs no. Microsoft will need to extend the multi-engine compute with fine-grained preemption support, and the API must support latest data latch for optimal head tracking. Only Mantle support these right now, but a standard will surely evolve in the future.
Since NV controls 70% of the market the developers will adjust ACE usage to NV. This means in principle that the potential more ACE power of AMD will have no measureable effect till NV decides to increase ACE on their hardware. So Business as usual.
Maybe it explains NV being quiet on this front, until Pascal.. then it's all aboard DX12 & VR train!
or they have mothing to worry about and they don't feed the trolls?
or they have mothing to worry about and they don't feed the trolls?
or they have mothing to worry about and they don't feed the trolls?
When NV didn't have tessellation: "Tessellation isn't important"
When NV had better tessellation: "Tessellation is very important, use it to the max!"
History, it aint been that long.
Since NV controls 70% of the market the developers will adjust ACE usage to NV. This means in principle that the potential more ACE power of AMD will have no measureable effect till NV decides to increase ACE on their hardware. So Business as usual.
This is correct, so I don't understand what all the fuss is about.
and its 76.4% of the market.
or they have mothing to worry about and they don't feed the trolls?
I think there's more to it than that. They have been extremely silent on this. I think they were taken back a bit by what happened and they expected a better result. That tells me they think they can make it work and are letting the engineers do their thing to figure out why and how.
It probably doesn't matter either way. By the time AC is that heavily relied upon that a glaring lack will make or break you, the card is probably too old to get much out of anyway.
I think we'll have a clearer picture of what's going on with Maxwell 2 and AC in a month or two.
You are sure that no iGPU can play The Witcher 3 at acceptable framerates?:sneaky:
https://www.youtube.com/watch?v=WvUu-MHZxMg
No, nvidia can utilize 100% of the async computing potential of their cards with only one "ACE" ,AMD needs 8 of them to get up to 100%So, what you guys are saying is that Nvidia is holding back PC gaming.
No, nvidia can utilize 100% of the async computing potential of their cards with only one "ACE" ,AMD needs 8 of them to get up to 100%
Not just can, they must use it. But NVAPI is not a real API, it's just a services library for the existing graphics APIs. It won't allow such a low-level optimization what AMD can do with Mantle, with API-to-API interoperability.Can Nvidia use Nvapi for VR?
So, what you guys are saying is that Nvidia is holding back PC gaming.
No, nvidia can utilize 100% of the async computing potential of their cards with only one "ACE" ,AMD needs 8 of them to get up to 100%
Technically your right, nvidia can utilize 100% of their async computing potential with 0 aces. But it may have something to do with their async potential equals 0.
Not doing something when you can't do it is doing it to 100% of your potential. Hard to argue with that line of thinking.
That is the same point everybody else is making though,amd has so much compute potential because it does not get used otherwise,they have 50% of (otherwise) uselless stuff and argue that you gain 50% if you use this (otherwise) useless stuff.
How is it better to have useless stuff on your card?
If you're trying to say there is 0 idle time in an nVidia gpu while gaming, you're wrong. Only their engineers truly know how much time is spent idle across most games