[Bug 30328] New: Arx Fatalis: portrait missing on the character creation screen
http://bugs.winehq.org/show_bug.cgi?id=30328 Bug #: 30328 Summary: Arx Fatalis: portrait missing on the character creation screen Product: Wine Version: 1.5.1 Platform: x86 URL: http://www.fileplanet.com/85489/80000/fileinfo/Arx-Fat alis-Demo-%5BEnglish---Updated%5D OS/Version: Linux Status: UNCONFIRMED Keywords: download, regression Severity: minor Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com CC: matteo.mystral(a)gmail.com Classification: Unclassified Regression SHA1: 439097c810bdcb2bd3f838d2ee47369d1f4d7e8a Created attachment 39631 --> http://bugs.winehq.org/attachment.cgi?id=39631 terminal output Steps to reproduce the problem with the demo version: 1. Install the demo. 2. Start the game with ARX.exe. You can skip the intro video by pressing <Esc>. In the main menu choose <New Quest>. You should see that the portrait of the character is missing on the character generation screen. For me, the problem appeared in Wine-1.5.1: 439097c810bdcb2bd3f838d2ee47369d1f4d7e8a is the first bad commit commit 439097c810bdcb2bd3f838d2ee47369d1f4d7e8a Author: Matteo Bruni <mbruni(a)codeweavers.com> Date: Wed Mar 28 13:52:11 2012 +0200 wined3d: Update the correct draw buffers mask. :040000 040000 a75b4bc6948f6fabc49710be4abe72a10e9ffae0 7d9ca1f018b013dfe324fdc382c02fab8ff8694f M dlls Reverting the patch fixed the problem. Fedora 16 Nvidia 250 / driver 295.33 X.Org X Server 1.11.4 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30328 --- Comment #1 from GyB <gyebro69(a)gmail.com> 2012-04-01 08:11:22 CDT --- Created attachment 39632 --> http://bugs.winehq.org/attachment.cgi?id=39632 screenshot (comparison) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30328 --- Comment #2 from Matteo Bruni <matteo.mystral(a)gmail.com> 2012-04-03 09:37:04 CDT --- Created attachment 39666 --> http://bugs.winehq.org/attachment.cgi?id=39666 Hack I can reproduce this on Nvidia binary drivers but not on fglrx, and it actually looks like a driver bug to me. The game draws to the backbuffer via ddraw/d3d and, every now and then, it also makes some GetDC calls on the same backbuffer. The issue is that the eventual glGetTexImage() call sometime returns stale texture data, e.g. the character creation screen as it was before drawing the character portrait. Juggling with the GL draw buffers settings (i.e. the hack I attached) somehow "fixes" the issue for me. It seems to me we're not doing anything wrong, e.g. there is no texture-render target rendering feedback and there is only one GL context involved, so I'm blaming the driver... -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30328 --- Comment #3 from Henri Verbeet <hverbeet(a)gmail.com> 2012-04-03 09:52:20 CDT --- It does sound somewhat similar to bug 30269, any chance they're related? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30328 --- Comment #4 from Matteo Bruni <matteo.mystral(a)gmail.com> 2012-04-03 10:17:01 CDT --- (In reply to comment #3)
It does sound somewhat similar to bug 30269, any chance they're related?
Your hack from bug 30269 "fixes" this too, so they are related somewhat. Although your patch touches stuff when uploading to GL while mine hacks the download path. Puzzling to say the least... But I guess this enforces the notion of a driver bug. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30328 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #5 from joaopa <jeremielapuree(a)yahoo.fr> 2013-04-13 01:17:34 CDT --- Can one close this bug as INVALID? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30328 --- Comment #6 from Matteo Bruni <matteo.mystral(a)gmail.com> 2013-04-13 09:13:45 CDT --- (In reply to comment #5)
Can one close this bug as INVALID?
It would be UPSTREAM, not INVALID. FWIW, I can still reproduce on Nvidia 313.30 drivers. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30328 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |UPSTREAM --- Comment #7 from Austin English <austinenglish(a)gmail.com> 2013-04-13 13:06:23 CDT --- Driver bug. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30328 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #8 from Matteo Bruni <matteo.mystral(a)gmail.com> --- This looks fixed for me on Nvidia drivers 349.16. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30328 --- Comment #9 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to Matteo Bruni from comment #8)
This looks fixed for me on Nvidia drivers 349.16.
I wonder if Nvidia will apply the fix in their legacy drivers as well? Still present here with the 340.76 drivers. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30328 --- Comment #10 from Matteo Bruni <matteo.mystral(a)gmail.com> --- (In reply to Béla Gyebrószki from comment #9)
(In reply to Matteo Bruni from comment #8)
This looks fixed for me on Nvidia drivers 349.16.
I wonder if Nvidia will apply the fix in their legacy drivers as well? Still present here with the 340.76 drivers.
Actually I talked to a Nvidia dev yesterday (not knowing yet that this was fixed after the 340.xx series) and I got a "no" back as an answer unfortunately. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30328 --- Comment #11 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to Matteo Bruni from comment #10)
(In reply to Béla Gyebrószki from comment #9)
(In reply to Matteo Bruni from comment #8)
This looks fixed for me on Nvidia drivers 349.16.
I wonder if Nvidia will apply the fix in their legacy drivers as well? Still present here with the 340.76 drivers.
Actually I talked to a Nvidia dev yesterday (not knowing yet that this was fixed after the 340.xx series) and I got a "no" back as an answer unfortunately.
I'm disappointed to say the least :( Matteo, would you be so kind and test bug #30045 for me? I think it's another driver related issue which is still present in their 340.76 drivers. I couldn't reproduce that issue with nouveau. Maybe that bug is fixed as well in the latest Nvidia drivers. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30328 --- Comment #12 from Matteo Bruni <matteo.mystral(a)gmail.com> --- *** Bug 30045 has been marked as a duplicate of this bug. *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30328 --- Comment #13 from Matteo Bruni <matteo.mystral(a)gmail.com> --- For the records, both this and bug 30045 are still present with driver version 343.36 and look okay with 346.72, so the bug was fixed at some point between them. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org