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.