Gee who cares about DX12 now anyway... The majority of games won't be using it to its full extend before 2-3 years anyway. So much will have changed by then.
Who cares? Gamers for one. Won't take 2-3 years, games are already starting to move on up.
Pretty sure the takeup for DX11 took along time (heck we're still getting alot of AAA DX10 games) so all this excitement won't mean anything until we start seeing the vast majority of games using DX12 or even Vulkan.
Lets not turn this into an AMD circle jerk and be realistic. nVidia have a much better funded R&D team and also have the potential to see games are more tailored towards them (be it through financial trickery or marketing). I'd love to see AMD come out, make some cash on top and force nVidia to try hard. AMD still however have to get a couple of basic things right in order to even hope of gaining ground, even with this DX12 lead.
nVidia are still top dog and won't let go of their place without a fight. Even if it means they have to really innovate.
It's been realistic so far, AMD have the lead currently.. and on a hardware level too.
How so? All that has really happened so far is that they've been making alot of noise about DX12. Its just marketing BS.
The whole benchmark thing with the 290X being as fast as the Titan X ended up with Futuremark saying 'do not use it to compare graphics cards' because its an API test. Until I see actual gains in DX12 GAMES (not benchmarks), be it with my 7870 or my 780Ti I'm going to stay skeptical and presume that all this noise is just AMD trying to hype people into buying their gpus. Don't get me wrong, it'd be cool if AMD wipes the floor but as I said earlier, this IS nVidia and they do have talent and the finances. Even if they do prefer to pay people off occasionally..
Good thing that the only benchmark out also just so happens to Be built in a game... It's not hype. The results are there for you. The game and benchmark use asynchronous compute. It's comparable. The fact the game releases this year also makes it even more valid as it's not a tech demo. AMD have hardly really made any noise, Nvidia keeps whining about the game/benchmark which gives AMD free marketing.
If it was Nvidia that was ahead in performance in AOTS no one would be moaning at all guaranteed but the moment AMD gets a leg up "HELL NO WTF NO WAY !!!!".
You are slowly taking your fanboyism way too far, even if Nvidia was in amds place right now more than enough people would be as critical as they are now, there is just something in us that doesnt want to believe these benchmarks. (Atleast in me that is)
You are slowly taking your fanboyism way too far, even if Nvidia was in amds place right now more than enough people would be as critical as they are now, there is just something in us that doesnt want to believe these benchmarks. (Atleast in me that is)
Driver's aren't the problem here for AMD. AMD on a hardware level supports Async Shaders. Nvidia do not. So the way Nvidia gets it's supoprt is through drivers, however it's not nearly as efficient and has it's limits. AMD doesn't have this issue. Your limited by the hardware and the devs have full access to it. So for AMD it's down to the devs more than themselves. Nvidia are just screwed. They better have it for Pascal otherwise they may just start to fall behind more. By now if Pascal on the design level for it's die doesn't have this capability, then they will probably end up losing a lot of marketing power since they won't compete well with AMD and AMDs next gen products. As of now Nvidia only hold the TX as a clear winner. That could easily change with limited drivers.
I've never said Drivers are the problem, all I've said is that Nvidia's financial resources are substancially bigger than AMD's meaning that AMD's jump on HBM might not potentially last long so they need to market this well and get people to jump ship to new tech.
IMO its Naive to say there's a winner or a loser...I see it as 2 companies both currently offering something thats the same but work different slightly.
Link to my AOTS benching thread if anyone wants to see how the cards actually perform on the bench.
http://forums.overclockers.co.uk/showthread.php?t=18690671
nVIDIA do support Asynchronous Compute on a hardware level but a large part of their scheduler is implemented in software. Therefore what feeds their Asynchronous Warp Schedulers is a series of Software solutions.
nVIDIAs solution is also limited to 32 Compute Queues (or 1 Graphic + 31 Compute). Therefore under any sort of high Asynchronous Compute workloads, they run the risk of hitting a bottleneck. This is further compounded by the Latency introduced under Preemption due to their slow context switching.
Face it... nVIDIA was not as prepared as AMD for DX12. That's to be expected given that AMD has had a lot of experience with Mantle as well as the console API's.
We may need to wait until Pascal in order to see the level of engineering talent over at nVIDIA as it pertains to DX12.
Good thing that the only benchmark out also just so happens to Be built in a game... It's not hype. The results are there for you. The game and benchmark use asynchronous compute. It's comparable. The fact the game releases this year also makes it even more valid as it's not a tech demo. AMD have hardly really made any noise, Nvidia keeps whining about the game/benchmark which gives AMD free marketing.
I will apply the same level of skepticism regardless of who it is, even if I feel more 'loyalty' to one company over the other. I mean FFS I'm currently waiting on the furyX2 to come out so I should be happy about this turn of events. So excuse me while I hold judgement until I see a load more games with async, not just this one example.
While nVidia are now supposedly being shady as f*ck when it comes to Oxide now they've got the talent to make async computing work for them. Heck it actually does work, albeit in a buggy manner from what I've read thus far. nVidia are not amd, they'll either make it work or pay people off so that it works in the way that favors nVidia cards.
Early days innit. My next card is almost certainly going to be AMD for a number of reasons but this is not a factor for me yet.