http://bugs.winehq.org/show_bug.cgi?id=16031
Summary: Missing categorising by video driver version in AppDB Product: WineHQ Apps Database Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: appdb-unknown AssignedTo: wine-bugs@winehq.org ReportedBy: mityukov@gmail.com
I found the AppDB is a bit unusable, when it comes to quick check on "Which games will run in my system", or "Will this game run for me".
The most important thing, when it come to games - is the Video Driver. For example, there are many games, that run for NVidia owners, but don't run for ATI, and so on.
Another point, when it comes to specific driver name and version. For example, open-source "radeon" supports only OpenGL 1.3, and Catalyst supports higher implementations. Moreover, different versions of the same, let say Catalyst, may work differently for this or that program. There are also regressions, etc.
Again: Video Drivers in Linux, are not ideal. I would say, this point have even higher affect than the Distribution.
What I would like to see, near the "Distribution" column -- is another one: "Video" or something like this, where it will say e.g. "Catalyst 8.9". This way it will be possible to link Rating with certain Video Setup, before taking the decision.
Some tools for searching Games, that work with specific video driver(s) would also be _HIGHLY_ appreciated.
http://bugs.winehq.org/show_bug.cgi?id=16031
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |kennybobs@o2.co.uk Ever Confirmed|0 |1
--- Comment #1 from Ken Sharp kennybobs@o2.co.uk 2011-10-11 18:01:46 CDT --- A column for graphics manufacturer might be useful, but only if there is a filter or stats to compare the differences between each result.
http://bugs.winehq.org/show_bug.cgi?id=16031
butraxz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |butraxz@gmail.com
--- Comment #2 from butraxz@gmail.com 2013-04-21 14:38:56 CDT --- No update for over 900 days. Is still an issue with 1.5.28 or higher ?
http://bugs.winehq.org/show_bug.cgi?id=16031
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |legluondunet@free.fr
--- Comment #3 from Ken Sharp imwellcushtymelike@gmail.com --- *** Bug 35131 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=16031
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com, | |winetest@luukku.com
https://bugs.winehq.org/show_bug.cgi?id=16031
--- Comment #4 from Austin English austinenglish@gmail.com --- (In reply to butraxz from comment #2)
No update for over 900 days. Is still an issue with 1.5.28 or higher?
It's not an issue in wine, it is an issue in the appdb. And yes, still present.
https://bugs.winehq.org/show_bug.cgi?id=16031
Jeff D. Hanson jhansonxi@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jhansonxi@gmail.com
--- Comment #5 from Jeff D. Hanson jhansonxi@gmail.com --- Another concern is test reports submitted against hardware that doesn't meet the minimum system requirements of the app being tested.
I think the best solution would be an automated report that could be attached or submitted. Something like Ubuntu's Apport crash reporter does for Launchpad bugs. This would avoid problems with formatting and would allow for easier parsing and analysis.
https://bugs.winehq.org/show_bug.cgi?id=16031
--- Comment #6 from Austin English austinenglish@gmail.com --- (In reply to Jeff D. Hanson from comment #5)
Another concern is test reports submitted against hardware that doesn't meet the minimum system requirements of the app being tested.
That information may or may not be known (and may not be accurate, e.g., the specs required under Wine may be higher than on Windows).
I think the best solution would be an automated report that could be attached or submitted. Something like Ubuntu's Apport crash reporter does for Launchpad bugs. This would avoid problems with formatting and would allow for easier parsing and analysis.
That may be useful, but it's also a significant amount of work and out of scope for this bug. You'd also have to find someone that is interested in working on that, where most Wine developers would rather hack on Wine itself.
https://bugs.winehq.org/show_bug.cgi?id=16031
--- Comment #7 from winetest@luukku.com --- I don't see much value on this.
Some people say their gpus and drivers even without specific fields. Some programs receive so infrequently updates that drivers have gone a lot forward meanwhile. And if you look at the bug tracker there arent so many bugs that some game works on certain hardware and doesn't work on some other.
https://bugs.winehq.org/show_bug.cgi?id=16031
--- Comment #8 from Jeff D. Hanson jhansonxi@gmail.com --- (In reply to Austin English from comment #6)
That information may or may not be known (and may not be accurate, e.g., the specs required under Wine may be higher than on Windows).
I'm aware of that. I'm concerned with false-positive errors.
That may be useful, but it's also a significant amount of work and out of scope for this bug. You'd also have to find someone that is interested in working on that, where most Wine developers would rather hack on Wine itself.
I wasn't proposing it as a solution to this bug, just using it as an example. Expecting reporters to supply that level of technical detail manually is unwise. A text box would result in a mess of nearly-useless unformatted data. A list box would be better but someone would have to keep it updated with driver names and versions.
https://bugs.winehq.org/show_bug.cgi?id=16031
--- Comment #9 from Rosanne DiMesio dimesio@earthlink.net --- IMO, the main problem with this proposal is the assumption that users actually know what GPU/driver they have. Many don't.
https://bugs.winehq.org/show_bug.cgi?id=16031
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |6aef8feeebe9d2e2d7f2e2d0cb8 | |65cd3dc9bbc35
--- Comment #10 from Rosanne DiMesio dimesio@earthlink.net --- We now have fields to collect information on the GPU manufacturer and graphics driver.
https://bugs.winehq.org/show_bug.cgi?id=16031
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Rosanne DiMesio dimesio@earthlink.net --- Closing fixed.
https://bugs.winehq.org/show_bug.cgi?id=16031
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Alias|pilat |
-
wine-bugs＠winehq.org