When running the Xonotic open-source first person shooter with its maximum visuals, the R9 290 and HD 6870 continued to deliver greater frame-rates with DRI3 enabled.
Announcement
Collapse
No announcement yet.
DRI2 vs. DRI3 Radeon Linux OpenGL Performance
Collapse
X
-
- Likes 1
-
Originally posted by profoundWHALE View PostHe likes to benchmark real world use (aka, the average user) meaning only flags that would be default. Anything special AFAIK would mean something like this which just has DRI2 vs DRI3
Openarena 0.8.8 benchmark has nothing to do what user will get by default from that game, etc...Last edited by dungeon; 02 November 2015, 02:43 PM.
Leave a comment:
-
Originally posted by dungeon View PostThere is cl_maxfps cvar in Xonotic to cap yor frame rate to desired value.
~ to open the console
max_fps 65
And it'll be easier to maintain that because your GPU won't try to render 200+ fps in an empty room. I say 65 because it'll always be a little bit less than that which definitely gives me tearing.
Originally posted by dungeon View PostBtw. there is cl_curl_enabled which Michael should disable in phoronix benchmark, to not benchmark network with Xonotic and also to not have that update now message to flow around
Originally posted by dungeon View Postedit: Yeah problem with traditional vsync is if let say your screen is 60Hz, but on moment fps rate goes at least 1 fps bellow that value then it tries to vsync again to 30Hz likely which introduce throttling and that makes things looks even worse.
Anyways, regarding the performance, it's always good to see improvements with no regressions.Last edited by profoundWHALE; 02 November 2015, 01:15 PM.
Leave a comment:
-
Originally posted by Espionage724 View PostI was messing with Xonotic last night; leaving FPS capped at 60 with vsync had my FPS dropping well below that at times. Disabling vsync (vblank_mode=0) easily allowed Xonotic to maintain above 60 fps most of the time.
Btw. there is cl_curl_enabled which Michael should disable in phoronix benchmark, to not benchmark network with Xonotic and also to not have that update now message to flow around
edit: Yeah problem with traditional vsync is if let say your screen is 60Hz, but on moment fps rate goes at least 1 fps bellow that value then it tries to vsync again to 30Hz likely which introduce throttling and that makes things looks even worse.Last edited by dungeon; 02 November 2015, 10:53 AM.
Leave a comment:
-
Originally posted by Espionage724 View Post
I was messing with Xonotic last night; leaving FPS capped at 60 with vsync had my FPS dropping well below that at times. Disabling vsync (vblank_mode=0) easily allowed Xonotic to maintain above 60 fps most of the time.
Leave a comment:
-
Guest repliedOriginally posted by Adriannho View PostFor me on arch man radeon | grep DRI gives:
Code:Enable DRI2 page flipping. The default is on. Pageflipping is supported on all radeon hardware.
Originally posted by duby229 View PostAnd this article proves exactly why rendering way above screen refresh is stupid. It doesn't matter. I'll bet you that if time was taken to configure the game for best settings to get close to 60hz average they would perform exactly the same. Which means that what has been taken as overall performance has been wrong all along.
The only metrics that make sense measuring are those that you'll be playing at.Last edited by Guest; 02 November 2015, 09:55 AM.
Leave a comment:
-
Originally posted by boffo View PostI tried this DRI 3 option. With team fortress 2 the system is stable, but firefox freezes with videos. On AMD trinity
Originally posted by Adriannho View PostFor me on arch man radeon | grep DRI gives:
Code:Enable DRI2 page flipping. The default is on. Pageflipping is supported on all radeon hardware.
Originally posted by duby229 View PostAnd this article proves exactly why rendering way above screen refresh is stupid. It doesn't matter. I'll bet you that if time was taken to configure the game for best settings to get close to 60hz average they would perform exactly the same. Which means that what has been taken as overall performance has been wrong all along.
The only metrics that make sense measuring are those that you'll be playing at.
Leave a comment:
-
And this article proves exactly why rendering way above screen refresh is stupid. It doesn't matter. I'll bet you that if time was taken to configure the game for best settings to get close to 60hz average they would perform exactly the same. Which means that what has been taken as overall performance has been wrong all along.
The only metrics that make sense measuring are those that you'll be playing at.
- Likes 1
Leave a comment:
Leave a comment: