I don't really care for 3D performance but this is ridiculous. Why is the performance gap that big ? I mean WTF ? They do have paid developers after all.
Still I do appreciate having a stable open source driver.
Pathetic at best.
Basically every oss driver is not for "real" gamers. I would not worry much about that if amd would not drop support for older cards for fglrx so soon. Ok, nvidia considered now dx9 cards as legacy but most likely they will update the 304 driver series to newer kernels/xservers still for a while. fglrx already dropped dx10 cards before having at least 1 driver you could use without that many bugs. 12.11 beta was a step in the right direction, maybe not perfect but better than the rest - but dx10 card users will stay with 12-6 beta forever, with all it's bugs - and even for systems with hybrid hd 4200/5400 a new driver does not work.
So I benchmarked Reaction Quake 3 on r600g. Here are the results:
With Phoronix Test Suite: 19 fps
Without Phoronix Test Suite: 121 fps
I wonder what PTS is doing differently.
Just in general, I noticed the performance doesn't scale well with OpenGL effects compared to Catalytst. Turning on bloom alone in the new version of openarena is enough to slaughter the framerate by 1/8th on r300g. I don't have the benchmarks with Catalyst and bloom, but I'm pretty sure it doesn't get slaughtered by 1/8th.
The less OpenGL effects you stack up, the closer the open source driver gets to Catalyst.
I noticed PTS likes to turn on every graphics option, including non-default graphics options. So pay attention to the graphics option as even a single option in there can sometimes absolutely slaughter the framerate of the open source driver compared to Catalyst.
It's not that the open source driver is a lot slower, rather it's just a tiny bit slower at some effect and then that effect is getting multiplied by 100x per second which adds up quickly. Turning off the graphics option and the framerate increases multiple fold. For some games, it's just a matter of finding which switch is killing your framerate with the open source driver, and it's almost always an optional graphics option.
Last edited by Sidicas; 10-30-2012 at 11:56 PM.
radeonsi can run piglit reliably with it now. It fixes hundreds of tests and prevents many more from crashing.
I wonder what the purpose of 300 fps would be. As far as I have heard the human eye will only register up to 60 fps - so perhaps a better measure would be "at what resolution does the driver performance sink below ideal fps".
This might give a different readout than just completely un-needed fps that do not give any noticeable difference for the human user.
Last edited by efikkan; 10-31-2012 at 02:19 AM.