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

[Bug 53216] New: d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs
by WineHQ Bugzilla Nov. 13, 2023

Nov. 13, 2023

https://bugs.winehq.org/show_bug.cgi?id=53216 Bug ID: 53216 Summary: d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d11:d3d11 - test_depth_bias() fails in the TestBot VMs: d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected 4.99999994e-003. d3d11.c:28093: Test failed: Got depth 4.99374978e-003, expected 4.99999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected 7.49999994e-003. d3d11.c:28093: Test failed: Got depth 7.48750009e-003, expected 7.49999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected 1.24999999e-002. d3d11.c:28093: Test failed: Got depth 1.24749998e-002, expected 1.24999999e-002. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected 6.42500000e-001. d3d11.c:28093: Test failed: Got depth 6.40899956e-001, expected 6.42500000e-001. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28093: Test failed: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:27965: Test marked todo: Got 0xffffff00, expected 0x00ffffff at (0, 0, 0), sub-resource 0. d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected 0x147ae (4.99999553e-003). d3d11.c:28101: Test failed: Got value 0x14745 (4.99373704e-003), expected 0x147ae (4.99999553e-003). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected 0x1eb85 (7.49999329e-003). d3d11.c:28101: Test failed: Got value 0x1eab3 (7.48747632e-003), expected 0x1eb85 (7.49999329e-003). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected 0x33333 (1.24999888e-002). d3d11.c:28101: Test failed: Got value 0x33190 (1.24750145e-002), expected 0x33333 (1.24999888e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected 0xa47ae1 (6.42500022e-001). d3d11.c:28101: Test failed: Got value 0xa41204 (6.40899935e-001), expected 0xa47ae1 (6.42500022e-001). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28101: Test failed: Got value 0x8528f (3.25097461e-002), expected 0x85293 (3.25099845e-002). d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290 (1.00099184e-002). d3d11.c:28110: Test failed: Got value 0x28e (9.97940032e-003), expected 0x290 (1.00099184e-002). d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334 (1.25123980e-002). d3d11.c:28110: Test failed: Got value 0x331 (1.24666209e-002), expected 0x334 (1.25123980e-002). d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b (1.75020981e-002). d3d11.c:28110: Test failed: Got value 0x476 (1.74258030e-002), expected 0x47b (1.75020981e-002). d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a (6.42496376e-001). d3d11.c:28110: Test failed: Got value 0xa411 (6.40894179e-001), expected 0xa47a (6.42496376e-001). https://test.winehq.org/data/patterns.html#d3d11:d3d11 These failures: * Don't happen on Debian 11 + Intel / KDE * Happen on Debian 11 + QXL + single-monitor * Happen on Debian 11 + QXL + multi-monitor * Don't happen on Debian Testing + QXL + multi-monitor So they are probably caused by some bug in the Debian 11 QXL support. Note that despite being systematic these failures could cause false positives due to the test multi-threading (see bug 53212). -- 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 4

[Bug 16552] New: CreateIoCompletionPort fails in Chromium unit tests
by wine-bugs＠winehq.org Nov. 10, 2023

Nov. 10, 2023

