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

[Bug 41080] New: Need For Speed Most Wanted 2005 not working after upgrade from Ubuntu 14.04 to 16.04
by wine-bugs＠winehq.org Oct. 22, 2021

Oct. 22, 2021

https://bugs.winehq.org/show_bug.cgi?id=41080 Bug ID: 41080 Summary: Need For Speed Most Wanted 2005 not working after upgrade from Ubuntu 14.04 to 16.04 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: naheelazawy(a)gmail.com Distribution: --- Created attachment 55265 --> https://bugs.winehq.org/attachment.cgi?id=55265 backtrace The game was working great on Ubuntu 14.04 but now after upgrading to 16.04 it just doesn't work. And by the way, I tried various versions of wine and nothing worked so far. -- 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 43

[Bug 34297] New: Allow reconnecting to disconnected joysticks
by wine-bugs＠winehq.org Oct. 22, 2021

Oct. 22, 2021

http://bugs.winehq.org/show_bug.cgi?id=34297 Bug #: 34297 Summary: Allow reconnecting to disconnected joysticks Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: achurch+wine(a)achurch.org Classification: Unclassified Created attachment 45660 --> http://bugs.winehq.org/attachment.cgi?id=45660 Proof-of-concept patch Currently, if a joystick is disconnected and then reconnected (because the cable is pulled out, for example), Wine acts as though the joystick is present but stuck at the last state it reported, and it fails to report any subsequent changes in device state, which is an arguably suboptimal user experience. The attached patch (against 1.7.0) changes the Linux evdev driver to attempt to reopen a joystick device after a read fails. This patch uses the simple heuristic of "if it's on the same device file and has the same name, it's the same joystick", which means (1) it won't reconnect if the device file changes and (2) it could falsely reconnect if there are multiple input devices with the same name, but it works for simple circumstances. Naturally, one could iterate over all possible input devices to try and find the device, but that could be fairly expensive to do on every poll operation, and it would probably involve concurrency issues relating to checking whether the device is already known as a different joystick. In the long run, it might be better to monitor the /dev/input directory for added and removed devices (perhaps using inotify) and use those events to handle reconnection. -- 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 10

[Bug 42695] New: PoE fail to start when launching with dx11 enabled
by wine-bugs＠winehq.org Oct. 22, 2021

Oct. 22, 2021

https://bugs.winehq.org/show_bug.cgi?id=42695 Bug ID: 42695 Summary: PoE fail to start when launching with dx11 enabled Product: Wine-staging Version: 2.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gufideg(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 57663 --> https://bugs.winehq.org/attachment.cgi?id=57663 console output I get an error from Poe that says: "Failed to retrive IDXGIFactory from adapter": In source code file: ..\Device \D3D11\DeviceD3D11.cpp at line 336, Processing file: Failed to retrive IDXGIFactory from adapter Error: E_NOINTERFACE Description: Message: Then I click OK and the game closes. Works nicely with dx9 and dx9 ex -- 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 69

[Bug 49296] New: ZWCAD 2020: cannot select the installation folder; the program doesn't start.
by WineHQ Bugzilla Oct. 22, 2021

Oct. 22, 2021

https://bugs.winehq.org/show_bug.cgi?id=49296 Bug ID: 49296 Summary: ZWCAD 2020: cannot select the installation folder; the program doesn't start. Product: Wine Version: 5.9 Hardware: x86-64 OS: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: depositmail(a)mail.ru Created attachment 67300 --> https://bugs.winehq.org/attachment.cgi?id=67300 Cannot select the installation folder. Hi, I tried to install the perfect program for drawing ZWCAD (a complete replacement for AutoCAD). At first, I couldn't select the installation folder (screenshot attached). But this is still half the trouble (the program is installed in the default folder). Then the program refused to start (log file attached). -- 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 29

[Bug 38696] New: Messy screen in DxTex.exe
by wine-bugs＠winehq.org Oct. 22, 2021

Oct. 22, 2021

