January 2019 - Wine-bugs - list.winehq.org

[Bug 46506] New: Why are you still not using Vulkan for WineD3D for D3D9, D3D10, D3D11? Why are you still using OpenGL?
by wine-bugs＠winehq.org 25 Jan '19

25 Jan '19

https://bugs.winehq.org/show_bug.cgi?id=46506 Bug ID: 46506 Summary: Why are you still not using Vulkan for WineD3D for D3D9, D3D10, D3D11? Why are you still using OpenGL? Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zefkerrigan(a)gmail.com Distribution: --- Hi! Thank you very much for you great work! Why are you still not using Vulkan for WineD3D for D3D9, D3D10, D3D11? Why are you still using OpenGL? The dizzying success of the DXVK project proved that using Vulkan provides excellent performance in D3D10 and D3D11 games. There is a huge amount of evidence that when using the Wine+DXVK bundle, usually only about ~10% performance loss is obtained relative to launching the same Windows game natively on Windows. But if you run the same game using the usual WineD3D, then the loss of performance is usually about ~80%, and this in turn deprives we of any reason to launch games using WineD3D. But DXVK has a free ZLIB license and open source code. Why not replace the WineD3D with the DXVK inside of the Wine code? Or at least it might be worth using the default DXVK in Wine, with the option of optionally choosing WineD3D for a GPUs without Vulkan support? Or perhaps DXVK would be used by default in Wine, and if some user couldn’t use Vulkan, would Wine automatically switch to WineD3D mode? I believe that the benefits of high performance, which gives the use of DXVK and Vulkan are very important. Please, see here: https://github.com/doitsujin/dxvk Thank you! -- 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 13

[Bug 46464] New: Strong hold 2 needs a native dll fallback mechanism
by wine-bugs＠winehq.org 22 Jan '19

22 Jan '19

https://bugs.winehq.org/show_bug.cgi?id=46464 Bug ID: 46464 Summary: Strong hold 2 needs a native dll fallback mechanism Product: Wine Version: 4.0-rc6 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: zzhang(a)codeweavers.com Distribution: --- Created attachment 63272 --> https://bugs.winehq.org/attachment.cgi?id=63272 patch See https://github.com/ValveSoftware/Proton/issues/506 for details. Strong hold 2 doesn't run. For it to run, use the following steps: $ STEAM_COMPAT_DATA_PATH=~/.steam/steam/steamapps/compatdata/40960 ~/.steam/steam/compatibilitytools.d/proton/proton run ~/.steam/steam/steamapps/compatdata/40960/pfx/drive_c/windows/system32/winecfg.exe And set msvcr100.dll and msvcp100.dll to builtin. And FFLauncher.exe is a .NET application. Since proton doesn't have mono support yet. We need to rename rename Stronghold2.exe to FFLaucher.exe, then it will launch. $ cd ~/.steam/steam/steamapps/common/Stronghold\ 2/ $ file msvcp100.dll msvcp100.dll: PE32+ executable (DLL) (GUI) x86-64, for MS Windows $ file FFLauncher.exe FFLauncher.exe: PE32 executable (GUI) Intel 80386, for MS Windows So the reason that the game doesn't run on proton is that it is bundled with dlls of wrong architecture in its application folder. On Windows, there is a dll architecture check[1] when loading dlls, whereas wine currently loads the first found. [1] Windows Internals # Known Dll Redirection: https://books.google.com/books?id=y83LDgAAQBAJ&pg=PT282&dq=dll+of+wrong+arc… -- 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 5402] Multiple MFC-based apps crash during non-modal child dialog control creation with active window being zero (Canon PhotoStitch 3.1.13, Flexible Renamer v8.4)
by wine-bugs＠winehq.org 22 Jan '19

22 Jan '19

https://bugs.winehq.org/show_bug.cgi?id=5402 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|1.2.0 |3.0.x -- 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 46491] New: "harddisk_ioctl Unsupported ioctl 2d0c00 (and 4d004)" breaks Olympus camera firmware updater
by wine-bugs＠winehq.org 21 Jan '19

21 Jan '19

