June 2021 - Wine-Bugs - list.winehq.org

[Bug 42856] New: osu! - high sound latency with winepulse compared to winealsa
by wine-bugs＠winehq.org April 20, 2023

April 20, 2023

https://bugs.winehq.org/show_bug.cgi?id=42856 Bug ID: 42856 Summary: osu! - high sound latency with winepulse compared to winealsa Product: Wine Version: 2.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dsound Assignee: wine-bugs(a)winehq.org Reporter: yalterz(a)gmail.com Distribution: --- I'm trying to set up PulseAudio to achieve the same low audio latency as I'm getting with just ALSA. Looks like I managed to achieve this, but not as I would expect. Currently my setup is: PulseAudio with default configuration, along with pulseaudio-alsa integration which basically forwards all ALSA-using programs straight to Pulse. I am using patched winealsa.drv for reduced latency (changing three constants at the top of mmdevdrv.c — DefaultPeriod, MinimumPeriod, EXTRA_SAFE_RT — to lower values, the ones that work for me: 20000, 20000, 11000 respectively). I applied a very similar patch to winepulse.drv. When running osu! through ALSA (sound=alsa), which effectively runs it through ALSA->PulseAudio->ALSA device, the audio latency is almost non-existant — similar if not the same as what I was getting with just ALSA. When running osu! through PulseAudio (sound=pulse), effectively PulseAudio->ALSA device, the audio latency is noticeably higher (at least 20ms higher), even though it practically removes one extra step from the audio "chain". -- 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 19

[Bug 50923] New: Long freezes in osu! when searching in beatmaps
by WineHQ Bugzilla April 20, 2023

April 20, 2023

https://bugs.winehq.org/show_bug.cgi?id=50923 Bug ID: 50923 Summary: Long freezes in osu! when searching in beatmaps Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: openglfreak(a)googlemail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 69739 --> https://bugs.winehq.org/attachment.cgi?id=69739 Patch that adds a single-entry sortguid cache to sortkey_compare Wine-Staging patchset libs-Unicode_Collation makes CompareStringEx far slower than before. This is because the sortkey_compare function added by the last patch and used by CompareStringEx makes a call to get_language_sort, which is not exactly cheap (it reads from the registry which involves server calls). A small patch that adds a simple cache for the last used sortguid makes the search function fast again. -- 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 5

[Bug 43769] New: Regression, osu!.exe freezes a few seconds after you start it, probably a critical zone inter thread deadlock
by wine-bugs＠winehq.org April 20, 2023

April 20, 2023

https://bugs.winehq.org/show_bug.cgi?id=43769 Bug ID: 43769 Summary: Regression, osu!.exe freezes a few seconds after you start it, probably a critical zone inter thread deadlock Product: Wine-staging Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matthias291999(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- wine-staging 2.17 causes my game called "osu!" to enter deadlock shortly after the audio starts playing. Works fine in wine-staging 2.16 Someone do a git blame on the audio system, could be it, don't know, all i know is that it works fine in wine-staging 2.16. If you have any tests that may give you more info, go ahead. I can not get out of borderless fullscreen, dont know why, dont care to report a 2'nd bug, as it works fine, and i can deal with it. I have CSMT enabled. If i have to disable CSMT, that is just a temporary fix, I am not at all satisfied if you seguest i disable it, go test it yourself, if you can actually reproduce my bug with CSMT enabled, go ahead and prove i could run it wo CSMT enabled with a video recording... -- 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 8

[Bug 48360] New: osu: .NET framework IndexOutOfRangeException crash
by WineHQ Bugzilla April 20, 2023

April 20, 2023

https://bugs.winehq.org/show_bug.cgi?id=48360 Bug ID: 48360 Summary: osu: .NET framework IndexOutOfRangeException crash Product: Wine Version: 4.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bugs.winehq(a)webfreak.org CC: julliard(a)winehq.org Regression SHA1: df3fad6383e79d1485413ad549c55240843d2418 Distribution: ArchLinux Created attachment 66104 --> https://bugs.winehq.org/attachment.cgi?id=66104 crash log occuring with wine 4.16 since wine 4.16 the game "osu!" started crashing often. For more application-specific context see the bug report there for more details: https://github.com/ppy/osu-stable-issues/issues/284 It seems that on Windows no such issue is present and prior to wine 4.15 this bug was not present. It seems to be an issue somewhere with array indexing on .NET inside some rendering function. This crash occurs when starting the game "osu!" and then moving the mouse cursor relatively quickly (causing longer lines to be rendered) The issue in wine seems to be that the behavior of the page faults has changed in df3fad6383e79d1485413ad549c55240843d2418 so that now it started to throw array index exceptions which don't happen on Windows. I have attached the full application log with ntdll warn log up with the crash with Wine 4.16 (precompiled from ArchLinux archives) -- 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 8

