[Bug]: Running Diablo 4

wesBass commented 6 months ago

Description

Battle-net downloads and updates, opens sign in, then crashes

Steps to reproduce

Open pin (battle-net.exe) in Win 10 bottle, running v 19042 & ESync Error log: thread_get_state failed on Apple Silicon - faking zero debug registers

Expected behaviour

Log in to battle net account

Logs

Whisky Version: 2.2.1
Date: 2023-12-15T19:46:30Z
macOS Version: 14.2.0

Bottle Name: Diablo
Bottle URL: /Users/wesmax/Library/Containers/com.isaacmarovitz.Whisky/Bottles/9472107F-E5DD-43A0-A4CB-9E2CE9A3D74E

Wine Version: 7.7.0
Windows Version: win10
Enhanced Sync: esync

Metal HUD: false
Metal Trace: false

Arguments: start /unix /Users/wesmax/Downloads/Battle.net-Setup.exe

Environment:
{
    "DXVK_ASYNC" = 1;
    "LC_ALL" = "en_US";
    WINEDEBUG = "fixme-all";
    WINEESYNC = 1;
    WINEPREFIX = "/Users/wesmax/Library/Containers/com.isaacmarovitz.Whisky/Bottles/9472107F-E5DD-43A0-A4CB-9E2CE9A3D74E";
}

esync: up and running.
0150: thread_get_state failed on Apple Silicon - faking zero debug registers
[mvk-info] MoltenVK version 1.2.3, supporting Vulkan version 1.2.243.
    The following 89 Vulkan extensions are supported:
        VK_KHR_16bit_storage v1
        VK_KHR_8bit_storage v1
        VK_KHR_bind_memory2 v1
        VK_KHR_buffer_device_address v1
        VK_KHR_copy_commands2 v1
        VK_KHR_create_renderpass2 v1
        VK_KHR_dedicated_allocation v3
        VK_KHR_depth_stencil_resolve v1
        VK_KHR_descriptor_update_template v1
        VK_KHR_device_group v4
        VK_KHR_device_group_creation v1
        VK_KHR_driver_properties v1
        VK_KHR_dynamic_rendering v1
        VK_KHR_external_fence v1
        VK_KHR_external_fence_capabilities v1
        VK_KHR_external_memory v1
        VK_KHR_external_memory_capabilities v1
        VK_KHR_external_semaphore v1
        VK_KHR_external_semaphore_capabilities v1
        VK_KHR_fragment_shader_barycentric v1
        VK_KHR_get_memory_requirements2 v1
        VK_KHR_get_physical_device_properties2 v2
        VK_KHR_get_surface_capabilities2 v1
        VK_KHR_imageless_framebuffer v1
        VK_KHR_image_format_list v1
        VK_KHR_maintenance1 v2
        VK_KHR_maintenance2 v1
        VK_KHR_maintenance3 v1
        VK_KHR_multiview v1
        VK_KHR_portability_subset v1
        VK_KHR_push_descriptor v2
        VK_KHR_relaxed_block_layout v1
        VK_KHR_sampler_mirror_clamp_to_edge v3
        VK_KHR_sampler_ycbcr_conversion v14
        VK_KHR_separate_depth_stencil_layouts v1
        VK_KHR_shader_draw_parameters v1
        VK_KHR_shader_float_controls v4
        VK_KHR_shader_float16_int8 v1
        VK_KHR_shader_subgroup_extended_types v1
        VK_KHR_spirv_1_4 v1
        VK_KHR_storage_buffer_storage_class v1
        VK_KHR_surface v25
        VK_KHR_swapchain v70
        VK_KHR_swapchain_mutable_format v1
        VK_KHR_timeline_semaphore v2
        VK_KHR_uniform_buffer_standard_layout v1
        VK_KHR_variable_pointers v1
        VK_EXT_buffer_device_address v2
        VK_EXT_debug_marker v4
        VK_EXT_debug_report v10
        VK_EXT_debug_utils v2
        VK_EXT_descriptor_indexing v2
        VK_EXT_external_memory_host v1
        VK_EXT_fragment_shader_interlock v1
        VK_EXT_hdr_metadata v2
        VK_EXT_host_query_reset v1
        VK_EXT_image_robustness v1
        VK_EXT_inline_uniform_block v1
        VK_EXT_memory_budget v1
        VK_EXT_metal_objects v1
        VK_EXT_metal_surface v1
        VK_EXT_pipeline_creation_cache_control v3
        VK_EXT_post_depth_coverage v1
        VK_EXT_private_data v1
        VK_EXT_robustness2 v1
        VK_EXT_sample_locations v1
        VK_EXT_scalar_block_layout v1
        VK_EXT_separate_stencil_usage v1
        VK_EXT_shader_atomic_float v1
        VK_EXT_shader_stencil_export v1
        VK_EXT_shader_viewport_index_layer v1
        VK_EXT_subgroup_size_control v2
        VK_EXT_surface_maintenance1 v1
        VK_EXT_swapchain_colorspace v4
        VK_EXT_swapchain_maintenance1 v1
        VK_EXT_texel_buffer_alignment v1
        VK_EXT_texture_compression_astc_hdr v1
        VK_EXT_vertex_attribute_divisor v3
        VK_AMD_gpu_shader_half_float v2
        VK_AMD_negative_viewport_height v1
        VK_AMD_shader_image_load_store_lod v1
        VK_AMD_shader_trinary_minmax v1
        VK_IMG_format_pvrtc v1
        VK_INTEL_shader_integer_functions2 v1
        VK_GOOGLE_display_timing v1
        VK_MVK_macos_surface v3
        VK_MVK_moltenvk v37
        VK_NV_fragment_shader_barycentric v1
        VK_NV_glsl_shader v1
