http://bugs.winehq.org/show_bug.cgi?id=15839
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |John-Whitlock@ieee.org
Will Robertson kassah@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kassah@gmail.com
kjella79@yahoo.no changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kjella79@yahoo.no
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |emmaguarda@gmail.com
Dario Corti dario@dariocorti.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dario@dariocorti.com
Nicky nheart@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nheart@gmail.com
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wbaghdadi@gmail.com
Steve Dougherty asksteved.com@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |asksteved.com@gmail.com
--- Comment #57 from Jeff Zaroyko jeffz@jeffz.name 2009-03-22 21:47:48 --- *** Bug 17827 has been marked as a duplicate of this bug. ***
--- Comment #58 from Wouter de Geus benv-wine.org@junerules.com 2009-04-06 10:00:17 --- Created an attachment (id=20312) --> (http://bugs.winehq.org/attachment.cgi?id=20312) Updated Patch for WineD3D to set Driver an Description for wine 1.1.18
Since the "Patch for WineD3D to set Driver an Description" patch didn't apply anymore for the -git version, I updated it so it works again.
--- Comment #59 from Will Robertson kassah@gmail.com 2009-04-11 20:09:59 --- Created bug#18011 with patch from "Updated Patch for WineD3D to set Driver an Description for wine 1.1.18". This is a clean request for the exact feature that this patch is for, to make it easier for devs to find, as well as for other apps that may have a need to report as related to them.
--- Comment #60 from Jeff Zaroyko jeffz@jeffz.name 2009-04-11 20:29:18 --- *** Bug 18011 has been marked as a duplicate of this bug. ***
--- Comment #61 from John Whitlock John-Whitlock@ieee.org 2009-04-12 02:38:46 --- (In reply to comment #59)
The devs are very aware of this bug, but they've rejected the attached patch. They prefer that a good value is automatically picked for the device description and driver name. That's completely reasonable, but harder than the registry override. I'm working on it, and I'm sad we missed 1.1.19, but I'm hopeful that this will be fixed in 1.1.20.
If you have a Windows box with Fallout 3 available, I could use some information. Please post the first few lines of (Doc Folder)/My Games/Fallout3/RendererInfo.txt. On Wine, they look something like:
Renderer Device Information: Direct3D HAL Display RenderPath : BSSM_SV_2
On Windows, they'll look like: Renderer Device Information: NVIDIA GeForce 7600 GT nv4_disp.dll RenderPath : BSSM_SV_2_A
Please include your OS (XP, Vista, etc.)
--- Comment #62 from knipl@in.tum.de 2009-04-12 03:20:41 --- Created an attachment (id=20394) --> (http://bugs.winehq.org/attachment.cgi?id=20394) RendererInfo.txt from Vista SP1
your efforts are very much appreciated. here is my rendererinfo.txt from vista SP1. hope it can be of use.
--- Comment #63 from kjella79@yahoo.no 2009-05-02 14:06:58 --- Created an attachment (id=20871) --> (http://bugs.winehq.org/attachment.cgi?id=20871) GeForce 8800 GTS on WinXP SP03
--- Comment #64 from kjella79@yahoo.no 2009-05-02 14:34:06 --- (In reply to comment #61)
The devs are very aware of this bug, but they've rejected the attached patch. They prefer that a good value is automatically picked for the device description and driver name.
Creating a situation where you must upgrade or patch/recompile wine simply to update it with a currently unreleased card description is foolish. This does not necessarily mean other changes to wine, for example new low/mid-class cards could bring new combinations of existing capabilities. Since they obviously DO rely on these magic strings, the best solution would be:
1. Check for manual overrides (your patch) 2. If empty, pick a good value automatically 3. Fallback to current dummy values
I realize they're pushing to make you write point 2. as well, but there's absolutely no reason to reject having a manual failsafe, nor implementing that one first before going for the fancy autodetection. Setting it manually could be the testing method to update the automatic code with new cards. What am I missing here?
--- Comment #65 from Jeff Zaroyko jeffz@jeffz.name 2009-05-05 18:19:29 --- *** Bug 18358 has been marked as a duplicate of this bug. ***
--- Comment #66 from Nicky nheart@gmail.com 2009-05-14 15:07:29 --- Shouldn't wine 1.1.20 fix this? My video card, at least, is correctly reported now (my system ain't powerful enough to run that game, though...)
--- Comment #67 from Jeff Zaroyko jeffz@jeffz.name 2009-05-14 19:25:01 --- *** Bug 9202 has been marked as a duplicate of this bug. ***
--- Comment #68 from Jeff Zaroyko jeffz@jeffz.name 2009-05-14 19:26:26 --- (In reply to comment #66)
Shouldn't wine 1.1.20 fix this? My video card, at least, is correctly reported now (my system ain't powerful enough to run that game, though...)
No, you might be referring to a different problem, Wine still reports Direct3D HAL instead of the real information as of Wine 1.1.21-138-gaea6418
--- Comment #69 from Steve Dougherty asksteved.com@gmail.com 2009-05-15 05:53:21 --- Renderer Device Information: ATI RADEON XPRESS 200 Series ati2dvag.dll RenderPath : BSSM_SV_2_B96
This is on Windows XP SP 3. I now have an NVidia GeForce 9500, but for some reason this file hasn't changed yet.
--- Comment #70 from Nicky nheart@gmail.com 2009-05-15 09:37:02 --- (In reply to comment #68)
(In reply to comment #66)
Shouldn't wine 1.1.20 fix this? My video card, at least, is correctly reported now (my system ain't powerful enough to run that game, though...)
No, you might be referring to a different problem, Wine still reports Direct3D HAL instead of the real information as of Wine 1.1.21-138-gaea6418
I'm talking about this commit http://source.winehq.org/git/wine.git/?a=commit;h=f2e2e3e49947490368900ef06a... It makes my GeForceFX 5200 reported as such (at least by MaxPayne and MaxPayne 2) http://i42.tinypic.com/2qvqas7.png - vanilla wine.
--- Comment #71 from Tymoteusz Paul puciek@gmail.com 2009-06-03 04:03:45 --- Created an attachment (id=21512) --> (http://bugs.winehq.org/attachment.cgi?id=21512) Console output
With latest git wine using any of available patches does not solve the issue and game still crashes after trying to start new game.