• 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.

Star Swarm - Oxide bench thread

Did GPU usage go up? Could be a case of giving the cpu more work to do brought frames down but the gpu may have been rendering more. Worth a check.

No it didn't, it still sat at 40% ish. 4.625Ghz is plenty to run a pair of Titans in any other game and keep them at 99% but not this Oxide demo. I am not fussed but does seem strange that only this one game does that.
 
Did this not turn out as you hoped? not updating this thread any more Gregster? :p:D

I don't mind updating it, I just would prefer a consistent bench, which this isn't. One person gets more units than others, hardly seems fair now does it?

Ohhhh and just to add part of the rules for those who may have missed it ;)

Also, all entries MUST have your CPU and your GPU and be titled "Official entry" Any entry will be ignored if it doesn't follow that criteria. That is starting from 3pm Saturday 1st Feb 2014.

I don't see that on any of the entries. It just makes it easier for me to keep track of what is done with the settings in the OP (thanks DamnedLife) and what is just a random run. I have no bias in any of the bench threads and love to see people pushing their hardware but simple rules need to be set.
 
Last edited:
Just a suggestion to save the thread from failure. :)

I am not sure why you and Humbug are getting all worked up about it. If you both bothered to look, there is entry after entry and I have no idea if they were run with the file in the OP or just a random file. Most of them don't even say what GPU was being used. It is nigh on impossible to work out, hence the reason for adding "official entry" to the title (like Andybird has) and that makes it much easier for me to sort out.

Relax the rules? It isn't that hard and I am not requiring GPU-Z/CPU-Z screen shots and a screenie of the text file or a video of the run.

Ohh and how is your Tomb Raider bench thread going Matt?
 
Last edited:
Can this thread be locked, then someone else can start it again without having to so accurately follow the 'rules'?

I was hoping to get some useful information out of this thread, but, again, down to some of the vocal minority has brought this section down to a laughing stock.

No need for locking and I will alter the rules to make them simpler for everyone to follow :)
 
Official entry

CPU 3930K @ 4.625Ghz - GPU GTX Titan at 1015Mhz

===========================================================
Oxide Games
Star Swarm Stress Test - ©2013
C:\Users\Greg\Documents\Star Swarm\Output_14_02_08_2048.txt
Version 1.00
02/08/2014 20:48
===========================================================

== Hardware Configuration =================================
GPU: NVIDIA GeForce GTX TITAN
CPU: GenuineIntel
Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz
Physical Cores: 6
Logical Cores: 12
Physical Memory: 17122181120
Allocatable Memory: 8796092891136
===========================================================


== Configuration ==========================================
API: DirectX
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: Enabled
Temporal AA Duration: 16
Temporal AA Time Slice: 2
Detailed Frame Info: Off
===========================================================


== Results ================================================
Test Duration: 360 Seconds
Total Frames: 17011

Average FPS: 47.25
Average Unit Count: 4140
Maximum Unit Count: 5309
Average Batches/MS: 851.57
Maximum Batches/MS: 4348.98
Average Batch Count: 20228
Maximum Batch Count: 129482
===========================================================
 
Rules are nothing new :confused:

Who spilt the milk?

I have made a step by step guide in the 1st post for those who struggled with what I thought were pretty straight forward rules.

Ok guys, post your bench results here for the Star Swarm - Oxide benchmark.

Rules.

1. List your GPU and CPU and what the clock speeds are.
2. Add "Official entry" to the top/title of your post.
3. Users can alter the deferred contexts number to 1 (from 0) if you wish (steam/steammaps/common/star swarm benchmark/assets/settings_Extreme.ini
4. Click Follow and click Extreme and then choose either "Start Mantle" or "Start D3D" (as shown in the spoiler)
5. Copy and paste you complete results with the rest of the info.

7c36fe284d9ba561ace25058cf61120b.jpg

Link to how your entry should look like.
http://forums.overclockers.co.uk/showpost.php?p=25813564&postcount=260

Any questions, fire away and enjoy :)