https://bugs.winehq.org/show_bug.cgi?id=46491 Bug ID: 46491 Summary: "harddisk_ioctl Unsupported ioctl 2d0c00 (and 4d004)" breaks Olympus camera firmware updater Product: Wine Version: 4.0-rc7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys Assignee: wine-bugs(a)winehq.org Reporter: bero(a)lindev.ch Distribution: --- The Olympus camera firmware updater (http://support.olympus-imaging.com/ou1download/) installs correctly, but fails to detect the camera. The camera is supposed to be connected in USB storage mode (that works overall, I see the camera as drive f: in "wine explorer.exe"); chances are the firmware updater would work if only it could identify the camera correctly instead of seeing it as some generic storage device. While probing for the camera, wine says 0019:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d0c00 (device=2d access=0 func=300 method=0) 0019:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d004 (device=4 access=3 func=401 method=0) I don't know anything about Windows IOCTLs, but I suppose those read a hardware identifier? -- 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 46486] New: Problem with mouse input when using two monitors
by wine-bugs＠winehq.org 20 Jan '19

20 Jan '19

https://bugs.winehq.org/show_bug.cgi?id=46486 Bug ID: 46486 Summary: Problem with mouse input when using two monitors Product: Wine Version: 4.0-rc7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bedp4488(a)protonmail.com Distribution: --- I'm using two monitors and have problem with mouse input. Monitor on my right is the main monitor. This picture explain when mouse input doesn't work in wine : https://imgur.com/a/hNAqvvS -- 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 8563] MechWarrior 4: Vengeance fails to start
by wine-bugs＠winehq.org 19 Jan '19

19 Jan '19

https://bugs.winehq.org/show_bug.cgi?id=8563 Paul Gofman <gofmanp(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gofmanp(a)gmail.com -- 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 8563] MechWarrior 4: Vengeance fails to start
by wine-bugs＠winehq.org 19 Jan '19

19 Jan '19

https://bugs.winehq.org/show_bug.cgi?id=8563 auxsvr(a)yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |auxsvr(a)yahoo.com -- 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 3756] ATMEL AVRStudio4 crash
by wine-bugs＠winehq.org 19 Jan '19

19 Jan '19

https://bugs.winehq.org/show_bug.cgi?id=3756 --- Comment #62 from james lara <james621lara(a)gmail.com> --- Hello there! I’d like to thank you for the shared websites. I’ll find the time to check each of the links above! It’s a quite big list of blogs! Game Lover - https://games.lol/puzzle/ -- 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 3756] ATMEL AVRStudio4 crash
by wine-bugs＠winehq.org 19 Jan '19

19 Jan '19

https://bugs.winehq.org/show_bug.cgi?id=3756 james lara <james621lara(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |james621lara(a)gmail.com --- Comment #61 from james lara <james621lara(a)gmail.com> --- I got this site from my friend who shared with me regarding this website and now this time I am browsing this web page and reading very informative posts here. Thanks Game Lover - https://games.lol/arcade/ -- 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 46477] New: wine not compatible nwt, it will occur one error
by wine-bugs＠winehq.org 19 Jan '19

19 Jan '19

https://bugs.winehq.org/show_bug.cgi?id=46477 Bug ID: 46477 Summary: wine not compatible nwt, it will occur one error Product: Wine Version: 3.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: smilence86(a)gmail.com Distribution: --- Created attachment 63300 --> https://bugs.winehq.org/attachment.cgi?id=63300 somewhen it will show an error window when I open one contact hello, I installed wine, the command line "wine --version" show "wine-3.0 (Ubuntu 3.0-1ubuntu1)". I run "winecfg" set the windows version to "Windows vista". then I need run this software in my ubuntu: http://www.51nwt.com/download.htm http://imoup.lieqikankan.com/update/nwt_setup_3.4.3044.exe It's a IM software in windows, but I found iptux can't compatible with it. so I run "wine nwt_setup_3.4.3044.exe" to install it, then I changed font to simsun.ttf to resovle garbled. And now only one bug left, somewhen it will show an error window when I open one contact, please look at the screenshot in attachment. thank you. -- 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 6