[Bug 45402] New: Sniper Elite V2 benchmark tool: white texture glitch
by wine-bugs＠winehq.org April 20, 2023

April 20, 2023

https://bugs.winehq.org/show_bug.cgi?id=45402 Bug ID: 45402 Summary: Sniper Elite V2 benchmark tool: white texture glitch Product: Wine Version: 3.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: moihack.inside(a)gmail.com Distribution: ArchLinux Created attachment 61715 --> https://bugs.winehq.org/attachment.cgi?id=61715 Sniper Elite V2 benchmark tool - white textures glitch You can download the free benchmark tool from here: http://www.guru3d.com/files-details/sniper-elite-v2-benchmark-tool.html The benchmark installs, runs and exits fine under wine. Yet, there are some white "glitched" textures here and there while the camera flies in the scene (see attached screenshoot). Here is how a normal run should look: https://www.youtube.com/watch?v=WNs3mnKAdRQ (without the glitched textures) System: Arch Linux fully updated with wine-3.11 and Radeon HD6870 GPU. -- 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 50619] New: Sniper Elite V2 has broken rendering with OpenGL renderer
by WineHQ Bugzilla April 20, 2023

April 20, 2023

https://bugs.winehq.org/show_bug.cgi?id=50619 Bug ID: 50619 Summary: Sniper Elite V2 has broken rendering with OpenGL renderer Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 69309 --> https://bugs.winehq.org/attachment.cgi?id=69309 example How it looks on AMD. wine-6.1-122-g2201ca08fb0 -- 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 50616] New: Sniper Elite 3 has broken rendering with OpenGL renderer
by WineHQ Bugzilla April 20, 2023

April 20, 2023

https://bugs.winehq.org/show_bug.cgi?id=50616 Bug ID: 50616 Summary: Sniper Elite 3 has broken rendering with OpenGL renderer Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 69307 --> https://bugs.winehq.org/attachment.cgi?id=69307 example When bug 50235 is for NVIDIA this one is for AMD. wine-6.1-122-g2201ca08fb0 -- 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 43637] New: Fallout New Vegas: Crash on launch using 64-bit prefix
by wine-bugs＠winehq.org April 20, 2023

April 20, 2023

https://bugs.winehq.org/show_bug.cgi?id=43637 Bug ID: 43637 Summary: Fallout New Vegas: Crash on launch using 64-bit prefix Product: Wine Version: 2.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iamtimscampi(a)gmail.com Distribution: --- Upon launching Fallout New Vegas (With or without New Vegas Script Extender) on a 64-bit prefix, the game crashes after the initial splash screen. On a 32-bit prefix, the game works as intended, without a crash. This was tested both with Staging and regular versions of Wine, with and without the "New Vegas Script Extender" addon. While not necessary to play the game, a 64bit prefix is necessary for the new version of Mod Organizer, a third party utility for the game that handles mod loading. This crash prevents users from using the latest version of it alongside the game. -- 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 38381] New: Fallout New Vegas (Steam Version) Crashes at Startup on the Splash Screen
by wine-bugs＠winehq.org April 20, 2023

April 20, 2023

https://bugs.winehq.org/show_bug.cgi?id=38381 Bug ID: 38381 Summary: Fallout New Vegas (Steam Version) Crashes at Startup on the Splash Screen Product: Wine Version: 1.7.40 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gordan(a)bobich.net Distribution: --- Created attachment 51228 --> https://bugs.winehq.org/attachment.cgi?id=51228 Fallout New Vegas Crash Backtrace Fallout New Vegas (Steam Version) Crashes at Startup on the Splash Screen. -- 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 9

[Bug 49051] New: Got "rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0" in Fallout3 and NV
by WineHQ Bugzilla April 20, 2023

April 20, 2023

https://bugs.winehq.org/show_bug.cgi?id=49051 Bug ID: 49051 Summary: Got "rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0" in Fallout3 and NV Product: Wine-staging Version: 5.7 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: avenjames(a)live.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com As title description I got this problem since I updated version after 5.0 stable, from 5.1 to 5.7 stable/staging/dev, the game's cursor could hardly move and unhandled at all. I tested version 5.7 staging as usually as I did once notice the update's coming, but this time I got messages: 0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0. 0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0. 0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0. 0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0. I think it must be related to the problem that I have, any idea friends? -- 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 8