September 2022 - Wine-Bugs - list.winehq.org

[Bug 53665] New: rawinput: Gamepad input lost after disconnect/reconnect
by WineHQ Bugzilla Sept. 12, 2022

Sept. 12, 2022

https://bugs.winehq.org/show_bug.cgi?id=53665 Bug ID: 53665 Summary: rawinput: Gamepad input lost after disconnect/reconnect Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: achurch+wine(a)achurch.org Regression SHA1: 8962ec5a83286488da6f839ceba3c39ad1cf00b3 Distribution: --- Since Wine 7.10 (at least on Linux), when a gamepad is disconnected and subsequently reconnected, a running program accessing that gamepad using the rawinput interface can no longer receive input from the gamepad (the gamepad is effectively lost). Testing indicates that GetRawInputDeviceInfo() on the device after reconnect fails with error 6 (invalid handle), preventing detection of the reconnect. git bisect blames 8962ec5a, which broke gamepad input completely (the gamepad is never detected by the application). 4c584fe7 fixes initial detection, but the gamepad is lost after a disconnect/reconnect cycle. -- 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.

1 2

[Bug 53664] New: Exceptions in std::async not handled properly
by WineHQ Bugzilla Sept. 12, 2022

Sept. 12, 2022

https://bugs.winehq.org/show_bug.cgi?id=53664 Bug ID: 53664 Summary: Exceptions in std::async not handled properly Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tteu.ingog(a)gmail.com Distribution: --- Created attachment 73070 --> https://bugs.winehq.org/attachment.cgi?id=73070 The source code for a minimal example Found this bug while investigating crashes of NTKDaemon.exe on launch, which is required in Native Access 2.4.0. When a C++ exception is thrown inside a callable passed in std::async with std::launch::async policy, the unhandled exception is rethrown in the main thread when getting the value of the std::future returned by std::async. When executing a program compiled in Visual Studio 2022, However, it didn't work as expected. The program will either execute as if the thread exited normally at the point of `throw`, or somehow crash without forwarding the exception to the caller thread of std::async(especially when winegdb is attached). I'm not sure if it's related, but it seems like std::current_exception is also not working as expected. -- 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.

1 1

[Bug 4418] black screen when starting Warlords Battlecry
by WineHQ Bugzilla Sept. 11, 2022

Sept. 11, 2022

https://bugs.winehq.org/show_bug.cgi?id=4418 --- Comment #27 from joaopa <jeremielapuree(a)yahoo.fr> --- Bug still occurs with wine-7.17. -- 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.

1 0

[Bug 39421] New: Majesty Gold HD runs very slowly
by wine-bugs＠winehq.org Sept. 9, 2022

Sept. 9, 2022

