Especially those of you who have performance problems are asked to run this. The test can, on older systems, take a few hours, so I'd recommend running it over night.
It will generate a log file. Please send me that log file (e.g. via forum PM) and also the following system details:
- system name
- CPU
- CPU clock frequency
- number of CPU cores
- RAM size
- operating system
- architecture (32bit or 64bit)
so I can add the data to the wiki page above. Alternatively, if you have editing permissions, you can add yourself to the wiki with the required data.
When we have this info, our goal is to describe hardware requirements of Xonotic. So please help us by providing benchmark results! Thanks.
rocknroll237
desktop
i7 960
@3.2ghz
4 cores
6gb RAM
GL_VENDOR: ATI Technologies Inc.
GL_RENDERER: ASUS ARES
GL_VERSION: 4.1.11161
Windows 7
64 bit
(How on Earth did a GTX 560ti beat my Ares? Is it because I'm running Windows and the 560 was on Linux? Also, why did the 6770 score so high? My Ares should eclipse it! I don't have the AMD app profiles installed, maybe that's why... WTF was someone thinking of when they benched a 6970 with a dual core Athlon and 2gb RAM?)
01-30-2012, 02:41 PM (This post was last modified: 01-30-2012, 02:43 PM by SavageX.)
@rocknroll237
Notice that all top spots are currently taken by Nvidia cards. Your card is clearly usually faster than some of those Nvidia cards that score better than your setup, so I'd guess the ATI driver somehow runs into a brickwall with Xonotic. Compare, for example, your beastly setup (much stronger CPU, much stronger GPU) with my old Phenom II X4 945 and very cheap 5670 card - on normal settings we're not very much apart.
Ahh, yes. With all 3 AMD gpus lined up in that graph I can see that the benchmarks are very similar. It seems that the AMD drivers aren't as strong as Nvidias.
Maybe the Xonotic devs could get AMD to optimise the drivers for Xonotic when it gets a bigger following.
01-30-2012, 06:18 PM (This post was last modified: 01-30-2012, 07:02 PM by Lee_Stricklin.)
EDIT (Again): OK, ran the tool and uploaded the log file. divVerent you should find the file if you check your private messages. Anyway the below information will still be left in tact in case it has any use.
EDIT: I messed this up, I was doing time demo on the big keybench. Will update these as soon as I use the actual benchmark tool included with the game.
System specs
-----------------------------------
Operating System: Ubuntu 10.04 64 bit (partially upgraded and pulseaudio has been stripped if you need the details)
Nvidia Driver Version: 195.36.24
Xonotic version: Autobuild (January 30 2012 release)
CPU: AM2+ Socket AMD Phenom II X4, 3GHz
RAM: 4 GB (2GB X 2) DDR2 1066MHz
GPU: NVIDIA Geforce 9800GTX, 1GB, 256 bit
Benchmarks
-----------------------------------
Frame rate listed from low/average/max. Old configurtation files were removed and Xonotic autobuild was updated immediately before these tests were done. Resolution is standard for PC gaming (1920 X 1080).
01-30-2012, 09:07 PM (This post was last modified: 01-30-2012, 09:10 PM by Lee_Stricklin.)
(01-30-2012, 07:34 PM)theShadow Wrote: I found an issue, and it's rather a serious one.
for OSX, it defaults to trying to run in full screen, and if you recall, xonotic won't run in fullscreen on lion.
sooooo... yeah.
You can get the same result by doing the following (basically copying what I initially did except at a lower resolution):
Remove your config file from the hidden .xonotic directory. Set the game resolution to 1024 X 768 and then run the big keybench demo in time demo mode using each effects preset available. At the end of each run just pull down the console and write down the frame rates for each setting.
To use the Ultimate and OMG settings you'll have to punch into your console:
(01-30-2012, 07:34 PM)theShadow Wrote: I found an issue, and it's rather a serious one.
for OSX, it defaults to trying to run in full screen, and if you recall, xonotic won't run in fullscreen on lion.
sooooo... yeah.
You can get the same result by doing the following (basically copying what I initially did except at a lower resolution):
Remove your config file from the hidden .xonotic directory. Set the game resolution to 1024 X 768 and then run the big keybench demo in time demo mode using each effects preset available. At the end of each run just pull down the console and write down the frame rates for each setting.
To use the Ultimate and OMG settings you'll have to punch into your console:
exec effects-ultimate.cfg
exec effects-omg.cfg
You really should rather use the benchmark script to ensure the configuration is the right one. Note that we also run the demo 4 times, and use the median of the last 3, to get shader compiling and measurement errors out of the equation.
My results for two test systems zipped (text files compress really well). Configurations given in archive names.
PS. for the most part biggest performance problems I have, are when I minimize and restore the game. Applying video settings immediately in options helps.
(01-31-2012, 12:09 PM)rafallus Wrote: PS. is there a way to sort this differently? Best idea would be to sort by ULTIMATE results, now you have 560 Ti below 9800GT in one case (!)
Normal settings are a much closer approximation to what people actually run than ultimate. The goal is to determine system requirements (i.e. what systems will deliver enjoyable gameplay at default settings), not (primarily) to rank individual system components (choose "omg" and you're testing the CPU, choose "ultmate" and you're testing the GPU - we need a mix of those. The default settings are sitting nicely in-between).
As for sorting, I agree the wiki is not an optimal solution for that yet. We will find a better one eventually, that will provide sorting controls to the user too.
02-03-2012, 08:16 AM (This post was last modified: 02-06-2012, 03:33 AM by Sless.)
Addition:
My HP nc6000 didnt deliver any benchmark-result. It simply froze after ~20mins. No idea what's causing this - the only guess i have is the 32MB graphic-card .
The even lower equipped subnotebook would then be a waste of time.
Stats of my nc6000:
Name: Troll
Win XP Prof. x32
Pentium M 1.6GHz
512MB RAM
ATI Mobility Radeon 9600 @32MB
(Aborted) Benchmark: Link
System six:
Name: FUmachine
WinXP Pro x32
Athlon 64 X2 Dual
Core Processor 5000+
2.66GHz, 2GB RAM
Graphic: GeForce 6100 nForce 405 --> 256 MB
Benchmark: Link
System seven:
Name Kiste2
Win XP Prof. x32
Intel Core 2 Duo
@ 1.86 GHz
1GB RAM
Graphics: Intel GMA 950 @256MB
Addition: HP nc6320
Benchmark: Link
One more is still benchmarking...
... and finished after 36 hours or so. Dont know what caused this tbh.
(Yes, after retrying it began to stutter again - needing 10 secs for ingame one second )
System eight:
Name: WrkBox
Win XP Prof. x32
Intel Core 2 Duo
T9600 @ 2.8 GHz
2GB RAM
Graphics: Intel 4 Series Express Chipset Family @ 1024MB
Addition: Dell Latitude e6400
Benchmark: Link
My HP nc6000 didnt deliver any benchmark-result. It simply froze after ~20mins. No idea what's causing this - the only guess i have is the 32MB graphic-card .
The even lower equipped subnotebook would then be a waste of time.
System six:
Name: FUmachine
XP Pro x32
Athlon 64 X2 Dual
Core Processor 5000+
2.66GHz, 2GB RAM
Graphic: GeForce 6100 nForce 405 --> 256 MB
Benchmark: Link
<Samual> I am the most unprofessional developer ever
<bluez> halogene, you make awesome music, but you have no clue about ctf.
<Halogene> I didn't know mappers include some mysterious waypoints so members of the BOT clan can navigate a map?
<divVerent> if you don't pay for a premium account, your movement speed is limited to 100qu/s