https://bugs.winehq.org/show_bug.cgi?id=38696 Bug ID: 38696 Summary: Messy screen in DxTex.exe Product: Wine Version: 1.7.44 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Created attachment 51621 --> https://bugs.winehq.org/attachment.cgi?id=51621 messy screen with wine-hq Steps to reproduce: Start DxTex.exe that is included in DirectxSDK available for download from https://www.microsoft.com/en-us/download/details.aspx?id=6812 1. New texture. Settings default 2. Open onto this surface and choose any graphic file. 3. see... With wine-stage the screen is good. To be sure: I used unmodified sources on wine-hq and wine-stage. There are no my patches at all. All settings are the same, just changed wine prefix. The logs difference is probably in this line ---- fixme:win:EnumDisplayDevicesW ((null),0,0x33f42c,0x00000000), stub! ---- -- 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 50607] New: Ghostrunner hangs when exit from Echoes level
by WineHQ Bugzilla Oct. 22, 2021

Oct. 22, 2021

https://bugs.winehq.org/show_bug.cgi?id=50607 Bug ID: 50607 Summary: Ghostrunner hangs when exit from Echoes level Product: Wine-staging Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lvb.crd(a)protonmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 69292 --> https://bugs.winehq.org/attachment.cgi?id=69292 terminal output wine-staging-6.1.r2.g32b29ad4.log Not sure if the problem is specifically related to Gstreamer, the `mfplat-streaming-support` patchset, or opens the problem in Wine itself. The game freezes, if you load the level, wait until the video on the first billboard will be played 1 time (for this one it is 22 seconds and the zone with it is close enough to the starting point, so that the video starts playing almost immediately. You can try to rely by the in-game timer or verbose terminal output), and then try to end/leave the zone (continue the game by going to Cybervoid or exit to the Main menu). I did some tests and found that using Wine + `mfplat-streaming-support` from Staging is enough to reproduce the problem. Inside the game, videos on billboards are played only 2 times (I'm not sure if this is correct because in this case, you will not even have the opportunity to see them, while you get to them in the game way), but despite the fact that the video is repeated a second time, the game will definitely freeze if you tried to exit at that moment or when it finishes showing the video a second time and stops. So, the minimal steps for repro: 1. will load into the Echoes level. 2. do not move and wait until the in-game timer (lower right corner) is more than 23 seconds. 3. press Esc and exit to the Main menu. I'm attachig some (add +timestamp,+tid,warn+mfplat and GST_DEBUG="3") terminal output timestamp 330.821 - loading on the level timestamp ~332-354 - this 22 seconds video (PROPAGANDA_FLASH6.mp4) (already after 354 the game definitely will be freeze if try exit) timestamp 372.887 - exit to the Main menu and hang also at the beginning the game plays 2 intro videos gstreamer: 1.18.3 (patched for mfplat-streaming-support) wine version: wine-staging-6.1.r2.g32b29ad4 game version: 0.32091.426 (I suppose it is possible to shorten or replace the video if the wait 22 seconds is too long for the terminal output) I also found that removing Ghostrunner/Content/Movies/LA/PROPAGANDA_FLASH6.mp4 (first billboard) Ghostrunner/Content/Movies/LA/PROPAGANDA_ANIM_DRONE2M.mp4 (it video for second billboard what is next on this level) - helps as workaround. (I was able to finish the whole game, after deleting these two files. There were no more such problems with video on billboards at other levels.) It also seems that the game does not swear at the substitution of these video files, so I tried: - replace video with a adjacent file from the same directory. - compress video with cfr=28 (file size less than 2MB) - https://github.com/ValveSoftware/wine/commit/3af15c54a6d8c781cbe32faa61b274… - delete audio stream. but none of this seems to help. I only have the Epic Games Store version of the game. (the launcher requires: WINEDLLOVERRIDES="libglesv2=d" wine64 EpicGamesLauncher.exe -opengl -SkipBuildPatchPrereq) Also to fully complete the game, in addition to mfplat-streaming-support, I had to use esync and vkd3d-proton (third-party dll). But I managed to reproduce the problem also on wined3d (dx11 mode) (but this is complicated by the fact that textures are not rendered on wined3d (opengl) so wined3d (vulkan) will sometimes be preferable because he has no such problem) and on dxvk (third-party dll). Please check it. -- 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 40658] New: Joystick POW hat switch rotated for JOYDEVDRIVER=(js) while JOYDEVDRIVER=(event) is Ok
by wine-bugs＠winehq.org Oct. 21, 2021

Oct. 21, 2021

https://bugs.winehq.org/show_bug.cgi?id=40658 Bug ID: 40658 Summary: Joystick POW hat switch rotated for JOYDEVDRIVER=(js) while JOYDEVDRIVER=(event) is Ok Product: Wine Version: 1.9.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: otty(a)gmx.net Distribution: --- I have a Saitek AV8R-01 joystick with a POV hat switch. When using the JOYDEVDRIVER=(event) device (dinput/joystick_linuxinput.c), the orientation is Ok both in the Wine Control Panel (control.exe) Joystick test POV area and in the games, i.e when moving the hat switch horizontally to the right the indicator moves towards the right, when moving the hat switch vertically up, the indicator moves up. Hoever the JOYDEVDRIVER=(js) device (dinput/joystick_linux.c) has its orientation mixed up: * when moving the hat switch horizontally to the right the indicator moves down. * when moving the hat switch vertically up, the indicator moves left. This happens on wine-1.9.9 on Ubuntu 14.04 (LTS) installed from http://ppa.launchpad.net/wine/wine-builds/ubuntu trusty main, but is also present in earlier versions, e.g. 1.6.1 Unfortunately I need to use the (js) device as I cannot get the game to recognise the rudder and thrust axes with the (event) device. (BTW, does the (event) device recognize the [HKEY_CURRENT_USER\Software\Wine\DirectInput] registry key in the same way as teh (js) device?) BR, -- 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 37

[Bug 44590] New: incorrect rendering in The Witness (ATOC?)
by wine-bugs＠winehq.org Oct. 21, 2021

Oct. 21, 2021

https://bugs.winehq.org/show_bug.cgi?id=44590 Bug ID: 44590 Summary: incorrect rendering in The Witness (ATOC?) Product: Wine Version: 3.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: notasas(a)gmail.com Distribution: --- Created attachment 60571 --> https://bugs.winehq.org/attachment.cgi?id=60571 bad rendering The Witness is still not rendering correctly in some cases (as of 7be8beab68c5): - objects in the water reflections are missing transparencies regardless of MSAA - all objects are missing transparencies with MSAA off perhaps these problems are related. Here is d3d apitrace (different from screenshot, can make a better one if that helps): https://drive.google.com/file/d/1fFCVytDdybsVgZqiTIKS5XseegIO5yzc/view?usp=… -- 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 42191] New: Diablo 3 2.4.3 was unable to initialize D3D
by wine-bugs＠winehq.org Oct. 21, 2021

Oct. 21, 2021

https://bugs.winehq.org/show_bug.cgi?id=42191 Bug ID: 42191 Summary: Diablo 3 2.4.3 was unable to initialize D3D Product: Wine Version: 2.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: nfamail(a)gmail.com Distribution: --- Created attachment 56824 --> https://bugs.winehq.org/attachment.cgi?id=56824 Diablo 3 Debug Log When I try to run the game in 64 bit after that I get the grey screen and the error creating d3d. Click ok a couple of times and it then gives you the option to retry/cancel and will do nothing. If you go to the battle.net app and go to game settings and change it to "Open game with 32-bit version instead" it will open just fine... Winehq 2.0-rc4 Ubuntu 16.04 64bit (latest updates) Intel® Core™ i7-4510U CPU @ 2.00GHz × 4 GeForce 840M/PCIe/SSE2 Battle.net 1.6.0.8265 (2.9.2.5362) Diablo 3 2.4.3.42934 -- 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 41

[Bug 21564] New: warning forever ignores keyboard input after losing/regaining focus
by wine-bugs＠winehq.org Oct. 21, 2021

Oct. 21, 2021

http://bugs.winehq.org/show_bug.cgi?id=21564 Summary: warning forever ignores keyboard input after losing/regaining focus Product: Wine Version: 1.1.37 Platform: x86 URL: http://www18.big.or.jp/~hikoza/Prod/index_e.html OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: madewokherd(a)gmail.com Steps to reproduce: * Install Warning Forever from the linked website. * Start the program by running c:\wf\wf.exe. (The installer does not create a shortcut. This is the same on Windows.) * Select "Window mode". * Verify that the 'z' key can be used to make selections in the menu. * Switch to another window. * Switch back to Warning Forever window. * Verify that keyboard input no longer works. -- 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 22