https://bugs.winehq.org/show_bug.cgi?id=39421 Bug ID: 39421 Summary: Majesty Gold HD runs very slowly Product: Wine Version: 1.7.52 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jonas.bugzilla(a)gmail.com Created attachment 52535 --> https://bugs.winehq.org/attachment.cgi?id=52535 Clamp the glFlush rate in the Mac driver to 60Hz The game Majesty Gold HD (http://www.gog.com/game/majesty_gold_hd ) runs very slowly under Wine for me (Late 2013 iMac 21.5", quad 2.9GHz Core i5, GeForce GT 750M with 1GB GDDR5, OS X 10.9.5). There is an in-game slider to speed up the game, but it has no effect. The game is a DirectDraw 7 game. There are also some reports on Windows regarding this problem, but most people can solve it by telling the game to use DirectDraw for blitting (set BlitMode=1 in the MajXPrefs, or use the -useddblit command line parameter -- see http://forum.paradoxplaza.com/forum/index.php?threads/bug-fixes.601217/#pos… ) The game performs its drawing commands in the same thread that runs the game logic (I don't know whether anything else is even supported by by DirectDraw 7). From a trace I can see that game performs many small blits to update only the parts of the screen that have changed. Example from a trace: trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (0,0)-(24,38), src_surface 0x16c9c8, src_rect (0,0)-(24,38), flags 0x1000000, fx 0x0. [ repeats 8 times ] trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (864,661)-(1009,803), src_surface 0x16c9c8, src_rect (864,661)-(1009,803), flags 0x1000000, fx 0x0. trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (806,999)-(986,1080), src_surface 0x16c9c8, src_rect (806,999)-(986,1080), flags 0x1000000, fx 0x0. trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (1097,734)-(1277,914), src_surface 0x16c9c8, src_rect (1097,734)-(1277,914), flags 0x1000000, fx 0x0. trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (860,481)-(1040,661), src_surface 0x16c9c8, src_rect (860,481)-(1040,661), flags 0x1000000, fx 0x0. trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (860,481)-(1040,661), src_surface 0x16c9c8, src_rect (860,481)-(1040,661), flags 0x1000000, fx 0x0. trace:ddraw:ddraw_surface7_Blt iface 0x16c160, dst_rect (1354,797)-(1534,977), src_surface 0x16c9c8, src_rect (1354,797)-(1534,977), flags 0x1000000, fx 0x0. ... I think Wine, however, always flushes a complete new screen via OpenGL, as the game spends almost all of its time waiting for glFlush() to finish. I have verified that this is the case by applying the attached patch to the Mac driver code to unconditionally clamp the glFlush rate to 60Hz. This solves the speed issue, even at 1920x1080 (without the patch, the game is glacial even at 800x600). Obviously, the patch cannot be integrated in wine, since it occasionally discards the "last" blit to screen after a static scene change, leaving old data visible and no longer updating. I previously posted about this issue (a long time ago) on wine-dev: https://www.winehq.org/pipermail/wine-devel/2015-February/106625.html . To answer some questions/suggestions from the end of that thread: a) the SkipSingleBufferFlushes registry key does not help (my system supports the GL_APPLE_flush_render extension) b) related to Henri Verbeet's suggestion that it may be related to wine possibly not implementing asynchronous ddraw blits: it's true that wine does not support this, but OTOH the game does not ask for them either: it calls ddraw_surface7_Blt rather than ddraw_surface7_BltFast (BltFast is documented on MSDN as always being asynchronous), and it does not set the DDBLT_ASYNC flag The game offers a built-in ability to wait for vsync via its configuration file (set the VSync variable in $HOME/Documents/My Games/MajestyHD/MajXPrefs to "1"), but that only results in trace:ddraw:ddraw7_WaitForVerticalBlank iface 0x146750, flags 0x1, event 0x0. fixme:ddraw:ddraw7_WaitForVerticalBlank iface 0x146750, flags 0x1, event 0x0 stub! I'm also not sure whether it would help, but looking at the ddraw log (which I will also attach -- it's a trace+ddraw,trace+d3d_draw log), I think it may since often there are several blits between the vsync waits. Some possible approaches to tackle this issue may be: * handle small direct rects more efficiently * add support for waiting for VSync in ddraw There is a demo of an older version of the game, but it can only run in 640x480 and there is no way to adjust the game speed via an in-game slider, and at least on my system the difference with and without my patch is not very visible there (http://www.cyberlore.com/Majesty/demo.htm ) -- 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.

2 24

[Bug 53639] New: Drakan - order of the flame: menu doesn't render properly, shows only big primitive shapes
by WineHQ Bugzilla Sept. 8, 2022