http://bugs.winehq.org/show_bug.cgi?id=16552 Summary: CreateIoCompletionPort fails in Chromium unit tests Product: Wine Version: 1.1.10 Platform: Other URL: http://chromium.org OS/Version: other Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: wineserver AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com http://src.chromium.org/viewvc/chrome/trunk/src/base/message_pump_win.cc contains the code port_.Set(CreateIoCompletionPort(INVALID_HANDLE_VALUE, NULL, NULL, 1)); DCHECK(port_.IsValid()); ... HANDLE port = CreateIoCompletionPort(file_handle, port_, key, 1); DCHECK(port == port_.Get()); The DCHECK fires when running one of the Chromium unit tests: wine Debug/ui_tests.exe ... 001b:Call KERNEL32.CreateFileW(00ed7208 L"\\\\.\\pipe\\chrome.ChromeTestingInterface:8.1",c0000000,00000000,00000000,00000003,40110000,00000000) ret=010e0220 001b:Ret KERNEL32.CreateFileW() retval=000000c0 ret=010e0220 ... 0021:Call KERNEL32.CreateIoCompletionPort(ffffffff,00000000,00000000,00000001) ret=01a304b3 0021:Ret KERNEL32.CreateIoCompletionPort() retval=000000c8 ret=01a304b3 0021:Call KERNEL32.CreateIoCompletionPort(000000c0,000000c8,00ed5aa0,00000001) ret=01a30760 trace:ntdll:NtSetInformationFile (0xc0,0x7cdee318,0x7cdee320,0x00000008,0x0000001e) 0021:Ret KERNEL32.CreateIoCompletionPort() retval=00000000 ret=01a30760 0021:Call KERNEL32.OutputDebugStringA(00ed95a8 "[26:33:1249:FATAL:message_pump_win.cc(428)] Check failed: port == port_.Get(). \r\n") ret=019a7af3 I think it's failing in wineserver for some reason during NtSetInformationFile in set_completion_info. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 52792] New: Error messages for invalid .exe files could be improved
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=52792 Bug ID: 52792 Summary: Error messages for invalid .exe files could be improved Product: Wine Version: 7.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Trying to run a 0 byte .exe file under Wine will get you this: Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found. This doesn't look correct. -- 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 48004] New: winserver memory overflow
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=48004 Bug ID: 48004 Summary: winserver memory overflow Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: heiko(a)stark-jena.de Distribution: --- with default and 'wineserver -d2 -f -p10' settings I run simulations with the software Opensim (https://opensim.stanford.edu/) and restart the Opensim one after the other with a script. This seems to cause a memory overflow (> 64 GB). Kill wineserver helps to fix the memory overflow. Is there a way to debug this? Best regards, Heiko -- 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 52716] New: Sending key stroke (using [System.Windows.Forms.SendKeys]::SendWait) fails (seems to go into a loop?)
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=52716 Bug ID: 52716 Summary: Sending key stroke (using [System.Windows.Forms.SendKeys]::SendWait) fails (seems to go into a loop?) Product: Wine Version: 7.4 Hardware: x86-64 URL: https://github.com/PowerShell/PowerShell/releases/down load/v7.0.3/PowerShell-7.0.3-win-x64.msi OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Created attachment 72077 --> https://bugs.winehq.org/attachment.cgi?id=72077 ps script Hi, I have a powershell script where I need to send a keystroke to a program. I found code snippet on the internet and made little script that I tested in windows (using powershell core) and it works. It sends ctrp^p to notepad, and that opens the printer-dialog correctly on windows. On wine however it doesn`t work, cpu-usage goes up so it seems to get into loop(???) Script (also see attachment): ################################################################### Start-Process "notepad.exe" Sleep 3 $WindowHandle = Get-Process | Where-Object { $_.MainWindowTitle -Match "Notepad" } | Select-Object -ExpandProperty MainWindowHandle [void][System.Reflection.Assembly]::LoadWithPartialName('System.Windows.Forms') [System.Windows.Forms.SendKeys]::SendWait("^{p}") ##################################################################### Steps to reproduce: 1. winetricks -q dotnet48 2. wget https://github.com/PowerShell/PowerShell/releases/download/v7.0.3/PowerShel… 3. wine PowerShell-7.0.3-win-x64.msi 4. Save the script from attachment as a.ps1 in current folder 5. wine pwsh -file ./a.ps1 Notepad opens but nothing really happens and cpu-usage goes 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.

1 4

[Bug 53213] New: d3d11:d3d11 - test_texture() fails in the TestBot VMs
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=53213 Bug ID: 53213 Summary: d3d11:d3d11 - test_texture() fails in the TestBot VMs Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d11:d3d11 - test_texture() fails in the TestBot VMs: d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff0000ff at (0, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ffff at (1, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff00ff00 at (2, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffff00 at (3, 0). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff0000 at (0, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffff00ff at (1, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff7f7f7f at (3, 1). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (1, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (2, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 2). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xffffffff at (0, 3). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (2, 3). d3d11.c:9837: Test failed: Test 60: Got unexpected color 0xff000000 at (3, 3). https://test.winehq.org/data/patterns.html#d3d11:d3d11 These failures don't happen on my box which has an Intel graphics card instead of QEmu's QXL graphics card. Note also that these failures still happen on my debian11 VM which has a single monitor instead of the TestBot VMs' multi-monitor setup. So this seems to be related to the VMs QXL GPU. Note that despite being systematic these failures could cause false positives (see bug 53212). -- 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 53218] New: d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=53218 Bug ID: 53218 Summary: d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d10core:d3d10core - test_uint_shader_instructions() fails in the TestBot VMs: d3d10core.c:13215: Test failed: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d10core.c:13215: Test failed: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d10core.c:13215: Test failed: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d10core.c:13215: Test failed: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. https://test.winehq.org/data/patterns.html#d3d10core:d3d10core These failures: * Don't happen on Debian 11 + Intel / KDE * Happen on Debian 11 + QXL + single-monitor * Happen on Debian 11 + QXL + multi-monitor * Happen on Debian Testing + QXL + multi-monitor (it actually has a couple extra) So they are probably related to QXL. Note that despite being systematic these failures could cause false positives due to the test multi-threading (see bug 53212). -- 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 4

[Bug 53217] New: d3d11:d3d11 - test_cube_maps() crashes in Wine
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=53217 Bug ID: 53217 Summary: d3d11:d3d11 - test_cube_maps() crashes in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d11:d3d11 - test_cube_maps() crashes in Wine: $ WINETEST_REPORT_SUCCESS=1 WINETEST_NO_MT_D3D=1 ./wine dlls/d3d11/tests/d3d11_test.exe d3d11 Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x70baff74). [...] 0614:err:d3d:wined3d_debug_callback 00165DA0: "GL_OUT_OF_MEMORY in glMapBufferRange(map failed)". 0614:err:d3d:wined3d_allocator_chunk_gl_map Failed to map chunk memory. 0614:err:d3d:wined3d_bo_gl_map Failed to map chunk. 0614:err:d3d:wined3d_context_gl_map_bo_address Failed to map bo. Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x70baff74). [...] Backtrace: =>0 0x70baff74 memset+0x24(dst=0x000000000, c=0, n=0x4b0000) [Z:\home\winetest\tools\testbot\var\wine\dlls\msvcrt\string.c:3150] in ucrtbase (0x020ef908) 1 0x715283e3 wined3d_texture_load_location+0x423(texture=0016C8C0, sub_resource_idx=0, context=0016D920, location=0x8) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:853] in wined3d (0x020ef9a8) 2 0x715173ae surface_cpu_blt+0x9ee(dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_box=020EFB38, src_texture=00171550, src_sub_resource_idx=0, src_box=020EFB50, flags=0x20000000, fx=020EFB68, filter=WINED3D_TEXF_POINT) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:752] in wined3d (0x020efaf8) 3 0x71518ea2 cpu_blitter_blit+0xc2(blitter=0016E408, op=WINED3D_BLIT_OP_RAW_BLIT, context=0016D920, src_texture=00171550, src_sub_resource_idx=0, src_location=0x10, src_rect=020EFE10, dst_texture=0016C8C0, dst_sub_resource_idx=<is not available>, dst_location=0x8, dst_rect=020EFE20, color_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1328] in wined3d (0x020efb98) 4 0x715368a2 ffp_blitter_blit+0xa2(blitter=0016E420, op=WINED3D_BLIT_OP_RAW_BLIT, context=0016D920, src_texture=00171550, src_sub_resource_idx=0, src_location=0x10, src_rect=020EFE10, dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_location=0x8, dst_rect=020EFE20, colour_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:6213] in wined3d (0x020efc58) 5 0x714dc91d glsl_blitter_blit+0x1ad(blitter=0016E438, op=WINED3D_BLIT_OP_RAW_BLIT, context=0016D920, src_texture=00171550, src_sub_resource_idx=0, src_location=0x10, src_rect=020EFE10, dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_location=0x8, dst_rect=020EFE20, colour_key=00000000, filter=WINED3D_TEXF_POINT, resolve_format=00000000) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\glsl_shader.c:13270] in wined3d (0x020efd78) 6 0x7151a181 texture2d_blt+0x3c1(dst_texture=0016C8C0, dst_sub_resource_idx=0, dst_box=013EFAC4, src_texture=00171550, src_sub_resource_idx=0, src_box=013EFAE4, flags=0x20000000, fx=013EFB00, filter=WINED3D_TEXF_POINT) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1639] in wined3d (0x020efe48) 7 0x7149b07d wined3d_cs_exec_blt_sub_resource+0xcd(cs=013E0020, data=013EFAB8) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:2579] in wined3d (0x020efec8) 8 0x7149cb2b wined3d_cs_command_unlock(queue=<internal error>, cs=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3310] in wined3d (0x020eff28) 9 0x7149cb2b wined3d_cs_execute_next+0x53(queue=<internal error>, cs=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3309] in wined3d (0x020eff28) 10 0x7149cb2b wined3d_cs_run+0x11b(ctx=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3375] in wined3d (0x020eff28) 11 0x7b62a170 in kernel32 (+0x2a170) (0x020eff48) 12 0x7bc5a937 in ntdll (+0x5a937) (0x020eff5c) 13 0x7bc5aff0 RtlCreateUserThread(entry=7149CA10, arg=013E0020) [Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\thread.c:261] in ntdll (0x020effec) 0x70baff74 memset+0x24 [Z:\home\winetest\tools\testbot\var\wine\dlls\msvcrt\string.c:3150] in ucrtbase: movl %eax,0x0(%ebx) 3150 *(unaligned_ui64 *)(d + 0) = v; https://test.winehq.org/data/patterns.html#d3d11:d3d11 The crash happens with sub_resource_idx = 30. This impacts Debian 11 + QXL (the TestBot VMs), Intel (fg-deb64) and AMD RX460 (cw-rx460)... but only for 32-bit builds. -- 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 21

