search

iXit / Mesa-3D

Please use official https://gitlab.freedesktop.org/mesa/mesa/ !
https://github.com/iXit/Mesa-3D/wiki
66 stars 13 forks source link

[nine] Poor performance in Split Second Velocity on any settings besides "low" #269

Open leipero opened 7 years ago

leipero commented 7 years ago

Radeon driver (HD 6770 + FX-4100@3.6GHz), 4.9.11-1-ARCH Wine 2.1-1 (tried on other versions as well (2.2-2) = same behaviour) Mesa 17.0.0-2

So, basically, any other settings than "low" results in worse performance compared to Wine-CSMT. As you can see from screen-shots (ignoring loading FPS at start), even tho GPU usage does go up, performance tank down, so on v-high preset on gallium nine there's minimum FPS=5, while on same settings for Wine-CSMT, min. FPS=15 with lower GPU usage. Obviously, with CSMT there are spikes down on low, so nine performs much better. That alone suggest that it is nine problem(?).

Note, game uses d3dx9_43 compiler. I've also tried to enable csmt_force=1, but I'm not sure if it works with radeon driver, or how to properly enable it, since when it is added as env. value before "wine" command it says: "ATTENTION: default value of option csmt_force overridden by environment." , while i did tried to enable it via environment I didn't saw any difference, so I'm assuming it isn't enabled.

Nine (order: low, medium, high, v-high): nine-1low nine-2medium nine-high nine-veryhigh

Wine-CSMT (order: low, medium, high, v-high): csmt-1low csmt-2medium csmt-high csmt-veryhigh

PS: I removed from logs, both continue spewing similar fixme msgs with different address trough the game, I included just first line in both logs. PS2: Game uses AA (i think MSAA) on very high preset. Logs: csmt-log.txt nine-log.txt

axeldavy commented 7 years ago

This is definitely weird.

The log is not interesting. To have interesting log, it needs NINE_DEBUG=all, and mesa must be compiled with --enable-debug

leipero commented 7 years ago

It is weird, that's why I tought it would be a good idea to report it, I don't know how it is compiled in the Arch repo, I will try and if needed, recompile mesa with that flag and report it as soon as possible.

leipero commented 7 years ago

Ok, I've compiled mesa with --enable-debug, now the output file have 40MB in jsut a few seconds of running game with NINE_DEBUG=all, so my question is, how much into the game you need? It also makes game works at 3-5 seconds per frame lol.

I mean I have no problem uploading 1GB log file, but I would like to know if it's enough to send output file of few megs just when starting game? Just entering and leaving game trough (very slow) menu leaves a file of ~476MB, I will upload file now and add in edited comment here, but toa ctually get into the race it would require 1,5+GB output file i guess.

https://drive.google.com/open?id=0B_j0gO_cc4rXYWNJRkIydEM4X3M

iiv3 commented 7 years ago

It might be duplicate of #222 .

leipero commented 7 years ago

Don't know if it's the same bug, but as soon as shadows are set to high, CPU load drops from ~50-70% to ~34-55% (it happens at some places that it goes to 55% and 34%, most of the time it is at around 40%). For what is worth, here are FC2 benchmark results with all presets if it's helpful (with exception of ultra presset with CSMT, it fails to run to the end). Also, "high" preset uses "medium" shadows for some reason (I didn't changed anything). Far_Cry_2.zip