[Bug 39464] New: Squished/squinted graphics in tech demo Rupture (by ASD)
https://bugs.winehq.org/show_bug.cgi?id=39464 Bug ID: 39464 Summary: Squished/squinted graphics in tech demo Rupture (by ASD) Product: Wine Version: 1.7.52 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aapmak(a)gmail.com Distribution: --- The tech demo in question can be downloaded here: http://www.pouet.net/prod.php?which=52931 For reference, here is a youtube video of what it is supposed to look like: https://www.youtube.com/watch?v=pmw87w7i6rQ However, what it does look like for me, on Wine 1.7.52 is hard to describe and even harder to take a proper screenshot of. Ultimately, I can best describe it as a squishing effect of some sort; or maybe more of a squinting effect. As if one were to squint ones eyes, seeing only a very minor portion of what one would see with eyes fully opened. Regardless, it simply does not render properly, at all. The sound plays perfectly normal though, flawless even. I am going to guess it is somehow resolution related. As in, Rupture using very exotic internal resolutions maybe, resolutions Wine simply does not render properly in. Should more specific information be required, I am obviously happy to provide it. -- 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=39464 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://www.pouet.net/prod.p | |hp?which=52931 --- Comment #1 from Austin English <austinenglish(a)gmail.com> --- (In reply to Armin Altorffer from comment #0)
Should more specific information be required, I am obviously happy to provide it.
Please attach terminal output. -- 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=39464 --- Comment #2 from Armin Altorffer <aapmak(a)gmail.com> --- Created attachment 53515 --> https://bugs.winehq.org/attachment.cgi?id=53515 Console Output -- Wine (Staging) 1.9.2 As requested, console output. -- 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=39464 --- Comment #3 from Armin Altorffer <aapmak(a)gmail.com> --- Please also note (on top of the attached console output) that the phenomenon is mildly different from what I originally described. After originally simply aborting the program upon first experiencing the problem, I now decided to simply watch the whole thing. And the best way to describe the phenomenon is as if only part of each individual frame is rendered. A very small fraction. These elements can still take up the whole screen but are far from the actual expected output. Almost as if the program renders its output in layers and we're seeing only one layer. Anyhow, the console output tells me personally extremely little. Basically, nothing worth mentioning there. -- 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=39464 Armin Altorffer <aapmak(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|1.7.52 |1.9.2 -- 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=39464 Armin Altorffer <aapmak(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |erich.e.hoover(a)wine-staging | |.com, michael(a)fds-team.de, | |sebastian(a)fds-team.de Component|-unknown |-unknown Product|Wine |Wine-staging -- 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=39464 --- Comment #4 from Michael Müller <michael(a)fds-team.de> --- I just tested it on my system and everything seems to work fine. The demo uses OpenGL, so the behavior heavily depends on the underlying driver. I am using the proprietary nvidia driver, what driver do you use? The output of glxinfo might be helpful. -- 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=39464 --- Comment #5 from Armin Altorffer <aapmak(a)gmail.com> --- (In reply to Michael Müller from comment #4)
I just tested it on my system and everything seems to work fine. The demo uses OpenGL, so the behavior heavily depends on the underlying driver. I am using the proprietary nvidia driver, what driver do you use? The output of glxinfo might be helpful.
(or, chrome://gpu) GL_VENDOR X.Org GL_RENDERER Gallium 0.4 on AMD SUMO (DRM 2.43.0, LLVM 3.7.1) GL_VERSION 3.0 Mesa 11.2.0-devel (git-a443b5b 2016-01-26 vivid-oibaf-ppa) I'm not quite confident it is driver related however; I'd have expected more titles (demos, games, etc) to demonstrate this kind of rendering issue. And so far, I can't say I've ever seen this phenomenon or something like it before. However, the fact it runs OK for you on nVidia's binary blob and doesn't for me on the open source AMD driver stack does hint at something in that direction. -- 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=39464 kutajydam-5795(a)yopmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED --- Comment #6 from kutajydam-5795(a)yopmail.com --- Given the fact there are configurations for which this problem apparently does not occur, it is most likely driver related and not Wine related. -- 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=39464 kutajydam-5795(a)yopmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from kutajydam-5795(a)yopmail.com --- ... -- 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