Posted January 02, 2016
SUGGESTION:
Please include following information in each of tests:
GPU vendor: AMD, Nvidia, Intel, (...)
GPU model: HD4770, 8800 GTX, 560 GTX, HD2000, HD3000
GPU VRAM in MiB: 256, 512, 4096
Kernel version: Kernel 4.1, 3.9.16, 3.8
Open or proprietary driver: open, proprietary
GPU driver name: radeon, intel, catalyst, nouveau, nvidia, etc
GPU driver version or Mesa version (in case of open driver): 380, 11.5, mesa 10.0-RC
Wine version: 1.5, 1.6-staging, 1.6
Wine patches: CSMT, none, (....)
Additional info:
This information can be found by running:
$ glxinfo
Reasons:
1) wine is winapi translation library.
So at least you need to provide which version of translator you are testing or running. Some may fail, some may bug, some may give very high fps.
2) after wine dispatches its calls to local library "libgl1.so", this re-routes the calls to local driver. This is where its going to be interesting, because there are several drivers, several versions, running on different hardware.
Example:
some titles run pretty good on Nvidia hardware using proprietary driver - because its basically windows driver, same code base; but will fail face on the ground on AMD hardware using proprietary OLD catalyst driver. Heck, 2013 catalyst crashed kernel when just switching TTYs (system consoles, Ctrl-F1..F8); or even refuse to run as with Intel, because hardware lacks something.
And then this problem is attributed to wine.....
Just a simple header and you can do nice case studies and skip all the problems.
Please include following information in each of tests:
GPU vendor: AMD, Nvidia, Intel, (...)
GPU model: HD4770, 8800 GTX, 560 GTX, HD2000, HD3000
GPU VRAM in MiB: 256, 512, 4096
Kernel version: Kernel 4.1, 3.9.16, 3.8
Open or proprietary driver: open, proprietary
GPU driver name: radeon, intel, catalyst, nouveau, nvidia, etc
GPU driver version or Mesa version (in case of open driver): 380, 11.5, mesa 10.0-RC
Wine version: 1.5, 1.6-staging, 1.6
Wine patches: CSMT, none, (....)
Additional info:
This information can be found by running:
$ glxinfo
Reasons:
1) wine is winapi translation library.
So at least you need to provide which version of translator you are testing or running. Some may fail, some may bug, some may give very high fps.
2) after wine dispatches its calls to local library "libgl1.so", this re-routes the calls to local driver. This is where its going to be interesting, because there are several drivers, several versions, running on different hardware.
Example:
some titles run pretty good on Nvidia hardware using proprietary driver - because its basically windows driver, same code base; but will fail face on the ground on AMD hardware using proprietary OLD catalyst driver. Heck, 2013 catalyst crashed kernel when just switching TTYs (system consoles, Ctrl-F1..F8); or even refuse to run as with Intel, because hardware lacks something.
And then this problem is attributed to wine.....
Just a simple header and you can do nice case studies and skip all the problems.
Post edited January 02, 2016 by Lin545