[mvk-info] Created VkInstance for Vulkan version 1.1.0, as requested by app, with the following 2 Vulkan extensions enabled:
        VK_KHR_surface v25
        VK_EXT_metal_surface v1
0298:err:winediag:ntlm_check_version ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
02f0: thread_get_state failed on Apple Silicon - faking zero debug registers
034c: thread_get_state failed on Apple Silicon - faking zero debug registers
rface v1
        VK_EXT_pipeline_creation_cache_control v3
        VK_EXT_post_depth_coverage v1
        VK_EXT_private_data v1
        VK_EXT_robustness2 v1
        VK_EXT_sample_locations v1
        VK_EXT_scalar_block_layout v1
        VK_EXT_separate_stencil_usage v1
        VK_EXT_shader_atomic_float v1
        VK_EXT_shader_stencil_export v1
        VK_EXT_shader_viewport_index_layer v1
        VK_EXT_subgroup_size_control v2
        VK_EXT_surface_maintenance1 v1
        VK_EXT_swapchain_colorspace v4
        VK_EXT_swapchain_maintenance1 v1
        VK_EXT_texel_buffer_alignment v1
        VK_EXT_texture_compression_astc_hdr v1
        VK_EXT_vertex_attribute_divisor v3
        VK_AMD_gpu_shader_half_float v2
        VK_AMD_negative_viewport_height v1
        VK_AMD_shader_image_load_store_lod v1
        VK_AMD_shader_trinary_minmax v1
        VK_IMG_format_pvrtc v1
        VK_INTEL_shader_integer_functions2 v1
        VK_GOOGLE_display_timing v1
        VK_MVK_macos_surface v3
        VK_MVK_moltenvk v37
        VK_NV_fragment_shader_barycentric v1
        VK_NV_glsl_shader v1
0370: thread_get_state failed on Apple Silicon - faking zero debug registers
0384: thread_get_state failed on Apple Silicon - faking zero debug registers
03c8: thread_get_state failed on Apple Silicon - faking zero debug registers
0450: thread_get_state failed on Apple Silicon - faking zero debug registers
0460: thread_get_state failed on Apple Silicon - faking zero debug registers

What version of Whisky are you using?

2.2.1

What version of macOS are you using?

Sonoma (macOS 14)

Issue Language

[X] Yes my issue is written in English

wesBass commented 6 months ago

Just saw this as well: 033c:err:winediag:ntlm_check_version ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.

wesBass commented 6 months ago

One more comment - it's throwing a "Blizzard" error - not a Whisky error. .. .

Eliichka commented 6 months ago

I'm getting the same error from blizzard crashing. 6A83124B-A7C4-4D0C-89AC-4EEF7FC1A754

2023-12-20T18:40:45Z.log

I've tried it with esync, no sync, multiple times, always crashing on Sonoma 14.2

ivan-konov commented 6 months ago

I am encountering the same error as @Eliichka Sonoma 14.2.1

twigandolive commented 6 months ago

Same error and same setup using Sonoma 14.2.1

Tried adding ntlm-auth 1.5.0 (pip install ntlm-auth) with no change and also tried ntlm_requests (pip install requests_ntlm) with no change. At a loss for how to proceed.

HuvosFromDarnassus commented 6 months ago

Same problem Sonoma 14.2.1

wesBass commented 6 months ago

I did the fix on #666 - which was to delete the battle.net folder (version 14052) and installed 14494 - from this response: https://github.com/Whisky-App/Whisky/issues/666#issuecomment-1835483684 - and I'm back up and running for the last few days. I leave battle_net running although it wants to update. I've had no issues running the game at all - but would love this to be fixed. Thanks

