https://bugs.winehq.org/show_bug.cgi?id=45489
Bug ID: 45489 Summary: World of Warcraft needs GetRawInputBuffer Product: Wine Version: 3.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: blue-t@web.de Distribution: ---
Since 8.0.1 i noticed quite a lot of noisy GetRawInputBuffer lines. Performance should be a lot better with this deduplicated or better implemented.
https://bugs.winehq.org/show_bug.cgi?id=45489
--- Comment #1 from Ker noa blue-t@web.de --- Created attachment 61844 --> https://bugs.winehq.org/attachment.cgi?id=61844 Logfile 3.12-staging WoW 8.0.1
https://bugs.winehq.org/show_bug.cgi?id=45489
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #2 from Fabian Maurer dark.shadow4@web.de --- Is there a real issue here? If the program runs properly I don't see a problem. You can always disable those FIXMEs by setting WINEDEBUG, if it's for performance.
https://bugs.winehq.org/show_bug.cgi?id=45489
--- Comment #3 from Matteo Bruni matteo.mystral@gmail.com --- Actually you should run Wine with WINEDEBUG=-all when you're not debugging some Wine issue. That doesn't simply silence traces, it also e.g. disables many error checks in wined3d. That's going to be even more significant as further performance improvements will be introduced in the future.
https://bugs.winehq.org/show_bug.cgi?id=45489
Steve Ebey eaglecomputers.ok@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eaglecomputers.ok@gmail.com
--- Comment #4 from Steve Ebey eaglecomputers.ok@gmail.com --- Does this bug exist in any of the more recent versions of wine or wine-staging, and if not, should this be listed as resolved?
https://bugs.winehq.org/show_bug.cgi?id=45489
Kimball kdt3rd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kdt3rd@gmail.com
--- Comment #5 from Kimball kdt3rd@gmail.com --- (In reply to Steve Ebey from comment #4)
Does this bug exist in any of the more recent versions of wine or wine-staging, and if not, should this be listed as resolved?
WoW does use this function, and it is still an unimplemented function in user32 as of wine 5.7. While this GetRawInputBuffer path might be faster for event processing, it does not appear to affect game play having it unimplemented
https://bugs.winehq.org/show_bug.cgi?id=45489
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Fixed by SHA1| |3a9edf9aad43c3e8ba724571da5 | |381f821f1dc56 Component|-unknown |user32 Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Gijs Vermeulen gijsvrm@gmail.com --- This function was implemented by https://source.winehq.org/git/wine.git/commit/3a9edf9aad43c3e8ba724571da5381f821f1dc56, marking FIXED.
https://bugs.winehq.org/show_bug.cgi?id=45489
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 5.19.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla