Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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.
Yet the makers have said they have spent loads of time on there dx implementation and very little time with mantle. It's been known for a long time that dx has it's limitations. Maybe this and mantle are showing just how bad dx really is.
You dont know but you still post for what? You dont know as you said so stop posting about the same subject again and again.
They are already so many games that cant pass 30-50% gpu usage. Try sc2,total war,company of heroes,mmos.If the dx11 thread cant keep up with the draw calls no matter what you have you will never gonna have higher gpu usage.Dx11 use a thread for its own work so the bottleneck is there. Even if your engine is multithread you will gonna get a draw call bottleneck or dx11 thread bottleneck call it w/e.Dx11 creates a data structure thats why it needs an additional thread vs mantle.Too many draw calls and you know the rest
Ok, I think I have got the gist of what you are saying.
How come when I change deferred contexts to enabled (switching the settings in profiles to 1), my GPU usage went to 80% and is hammering all the Mantle scores?
If they dont have DC in their graphic engine which i doubt then its gonna help.But its not optimal for a engine like frostbite. I dont know yet about this one
Proof of those frames? Not that I doubt you but looking through here, I couldn't see any (maybe I missed them).
If the most I can get my GPU to is 40% (without having to mess about), I can't see how having SLI working will help?
Doesn't it seem strange that Oxide have this bench and state that they have spent all this time on DX and only a fraction on Mantle and yet, I can change a 0 to a 1 and get double the performance I previously had?
This is why I call BS to this bench and claim it is aimed at making Mantle look good (which isn't a bad thing) but at least do it honestly.
Just to update, I am not after specifics but I must reiterate that you put "official entry" as the heading of your score else it will get mixed up with the countless other scores that have no relevance in this thread. Please follow the outlined rules from post #1
I don't know why your now pleading dumb, you know why I quoted you.
All I'm getting at is your result isn't indicative of SW DX performance, be it changing config files to boost performance or a random result anomaly, essentially though your result doesn't add up.
Seriously... What are you on about? Read the rules run the bench report your clocks. It isn't rocket science and if you are accusing me of cheating, don't be a coward and hide, just come out and say it.
If I was going to say you were cheating, I'd just say it outright, I've questioned your result, gave you the benefit of the doubt, config files have been getting modified from almost launch, asking if mistakes have been made, you are being very vague to say the least.
Well I suggest you drop it then. Nothing to see here and certainly no cheating. You have had a couple of digs at me and accusations but unless you have any proof, give it a rest.
Not to accuse anyone of anything, to take your point it is very easy to edit the config file and boost your score by ~40% and it not show in the results text.
For example. calculate the batches and Frame ecte... its right.
This bench needs to be toughened up, its far to easy to hack.
== Configuration ==========================================
API: Mantle
Scenario: ScenarioFollow.csv
User Input: Disabled
Resolution: 1920x1080
Fullscreen: True
GameCore Update: 16.6 ms
Bloom Quality: High
PointLight Quality: High
ToneCurve Quality: High
Glare Overdraw: 16
Shading Samples: 64
Shade Quality: Mid
Deferred Contexts: Disabled
Temporal AA Duration: 16
Temporal AA Time Slice: 2
Detailed Frame Info: Off
===========================================================
== Results ================================================
Test Duration: 360 Seconds
Total Frames: 30840
Average FPS: 85.67
Average Unit Count: 4797
Maximum Unit Count: 6184
Average Batches/MS: 303.46
Maximum Batches/MS: 1422.67
Average Batch Count: 3806
Maximum Batch Count: 20944
===========================================================
This bench is clearly inconsistent and it shows with your own scores Humbug. You get 7 fps more with a 290 over a 7870, and this clearly shows how inconsistent and over the place the bench is.
I don't for one minute feel any of the scores are cheating and there is nothing to be won, so can't see any reason why anyone would cheat.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.