July 2017 - Wine-Bugs - list.winehq.org

[Bug 43239] The Witcher 3: ground is too dark in some areas

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43239 --- Comment #6 from Jonathan Strander <mblackwell1024(a)gmail.com> --- (In reply to scix from comment #5) > (In reply to Jonathan Strander from comment #3) > > Vague thought is it is related to a similar issue I saw a screenshot of > > where it appears some shaders "glitch out". Perhaps not but I sometimes see > > objects including surfaces like the ground manifest as dark and switching > > around some graphical options seems to fix it until a new area is streamed > > in. > > I have that bug as well (perhaps Nvidia specific going by Shmerl's > experience), but it doesn't affect the ground being dark issue. That is too bad. Killing two birds with one stone would be nice! -- 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.

July 1, 2017

[Bug 41363] Starcraft Editor crash when accessing Triggers.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=41363 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #3 from winetest(a)luukku.com --- Could you upgrade your wine-staging? It's rather old by now. -- 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.

July 1, 2017

[Bug 39023] Final Fantasy XI Using a Bluetooth PS3 Controller crashes the game.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=39023 --- Comment #38 from Alex Vallée <avallee(a)chromium.org> --- (In reply to Ken Thomases from comment #33) > I suspect the problem may be that two threads are calling into the Mac HID > library at the same time. It may be that we need to use a critical section > to prevent that entirely. Or maybe using IOHIDTransaction objects will be > enough to fix it. The latter would fix it if the problem is just that the > element values are being released by one thread (because a new HID report > has been received) while the other thread is still using them. I went with the idea and added a mutex for each device id. Seems to work for me. -- 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.

July 1, 2017

[Bug 43264] The Witcher 3: Black and red face textures and missing vegetation

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43264 Jonathan Strander <mblackwell1024(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mblackwell1024(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.

July 1, 2017

[Bug 43263] Wine cannot coexist with other ALSA programs, even with dmix

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43263 --- Comment #2 from sgilles(a)math.umd.edu --- I realize I should clarify the original report. Programs can still be run if ALSA is in use, they just don't produce any sound (and spit out DSOUND_ReopenDevice errors every now and then). -- 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.

July 1, 2017

[Bug 39023] Final Fantasy XI Using a Bluetooth PS3 Controller crashes the game.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=39023 Alex Vallée <avallee(a)chromium.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |avallee(a)chromium.org --- Comment #37 from Alex Vallée <avallee(a)chromium.org> --- Created attachment 58590 --> https://bugs.winehq.org/attachment.cgi?id=58590 Add locking around access to the same device id. Ignore the extra logging, I think the main issue for the crash is that FFXI is accessing the same HID device from 2 threads. I noticed that if one of the threads dies the whole game goes down. In other cases you can just continue and that thread dies but the rest of the game is fine. -- 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.

July 1, 2017

[Bug 43264] New: The Witcher 3: Black and red face textures and missing vegetation

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43264 Bug ID: 43264 Summary: The Witcher 3: Black and red face textures and missing vegetation Product: Wine Version: 2.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: asheldon55(a)gmail.com Distribution: --- Created attachment 58589 --> https://bugs.winehq.org/attachment.cgi?id=58589 Terminal output Game has black and red textures (particularly in faces, mainly visible in cutscenes), and missing vegetation: https://i.imgur.com/uSKHNMw.jpg https://i.imgur.com/VvxdZZY.jpg Problem can be worked around by changing any graphical setting (such as Shadow Quality), resulting in near correct output (disregarding other bugs): https://i.imgur.com/8BbM5ZU.jpg https://i.imgur.com/NZk24Cq.jpg If I reload a save, the problem will occur again. Problem is not limited to cutscenes, but the red/black face problem appears to be consistent in cutscenes, but intermittent outside of cutscenes. Testing was done using this mod: http://www.nexusmods.com/witcher3/mods/2033/? allowing setting changes during cutscenes. System information: Wine version: 2.11-staging (likely affects wine-devel, but other bugs prevent the game working) Distribution: Gentoo stable OpenGL: OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 980 Ti/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 384.47 OpenGL core profile shading language version string: 4.50 NVIDIA OpenGL version string: 4.5.0 NVIDIA 384.47 CPU: Ryzen R1600 RAM: 16GB Terminal log attached. Discussions on other forums suggest the problem may be Nvidia binary driver specific. -- 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.

July 1, 2017

[Bug 42592] The Witcher 3 has poor performance

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42592 scix <asheldon55(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asheldon55(a)gmail.com --- Comment #8 from scix <asheldon55(a)gmail.com> --- Performance is still quite bad with my Nvidia system (20 - 35 FPS average), and is mainly not affected by graphical settings. Hardware info: CPU: Ryzen 1600 @ 3.6 ghz RAM: 16 GB GPU: 980 TI with 384.47 binary drivers Wine version: 2.11-staging Resolution: 2560x1440 (but still equally slow at lower resolutions) -- 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.

July 1, 2017

[Bug 43263] Wine cannot coexist with other ALSA programs, even with dmix

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43263 --- Comment #1 from sgilles(a)math.umd.edu --- Created attachment 58588 --> https://bugs.winehq.org/attachment.cgi?id=58588 output of Warning Forever described in inital post -- 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.

July 1, 2017

[Bug 43263] New: Wine cannot coexist with other ALSA programs, even with dmix

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43263 Bug ID: 43263 Summary: Wine cannot coexist with other ALSA programs, even with dmix Product: Wine Version: 2.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winealsa.drv Assignee: wine-bugs(a)winehq.org Reporter: sgilles(a)math.umd.edu Distribution: --- Created attachment 58587 --> https://bugs.winehq.org/attachment.cgi?id=58587 .asoundrc This machine runs Gentoo and ALSA + dmix (.asoundrc attached). I have observed this issue with wine installed from Gentoo's repositories, but also with wine built from git (I have observed this with commit 6ec3cd9434488ba5bc0fd271a47b7d46827477c5 for example, which is the latest at time of writing). Every native program on this machine (mpv, mpd, ffplay, firefox, etc) is able to play sound concurrently with every other such program. My options under winecfg's audio tab are different depending on whether an ALSA-using program is currently running: [A] (System default) [A] Out: default [A] Out: HDA NVidia - HDMI 3 [A] Out: HDA NVidia - HDMI 2 [A] Out: HDA NVidia - HDMI 0 [A] Out: HDA NVidia - HDMI 1 [B] Out: HDA Intel PCH-ALC887-VD Anal... The entry marked [B] only appears if there is no such program running. The entries marked [A] cause the "Test Sound" to be truncated abruptly, while the entry marked [B] allows the test sound to fully die down. Furthermore, if an entry marked [A] is selected, running a program that produces sound will fail with lines like err:dsound:DSOUND_ReopenDevice Initialize failed: 8889000f in the output. I have attached a log created with wine from commit 6ec3cd9434488ba5bc0fd271a47b7d46827477c5, from a fresh, WINEARCH="win32" wineprefix, running Warning Forever 1.08, with "(System default)" selected (mpd is running in the background), and with WINEDEBUG="+tid,+mmdevapi,+winmm,+driver,+midi,+dsound,+dsound3d,+dmusic,+mci,+oss,+alsa,+coreaudio" The expected behavior is that, since I have dmix configured, wine should behave like other programs and play sound concurrently with them. I've looked around for solutions to this, and people claim that wine has been able to coexist with other programs in the past (hence my reporting it as a bug), but every piece of advice I find seems to be outdated. -- 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.

July 1, 2017