Sept. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=53639 Bug ID: 53639 Summary: Drakan - order of the flame: menu doesn't render properly, shows only big primitive shapes Product: Wine Version: 7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kotowhiskas(a)protonmail.com Distribution: --- Created attachment 73039 --> https://bugs.winehq.org/attachment.cgi?id=73039 log When launching a game, menu shows only big primitive shapes, which are hard to click. It's actually a regression from wine 6.0, wine 5.7-11 works fine, also enabling dgvoodoo2 partially fixes the problem. The game is not an official copy (becuase I can't find one, even on gog, it's an old game which doesn't being sold anymore) but a repack, but I don't know if I can share the link to a torrent here. I have (probably) an copy from disc on another pc but it's complicated to get copy it on my system. wine version: staging 7.16 OS: Arch Linux x86_64 Kernel: 5.19.6-arch1-1 -- 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.

1 7

[Bug 53643] New: Drakan - order of the flame: creating server doesn't work
by WineHQ Bugzilla Sept. 8, 2022

Sept. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=53643 Bug ID: 53643 Summary: Drakan - order of the flame: creating server doesn't work Product: Wine Version: 7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dplay Assignee: wine-bugs(a)winehq.org Reporter: kotowhiskas(a)protonmail.com Distribution: --- Created attachment 73046 --> https://bugs.winehq.org/attachment.cgi?id=73046 wine log When trying to create multiplayer session, it shows "check your connection settings" because dplay fails. Installing directplay dll from winetricks fixed the issue. It's a repack because multiplayer feature is not implemented in the official demo. wine version: staging 7.16 OS: Arch Linux x86_64 Kernel: 5.19.6-arch1-1 -- 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.

1 3

[Bug 9221] Force Feedback doesn't work but does after little source modification
by WineHQ Bugzilla Sept. 8, 2022

Sept. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=9221 groybe(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |groybe(a)gmail.com --- Comment #49 from groybe(a)gmail.com --- Created attachment 73049 --> https://bugs.winehq.org/attachment.cgi?id=73049 console WINEDEBUG=+dinput No FFB with G25 on wine-7.16. Attached console output. Is there anything else you need? Thanks -- 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.

1 0

[Bug 49817] New: d3d9: Crashes on invalid opengl context with disabled csmt in IDirect3DDevice9Ex_CreateOffscreenPlainSurface
by WineHQ Bugzilla Sept. 7, 2022

Sept. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=49817 Bug ID: 49817 Summary: d3d9: Crashes on invalid opengl context with disabled csmt in IDirect3DDevice9Ex_CreateOffscreenPlainSurface Product: Wine Version: 5.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: piotr.caban(a)gmail.com Distribution: --- Created attachment 68148 --> https://bugs.winehq.org/attachment.cgi?id=68148 test that shows invalid error handling on invalid opengl context The simplest way to reproduce the crash is (I was only testing it running 32-bit process): - disable csmt - run the test with WINEDEBUG=warn+heap (to guarantee the crash) The test destroys window/hdc used by current gl context. After that it's not possible to restore previous context in Direct3DCreate9Ex. It also leads to a crash when deleting "destroyed" context in IDirect3DDevice9Ex_CreateOffscreenPlainSurface. -- 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.

1 2

[Bug 36869] New: Chronology under wine-mono fails to start
by wine-bugs＠winehq.org Sept. 6, 2022

Sept. 6, 2022

http://bugs.winehq.org/show_bug.cgi?id=36869 Bug ID: 36869 Summary: Chronology under wine-mono fails to start Product: Wine Version: 1.7.21 Hardware: x86 URL: http://store.steampowered.com/app/269330/ OS: Linux Status: NEW Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Chronology fails to start and consumes 100% of a CPU when run under wine-mono until killed. Based on a log with WINE_MONO_TRACE=wrapper, the only thing it does is call Steamworks.NativeMethods:SteamAPI_InitSafe, which is a cdecl function with no arguments. That function then endlessly throws breakpoint exceptions. InitSafe is a cdecl function with no arguments returning signed char. I have no idea how we could be screwing this up. -- 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.

2 5

[Bug 9127] Multiple applications require system stream support in the MPEG-I splitter (Drome Racers, Ninki Seiyuu no Tsukukurikata)
by WineHQ Bugzilla Sept. 6, 2022

Sept. 6, 2022

1 0