[Bug 43935] New: Wolfenstein 2: The new Colossus does not start, requires VK_KHR_get_physical_device_properties2
https://bugs.winehq.org/show_bug.cgi?id=43935 Bug ID: 43935 Summary: Wolfenstein 2: The new Colossus does not start, requires VK_KHR_get_physical_device_properties2 Product: Wine-staging Version: 2.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: philip.rebohle(a)tu-dortmund.de CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59575 --> https://bugs.winehq.org/attachment.cgi?id=59575 vkGetPhysicalDeviceProperties2KHR hack The game crashes on startup, with wine complaining that vkGetPhysicalDeviceProperties2KHR (from the VK_KHR_get_physical_device_properties2 extension) is not implemented. I'm using wine-staging 2.19 and the RADV driver, which supports the extension. The attached patch provides a dummy implementation of this function that falls back to calling vkGetPhysicalDeviceProperties, which allows the game to start. I apologize that I have no idea how to properly implement Vulkan functions in wine, it's just a very dirty hack. Note that even with the patch the game doesn't even render the menu on my system, but that might be due to driver issues. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Anthony Jagers <noonetinone(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noonetinone(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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Dave Airlie <airlied(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |airlied(a)gmail.com --- Comment #1 from Dave Airlie <airlied(a)gmail.com> --- Going to see if I can bring this up on radv, will need a proper wine fix of course. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 GloriousEggroll(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |GloriousEggroll(a)gmail.com --- Comment #2 from GloriousEggroll(a)gmail.com --- can confirm this hack does actually get the game to launch, but gives a black screen once you get past the machinegames animation and the copyright information. tested on vega 64 with radv on mesa 17.2.2 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 mo78(a)abv.bg changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mo78(a)abv.bg --- Comment #3 from mo78(a)abv.bg --- I can confitm this bug too: fixme:winediag:start_process Wine Staging 2.19 is a testing version containing experimental patches. fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. fixme:heap:RtlSetHeapInformation 0x550000 0 0x32ed20 4 stub fixme:ver:GetCurrentPackageId (0x32d270 (nil)): stub fixme:win:DisableProcessWindowsGhosting : stub fixme:heap:RtlSetHeapInformation 0x10000 0 0x23ee4f8 4 stub fixme:module:load_dll Loader redirect from L"wined3d.dll" to L"wined3d-csmt.dll" err:module:import_dll Library d3d11.dll (which is needed by L"C:\\windows\\system32\\nvapi64.dll") not found fixme:vulkan:vkGetInstanceProcAddr missing function "vkGetPhysicalDeviceProperties2KHR" fixme:bcrypt:BCryptGenRandom ignoring selected algorithm fixme:bcrypt:BCryptGenRandom ignoring selected algorithm wine: Unhandled page fault on execute access to 0x00000000 at address (nil) (thread 0030), starting debugger... -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #4 from mo78(a)abv.bg --- (In reply to mo78 from comment #3)
I can confitm this bug too:
fixme:winediag:start_process Wine Staging 2.19 is a testing version containing experimental patches. fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. fixme:heap:RtlSetHeapInformation 0x550000 0 0x32ed20 4 stub fixme:ver:GetCurrentPackageId (0x32d270 (nil)): stub fixme:win:DisableProcessWindowsGhosting : stub fixme:heap:RtlSetHeapInformation 0x10000 0 0x23ee4f8 4 stub fixme:module:load_dll Loader redirect from L"wined3d.dll" to L"wined3d-csmt.dll" err:module:import_dll Library d3d11.dll (which is needed by L"C:\\windows\\system32\\nvapi64.dll") not found fixme:vulkan:vkGetInstanceProcAddr missing function "vkGetPhysicalDeviceProperties2KHR" fixme:bcrypt:BCryptGenRandom ignoring selected algorithm fixme:bcrypt:BCryptGenRandom ignoring selected algorithm wine: Unhandled page fault on execute access to 0x00000000 at address (nil) (thread 0030), starting debugger...
Forgot to mention - Nvidia card here. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #5 from Dave Airlie <airlied(a)gmail.com> --- I'd be interested in knowing if the nvidia gets started with the hack patch. On radv you can disable the extension and get to the black screen, we are currently thinking some intro video decode is failing so it just sits their rendering 60fps of black screen, I've looked in renderdoc, and it really is just rendering black. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #6 from mo78(a)abv.bg --- (In reply to Dave Airlie from comment #5)
I'd be interested in knowing if the nvidia gets started with the hack patch.
On radv you can disable the extension and get to the black screen, we are currently thinking some intro video decode is failing so it just sits their rendering 60fps of black screen, I've looked in renderdoc, and it really is just rendering black.
No, there isn't a patch, vanila Wine-staging, with Nvidia blob. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Timothee Besset <ttimo(a)ttimo.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ttimo(a)ttimo.net -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 javitonino(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |javitonino(a)gmail.com --- Comment #7 from javitonino(a)gmail.com --- (In reply to Dave Airlie from comment #5)
I'd be interested in knowing if the nvidia gets started with the hack patch.
nvidia + wine-staging 2.19 + vkGetPhysicalDeviceProperties2KHR patch here. After the videos and splash screens I get a black screen, with a cursor (a white 90º angle). I get audio cues when playing with the keyboard, so the menu seems to be working even if it isn't rendering. If I press enter 3 or 4 times in a row, I get into an intro cinematic (previously on Wolfenstein). After the cinematic ends (or if I try to skip it), the screen freezes in the last frame from the intro, loses the input grab, and gets stuck, no sound nor video. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #8 from GloriousEggroll(a)gmail.com --- That's interesting. After today's update I get a notice about my driver being out of date. Log: Winsock Initialized idCommonLocal::Init() time 20: 0.051s ------ Initializing File System ------ Current search path: - C:/users/GLOR~VVW/SAVE~YWG/MachineGames/Wolfenstein II The New Colossus/base/ - Z:/mnt/Storage/Games/Steam/steamapps/common/Wolfenstein.II.The.New.Colossus/base/ ------ File System initialized. WARNING: ReadJsonFile: could not read file: packagechunklist.json Executing build.cfg... ------ Command Line ------ Z:\mnt\Storage\Games\Steam\steamapps\common\Wolfenstein.II.The.New.Colossus\NewColossus_x64vk.exe ------ CPU Information ------ 1 CPU package, 16 physical cores, 16 logical cores 3900 MHz AMD CPU with MMX & SSE & SSE2 & SSE3 & SSSE3 & SSE41 & SSE42 & AVX 65536 kB 1st level cache, 524288 kB 2nd level cache, 8388608 kB 3rd level cache 16048 MB System Memory idCommonLocal::Init() time 30: 0.094s idLib::SetProduction( PROD_PRODUCTION ) idCommonLocal::Init() time 40: 0.255s ------- Initializing renderSystem -------- PreliminaryRenderSetup ...registered window class ------------------------- Application Info ------------------------- App : Wolfenstein II The New Colossus - 1.0.2 Engine : idTech - 6.5.0 ------------------------- Instance Extensions ------------------------- + VK_KHR_surface + VK_KHR_win32_surface + VK_KHR_get_physical_device_properties2 ------------------------- Device Extensions ------------------------- WARNING: Could not predicate PCI-E bandwidth ERROR: Driver is too old, please update TIMER: idRenderSystemLocal::Init() took 43075.1133 ms Dumped console text to C:\users\GLOR~VVW\SAVE~YWG\MachineGames\Wolfenstein II The New Colossus\base\ErrorLog_10-30-2017__09-46-07pm.txt. idRenderSystem::Shutdown() ImageStreaming shutdown took 0.00s *************************** ERROR: Driver is too old, please update *************************** -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #9 from Dave Airlie <airlied(a)gmail.com> --- (In reply to javitonino from comment #7)
(In reply to Dave Airlie from comment #5)
I'd be interested in knowing if the nvidia gets started with the hack patch.
nvidia + wine-staging 2.19 + vkGetPhysicalDeviceProperties2KHR patch here.
After the videos and splash screens I get a black screen, with a cursor (a white 90º angle). I get audio cues when playing with the keyboard, so the menu seems to be working even if it isn't rendering. If I press enter 3 or 4 times in a row, I get into an intro cinematic (previously on Wolfenstein). After the cinematic ends (or if I try to skip it), the screen freezes in the last frame from the intro, loses the input grab, and gets stuck, no sound nor video.
Oh cool, I've reproduced the same thing on radv here now, pressed enter a few times, video and hang. err:ntdll:RtlpWaitForCriticalSection section 0x142fde5f8 "?" wait timed out in thread 00aa, blocked by 00ab, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x142fde5f8 "?" wait timed out in thread 00aa, blocked by 00ab, retrying (60 sec) I get a couple of those, but it doesn't seem to be a gpu hang at least. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #10 from GloriousEggroll(a)gmail.com --- (In reply to GloriousEggroll from comment #8)
That's interesting. After today's update I get a notice about my driver being out of date. Log:
Winsock Initialized idCommonLocal::Init() time 20: 0.051s ------ Initializing File System ------ Current search path: - C:/users/GLOR~VVW/SAVE~YWG/MachineGames/Wolfenstein II The New Colossus/base/ - Z:/mnt/Storage/Games/Steam/steamapps/common/Wolfenstein.II.The.New.Colossus/ base/ ------ File System initialized. WARNING: ReadJsonFile: could not read file: packagechunklist.json Executing build.cfg... ------ Command Line ------ Z:\mnt\Storage\Games\Steam\steamapps\common\Wolfenstein.II.The.New. Colossus\NewColossus_x64vk.exe ------ CPU Information ------ 1 CPU package, 16 physical cores, 16 logical cores 3900 MHz AMD CPU with MMX & SSE & SSE2 & SSE3 & SSSE3 & SSE41 & SSE42 & AVX 65536 kB 1st level cache, 524288 kB 2nd level cache, 8388608 kB 3rd level cache 16048 MB System Memory idCommonLocal::Init() time 30: 0.094s idLib::SetProduction( PROD_PRODUCTION ) idCommonLocal::Init() time 40: 0.255s ------- Initializing renderSystem -------- PreliminaryRenderSetup ...registered window class ------------------------- Application Info ------------------------- App : Wolfenstein II The New Colossus - 1.0.2 Engine : idTech - 6.5.0 ------------------------- Instance Extensions ------------------------- + VK_KHR_surface + VK_KHR_win32_surface + VK_KHR_get_physical_device_properties2 ------------------------- Device Extensions ------------------------- WARNING: Could not predicate PCI-E bandwidth ERROR: Driver is too old, please update TIMER: idRenderSystemLocal::Init() took 43075.1133 ms Dumped console text to C:\users\GLOR~VVW\SAVE~YWG\MachineGames\Wolfenstein II The New Colossus\base\ErrorLog_10-30-2017__09-46-07pm.txt.
idRenderSystem::Shutdown() ImageStreaming shutdown took 0.00s
*************************** ERROR: Driver is too old, please update
***************************
It's requesting version 17.10.3 driver, and reporting 0.0.0 found -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #11 from Dave Airlie <airlied(a)gmail.com> --- Also the pull down works at the black screen. hit ` Mine is dumping a lot of WARNING: failed to read cache line at <number> from the hard disk. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #12 from Dave Airlie <airlied(a)gmail.com> --- The latest update appears to force the AMD AGS library to test the driver version this fails under Wine totally. Maybe need to write a fake AMD AGS library -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Sven Arvidsson <sa(a)whiz.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sa(a)whiz.se -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Lam <winehq(a)lam.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq(a)lam.pl --- Comment #13 from Lam <winehq(a)lam.pl> --- According to http://steamcommunity.com/app/612880/discussions/0/1479856439046864535/ you can disable driver check by adding +r_disableDriverVersionCheck 1 to the command line in Steam. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #14 from GloriousEggroll(a)gmail.com --- (In reply to Dave Airlie from comment #12)
The latest update appears to force the AMD AGS library to test the driver version this fails under Wine totally.
Maybe need to write a fake AMD AGS library
after using the +r_disableDriverVersionCheck 1 along with the hack patch, i was able to get to the same point you did - white corner-cursor, ` works for drop down console with several failed to read cache line xxxxxxxx from the hard disk warnings -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Laszlo Monda <laci(a)monda.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |laci(a)monda.hu --- Comment #15 from Laszlo Monda <laci(a)monda.hu> --- I'd like to give this patch a try, but I cannot apply it because dlls/vulkan doesn't exist in the repo. Any ideas, guys? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #16 from GloriousEggroll(a)gmail.com --- (In reply to Laszlo Monda from comment #15)
I'd like to give this patch a try, but I cannot apply it because dlls/vulkan doesn't exist in the repo. Any ideas, guys?
the patch needs to be applied to wine staging, not vanilla. wine staging has the vulkan patches. Option A: get wine vanilla, apply wine-staging patches, apply patch. Option B: Download prepatched wine-staging from github:https://github.com/wine-compholio/wine-patched/releases/tag/staging-2.19, then apply the patch. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #17 from Laszlo Monda <laci(a)monda.hu> --- Thanks for the help! I could make the patch working. I have a GTX 970, use the proprietary Nvidia 384.59 driver, and experienced exactly the same as comment #7. When I hit the ` key I can see exacly the same as comment #11 in the engine console. For some reason, audio is choppy. This wasn't an issue for Doom 4 at all which also uses id Tech 6. Maybe it's because I custom compiled Wine this time. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 amazzy <mazzarito(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mazzarito(a)gmail.com --- Comment #18 from amazzy <mazzarito(a)gmail.com> ---
From what I can tell the root of this issue is that the Vulkan implementation in wine-staging is only up to 1.0.30, and this particular extension was added in 1.0.39 (see https://www.phoronix.com/scan.php?page=news_item&px=Vulkan-1.0.39-Released)
I have no idea how to do this either but it seems like the methods are simply redirected to the runtime installed on the system... See the patch here: https://github.com/wine-compholio/wine-staging/blob/master/patches/vulkan-Vu... So hopefully this can happen pretty easily ... Would love to hear from someone who actually knows though. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 George Gibbs <vash63(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vash63(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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #19 from Anthony Jagers <noonetinone(a)gmail.com> --- I get javitonino's cursor in Windows 10. So, it is normal. With the latest Radeon windows drivers the game froze in the middle of a cut scene, in Windows! Don't waste your breath trying to get this game to work. In linux with 2.20(s), I get the tilde console with the same message reported by Arlie. The screen is black in the main menu. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #20 from GloriousEggroll(a)gmail.com --- (In reply to Anthony Jagers from comment #19)
I get javitonino's cursor in Windows 10. So, it is normal. With the latest Radeon windows drivers the game froze in the middle of a cut scene, in Windows! Don't waste your breath trying to get this game to work.
that's a radeon specific driver related issue, not game related. does not mean it will not work period. in addition new game + new drivers = bound to be hotfixed. no reason to stop trying to get it working. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Stefan Dösinger <stefan(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan(a)codeweavers.com --- Comment #21 from Stefan Dösinger <stefan(a)codeweavers.com> --- Created attachment 59651 --> https://bugs.winehq.org/attachment.cgi?id=59651 ntdll: Return STATUS_PENDING from NtReadFileScatter The black screen is not a Vulkan problem. The game thinks it failed to read its data files. It apparently doesn't expect NtReadFile to finish synchronously. This hack makes NtReadFile return STATUS_PENDING. It makes the main menu show up for me (on top of wine-staging's Vulkan code + attachment 59575). The intro sequence seems to render fine (Nvidia GPU). Sound appears to work. I haven't done more testing yet though. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #22 from Philip Rebohle <philip.rebohle(a)tu-dortmund.de> --- Can confirm that the game is playable with the ntdll patch on my RX 480. Disable "deferred rendering" and "asynchronous compute" in the graphics options when using RADV though, it is extremely slow with either option enabled. Using latest mesa-git also helps a lot with performance. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #23 from mo78(a)abv.bg --- Hello, can someone give me the patched wine version to try it with Nvidia? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #24 from Stefan Dösinger <stefan(a)codeweavers.com> --- (In reply to Stefan Dösinger from comment #21)
This hack makes NtReadFile return STATUS_PENDING. I just noticed a typo in this: The function causing the trouble is NtReadFileScatter, not NtReadFile.
-- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #25 from Laszlo Monda <laci(a)monda.hu> --- GTX 970 with proprietary Nvidia 384.59 driver on Linux Mint 18.2 here. Grabbed wine-staging-2.20, and applied the two patches. The menu works, the intro video plays nicely, then the engine starts up. It's buttery smooth in uber quality, and the angry father scene is shown, then the "kill the dog" scene. Regardless of whether I kill the dog, the screen turns black afterwards, and I cannot proceed further. These are the last lines before the hang that I can see this in the console: fixme:bcrypt:BCryptGenerateSymmetricKey ignoring object buffer fixme:bcrypt:BCryptGenRandom ignoring selected algorithm fixme:bcrypt:BCryptGenRandom ignoring selected algorithm fixme:bcrypt:BCryptCreateHash ignoring object buffer fixme:bcrypt:BCryptCreateHash ignoring object buffer fixme:bcrypt:BCryptGenRandom ignoring selected algorithm fixme:bcrypt:BCryptCreateHash ignoring object buffer fixme:bcrypt:BCryptCreateHash ignoring object buffer fixme:bcrypt:BCryptGenerateSymmetricKey ignoring object buffer fixme:bcrypt:BCryptGenRandom ignoring selected algorithm fixme:bcrypt:BCryptGenRandom ignoring selected algorithm fixme:bcrypt:BCryptCreateHash ignoring object buffer fixme:bcrypt:BCryptCreateHash ignoring object buffer fixme:bcrypt:BCryptGenRandom ignoring selected algorithm fixme:avrt:AvRevertMmThreadCharacteristics (0x12345678): stub fixme:pulse:AudioSessionControl_UnregisterAudioSessionNotification (0x19a537c0)->(0x36588338) - stub I'm happy to provide more information if needed. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #26 from Stefan Dösinger <stefan(a)codeweavers.com> --- I can see the same hangs, but it is random. I got past that scene after a few tries. However, a similar hang occurs when leaving the Ausmerzer, and so far I didn't get past it; I only tried a few times though. It doesn't seem to be a crash, or at least gdb doesn't pick up any exceptions. The game continues to run and consume plenty of CPU time. It'll probably need a +relay log to find out more, or even +all,-snoop. And then finding what's causing the problem will be like finding a needle in a heystack with the 10-something threads doing work, some of it working as intended, and one piece subtly broken. It could very well be a side effect of my ReadFileScatter hack. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #27 from Laszlo Monda <laci(a)monda.hu> --- I can confirm that the engine keeps running after the black screen. Tried WINEDEBUG=+relay which resulted in a gigantic 4T+ logfile before starting up the engine, so I consider this practically useless. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #28 from Stefan Dösinger <stefan(a)codeweavers.com> --- You can use winedbg to enable and disable log channels while the process is running (attach the debugger, "set - relay", then later "set + relay"). Note that the process has to be started with WINEDEBUG=relay for this to work. So you have to turn it on, then off, then back on again. That assumes that the copy protection doesn't decide to terminate the game because you have a debugger 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Adam Bolte <abolte(a)systemsaviour.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte(a)systemsaviour.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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #29 from GloriousEggroll(a)gmail.com --- using both the above mentioned patches - menu loads, intro runs, cutscene runs, as soon as the angry father scene ends my entire system locks up. system: arch 4.13, mesa-git, llvm-svn, vulkan-radeon-git, rx vega 64 also tried using mesa 17.2.4, llvm 5, and normal vulkan radeon - this just resulted in the game not loading at all for me. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #30 from GloriousEggroll(a)gmail.com --- (In reply to GloriousEggroll from comment #29)
using both the above mentioned patches - menu loads, intro runs, cutscene runs, as soon as the angry father scene ends my entire system locks up. system: arch 4.13, mesa-git, llvm-svn, vulkan-radeon-git, rx vega 64 also tried using mesa 17.2.4, llvm 5, and normal vulkan radeon - this just resulted in the game not loading at all for me.
by not loading at all i mean it opens to a black screen, but no sounds no cursor and no console. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #31 from Dave Airlie <airlied(a)gmail.com> --- on radv, just FYI the async compute mode seems to trigger a bunch of vram memory evictions per frame, I'll have to dig into why that is going so badly. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 winebugs(a)greyoak.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winebugs(a)greyoak.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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #32 from javitonino(a)gmail.com --- Created attachment 59691 --> https://bugs.winehq.org/attachment.cgi?id=59691 ntdll: Return STATUS_PENDING from NtReadFileScatter on success or EOF Building on top of Stefan's patch I managed to solve the black screen lock when switching levels, by treating EOF errors as SUCCESS. I noticed that when the game locked, it was looping trying to get the status of a EOF file, and this seems to work around it. If you want to apply this, revert Stefan's patch first, or else you'll get the patch applied to a wrong part of the code (Hunk offset ~ 400 lines). With this, I managed to get a handful of chapters into the game without major problems, aside from some audio choppiness, which ranges in severity depending on the level (framerate related maybe?). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #33 from GloriousEggroll(a)gmail.com --- (In reply to javitonino from comment #32)
Created attachment 59691 [details] ntdll: Return STATUS_PENDING from NtReadFileScatter on success or EOF
Building on top of Stefan's patch I managed to solve the black screen lock when switching levels, by treating EOF errors as SUCCESS. I noticed that when the game locked, it was looping trying to get the status of a EOF file, and this seems to work around it. If you want to apply this, revert Stefan's patch first, or else you'll get the patch applied to a wrong part of the code (Hunk offset ~ 400 lines).
With this, I managed to get a handful of chapters into the game without major problems, aside from some audio choppiness, which ranges in severity depending on the level (framerate related maybe?).
for pulseaudio try adding a delay to the launch option envars. i found this fixes a lot of wine audio problems with various games. will give this patch a try when i'm off work. PULSE_LATENCY_MSEC=60 I don't know why I didn't think to try it your way, as I actually tested setting the status to EOF rather than leaving it as pending and checking if the status was EOF or success as you did. good call :D -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #34 from winebugs(a)greyoak.com --- Confirmed, updated patch is working for me. I got past the dog scene and played a few chapters. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #35 from Laszlo Monda <laci(a)monda.hu> --- I can also confirm that the patch seems to work perfectly. My hats off to you, guys! Any ideas why the audio is super choppy? PULSE_LATENCY_MSEC=60 didn't help at all. Interestingly, Doom 4 doesn't have any audio issues, even though it's also powered by id Tech 6. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #36 from GloriousEggroll(a)gmail.com --- Any of you using an AMD card on Mesa? I'm getting a black screen using mesa 17.2.5, vulkan radeon 17.2.5, llvm 5 on Arch Also tested using mesa-git, llvm-svn, vulkan-radeon-git and this loads the game and the menus, but hard locks as soon as it tries to render anything in the game I'm on a vega 64 so it could just be me, just wanted to verify with other AMD owners -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #37 from GloriousEggroll(a)gmail.com --- (In reply to GloriousEggroll from comment #36)
Any of you using an AMD card on Mesa? I'm getting a black screen using mesa 17.2.5, vulkan radeon 17.2.5, llvm 5 on Arch
Also tested using mesa-git, llvm-svn, vulkan-radeon-git and this loads the game and the menus, but hard locks as soon as it tries to render anything in the game
I'm on a vega 64 so it could just be me, just wanted to verify with other AMD owners
edit: reverse those results: non-git can play the game but textures dont load/come out all black/blobby git freezes right before loading game engine(In reply to GloriousEggroll from comment #36)
Any of you using an AMD card on Mesa? I'm getting a black screen using mesa 17.2.5, vulkan radeon 17.2.5, llvm 5 on Arch
Also tested using mesa-git, llvm-svn, vulkan-radeon-git and this loads the game and the menus, but hard locks as soon as it tries to render anything in the game
I'm on a vega 64 so it could just be me, just wanted to verify with other AMD owners
alright yeah, there's some problems with mesa/mesa-git mesa + vulkan radeon I'm able to load movie cutscenes and load into the game - but game cutscenes and the game itself dont load textures. everything is blobby blurry objects -- but I am able to listen to audio, move around, kill enemies. mesa git + vulkan radeon git - game hard locks my system right at the transition at the beginning of finding blaskovich before loading the "in the helicopter" scene - basically as soon as it tries to render anything in the actual game engine. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Stefan Dösinger <stefan(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #59651|0 |1 is obsolete| | --- Comment #38 from Stefan Dösinger <stefan(a)codeweavers.com> --- Comment on attachment 59651 --> https://bugs.winehq.org/attachment.cgi?id=59651 ntdll: Return STATUS_PENDING from NtReadFileScatter Marking as obsolete -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #39 from Stefan Dösinger <stefan(a)codeweavers.com> --- Nice work on extending my patch! I haven't tested it myself yet, but it makes sense that EOF is kinda a success case as well. I have marked my patch obsolete. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #40 from mo78(a)abv.bg --- With Nvidia game runs perfectly smooth and there isn't any sound choppiness. Thank you for the patches, great work!!! -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #41 from mo78(a)abv.bg --- Here you are a video: https://youtu.be/RKItS0TP328 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #42 from Philip Rebohle <philip.rebohle(a)tu-dortmund.de> --- (In reply to GloriousEggroll from comment #37)
mesa git + vulkan radeon git - game hard locks my system right at the transition at the beginning of finding blaskovich before loading the "in the helicopter" scene - basically as soon as it tries to render anything in the actual game engine.
Don't have any freeze or texture issues with RADV from latest mesa-git. Some levels do actually render more or less correctly, others just turn into a black screen after a few seconds, and particles in general are so huge that I literally can't see anything anymore as soon as a single enemy opens fire. But this isn't really related to wine anymore, we should report this to the Mesa bug tracker instead. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #43 from Anthony Jagers <noonetinone(a)gmail.com> --- Congrats to the wine developers and those who contributed the patches. You did your job. The game works as well as it can. (In reply to GloriousEggroll from comment #20)
(In reply to Anthony Jagers from comment #19)
Don't waste your breath trying to get this game to work.
that's a radeon specific driver related issue, not game related. does not mean it will not work period. in addition new game + new drivers = bound to be hotfixed. no reason to stop trying to get it working.
I stand by what I wrote. The games is way too buggy to recommend. There is no reason to think, according to the reviews & the steam comments that the current difficulties are in any way related to amd hardware or drivers. All I can tell you is the crashes happen at the same level in the game and are shared with Windows 10, as I have stated above. Wine users are now in a position to aid Bethesda in determining what is the cause of these crashes. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 ospf(a)gmx.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ospf(a)gmx.net --- Comment #44 from ospf(a)gmx.net --- Can anyone explain to my why this is still unconfirmed? Isn't it already solved and plenty of people have reported it to exist? I tried it with staging 2.20 and it shows the same symptom. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Stefan Dösinger <stefan(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #45 from Stefan Dösinger <stefan(a)codeweavers.com> --- Because nobody bothered to set the status yet. I've done so now. Note that hacks being attached to a bug report isn't exactly a fix though. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 dylanmc <pinturiano(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pinturiano(a)gmail.com --- Comment #46 from dylanmc <pinturiano(a)gmail.com> --- Same error there. I hope in a fix soon.. I don't want to play it trought windows :( -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #47 from GloriousEggroll(a)gmail.com --- (In reply to Philip Rebohle from comment #42)
(In reply to GloriousEggroll from comment #37)
mesa git + vulkan radeon git - game hard locks my system right at the transition at the beginning of finding blaskovich before loading the "in the helicopter" scene - basically as soon as it tries to render anything in the actual game engine.
Don't have any freeze or texture issues with RADV from latest mesa-git. Some levels do actually render more or less correctly, others just turn into a black screen after a few seconds, and particles in general are so huge that I literally can't see anything anymore as soon as a single enemy opens fire.
But this isn't really related to wine anymore, we should report this to the Mesa bug tracker instead.
I managed to resolve it - turns out llvm-svn was causing my lockups. I compiled mesa-git using normal llvm 5 and was able to run the game. Some things don't exactly render properly but it's playable, about the same as you mentioned, this as you mentioned probably has to do with mesa and isnt wine related, but as for these patches they do get the game running -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #48 from GloriousEggroll(a)gmail.com --- (In reply to GloriousEggroll from comment #47)
(In reply to Philip Rebohle from comment #42)
(In reply to GloriousEggroll from comment #37)
mesa git + vulkan radeon git - game hard locks my system right at the transition at the beginning of finding blaskovich before loading the "in the helicopter" scene - basically as soon as it tries to render anything in the actual game engine.
Don't have any freeze or texture issues with RADV from latest mesa-git. Some levels do actually render more or less correctly, others just turn into a black screen after a few seconds, and particles in general are so huge that I literally can't see anything anymore as soon as a single enemy opens fire.
But this isn't really related to wine anymore, we should report this to the Mesa bug tracker instead.
I managed to resolve it - turns out llvm-svn was causing my lockups. I compiled mesa-git using normal llvm 5 and was able to run the game. Some things don't exactly render properly but it's playable, about the same as you mentioned, this as you mentioned probably has to do with mesa and isnt wine related, but as for these patches they do get the game running
I've made a video showing amdgpu + RADV on mesa-git with vega 64 that shows what has issues from what I could tell. Cutscenes render ok. In-engine cutscenes have some minor problems mostly related to faces and facial expressions/mouth movement. Game engine itself has some odd rendering issues regarding bloom, lights, and the lighting from gunfire, and what looks like it should be water dripping from pipes? can't tell. Video using amdgpu + RADV on mesa-git with vega 64: https://www.youtube.com/watch?v=f0EzOxs_Ofc -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #49 from dylanmc <pinturiano(a)gmail.com> --- anyone can tell me how to aplly that patch? To a wine staging version? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #50 from mo78(a)abv.bg --- (In reply to dylanmc from comment #49)
anyone can tell me how to aplly that patch? To a wine staging version?
Here you are the kind answer from László Monda: 1. Fetch the most recent wine from https://github.com/wine-compholio/wine-patched/releases/tag/staging-2.20 2. Copy the two patch files of the https://bugs.winehq.org/show_bug.cgi?id=43935 thread to the directory of wine staging 3. Apply the patches with `patch -p1 < patchfile.patch` - пачовете се прилагат един по един а не наведнъж! 4. Run ./configure --enable-win64 5. Run wine64 yourprogram in the loader directory You will likely need to install a fair amount of dev dependencies as dictated by the configure script. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #51 from dylanmc <pinturiano(a)gmail.com> --- Thanks a lot :) I was missing how I have to put the patch files :) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #52 from mo78(a)abv.bg --- (In reply to dylanmc from comment #51)
Thanks a lot :) I was missing how I have to put the patch files :)
You are welcome :) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #53 from dylanmc <pinturiano(a)gmail.com> --- I've patched, configured with the --enable-win64 and compiled. Moving to the game dir, run wine64 gamne executable but doesen't start at all :( -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #54 from mo78(a)abv.bg --- (In reply to dylanmc from comment #53)
I've patched, configured with the --enable-win64 and compiled. Moving to the game dir, run wine64 gamne executable but doesen't start at all :(
Don't compilr it, just ./configure --enable-win64 is enough. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #55 from mo78(a)abv.bg --- (In reply to mo78 from comment #54)
(In reply to dylanmc from comment #53)
I've patched, configured with the --enable-win64 and compiled. Moving to the game dir, run wine64 gamne executable but doesen't start at all :(
Don't compilr it, just ./configure --enable-win64 is enough.
Compile* -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #56 from dylanmc <pinturiano(a)gmail.com> --- (In reply to mo78 from comment #50)
(In reply to dylanmc from comment #49)
anyone can tell me how to aplly that patch? To a wine staging version?
Here you are the kind answer from László Monda:
1. Fetch the most recent wine from https://github.com/wine-compholio/wine-patched/releases/tag/staging-2.20 2. Copy the two patch files of the https://bugs.winehq.org/show_bug.cgi?id=43935 thread to the directory of wine staging 3. Apply the patches with `patch -p1 < patchfile.patch` - пачовете се прилагат един по един а не наведнъж! 4. Run ./configure --enable-win64 5. Run wine64 yourprogram in the loader directory
You will likely need to install a fair amount of dev dependencies as dictated by the configure script.
luca(a)snoopx /media/seagate/steam/steamapps/common/Wolfenstein.II.The.New.Colossus $ /home/luca/Scaricati/wine-patched-staging-2.20/wine64 NewColossus_x64vk.exe wine64: could not locate the Wine build tree I know I'm missing something but I don't know exactly what :/ -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #57 from mo78(a)abv.bg --- (In reply to dylanmc from comment #56)
(In reply to mo78 from comment #50)
(In reply to dylanmc from comment #49)
anyone can tell me how to aplly that patch? To a wine staging version?
Here you are the kind answer from László Monda:
1. Fetch the most recent wine from https://github.com/wine-compholio/wine-patched/releases/tag/staging-2.20 2. Copy the two patch files of the https://bugs.winehq.org/show_bug.cgi?id=43935 thread to the directory of wine staging 3. Apply the patches with `patch -p1 < patchfile.patch` - пачовете се прилагат един по един а не наведнъж! 4. Run ./configure --enable-win64 5. Run wine64 yourprogram in the loader directory
You will likely need to install a fair amount of dev dependencies as dictated by the configure script.
luca(a)snoopx /media/seagate/steam/steamapps/common/Wolfenstein.II.The.New.Colossus $ /home/luca/Scaricati/wine-patched-staging-2.20/wine64 NewColossus_x64vk.exe wine64: could not locate the Wine build tree
I know I'm missing something but I don't know exactly what :/
You must define the path to the game's exe. Open terminal where the patched wine is and use the following comand: wine 64 /media/seagate/steam/steamapps/common/Wolfenstein.II.The.New.Colossus/NewColossus_x64vk.exe -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #58 from dylanmc <pinturiano(a)gmail.com> --- Sorry, but I still don't understand. I don't want to monopolize this thread with my problem... but I don't understand how a patched wine *NOT* compiled will start up this game :/ I've 1. Fetch the most recent wine from https://github.com/wine-compholio/wine-patched/releases/tag/staging-2.20 2. Copy the two patch files of the https://bugs.winehq.org/show_bug.cgi?id=43935 thread to the directory of wine staging 3. Applyed the patches with `patch -p1 < patchfile.patch` - пачовете се 4. Run ./configure --enable-win64 5. cd patchedwine path 6 run ./wine64 /media/seagate/steam/steamapps/common/Wolfenstein.II.The.New.Colossus/NewColossus_x64vk.exe result: wine64: could not locate the Wine build tree -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Lam <winehq(a)lam.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|winehq(a)lam.pl | --- Comment #59 from Lam <winehq(a)lam.pl> --- Apparently this is now a unix newbie forum and no one here is actually working on any bug. [ unsubscribe ] -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 dylanmc <pinturiano(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|pinturiano(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.
https://bugs.winehq.org/show_bug.cgi?id=43935 dylanmc <pinturiano(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pinturiano(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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #60 from mo78(a)abv.bg --- (In reply to dylanmc from comment #58)
6 run ./wine64 /media/seagate/steam/steamapps/common/Wolfenstein.II.The.New.Colossus/NewColossus_x64vk.exe
Where I wrote to put ./ in the command? Here is what you exactly must issue in terminal, better copy/paste it: wine64 /media/seagate/steam/steamapps/common/Wolfenstein.II.The.New.Colossus/NewColossus_x64vk.exe -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #61 from Zebediah Figura <z.figura12(a)gmail.com> --- Please take this discussion to the forums. This bug report is the place for discussing information relevant to the bug, not for instructions on how to build a patched Wine. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #62 from mo78(a)abv.bg --- The bug is fixed with the to patches available. I already play the game without problems at all :) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 oscarbg <rtfss1(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rtfss1(a)gmail.com --- Comment #63 from oscarbg <rtfss1(a)gmail.com> --- Hi, just wanted to say I tested with two patches and runs on Nvidia GPU but fails with Intel HD530 Skylake Vulkan driver (Anvil) using latest Mesa from padoka PPA.. Log says (see below) a vulkan missing feature.. Notice it works on Windows with Intel iGPU using latest 15.60 drivers.. so it would be nice to see which Vulkan feature is missing Mesa drivers vs Intel Windows Vulkan driver or versus RADV driver.. log: Application Info ------------------------- App : Wolfenstein II The New Colossus - 1.0.2 Engine : idTech - 6.5.0 ------------------------- Instance Extensions ------------------------- + VK_KHR_surface + VK_KHR_win32_surface + VK_KHR_get_physical_device_properties2 ------------------------- Device Extensions ------------------------- FATAL ERROR: vkCreateDevice failed with error (VK_ERROR_FEATURE_NOT_PRESENT) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #64 from Anthony Jagers <noonetinone(a)gmail.com> --- That extension is marked as done in the anv driver. But try to run vulkaninfo, just to be sure. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #65 from oscarbg <rtfss1(a)gmail.com> --- (In reply to Anthony Jagers from comment #64)
That extension is marked as done in the anv driver. But try to run vulkaninfo, just to be sure. I'm pretty sure is failing because some feature not printed in log is missing in Anvil..
You can see my report here: http://vulkan.gpuinfo.org/displayreport.php?id=2167#extensions -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #66 from Anthony Jagers <noonetinone(a)gmail.com> --- If you are interested, I have just learned of a new wine fork that touts a proper ICD loader. The repository looks like you need to apply the staging patches, first. https://www.phoronix.com/scan.php?page=news_item&px=Wine-Vulkan-ICD-Patches -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #67 from winebugs(a)greyoak.com --- FWIW this is what I get on an Intel HD Graphics 530 (Skylake GT2) with mesa 17.2.2 on Fedora 26: trace:vulkan:vkEnumerateInstanceExtensionProperties ((nil), 0x5b04980, (nil)) trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xcb_surface" for VK_KHR_win32_surface support trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xlib_surface" for VK_KHR_win32_surface support trace:vulkan:vkEnumerateInstanceExtensionProperties ((nil), 0x5b04980, 0x6763be0) trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xcb_surface" for VK_KHR_win32_surface support trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xlib_surface" for VK_KHR_win32_surface support trace:vulkan:vkCreateInstance (0x5b04a00, (nil), 0x1438df6c0) trace:vulkan:convert_VkInstanceCreateInfo (0x5b04840, 0x5b04a00) trace:vulkan:convert_VkAllocationCallbacks (0x5b04810, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil)) trace:vulkan:release_VkInstanceCreateInfo ((nil), 0x5b04840) trace:vulkan:vkEnumeratePhysicalDevices (0x7f04580d63a0, 0x5b04ac8, (nil)) trace:vulkan:vkEnumeratePhysicalDevices (0x7f04580d63a0, 0x5b04ac8, 0x66a6770) trace:vulkan:vkEnumerateDeviceExtensionProperties (0x7f045807c0f0, (null), 0x5b04400, (nil)) trace:vulkan:vkEnumerateDeviceExtensionProperties (0x7f045807c0f0, (null), 0x5b04400, 0x6763be0) trace:vulkan:vkGetInstanceProcAddr (0x7f04580d63a0, "vkGetPhysicalDeviceProperties2KHR") trace:vulkan:vkGetPhysicalDeviceProperties2KHR (0x7f045807c0f0, 0x5b04710) trace:vulkan:vkGetPhysicalDeviceProperties (0x7f045807c0f0, 0x5b04720) trace:vulkan:vkGetPhysicalDeviceMemoryProperties (0x7f045807c0f0, 0x1438df6d8) trace:vulkan:vkGetPhysicalDeviceFeatures (0x7f045807c0f0, 0x1438dfc38) trace:vulkan:vkGetPhysicalDeviceQueueFamilyProperties (0x7f045807c0f0, 0x5b04ac0, (nil)) trace:vulkan:vkGetPhysicalDeviceQueueFamilyProperties (0x7f045807c0f0, 0x5b04ac0, 0x66a6970) trace:vulkan:vkCreateDevice (0x7f045807c0f0, 0x5b04510, (nil), 0x1438df6c8) trace:vulkan:convert_VkAllocationCallbacks (0x5b042e0, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil)) trace:vulkan:vkDestroyDevice ((nil), (nil)) trace:vulkan:convert_VkAllocationCallbacks (0x5af9360, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil)) trace:vulkan:vkDestroyInstance (0x7f04580d63a0, (nil)) trace:vulkan:convert_VkAllocationCallbacks (0x5af9360, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil)) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Laszlo Monda <laci(a)monda.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|laci(a)monda.hu | -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #68 from Anthony Jagers <noonetinone(a)gmail.com> --- (In reply to oscarbg from comment #65)
I'm pretty sure is failing because some feature not printed in log is missing in Anvil..
You can see my report here: http://vulkan.gpuinfo.org/displayreport.php?id=2167#extensions
By your link the RADV-POLARIS11 which is my driver has less extensions than the intel-anvil driver. Do you have any other problems with your vulkan driver? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #69 from dylanmc <pinturiano(a)gmail.com> --- I finally got the game working on Gentoo Linux / Nvidia Geforce 960 TI with lastest drivers 384.98 The Audio is choppy, also tried PULSE_LATENCY_MSEC=60 with no luck. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #70 from dylanmc <pinturiano(a)gmail.com> --- I finally got the game working on Gentoo Linux / Nvidia Geforce 960 TI with lastest drivers 384.98 The Audio is choppy, also tried PULSE_LATENCY_MSEC=60 with no luck. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #71 from oscarbg <rtfss1(a)gmail.com> --- (In reply to winebugs from comment #67)
FWIW this is what I get on an Intel HD Graphics 530 (Skylake GT2) with mesa 17.2.2 on Fedora 26:
trace:vulkan:vkEnumerateInstanceExtensionProperties ((nil), 0x5b04980, (nil)) trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xcb_surface" for VK_KHR_win32_surface support trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xlib_surface" for VK_KHR_win32_surface support trace:vulkan:vkEnumerateInstanceExtensionProperties ((nil), 0x5b04980, 0x6763be0) trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xcb_surface" for VK_KHR_win32_surface support trace:vulkan:vkEnumerateInstanceExtensionProperties found "VK_KHR_xlib_surface" for VK_KHR_win32_surface support trace:vulkan:vkCreateInstance (0x5b04a00, (nil), 0x1438df6c0) trace:vulkan:convert_VkInstanceCreateInfo (0x5b04840, 0x5b04a00) trace:vulkan:convert_VkAllocationCallbacks (0x5b04810, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil)) trace:vulkan:release_VkInstanceCreateInfo ((nil), 0x5b04840) trace:vulkan:vkEnumeratePhysicalDevices (0x7f04580d63a0, 0x5b04ac8, (nil)) trace:vulkan:vkEnumeratePhysicalDevices (0x7f04580d63a0, 0x5b04ac8, 0x66a6770) trace:vulkan:vkEnumerateDeviceExtensionProperties (0x7f045807c0f0, (null), 0x5b04400, (nil)) trace:vulkan:vkEnumerateDeviceExtensionProperties (0x7f045807c0f0, (null), 0x5b04400, 0x6763be0) trace:vulkan:vkGetInstanceProcAddr (0x7f04580d63a0, "vkGetPhysicalDeviceProperties2KHR") trace:vulkan:vkGetPhysicalDeviceProperties2KHR (0x7f045807c0f0, 0x5b04710) trace:vulkan:vkGetPhysicalDeviceProperties (0x7f045807c0f0, 0x5b04720) trace:vulkan:vkGetPhysicalDeviceMemoryProperties (0x7f045807c0f0, 0x1438df6d8) trace:vulkan:vkGetPhysicalDeviceFeatures (0x7f045807c0f0, 0x1438dfc38) trace:vulkan:vkGetPhysicalDeviceQueueFamilyProperties (0x7f045807c0f0, 0x5b04ac0, (nil)) trace:vulkan:vkGetPhysicalDeviceQueueFamilyProperties (0x7f045807c0f0, 0x5b04ac0, 0x66a6970) trace:vulkan:vkCreateDevice (0x7f045807c0f0, 0x5b04510, (nil), 0x1438df6c8) trace:vulkan:convert_VkAllocationCallbacks (0x5b042e0, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil)) trace:vulkan:vkDestroyDevice ((nil), (nil)) trace:vulkan:convert_VkAllocationCallbacks (0x5af9360, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil)) trace:vulkan:vkDestroyInstance (0x7f04580d63a0, (nil)) trace:vulkan:convert_VkAllocationCallbacks (0x5af9360, (nil)) trace:vulkan:release_VkAllocationCallbacks ((nil), (nil))
just posted on my twitter that to one of the Wolf2 devs (slightly edited): Wolfenstein 2 runs via Wine with Nvidia propietary driver, AMDGPU Pro Vulkan driver and Mesa RADV Vulkan.. and even on Intel HD 530 GPU on Windows but not with Anvil Vulkan Mesa drv.. making a diff of VK features (using vulkan.gpuinfo DB) by drv seems Wolf2 requires variableMultisampleRate unconditionally? so as said doesn't run on Intel Vulkan Mesa drv (Anvil).. will be nice to know what feature Anvil is missing vs RADV that allows it to run.. as said seems variableMultisampleRate is that missing feature that all others drivers present.. just wanting to request to mesa devs implement that if that's the missing feature missing.. thanks.. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #72 from dylanmc <pinturiano(a)gmail.com> --- (In reply to Laszlo Monda from comment #35)
I can also confirm that the patch seems to work perfectly. My hats off to you, guys!
Any ideas why the audio is super choppy? PULSE_LATENCY_MSEC=60 didn't help at all. Interestingly, Doom 4 doesn't have any audio issues, even though it's also powered by id Tech 6.
I have the same problem Tried Windows 7, XP 10 version but the problem persist. Have you solved it in any way? The game works great, exept the sound -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #73 from mo78(a)abv.bg --- I'm with ASUS Xonar Audio and I haven't problems with the sound. Is the onboard audio a possible reason? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|z.figura12(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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #74 from dylanmc <pinturiano(a)gmail.com> --- Doom4 works perfectly, other Wolfestein too. Only this is choppy. My audio device 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) It's a very old chipset,newt week I have to upgrade the entire system.. maybe it can run without problems :( But I think is pulseaudio the problem.. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #75 from mo78(a)abv.bg --- I'm with pulseudio too and as cam you see on the video, there isn't any problems with the game: https://www.youtube.com/watch?v=IbDPa9p_1Ac -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 KG <jjkenneth.grip(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jjkenneth.grip(a)gmail.com --- Comment #76 from KG <jjkenneth.grip(a)gmail.com> --- Tried on Fedora27 NVIDIA driver 387.22 and get this error: fixme:winediag:start_process Wine Staging 2.20 is a testing version containing experimental patches. fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. fixme:heap:RtlSetHeapInformation 0x470000 0 0x33ed10 4 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Laszlo Monda <laci(a)monda.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |laci(a)monda.hu --- Comment #77 from Laszlo Monda <laci(a)monda.hu> ---
Any ideas why the audio is super choppy? PULSE_LATENCY_MSEC=60 didn't help at all. Interestingly, Doom 4 doesn't have any audio issues, even though it's also powered by id Tech 6.
I have the same problem Have you solved it in any way?
Nope, unfortunately. I'm using a Speedlink VIGO SL-8850-BK USB sound card, and no apps/games produce choppy audio except this. I'm wondering whether it's possible to use an audio backend other than PulseAudio for wine, and if so how. I understand that PulseAudio works well for most, but it clearly produces choppy audio on some configurations for this 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #78 from Anthony Jagers <noonetinone(a)gmail.com> --- This configure switch might help. --without-pulse -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #79 from mo78(a)abv.bg --- Completed the game without a single glitch. Thank you once again for the magnificent patches, cheers! -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #80 from Laszlo Monda <laci(a)monda.hu> --- (In reply to Anthony Jagers from comment #78)
This configure switch might help.
--without-pulse
I've recompiled wine this way, so only ALSA should be used. Unfortunately, audio was just as choppy as before. I also used `pasuspender -- wine` which muted audio, so even though ALSA should be used, it gets somehow routed through pulse. Wondering whether there's a way to only involve ALSA without pulse and still get sound. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Andrew Eikum <aeikum(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aeikum(a)codeweavers.com --- Comment #81 from Andrew Eikum <aeikum(a)codeweavers.com> --- (In reply to javitonino from comment #32)
Created attachment 59691 [details] ntdll: Return STATUS_PENDING from NtReadFileScatter on success or EOF
Building on top of Stefan's patch I managed to solve the black screen lock when switching levels, by treating EOF errors as SUCCESS. I noticed that when the game locked, it was looping trying to get the status of a EOF file, and this seems to work around it. If you want to apply this, revert Stefan's patch first, or else you'll get the patch applied to a wrong part of the code (Hunk offset ~ 400 lines).
With this, I managed to get a handful of chapters into the game without major problems, aside from some audio choppiness, which ranges in severity depending on the level (framerate related maybe?).
These patches should no longer be needed. Obviously you still need the Vulkan stuff. commit f87a2f0e4cd4d36f3a218ac499d7a8f1933335a5 Author: Andrew Eikum <aeikum(a)codeweavers.com> Date: Wed Dec 6 15:08:00 2017 -0600 ntdll: Don't require full-page reads in NtReadFileScatter. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Matt <m.mcnutt(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.mcnutt(a)gmail.com --- Comment #82 from Matt <m.mcnutt(a)gmail.com> --- I have opened a bug for RADV driver on freedesktop.org https://bugs.freedesktop.org/show_bug.cgi?id=104302 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Roderick Colenbrander <thunderbird2k(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thunderbird2k(a)gmail.com --- Comment #83 from Roderick Colenbrander <thunderbird2k(a)gmail.com> --- For people interested in playing Wolfenstein 2, I would like to ask you to try my vulkan icd branch (https://github.com/roderickc/wine-vulkan). It is based on Wine 3.0 and Wolfenstein should work out of the box. Let me know on the github page if you find any vulkan related bugs, which I like to resolve before submitting the patches to Wine. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 --- Comment #84 from Matt <m.mcnutt(a)gmail.com> --- (In reply to Roderick Colenbrander from comment #83)
For people interested in playing Wolfenstein 2, I would like to ask you to try my vulkan icd branch (https://github.com/roderickc/wine-vulkan). It is based on Wine 3.0 and Wolfenstein should work out of the box. Let me know on the github page if you find any vulkan related bugs, which I like to resolve before submitting the patches to Wine.
I have compiled your branch of wine today - but still get the artefacts present in the video posted by GloriusEggroll (https://www.youtube.com/watch?v=f0EzOxs_Ofc) on my R9 Fury. It must truly be a driver bug, however there has been no movement on the logged bug on freedesktop -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Roderick Colenbrander <thunderbird2k(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #85 from Roderick Colenbrander <thunderbird2k(a)gmail.com> --- VK_KHR_get_physical_device_properties2 is implemented as part of winevulkan in Wine 3.4. Closing. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown Product|Wine-staging |Wine -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #86 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 3.5. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com Component|-unknown |winevulkan -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Laszlo Monda <laci(a)monda.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|laci(a)monda.hu | -- 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.
https://bugs.winehq.org/show_bug.cgi?id=43935 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net Fixed by SHA1| |79c2ee529b530fa49fae0d3ded4 | |d4d3d6e09d7b8 -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla