• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

gamegpuMirror's Edge Catalyst Beta GPU Benchmarks

Page 4 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Looking at 970 ramgate, i don't think so. because it took these posters to find out they forgot something to tell us.


560ti/670/970 user here.

You mean to say they didn't know about the 970's vram limitations? the pr department maybe but the designers of course did.
 
DX11.2 was the AMD "misinformation".

Both companies got long histories with..these issues.
Please , on the gtx670 i had dx11.2 support was written on the box. but it cannot even run bf4 using dx11.1. it was always just dx11.

And amd gcn cards do run bf4 using dx11.1/mantle.
 
Which is something that need not happen with GCN based consoles and PC hardware all running on Vulkan. 😉

PC gamers should want this, that's what I don't understand. Surely you realise that AMD can bring an end to these crappy ports forever? We just need to find a place for Nvidia in the market too so that AMD doesn't get lazy.

Vulkan is the saviour that MS wants to kill before it's given a chance. But they are doing a terrible job of it with UWP haha.

Btw, Robert Hallock just now talking about the long-term master plan:

https://youtu.be/CIuVZLw-n8g?t=2m32s

You should hit him up on twitter, with your video, so he can chip in. 😉
 
I think it's safe to say these minor decimals of DX is pointless since few or zero games are ever made to utilize them in a meaningful manner.

Btw, Frostbite/EA according to Johan, plans to shift to DX12 later at the end of 2016 if we take their twitter posts as legit. Until then it's still DX11.
 
Kepler did have D3D 11.2 support (now D3D 12) but only feature level 11. There isn't a feature level 11_2 because D3D 11.2 just added features to feature level 11 and 11_1 cards. Kepler/Fermi/Maxwell 1 support feature level 11, GCN 1.0 feature level 11_1, GCN 1.1/1.2 feature level 12, and Maxwell 2 feature level 12_1
 
Kepler did have D3D 11.2 support (now D3D 12) but only feature level 11. There isn't a feature level 11_2 because D3D 11.2 just added features to feature level 11 and 11_1 cards. Kepler/Fermi/Maxwell 1 support feature level 11, GCN 1.0 feature level 11_1, GCN 1.1/1.2 feature level 12, and Maxwell 2 feature level 12_1

nvidia exposing driver features is not to be trusted the whole mess of async should have been a lesson for them....

since when nvidia has dx12.1 compliance? dx12.1 is an evolution of dx12 you NEED to have a full dx12.0 card in order to claim a dx12.1 support which they dont have...


remember this?
http://www.legitreviews.com/nvidia-highlights-directx-12-strengths-amd_138178
yeah nothing has changed only pr bullshit when they saw on december that the whole mess of async was coming down suddenly you saw nvidia supporting dx12.1
i mean lol just lol
 
Clickbait Beta benchmarks sure do whip the fanboys into a frenzy. On both teams.

This. There's really not much to see here, seems to be performing alright for the most part and isn't too far off from what we've seen from a lot of titles. Still beta, but we see kepler's top dog 780 Ti behind a 290, the 970 edging out the 290, the 390X falling between the 970 and the 980. Fury and Fury X not tested. How did this thread reach 4 pages get totally off topic.. moving on.
 
Gamegpu's Battlefront beta benches matched the release ones pretty closely; minimum FPS saw a big jump, but averages are about the same.

6KmMu5H.jpg

cQUAmFK.jpg
 
I think it's safe to say these minor decimals of DX is pointless since few or zero games are ever made to utilize them in a meaningful manner.

Btw, Frostbite/EA according to Johan, plans to shift to DX12 later at the end of 2016 if we take their twitter posts as legit. Until then it's still DX11.

This is disappointing they dropped AMD Mantle support so suddenly despite championing it with Battlefield 4. I was hoping Star Wars:Battlefront would run Mantle but no luck and now its looking like Mirrors Edge:Catalyst and Battlefield 5 won't support it either.

