[Bug 59008] New: Red dead redemption hangs
http://bugs.winehq.org/show_bug.cgi?id=59008 Bug ID: 59008 Summary: Red dead redemption hangs Product: vkd3d Version: 1.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)list.winehq.org Reporter: levanchelidze(a)gmail.com Distribution: --- Created attachment 79745 --> http://bugs.winehq.org/attachment.cgi?id=79745 terminal output On uhd 620 graphics after in game some time passes the game hangs Using wine 10.19 and installed vkd3d from winetricks BufferCount = 3. 10029.717:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_init_sync_objects: Ensure maximum latency of 3 frames with KHR_present_wait. 10029.728:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_init_waiter_thread: Enabling present wait path for frame latency. 10029.728:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_init_sleep_state: Timer interval is 1.0 ms. warn: DXGI: MakeWindowAssociation: Ignoring flags 10029.751:0020:01f8:info:vkd3d-proton:dxgi_vk_swap_chain_recreate_swapchain_in_present_task: Got 3 swapchain images. 10029.923:0020:01f8:info:vkd3d-proton:dxgi_vk_swap_chain_recreate_swapchain_in_present_task: Got 3 swapchain images. 10030.179:0020:01f0:info:vkd3d-proton:vkd3d_pipeline_library_disk_thread_main: Flushing disk cache (wakeup counter since last flush = 1791). It seems like application has stopped creating new PSOs for the time being. 01d8:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x230 for device 0. 10063.639:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_ChangeProperties: Reallocating swapchain (1280 x 720), BufferCount = 3. 01d8:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x230 for device 0. 01d8:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x230 for device 0. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. ^C0264:fixme:console:default_ctrl_handler Terminating process 20 on event 0 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #1 from Henri Verbeet <hverbeet(a)gmail.com> --- Hi, that looks like a vkd3d-proton[1] log. If you did indeed intend to file this bug against upstream vkd3d, you'll most likely want to recreate the log using a clean WINEPREFIX, without vkd3d-proton or DXVK installed. [1] https://github.com/HansKristian-Work/vkd3d-proton -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #2 from Levan <levanchelidze(a)gmail.com> --- Created attachment 79746 --> http://bugs.winehq.org/attachment.cgi?id=79746 fresh wine prefix -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #3 from Henri Verbeet <hverbeet(a)gmail.com> --- Unfortunately it's not immediately obvious from the log what the issue may be. I'll try to reproduce the issue myself, but it'll likely take a while. It may help to get a log with WINEDEBUG="+dxgi,+d3d12,+seh" and VKD3D_DEBUG=trace, but note that these logs tend to be very large, especially in cases where it takes a while to get to the point where the issue occurs. If you're able to attach a debugger when the game hangs, it may also be helpful to get stack traces for the game's threads. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #4 from Levan <levanchelidze(a)gmail.com> --- (In reply to Henri Verbeet from comment #3)
Unfortunately it's not immediately obvious from the log what the issue may be. I'll try to reproduce the issue myself, but it'll likely take a while.
It may help to get a log with WINEDEBUG="+dxgi,+d3d12,+seh" and VKD3D_DEBUG=trace, but note that these logs tend to be very large, especially in cases where it takes a while to get to the point where the issue occurs. If you're able to attach a debugger when the game hangs, it may also be helpful to get stack traces for the game's threads.
I been suggested on vkd3d-proton that it's a driver issue https://github.com/HansKristian-Work/vkd3d-proton/issues/2720#issuecomment-3... here is it on mesa gitlab.freedesktop.org/mesa/mesa/-/issues/14348 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #5 from Levan <levanchelidze(a)gmail.com> --- Here is wine debug logs on 10.20 https://www.mediafire.com/file/m1awa3qv80a5lgm/wine_debug.log.7z/file -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 Stian Low <wineryyyyy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy@gmail.com --- Comment #6 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Levan from comment #4)
I been suggested on vkd3d-proton that it's a driver issue https://github.com/HansKristian-Work/vkd3d-proton/issues/2720#issuecomment- 3569762453 here is it on mesa gitlab.freedesktop.org/mesa/mesa/-/issues/14348
Please retest if still not fixed since latest test. Recent fix for Mesa Intel(R) UHD Graphics 620 (KBL GT2) seems to match your GPU: https://bugs.winehq.org/show_bug.cgi?id=59186#c14 Games reported with better performance after 620 0x5917 support was merged: https://gitlab.winehq.org/wine/wine/-/merge_requests/10990 Please run `glxinfo` and attach logs to this bug to confirm if your GPU matches 620 0x5917 variant. Pending merge request will boost gpu memory even more for 620 0x5917 based on reporters glxinfo: https://gitlab.winehq.org/wine/wine/-/merge_requests/11062 Curious if glxinfo reports your gpu memory matching other reporters because correct value is still a bit unclear. 620 already existed prior to adding 0x5917 with gpu memory assigned ~3GB which was copied as basis for 0x5917. But reporters glxinfo indicates ~32GB gpu memory so merge request 11062 will reassign to glxinfo reported value for consistency with how Qualcomm gpu memory will be supported. Prior to adding 620 0x5917, reporters card fell back to default gpu memory as low as ~1.5GB. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #7 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Stian Low from comment #6)
Curious if glxinfo reports your gpu memory matching other reporters because correct value is still a bit unclear.
Nevermind. Clarity achieved. glxinfo for 620 0x5916 reported 3072MB gpu memory so if your card is 0x5917 then you'll get up to 32GB gpu memory support soon which may fix Red Dead hangs: https://bugs.winehq.org/show_bug.cgi?id=46729 https://bugs.winehq.org/attachment.cgi?id=63715 https://gitlab.winehq.org/wine/wine/-/commit/88aaee78fe96084f2d1ff5c224b04d1... -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #8 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Stian Low from comment #7)
glxinfo for 620 0x5916 reported 3072MB gpu memory so if your card is 0x5917 then you'll get up to 32GB gpu memory support soon which may fix Red Dead hangs:
Confirming 620 0x5917 per your glxinfo reported for: https://gitlab.freedesktop.org/mesa/mesa/-/issues/14348 I'll link this bug and pending merge request to mesa bug so they will know it may be fixed soon and not their 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #9 from Levan <levanchelidze@gmail.com> --- Created attachment 81090 --> http://bugs.winehq.org/attachment.cgi?id=81090 glxinfo -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #10 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Levan from comment #9)
Created attachment 81090 [details] glxinfo
Thanks. Double confirming pending MR will boost your gpu memory support to 32GB: https://gitlab.freedesktop.org/mesa/mesa/-/issues/14348 Your glxinfo reports 23372MB which is based on your RAM that your GPU shares so if you may increase up to 32GB for support by wine after merge. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #11 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Stian Low from comment #8)
I'll link this bug and pending merge request to mesa bug so they will know it may be fixed soon and not their problem.
https://gitlab.freedesktop.org/mesa/mesa/-/work_items/14349#note_3505981 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #12 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Levan from comment #0)
Using wine 10.19 and installed vkd3d from winetricks
BufferCount = 3. 10029.717:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_init_sync_objects:
Regarding BufferCount = 3 logged (probably not part of performance hang bugs), this merge pending per ongoing tests will add support for swapchains with BufferCount > 1 which may allow Red Dead to run without dxvk/vkd3d via plainer vanilla wine: https://gitlab.winehq.org/wine/wine/-/merge_requests/10567#note_140357 I'll also test Red Dead against MR-10567 and vkd3d/dxvk and report back comparison results. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #13 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Stian Low from comment #10)
Your glxinfo reports 23372MB which is based on your RAM that your GPU shares so if you may increase up to 32GB for support by wine after merge.
Per latest testing 32 GB boost will not be added for UHD 620 because it only affects a fallback mechanism that egl/vulkan is supposed to handle via auto-detect features otherwise. https://bugs.winehq.org/show_bug.cgi?id=59186#c35 Even for fallback case, current 3 GB may be safer despite the GPU supporting up to 32 GB because it varies based on system RAM. (In reply to Levan from comment #5)
Here is wine debug logs on 10.20
EGL/vulkan auto-detect features should have been available for version 10.20 reported so my guess about red dead hanging due to GPU not being supported for the fallback mechanism may be wrong. Regardless it may be worth a test for latest wine to see if bugs persist. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #14 from Levan <levanchelidze@gmail.com> --- It still crashes on 11.11 (clean prefix) 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! vkd3d:024c:fixme:vkd3d:d3d12_command_list_ResourceBarrier Unhandled sub-resource idx 1. 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! vkd3d:0024:fixme:vkd3d:d3d12_pipeline_state_GetCachedBlob iface 0000000013FE5690, blob 000000000010F0C0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! 024c:fixme:dxgi:d3d12_swapchain_GetFrameStatistics iface 000000000E7A85B0, stats 0000000010C6F2B0 stub! Killed wine RDR.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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #15 from Levan <levanchelidze@gmail.com> --- Created attachment 81218 --> http://bugs.winehq.org/attachment.cgi?id=81218 Crashes on 11.11 with mesa 26.3.1 (clean prefix) -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #16 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Levan from comment #15)
Created attachment 81218 [details] Crashes on 11.11 with mesa 26.3.1 (clean prefix)
Thanks for retesting. Closed bug that shares your GPU is still being updated with test results: https://bugs.winehq.org/show_bug.cgi?id=59186#c38 My GPU also shares RAM but glxinfo reports memory is not unified vs yours so my BIOS supports pre-allocating RAM from 1-4 GB which mesa driver uses. Test results for Witcher GOG show slightly better performance of +10 FPS when using only 1GB (auto default) vs 4GB so regardless it seems minimizing RAM range may be optimal for some GPUs that share RAM. In the case of your GPU however, all RAM seems to be considered open for allocation which may lead to significant fragmentation and reduced memory locality and performance over time. Please report back how much RAM is being used around the time that the game crashes if your are able. If red dead eventually uses all available RAM then some mechanisms may be needed to limit it similar to what my BIOS/driver offers but unclear whether mesa or wine or both should offer that capability. There have also been reports of memory leaks which may further exacerbate maxing out your RAM if that is in fact the problem. Otherwise it may be just the memory leak which still needs to be identified and resolved. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #17 from Levan <levanchelidze@gmail.com> --- Crash video and with resource usage https://imgur.com/aNnxD6A -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #18 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Levan from comment #17)
Crash video and with resource usage
Thanks for the video. I did not realize it was crashing at the very beginning so you are well under the limit. Is this crash what you mean by it hanging or is this new behavior? Which version of Red Dead? Also are still using proton vkd3d for testing? I may be able to reproduce this for my system. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #19 from Levan <levanchelidze@gmail.com> --- If you seen my mesa report or vkd3d-porton report it hangs in game but there I'm using vkd3d-proton if i install vkd3d proton it will go in game and hang there but with regular vkd3d the game crashes at that point and the behavior didn't change. If i remember correctly and i will re test this if i change the reg configuration in wine and increase 3d memory the game will go in game and hang there i will re test this and post to confirm this -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #20 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Levan from comment #19)
If you seen my mesa report or vkd3d-porton report it hangs in game but there I'm using vkd3d-proton if i install vkd3d proton it will go in game and hang there but with regular vkd3d the game crashes at that point and the behavior didn't change. If i remember correctly and i will re test this if i change the reg configuration in wine and increase 3d memory the game will go in game and hang there i will re test this and post to confirm this
(In reply to Levan from comment #19)
If you seen my mesa report or vkd3d-porton report it hangs in game but there I'm using vkd3d-proton if i install vkd3d proton it will go in game and hang there but with regular vkd3d the game crashes at that point and the behavior didn't change.
Thanks for clarifying. Seems the same bug effects vanilla and proton may run it via different vram settings.
If i remember correctly and i will re test this if i change the reg configuration in wine and increase 3d memory the game will go in game and hang there i will re test this and post to confirm this
I guess you mean HKEY_CURRENT_USER/Software/Wine/Direct3D/VideoMemorySize? Without regedits, vram should be handled by egl/vulkan so if it fails later via regedit then it may suggest that vram auto-detect calculus is choosing lower limits for GPUs with unified shared RAM regardless upper limits. Does that same popup error occur when it crashes later? It's a bit difficult to read in the video so please post the message if you are able (imgur keeps throwing 403s). Also please specify which Red Dead version (1 or 2, Steam or other). -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59008 --- Comment #21 from Levan <levanchelidze@gmail.com> --- HKEY_CURRENT_USER/Software/Wine/Direct3D/VideoMemorySize? Changing the ram size didn't change the crash i must have thought about another 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.
participants (2)
-
WineHQ Bugzilla -
WineHQ Bugzilla