Easy enough guys?
 
Problem with lots of results being posted and not meeting rules imo makes it akward for whatever benchmark thread there is,, All these people give up their own time to sift through the thread and adding to the op just makes it easier i would think for the OP if there a way to see whats actually a result someone wants entered or just someone one quoting someone else etc
Btw thats for all benchmark threads not just this one i appreciate the time any of the guys/girls take keeping these updated

Thanks.

I have no issues with any of the other bench threads I do and the rules are just as simple. People quoting peoples scores and people changing settings and saying this is what I got made it a complete nightmare.

Not sure why people are finding the rules hard? I thought they were pretty basic and then I changed them to make them even easier and I am still doing it wrong apparently.

Rules like CPU/GPU are fine, but not putting responses to the thread in the list just because the hadn't used the correct title in the response, or other nonsensical reasons - just makes the OP look like a big troll..

//edit..

Then he goes on to totally ignore the requested additional information in the list and just go by pure FPS.

Thanks for your input. I am more of an Ogre than a Troll btw.
 
Last edited:
No idea. 6 minutes bench run and I took the dog for her last walk and came back to that result. No overclocks except for the CPU. I changed deferred contexts to 1 but I would expect you to score similar or more with your newer CPU.

And for sure, I can add the CPU's and GPU's (I probably should have done that but was trying to get the thread back on track ASAP).

Edit:

It is going to be hard to tell what GPU clocks are for nVidia guys (unless they are on a non boosting bios).
 
Last edited:
Official entry

CPU 3930K @ 4.625 - GPU at 1015Mhz

===========================================================
Oxide Games
Star Swarm Stress Test - ©2013
C:\Users\Greg\Documents\Star Swarm\Output_14_02_08_2229.txt
Version 1.00
02/08/2014 22:29
===========================================================

== Hardware Configuration =================================
GPU: NVIDIA GeForce GTX TITAN
CPU: GenuineIntel
Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz
Physical Cores: 6
Logical Cores: 12
Physical Memory: 17122181120
Allocatable Memory: 8796092891136
===========================================================


== Configuration ==========================================
API: DirectX
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: Enabled
Temporal AA Duration: 16
Temporal AA Time Slice: 2
Detailed Frame Info: Off
===========================================================


== Results ================================================
Test Duration: 360 Seconds
Total Frames: 26339

Average FPS: 73.16
Average Unit Count: 4016
Maximum Unit Count: 5358
Average Batches/MS: 829.87
Maximum Batches/MS: 3793.68
Average Batch Count: 12461
Maximum Batch Count: 64663
===========================================================

lol. Watched it this time and thought I was going to be much lower, as it was down to 18fps in one place for quite some time. :D
 
I know this is a complete pain in the bum, but would it be a good idea to include avg. batches in the required info and in the tables - the FPS alone is massively skewing the data

For table position you could do batches divided by fps = benchscore (or multiplied, not sure what works out fair)

The whole bench is a pain in the bum :D I will give that some thought and see what else people post. Not sure on batches and units but I am sure something can be done to make it a little fairer.
 
Been having a fiddle to use the results and come up with a fair average using all the averages but nothing is working out for me. I am useless at math, so I am open to suggestions.
 
Its not a game though is it. Its a benchmark designed to showcase the limitations of D3D and show it for the inefficient API it is when compared to Mantle. :)

Ahhh but if it is incorporated into a game (Of which I am sure the nitrous engine is for), I will be avoiding anything that uses it.

If it is purely a showcase for Mantle vS DX, then it is fixed. AMD paid for it and are showing the results they want you to see ;)
 
You have absolutely no idea on coding for DX or Mantle Matt/Humbug (as I don't) but feel you know enough to trust that DX is so badly optimised that it can't get my GPU running faster than 40% (when left on default settings) and that is with my CPU at 5Ghz (and that only reaches 30% usage on a couple of cores).... Probably best you are out to save embarrassing yourself.
 
Back
Top Bottom