I understand the need for DX11 backwards compatibility for all of the Windows 7 / 8 nVidia users but to not support a next-gen API like Mantle in 2016 already is lame - especially when the support was previously built in to their engine.
 
This is disappointing they dropped AMD Mantle support so suddenly despite championing it with Battlefield 4. I was hoping Star Wars:Battlefront would run Mantle but no luck and now its looking like Mirrors Edge:Catalyst and Battlefield 5 won't support it either.

I understand the need for DX11 backwards compatibility for all of the Windows 7 / 8 nVidia users but to not support a next-gen API like Mantle in 2016 already is lame - especially when the support was previously built in to their engine.
Probably they will support vulkan/dx12 for bf5/bc3 . which is pretty much same thing as mantle.

For mirrors edge ? whatever nvidia forces them to do. so most likely good dx11 and broken dx12 patch later. unless pascal performs good on dx12.
 
Does it not support DX12?? DICE has always been leading on designing their engines to take advantage of the latest features in GPU APIs. Considering they've tweeted that that would have loved to see DX12 be mandatory by christmas I was expecting to see Mirrors Edge and any other releases this year on frostbite to use DX12 along side DX11 just like they did Mantle along with DX11.
 
It's even stranger that they have to port anything over to DX12 and that it will take so long, since I've heard from plenty of people here that DX12 is Mantle...

Weird.
 
It's even stranger that they have to port anything over to DX12 and that it will take so long, since I've heard from plenty of people here that DX12 is Mantle...

Weird.

i actually heard people said dx12 is based on mantle or has lots of code. who is right :sneaky:
 
If SW:BF and PvZ:GW2 both didn't have Mantle (which they didn't) then it's pretty obvious the new feature development in Frostbite since BF:H was done on DX11. I don't doubt they'll reuse applicable code when it comes time to move DX12 or Vulkan.

But no, not having dx12 instantly in their next game definitely means Mantle and DX12 had nothing to do with each other. 🙄
 
Well, this game runs like ass.

https://www.youtube.com/watch?v=Jp_AfW9slsI

If you're a fan of horrible stuttering on an i5/970, this game is for you! I can see why it got delayed, hopefully the issues are ironed out before launch.

Honestly, all of these new games have been pretty terrible on performance for one or both vendors.
Again, we need to require from game devs that BOTH gpu camps run at a decent frame rate. This whole "I want my team to win" at the expense of the whole game is getting ridiculous.
 
Honestly, all of these new games have been pretty terrible on performance for one or both vendors.
Again, we need to require from game devs that BOTH gpu camps run at a decent frame rate. This whole "I want my team to win" at the expense of the whole game is getting ridiculous.

This is what consumers wanted! The fragmentation has begun!!!

Been playing a bunch of PS3 or older ports finally seeing PC versions. I got no issues, yet 😀
 
Does it not support DX12?? DICE has always been leading on designing their engines to take advantage of the latest features in GPU APIs. Considering they've tweeted that that would have loved to see DX12 be mandatory by christmas I was expecting to see Mirrors Edge and any other releases this year on frostbite to use DX12 along side DX11 just like they did Mantle along with DX11.

I suspect the game will support dx12 at launch. These results are the dx11 version. They said around september last year that frostbite 3 already supported dx12. Their recommended settings say windows 10, which would not be necessary without a dx12 requirement. With that recommendation they put a 280x with a 970, which again suggests dx12.

But I don't expect physx works with dx12 yet and if it did I'd expect nvidia cards to self destruct running both at the same time.
 
I suspect the game will support dx12 at launch. These results are the dx11 version. They said around september last year that frostbite 3 already supported dx12. Their recommended settings say windows 10, which would not be necessary without a dx12 requirement. With that recommendation they put a 280x with a 970, which again suggests dx12.

But I don't expect physx works with dx12 yet and if it did I'd expect nvidia cards to self destruct running both at the same time.
dx12 and gameworks features dont really mix together
 
Back
Top