Bug 99995 - Dirt showdown very low fps (~3fps) after update mesa
Summary: Dirt showdown very low fps (~3fps) after update mesa
Status: NEW
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/nouveau (show other bugs)
Version: 17.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Nouveau Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 77449
  Show dependency treegraph
 
Reported: 2017-02-27 23:47 UTC by Kevin Puertas
Modified: 2018-05-01 14:50 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Puertas 2017-02-27 23:47:59 UTC
Hi, I updated from mesa 13.0.x to 17.0 and Dirt showdown in mesa 13 has around 25 fps and with mesa 17 has about 2fps..
I tried in ArchLinux and Fedora (fedora 26 mesa builds), and is the same, mesa 13 works a lot better in this game

My computer is a i5 4690 and has a Nvidia GTX 750

Mesa 17: CPU is 1 core 100% and the rest about 10%
Mesa 13.0.4: CPU is about 15-20% all cores

Maybe mesa is taking all work to CPU?
Comment 1 Ilia Mirkin 2017-02-28 00:22:00 UTC
One difference is that 17.0 has GL 4.3 enabled for Maxwell (e.g. GTX 750), which perhaps causes the game to choose a different path, thus not really be directly comparable. Try it with

MESA_GL_VERSION_OVERRIDE=4.1

which will get it back to the same GL version that was available with 13.0. Or try it with

MESA_EXTENSION_OVERRIDE='-GL_ARB_shader_image_load_store -GL_ARB_compute_shader'
Comment 2 Gregor Münch 2017-02-28 09:08:46 UTC
Maybe related:
With higher GL versions, Dirt enables "advanced lighting" options in the graphics menu. Setting this to "On" makes the game basically a slide show. But Im on a Radeon HD 7970. Also all other Radeon cards have a performance problem:
http://www.phoronix.com/scan.php?page=article&item=mesa171-pro60-rx470&num=2

where figures looked better in 2015:
http://www.phoronix.com/scan.php?page=article&item=dirt-showdown-linux&num=3

Some more infos about the lightning options:
http://www.rage3d.com/articles/gaming/codemaster_dirt_showdown_tech_review/index.php?p=2
Comment 3 Kevin Puertas 2017-02-28 11:17:52 UTC
(In reply to Ilia Mirkin from comment #1)

> One difference is that 17.0 has GL 4.3 enabled for Maxwell (e.g. GTX 750),
> which perhaps causes the game to choose a different path, thus not really be
> directly comparable. Try it with
> 
> MESA_GL_VERSION_OVERRIDE=4.1

If I export this before opening steam, steam causes a segfault


> Or try it with
> 
> MESA_EXTENSION_OVERRIDE='-GL_ARB_shader_image_load_store
> -GL_ARB_compute_shader'

If I try this, game loads smooth and works about 45fps, better than with mesa 13



(In reply to Gregor Münch from comment #2)
>With higher GL versions, Dirt enables "advanced lighting" options in the graphics menu.
At least for me, it is there, but Off in all the tests
Comment 4 Ilia Mirkin 2017-02-28 19:45:09 UTC
The speed improvement on Maxwell is expected - Mesa 17.0 starts to add proper shader instruction scheduling information. In various tests it has improved overall perf ~2x (varies a lot based on how shader-computation-limited the software is, vs memory bandwidth-limited).
Comment 5 Kevin Puertas 2017-03-01 14:09:41 UTC
(In reply to Ilia Mirkin from comment #4)
> The speed improvement on Maxwell is expected - Mesa 17.0 starts to add
> proper shader instruction scheduling information. In various tests it has
> improved overall perf ~2x (varies a lot based on how
> shader-computation-limited the software is, vs memory bandwidth-limited).

I know :)
But I dont know why I have to "workaround" mesa this way to play, maybe there are lot of people that not know this too and it are with mesa 17..
Comment 6 Gregor Münch 2018-05-01 14:50:51 UTC
Just want to add, using:

MESA_EXTENSION_OVERRIDE='-GL_ARB_shader_image_load_store -GL_ARB_compute_shader'

Makes the advanced lightning options disappear in the options.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.