• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Upcoming games to support Mantle

Rusty you not fancy running that frametimes test bud?..

->

I can't really be bothered mate. I'm not really that into benchmarking to be honest but I'm sure somebody else will take you up on your offer.

Frametimes aren't the be all and end all of 'smoothness' anyway. There's various things which drive how 'smooth' your game is.
 
Whatever you make of it they give you a reason.

Which is more than just sitting there saying "i don't see why it needs Mantle, it doesn't need Mantle"

If to you anything contributed in answering that is "just PR" then frankly your beyond reason.

You literately responded to it with PR buzz to build hype for the game. So calling it as such doesn't make me beyond reasonable.

And I don't do the "Why does it need Mantle" either. Mantle in CIV will help with the overheads that DX has to put it as simple as possible.
 
->



Frametimes aren't the be all and end all of 'smoothness' anyway. There's various things which drive how 'smooth' your game is.

Completely agree bud, but they play a big part, no worries though, just would have just been nice to see what sort of frametimes your getting.

I'm sure another member will help.
 
47 Developers currently working with Mantle, they have to come from somewhere.

As for Ubisoft, they were 'in bed with AMD' before AC4, no reason why a developer can't use anyone's tech if they want to. Thief is built on the Unreal engin, another Nvidia bed buddy and probably the most well implemented Mantle game yet.

There are what 4 Mantle games? 3 of which use the same engine and thus Mantle implementation?
So saying Thief is the best implementation so far isn't really saying that much is it?

Also, you were offering help with BF4 under Mantle?
I could do with some help running it on my 7950CF setup. I can stop the issue by lower the graphics settings but that seems sorta silly. So if you can stop it hitting the VRAM limit without changing the settings that would be very useful.
It'd be also be really useful if you could stop it crashing after 10 seconds when I launch the game using the Mantle API. I can get around it by Alt-Tabbing to desktop and back again (before it crashes) but that's not ideal. DX works fine btw.
On this topic, I've said before, I've used BF4 in DX and Mantle and don't notice the difference in Frametimes. Well until Mantle hits the VRAM limit and grinds to a halt.

This FCAT thing, that was used originally to show the frametime issues that AMD had?
So at this time did all the AMD users go "This makes so much sense and is why I can't enjoy gaming on my Crossfire setup. Playing on my friend's Nvidia SLI setup is a thousand times better" or did they play it down? And now it's the other way around frametimes are a real thing and are suddenly super important?
 
There are what 4 Mantle games? 3 of which use the same engine and thus Mantle implementation?
So saying Thief is the best implementation so far isn't really saying that much is it?

Also, you were offering help with BF4 under Mantle?
I could do with some help running it on my 7950CF setup. I can stop the issue by lower the graphics settings but that seems sorta silly. So if you can stop it hitting the VRAM limit without changing the settings that would be very useful.
It'd be also be really useful if you could stop it crashing after 10 seconds when I launch the game using the Mantle API. I can get around it by Alt-Tabbing to desktop and back again (before it crashes) but that's not ideal. DX works fine btw.
On this topic, I've said before, I've used BF4 in DX and Mantle and don't notice the difference in Frametimes. Well until Mantle hits the VRAM limit and grinds to a halt.

This FCAT thing, that was used originally to show the frametime issues that AMD had?
So at this time did all the AMD users go "This makes so much sense and is why I can't enjoy gaming on my Crossfire setup. Playing on my friend's Nvidia SLI setup is a thousand times better" or did they play it down? And now it's the other way around frametimes are a real thing and are suddenly super important?

Yeah but when are you going to use them 290s in Battlefield with mantle and give us feedback?
 
Why's it matter? Saying "My 290's work fine" doesn't change the problems that do exist with other series, bearing in mind the 290/290X owners will be in the minority

Because saying he don't notice any difference between mantle and directx when running GPUs that are known to have issues don't make sense. It makes sense to try the 290's and feel the difference, and then you can compare.
 
Completely agree bud, but they play a big part, no worries though, just would have just been nice to see what sort of frametimes your getting.

I'm sure another member will help.

+1

I remember when the shoe was on the other foot. Frame times and then FCAT were what decided how smooth your gaming experience was. Now it does not not matter and it's i see no difference. The graph's that were so in favour of Nvidia now haunt them.
 
Last edited:
As an AMD user i have not played a single Mantle game yet, none of the current ones interest me and on the list of upcoming games only GTA V interests me and even that is not confirmed yet.
 
Yeah but when are you going to use them 290s in Battlefield with mantle and give us feedback?

So, assuming I didn't have my 290 CF setup, your solution to this Mantle issue is to buy new graphics cards?

If a game played fine on an Nvidia card and barely worked on an AMD card and the developer said they wouldn't be fixing it, there are a lot of people that wouldn't be happy with the solution "Buy 780Ti's to make the game run ok". But "Buy AMD 290s" is a perfectly fine solution in this instance?