[Bug 53522] New: Need for Speed III: joystick doesn't work after evdev removal
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=53522 Bug ID: 53522 Summary: Need for Speed III: joystick doesn't work after evdev removal Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: DirtY.iCE.hu(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: adfee25b45af8160848f94fdb24279d63d5f91f4 Distribution: Gentoo Created attachment 72888 --> https://bugs.winehq.org/attachment.cgi?id=72888 WINEDEBUG=+dinput, ds4 usb, overriden, nfs3 demo with git master wine I decided to try NFS3 after some time and realized that joystick no longer works with newer releases. Git bisect lead me to commit adfee25b45af8160848f94fdb24279d63d5f91f4, where the evdev and js backends were removed. With the new backend, in NFS3 deadzone calibration screen, all axes are at constant 0, and it doesn't respond to any keypress either. I've tried it with DualShock 4 (both usb and bt), DS3 (only usb), and some noname cheap controller, the same results. Interestingly, in joy.cpl the joysticks do work, I've tried to click on override to move the controller from the xinput to the non-xinput list, but no change. I also have no force-feedback support with the new backend. Tested it with the retail version of nfs3 and also with this patch, the results are the same: https://veg.by/en/projects/nfs3/ Also tested it with the demo version and the latest git (bfc73b0b80a1da2b137b5da4a2fcf530ee3a9d7d), same results. 1. Download demo from here: https://archive.org/details/nfs3_demo 2. Create a new 32-bit wine prefix (I've only compiled a 32-bit wine) 3. In winecfg, set windows compatibility to 98 (otherwise the install refuses to start), go to drives and add a (fake) cdrom device (otherwise setup refuses to start), and probably you should set a virtual desktop (the game likes to mess with your resolution) 4. Run setup.exe (it will throw a registry error but still installs the game) 5. Start the game with taskset: `taskset -c 0 path/to/wine nfs3demo -d3d0` (the game crashes/freezes if run on multicore cpu) 6. After the race countdown, press esc, controls, and try to bind some keys or click on dead zone to see axes values. I'm attaching a log with WINEDEBUG=+dinput and overridden joystick on joy.cpl. -- 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 49988] New: NosTale (and probably some other games) doesn't handle mouse clicks correctly
by WineHQ Bugzilla Nov. 10, 2023

Nov. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=49988 Bug ID: 49988 Summary: NosTale (and probably some other games) doesn't handle mouse clicks correctly Product: Wine Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: theszczepancio(a)gmail.com Distribution: --- Created attachment 68390 --> https://bugs.winehq.org/attachment.cgi?id=68390 Wine-staging 5.19 log Releated issues: https://bugs.winehq.org/show_bug.cgi?id=42999 https://bugs.winehq.org/show_bug.cgi?id=21739 Some info: Tested the issue with wine and wine-staging. Bug persists in 5.17, 5.18, 5.19 versions of wine. I have installed Arch Linux on r5 3600/rx5700 XT. I use D9VK (newest) for improvements of performance. Installing dinput8 is not fixing anything. I use Sway/wlroots on wayland, also I own newest kernel. Game works as should on steam proton with same version of D9VK. OpenGL backend works fine. Wine log in attachement. -- 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 14