January 2018 - Wine-Bugs - list.winehq.org

[Bug 44381] New: Skyrim Special Edition: NPC dialogue not initiating

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44381 Bug ID: 44381 Summary: Skyrim Special Edition: NPC dialogue not initiating Product: Wine Version: 3.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andrew.mrolko(a)gmail.com Distribution: --- In Skyrim Special Edition, when a player is supposed to interact with an NPC, nothing happens. The player does not hear any audio, and cut scenes associated with a given interaction do not play. Furthermore, the NPC's don't move their mouths is if they are trying to talk. The issue is best described as if the characters don't know that they're supposed to do anything. They just sit there and nothing happens. Unfortunately, this breaks the game, as the player cannot make it through the opening tutorial. Please see this video showing what the player is to expect when the opening cut scene ends: https://youtu.be/p3teMHOfmsg?t=3m37s The player is removed from the cart, which brings them to the character selection screen. When running under WINE, the player remains sitting in the cart with the 3 other NPCs, and nothing happens when the cart comes to a stop. Outside of that, the audio in the game appears to work correctly. Sound effects such as horses grunting, and the wheels of carts rolling along cobblestone paths play as they should. I have attached a log file when the following command was executed in the Steam directory '$ wine Steam.exe &>log.txt'. I also have a screenshot showing the cart ride cut scene, where normally player would hear the stormcloak soldier saying "Hey, you, finally awake...etc": (Please see https://youtu.be/p3teMHOfmsg?t=43s for an example.) Where in my screenshot, said soldier just sits there and doesn't say a word. Tested on: Wine 3.0 Distro is Solus AMD FX-8350 AMD R9 280X with the opensource mesa drivers xaudio2_7 (builtin then native) override in place -- 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.

Jan. 20, 2018

[Bug 35127] Gamehall (Chinese game client) crashes in comctl32

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=35127 --- Comment #24 from Nikolay Sivov <bunglehead(a)gmail.com> --- (In reply to Zhiyi Zhang from comment #23) > Tests show that there are times the content 2 bytes before and after > $HTREEITEM+0x1a is not zero(Once there are 0x1 at lower 2 bytes). You can > dump the memory of HTREEITEM pointed to to check it. And since MSDN says the > pszText max displayed text will be 260 characters, I am pretty sure > textWidth is a WORD. Number of allowed characters does not limit measured width, in this case 260 char limit can't possibly guarantee that pixel width will fit in 2 bytes. -- 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.

Jan. 20, 2018

[Bug 44380] Battle.net fails to launch with wine 3.0

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44380 --- Comment #2 from Otto <b1779506(a)trbvn.com> --- Created attachment 60302 --> https://bugs.winehq.org/attachment.cgi?id=60302 Blizzard error: 05C2508F-9EC9-4D68-A1EC-B55C65D54FCE -- 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.

Jan. 20, 2018

[Bug 44380] Battle.net fails to launch with wine 3.0

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44380 --- Comment #1 from Otto <b1779506(a)trbvn.com> --- Created attachment 60301 --> https://bugs.winehq.org/attachment.cgi?id=60301 Battle.net.exe -- 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.

Jan. 20, 2018

[Bug 44380] New: Battle.net fails to launch with wine 3.0

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44380 Bug ID: 44380 Summary: Battle.net fails to launch with wine 3.0 Product: Wine Version: 3.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: b1779506(a)trbvn.com Distribution: --- Created attachment 60300 --> https://bugs.winehq.org/attachment.cgi?id=60300 Battle.net Launcher.exe The login screen opens and closes. See log. ii wine-stable 3.0.0~artful amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-stable-amd64 3.0.0~artful amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-stable-i386:i386 3.0.0~artful i386 WINE Is Not An Emulator - runs MS Windows programs ii winehq-stable 3.0.0~artful amd64 WINE Is Not An Emulator - runs MS Windows programs -- 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.

Jan. 20, 2018

[Bug 23193] wine notepad: Slow to open large files

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=23193 --- Comment #21 from Thomas Faber <thomas.faber(a)reactos.org> --- fb44feb62fd speeds this up a bunch, so it might warrant a retest. It's still noticeably slower than Windows for me though, so I'm guessing it's not enough to call this 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.

Jan. 20, 2018

[Bug 40986] DirectX11 application fails with error message " Failed to create IDXGIFactory2"

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=40986 --- Comment #7 from Nikolay Sivov <bunglehead(a)gmail.com> --- IDXGIFactory2 is supported now, see https://source.winehq.org/git/wine.git/commit/f99a548148bae4a8db904171a5379…. Please retest. -- 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.

Jan. 20, 2018

[Bug 44245] Gray screen on some Android devices

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44245 --- Comment #16 from Alexandre Julliard <julliard(a)winehq.org> --- It's probably some incompatibility with Android 8. I don't have an Android 8 device yet 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.

Jan. 20, 2018

[Bug 44245] Gray screen on some Android devices

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44245 Alexandr <sasha01945(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Gray screen on OnePlus 3 / |Gray screen on some Android |3T / 5 |devices -- 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.

Jan. 20, 2018

[Bug 44245] Gray screen on OnePlus 3 / 3T / 5

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44245 --- Comment #15 from Jacob McSwain <jacob.a.mcswain(a)gmail.com> --- If anyone needs any other logs or any more information I'm happy to provide. I also tested 3.0rc1 and 3.0rc6 to see if there was a regression, and both had the same result -- 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.

Jan. 20, 2018