Also, where is this "known issues" coming from? Link?
Thracks has said that the 7000 series cards have parity with the 290 cards as far as Mantle goes, so you're saying that the Frostbite engine treats GCN 1 different to GCN 1.1? Why would it do that? Does Mantle mean that they need a separate rendering path for each architecture or each graphics card model (That's gonna be a lot of work in the future as more cards support it)? Or did they purposely sabotage performance on 7000 series cards to help AMD GPU sales?
 
So, assuming I didn't have my 290 CF setup, your solution to this Mantle issue is to buy new graphics cards?

If a game played fine on an Nvidia card and barely worked on an AMD card and the developer said they wouldn't be fixing it, there are a lot of people that wouldn't be happy with the solution "Buy 780Ti's to make the game run ok". But "Buy AMD 290s" is a perfectly fine solution in this instance?

Also, where is this "known issues" coming from? Link?
Thracks has said that the 7000 series cards have parity with the 290 cards as far as Mantle goes, so you're saying that the Frostbite engine treats GCN 1 different to GCN 1.1? Why would it do that? Does Mantle mean that they need a separate rendering path for each architecture or each graphics card model (That's gonna be a lot of work in the future as more cards support it)? Or did they purposely sabotage performance on 7000 series cards to help AMD GPU sales?

Because amd said when mantle first came out about mantle and 7000 series needing more work. Have they said in any patch notes or driver since 7000 series now working? I don't think they have so therefore they not had the issue fixed.
And no I wouldn't say buy another gpu I would tell you to stick with directx till either it does get fixed or you do one day upgrade.
 
Thracks on this forum said that the GCN 1 (7000 series) and GCN 1.1 (290s) have parity in Mantle. Which I take to mean they are supported to the same level.

Unless you know more than Thracks about this and are calling him a liar?
 
I realise this has probably been gone over many times, but what exactly is the problem you're having with mantle/BF4, apart from the obvious vram thing on the 79's, Googs?

Apart from that one thing, I personally don't have any issues with it on either 290 or 7970CF FWIW.
 
Thracks on this forum said that the GCN 1 (7000 series) and GCN 1.1 (290s) have parity in Mantle. Which I take to mean they are supported to the same level.

Unless you know more than Thracks about this and are calling him a liar?

First I have heard, am going by release notes from both bf4 and driver.
Go and look at the first patch notes when mantle came out look at the known issues and then look at the notes after each release you see.
I also had 7950s and mantle was also not working for me, changed to 290s and it now works fine so how can that be if there supposed to be the same?
 
+1

I remember when the shoe was on the other foot. Frame times and then FCAT were what decided how smooth your gaming experience was. Now it does not not matter and it's i see no difference. The graph's that were so in favour of Nvidia now haunt them.

Don't act like such a child.

I never once said that the FCAT graphs were the be all and end all. In fact I said numerous times that my AMD CF set up was on the whole identically smooth to my nVidia SLI set up except in certain games and then in triple screens. If AMD made improvements on the back of what the FCAT graphs showed then that's good for AMD users isn't it? I remember talking to Matt about it over email and said the whole thing was a bit 'meh'.

What do you personally think about it when your only experience of the subject matter is what you read on the internet?
 
I realise this has probably been gone over many times, but what exactly is the problem you're having with mantle/BF4, apart from the obvious vram thing on the 79's, Googs?

Apart from that one thing, I personally don't have any issues with it on either 290 or 7970CF FWIW.

The VRAM thing and the fact it crashes after 10 seconds unless I alt-tab to the desktop and back. Doesn't matter if you're in a menu or in the game, once the game has loaded it will happen, doesn't matter what server.

Obviously the VRAM thing means my fps drops to near single digits (if not single digits, I seem to recall seeing a 3) and the game stutters and becomes unplayable. I don't think I've recorded any frametimes while it's happening, but I'll try to remember to so someone can make a graph.
 
First I have heard, am going by release notes from both bf4 and driver.
Go and look at the first patch notes when mantle came out look at the known issues and then look at the notes after each release you see.
I also had 7950s and mantle was also not working for me, changed to 290s and it now works fine so how can that be if there supposed to be the same?

I'd suggest you ask Thracks (wouldn't call him a liar to his face though).
Does every Mantle tweak get mentioned in the patch notes then?

As LtMatt would say, given the choice between you and an AMD employee I'll believe the AMD employee in this case regarding AMD's Mantle.
 
That's a very strong lineup of triple a games AMD have bagged themselves thier. The only I doubt is the Crytek game as it may not see the light of day (for obvious reasons).
 
Don't act like such a child.

I never once said that the FCAT graphs were the be all and end all. In fact I said numerous times that my AMD CF set up was on the whole identically smooth to my nVidia SLI set up except in certain games and then in triple screens. If AMD made improvements on the back of what the FCAT graphs showed then that's good for AMD users isn't it? I remember talking to Matt about it over email and said the whole thing was a bit 'meh'.

What do you personally think about it when your only experience of the subject matter is what you read on the internet?

:confused:

What makes you think my post was aimed at you. I was just stating a fact from a year or two ago. I suggest you grow up yourself.

It's funny though as you base your results on a friends machine when i myself have access to much more powerful machines myself.
 
Back
Top Bottom