[Bug 37863] New: Halo only works using Nvidia graphics
https://bugs.winehq.org/show_bug.cgi?id=37863 Bug ID: 37863 Summary: Halo only works using Nvidia graphics Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: vroom.henderson(a)gmail.com Distribution: --- Using GPUs other than Nvidia (confirmed with Intel and AMD), Halo will launch but will just display a black screen. The music and menu sounds work correctly when the arrow keys are pressed giving evidence that other than the graphics component, the game is still actually running. When the game is placed in "Safe Mode" the screen is all black except for some flashing vertices in the lower right quadrant of the screen. The terminal also outputs the following error repeatedly: fixme:d3d:process_vertices_strided Didn't expect the destination to have a normal -- 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=37863 vroom.henderson(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vroom.henderson(a)gmail.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.
https://bugs.winehq.org/show_bug.cgi?id=37863 --- Comment #1 from Bruno Jesus <00cpxxx(a)gmail.com> --- Can you reproduce with a demo? If yes where can the demo be downloaded from? -- 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=37863 Elias Vanderstuyft <Elias.vds(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Elias.vds(a)gmail.com --- Comment #2 from Elias Vanderstuyft <Elias.vds(a)gmail.com> --- It is reproducible with the demo on Intel HD graphics using wine 1.7.34 Demo: http://download.cnet.com/Halo-Combat-Evolved/3000-7441_4-10235611.html I attached a video of the result. Note that the screen is not black, but rather some pixel-color (or an average of many pixel-colors) scaled to fit the whole screen: see end of video. Also, at the beginning - the menu - some color changes can be noticed. And also interesting to note, is that on an Nvidia card (GTX 760) running the opensource driver "nouveau", it does work! So it seems like it's HW-dependent... -- 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=37863 --- Comment #3 from Elias Vanderstuyft <Elias.vds(a)gmail.com> --- Video of Halo (Trial) on Intel HD: https://www.dropbox.com/s/uz44tyg64chdpsk/halotrial-intel-wine.mkv?dl=1 Make sure you watch it in fullscreen in order to easily see the color-changes. -- 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=37863 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://download.cnet.com/Ha | |lo-Combat-Evolved/3000-7441 | |_4-10235611.html --- Comment #4 from Bruno Jesus <00cpxxx(a)gmail.com> --- I can't reproduce this, I'm using Mesa 10.4.2 and wine-git. I can get to the menu and the game, there are minor glitches in the weapon and the weapon sound is not played when I shoot but the game is playable. This is what glxgears -info tells about my graphics card: GL_RENDERER = Mesa DRI Intel(R) Ironlake Mobile GL_VERSION = 2.1 Mesa 10.4.2 GL_VENDOR = Intel Open Source Technology Center -- 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=37863 --- Comment #5 from Elias Vanderstuyft <Elias.vds(a)gmail.com> --- I retried with wine-git: Exactly the same results as in previous video. $ WINEPREFIX=$HOME/Games/WineHaloTrialPrefix2 ~/wine-git/wine --version wine-1.7.34-144-g412a070 $ glxgears -info GL_RENDERER = Mesa DRI Intel(R) Haswell Mobile GL_VERSION = 3.0 Mesa 10.3.3 GL_VENDOR = Intel Open Source Technology Center $ uname -sro Linux 3.16.7-200.fc20.x86_64 GNU/Linux Maybe upgrading Mesa will solve it, I will try that when I have more time. -- 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=37863 --- Comment #6 from Elias Vanderstuyft <Elias.vds(a)gmail.com> --- Created attachment 50559 --> https://bugs.winehq.org/attachment.cgi?id=50559 Running Halo on Intel Haswell with wine-1.7.34-144-g412a070 Command-line output of running Halo on Intel Haswell with wine-1.7.34-144-g412a070; -- 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=37863 --- Comment #7 from Elias Vanderstuyft <Elias.vds(a)gmail.com> --- (In reply to Bruno Jesus from comment #4)
I can't reproduce this, I'm using Mesa 10.4.2 and wine-git. I can get to the menu and the game, there are minor glitches in the weapon and the weapon sound is not played when I shoot but the game is playable. This is what glxgears -info tells about my graphics card:
GL_RENDERER = Mesa DRI Intel(R) Ironlake Mobile GL_VERSION = 2.1 Mesa 10.4.2 GL_VENDOR = Intel Open Source Technology Center
I retested with Mesa-git-10.5_git2015.02.04 (using live-usb from http://www.gearsongallium.com/?p=1752), and this solved the issue! Now I don't have any glitches, game runs perfectly with the Intel (OTC) driver. So this means the title of this bugreport is invalid. Can someone with an AMD card please retest the demo using the live-usb I used? -- 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=37863 --- Comment #8 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to Elias Vanderstuyft from comment #7)
I retested with Mesa-git-10.5_git2015.02.04 (using live-usb from http://www.gearsongallium.com/?p=1752), and this solved the issue! Now I don't have any glitches, game runs perfectly with the Intel (OTC) driver.
So this means the title of this bugreport is invalid. Can someone with an AMD card please retest the demo using the live-usb I used?
Since updating mesa solved the issue for you and probably for me (didn't test in older mesa) the bug is more likely upstream and already fixed. Let's wait a bit longer for someone with AMD test. -- 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=37863 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3d |-unknown Version|unspecified |1.7.34 -- 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=37863 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #9 from super_man(a)post.com --- I can't get into game. It complains that it cant initilize directdraw. Safe mode and bypass that error options are grayed out. Basic console output basically just fixme:win:EnumDisplayDevicesW ((null),0,0x33cf28,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33d288,0x00000000), stub! r9 290 amd wine-1.8-60-g35eebee -- 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=37863 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx(a)gmail.com, | |dimesio(a)earthlink.net, | |winetest(a)luukku.com --- Comment #10 from winetest(a)luukku.com --- This is fixed. I have never played this before. Mission starts on some airships and you begin your invasion when you land to the ground. wine 2.0rc5. Amd rx480 8Gb. -- 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=37863 Zachary J <zakarjor(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zakarjor(a)yahoo.com --- Comment #11 from Zachary J <zakarjor(a)yahoo.com> --- It still has the same black/flashing screen issue as of wine 3.2 with Intel integrated graphics driver. It works with nvidia GT630M discrete graphics that is part of nvidia optimus on the same laptop, if using proprietary nvidia driver. So at least I can play this way. -- 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=37863 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #12 from joaopa <jeremielapuree(a)yahoo.fr> --- Tested with Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) Ivybridge Mobile (0x166) Version: 18.2.2 Accelerated: yes Video memory: 1536MB Everything is working fine with wine-3.21. Can an administrator close this bug as FIXED. -- 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=37863 Jeff Zaroyko <jeffz(a)jeffz.name> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #13 from Jeff Zaroyko <jeffz(a)jeffz.name> --- Reported fixed. -- 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=37863 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #14 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 4.0-rc1. -- 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