HuvosFromDarnassus commented 6 months ago

I'm trying to launch Diablo 2 Resurrected using the Diablo 4 Battle.net version launch guide. A crash occurs when launching D2R from Battle.net. @wesBass Are there any special settings and conditions for running D2R? It would be very cool to also see a guide to launching D2R. The demand for this game among the Mac community is also very high.

wesBass commented 6 months ago

I'm trying to launch Diablo 2 Resurrected using the Diablo 4 Battle.net version launch guide. A crash occurs when launching D2R from Battle.net. @wesBass Are there any special settings and conditions for running D2R? It would be very cool to also see a guide to launching D2R. The demand for this game among the Mac community is also very high.

Unfortunately, I've only been running III & IV - not 2R. Looks fantastic though!
When this issue first hit me, I would get issues similar to this - double check the guide for IV - and make sure they are the same. . .like the win version (19042) and esync - as well as turning OFF the hardware acceleration in the battle net launcher.

joroKr21 commented 6 months ago

I was running D2R on Mac based on this guide: https://www.outcoldman.com/en/archive/2023/06/07/playing-diablo-4-on-macos but that was before the Battle.net update. Now I'm waiting for the fix 😢 - but I don't see why it shouldn't be able to run with Whisky too since it's based on the game porting toolkit.

ivan-konov commented 6 months ago

I did the fix on #666 - which was to delete the battle.net folder (version 14052) and installed 14494 - from this response: #666 (comment) - and I'm back up and running for the last few days. I leave battle_net running although it wants to update. I've had no issues running the game at all - but would love this to be fixed. Thanks

I ended up doing the same thing. I just was hesitant to suggest it since that would involve downloading binaries from a non-official source. I am now sure that the issue lies completely in Battle.net and Whisky does not need to do anything ab out it. The CrossOver fix they did was patching the vanilla version of Wine. Whisky gets its Wine from the GPTK and has no control over it.

Probably worth closing this issue.

wesBass commented 6 months ago

I did the fix on #666 - which was to delete the battle.net folder (version 14052) and installed 14494 - from this response: #666 (comment) - and I'm back up and running for the last few days. I leave battle_net running although it wants to update. I've had no issues running the game at all - but would love this to be fixed. Thanks

I ended up doing the same thing. I just was hesitant to suggest it since that would involve downloading binaries from a non-official source. I am now sure that the issue lies completely in Battle.net and Whisky does not need to do anything ab out it. The CrossOver fix they did was patching the vanilla version of Wine. Whisky gets its Wine from the GPTK and has no control over it.

Probably worth closing this issue.

Good points Ivan - thank you. Closing.

wesBass commented 6 months ago

Good points Ivan - thank you. Closing.

tomohulk commented 5 months ago

Im not positive if this is entirely related, I renamed the battle.net folder to the older version, battle.net launches, but for some reason the Diablo4 play screen is black:

I have disabled the hardware acceleration feature and restarted. The stranger part is it's only this game, all of the other games render.

Maybe a new ticket needs to be opened on this?

wesBass commented 4 months ago

Diablo 4 has been unplayable albeit for a brief week or so - for a couple months now. It is not currently working either. Time to look for another method - or game. I'm open to any suggestions . . . .

zentavr commented 4 months ago

@wesBass the workaround in #666 works for me right now.

arcataroger commented 4 months ago

Diablo 4 has been unplayable albeit for a brief week or so - for a couple months now. It is not currently working either. Time to look for another method - or game. I'm open to any suggestions . . . .

I gave up on trying to run this in Whisky, but FYI the game finally came out on GeForce Now (both the Steam and Battle.net versions): https://blogs.nvidia.com/blog/geforce-now-thursday-battlenet-march-games-list/

It works superbly and doesn't require any workarounds. Really smooth even on ultra graphics... recommend that rather than trying to fiddle with Whisky.

zentavr commented 4 months ago

@arcataroger Just use an older battle.net

arcataroger commented 4 months ago

@arcataroger Just use an older battle.net

Even when it worked, the experience was poor on my M2. Thanks though!

tomohulk commented 4 months ago

I just want to re iterate, that the reason I opened this issue is because I can't even install D4, the Install button never renders. The "use an older version of bnet" work around does not fix that.

zentavr commented 4 months ago

@tomohulk this is actually how I installed that (D4) in early February. Put the old battle.net folder, removed the new one. Edited the render settings, installed D4 (and a couple of updates so far) and still playing.

tomohulk commented 4 months ago

Thanks @zentavr and my apologies, I opened a different ticket from this one, I thought this was my ticket I was commenting on. but I will give that a try. thanks.