[Bug]: "Battle.net" crashed when login

klzami commented 7 months ago

Description

Battle.net crash at login page

Steps to reproduce

Install Whisky on Mac OS 14.0;
Upgrade Whisky to version 2.2.1 and restart Whisky;
Run Battle.net-Setup.exe and wait;
Battle.net will crash at login page;
You can find error tips in log file.

Expected behaviour

Battle.net not crash

Logs

Whisky Version: 2.2.1
Date: 2023-12-01T04:10:56Z
macOS Version: 14.0.0

Bottle Name: Windows 10
Bottle URL: /Users/MyUserName/Library/Containers/com.isaacmarovitz.Whisky/Bottles/3DD9C074-277B-449A-B039-D0E30CDE9592

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

Metal HUD: false
Metal Trace: false

Arguments: start /unix /Users/MyUserName/Library/Containers/com.isaacmarovitz.Whisky/Bottles/3DD9C074-277B-449A-B039-D0E30CDE9592/drive_c/Program Files (x86)/Battle.net/Battle.net Launcher.exe

Environment:
{
    "DXVK_ASYNC" = 1;
    "LC_ALL" = "en_US";
    WINEDEBUG = "fixme-all";
    WINEESYNC = 1;
    WINEPREFIX = "/Users/MyUserName/Library/Containers/com.isaacmarovitz.Whisky/Bottles/3DD9C074-277B-449A-B039-D0E30CDE9592";
}

esync: up and running.
0068:err:module:open_builtin_so_file failed to load .so lib "/Users/MyUserName/Library/Application Support/com.isaacmarovitz.Whisky/Libraries/Wine/lib/wine/x86_64-unix/wineusb.sys.so"
0068:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142
0150: thread_get_state failed on Apple Silicon - faking zero debug registers
0160: thread_get_state failed on Apple Silicon - faking zero debug registers
018c: thread_get_state failed on Apple Silicon - faking zero debug registers
01b8: 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_su[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
[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
01f4: thread_get_state failed on Apple Silicon - faking zero debug registers
0188:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
0188:err:winediag:wined3d_adapter_create Using the Vulkan renderer for d3d10/11 applications.
0188: thread_get_state failed on Apple Silicon - faking zero debug registers
024c: thread_get_state failed on Apple Silicon - faking zero debug registers
0258: thread_get_state failed on Apple Silicon - faking zero debug registers
028c: thread_get_state failed on Apple Silicon - faking zero debug registers
01b0: thread_get_state failed on Apple Silicon - faking zero debug registers
0308: thread_get_state failed on Apple Silicon - faking zero debug registers
0330: 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

huynguyen-quoc commented 7 months ago

i got same issues for new macos 14.1.2

akmad commented 7 months ago

I think this may be related to the latest version of Battle.net (build 14542). If you have a previous version of Battle.net that was installed there should be multiple directories under [bottle_dir]/drive_c/Program Files (x86)/Battle.net/ and you can delete (or rename) the Battle.net.14542 directory and then Battle.net should start. It does look like the Battle.net.14542 directory will be recreated and presumably used the next time Battle.net is started so this is just a stopgap solution until others are able to figure out what's going on with the latest version.

Note - I did not test this specifically with Whisky as I set up Battle.net on my Mac manually but I was experiencing the same issue with my manual setup and this fixed it.

huynguyen-quoc commented 7 months ago

I think this may be related to the latest version of Battle.net (build 14542). If you have a previous version of Battle.net that was installed there should be multiple directories under [bottle_dir]/drive_c/Program Files (x86)/Battle.net/ and you can delete (or rename) the Battle.net.14542 directory and then Battle.net should start. It does look like the Battle.net.14542 directory will be recreated and presumably used the next time Battle.net is started so this is just a stopgap solution until others are able to figure out what's going on with the latest version.

Note - I did not test this specifically with Whisky as I set up Battle.net on my Mac manually but I was experiencing the same issue with my manual setup and this fixed it.

can you share your battle net old version ?

akmad commented 7 months ago

Here is the version that was working for me: https://file.io/uu9AkN9xEyGz (Battle.net.14494.zip). Just unzip that into the directory I mentioned earlier, it should create a Battle.net.14494 directory.

I have no idea if the main Battle.net.exe or Launcher uses some directory name logic to find the correct version to use or if there is a config file somewhere you'd have to update to get that working. For me, I didn't have to change anything and the older version was used.

klzami commented 7 months ago

How to use the old version (Battle.net.14494.zip) ? Just replace all files of new version?

huynguyen-quoc commented 7 months ago

How to use the old version (Battle.net.14494.zip) ? Just replace all files of new version?

@klzami just remove Battle.net.14542 folder and battle net app will take the old version. Everytime before start battlenet we need to remove it

stemicha commented 7 months ago

Here is the version that was working for me: https://file.io/uu9AkN9xEyGz (Battle.net.14494.zip). Just unzip that into the directory I mentioned earlier, it should create a Battle.net.14494 directory.

I have no idea if the main Battle.net.exe or Launcher uses some directory name logic to find the correct version to use or if there is a config file somewhere you'd have to update to get that working. For me, I didn't have to change anything and the older version was used.

May you please be so kind and share the version again, the file is deleted. Thanks

di3tc0ke commented 7 months ago

I think this may be related to the latest version of Battle.net (build 14542). If you have a previous version of Battle.net that was installed there should be multiple directories under [bottle_dir]/drive_c/Program Files (x86)/Battle.net/ and you can delete (or rename) the Battle.net.14542 directory and then Battle.net should start. It does look like the Battle.net.14542 directory will be recreated and presumably used the next time Battle.net is started so this is just a stopgap solution until others are able to figure out what's going on with the latest version.

Note - I did not test this specifically with Whisky as I set up Battle.net on my Mac manually but I was experiencing the same issue with my manual setup and this fixed it.

This does the trick! thx!

hs-graphic commented 7 months ago

Here is the version that was working for me: https://file.io/uu9AkN9xEyGz (Battle.net.14494.zip). Just unzip that into the directory I mentioned earlier, it should create a Battle.net.14494 directory.

I have no idea if the main Battle.net.exe or Launcher uses some directory name logic to find the correct version to use or if there is a config file somewhere you'd have to update to get that working. For me, I didn't have to change anything and the older version was used.

@akmad Can you kindly share the zip file again please? The link seems deleted - thanks in advance!

subzer0x commented 7 months ago

yes please share the file again, link is not working - thanks

akmad commented 7 months ago

Sorry that the original link stopped working, here's one that should stay up for a while: https://www.dropbox.com/scl/fi/68zr85eh5qfwzvum8jb7w/Battle.net.14494.zip?rlkey=wsv1wv4b3iavkum35ccix4a5s&dl=0

stemicha commented 7 months ago

Thank you for sharing ! It works again. Never change a running system ;-)

subzer0x commented 7 months ago

Sorry that the original link stopped working, here's one that should stay up for a while: https://www.dropbox.com/scl/fi/68zr85eh5qfwzvum8jb7w/Battle.net.14494.zip?rlkey=wsv1wv4b3iavkum35ccix4a5s&dl=0

Thanks akmad

hs-graphic commented 7 months ago

Sorry that the original link stopped working, here's one that should stay up for a while: https://www.dropbox.com/scl/fi/68zr85eh5qfwzvum8jb7w/Battle.net.14494.zip?rlkey=wsv1wv4b3iavkum35ccix4a5s&dl=0

Thanks alot @akmad It seems going through to the battle.net dashboard window but it comes out as total black - does everyone have the same issue?

subzer0x commented 7 months ago

Sorry that the original link stopped working, here's one that should stay up for a while: https://www.dropbox.com/scl/fi/68zr85eh5qfwzvum8jb7w/Battle.net.14494.zip?rlkey=wsv1wv4b3iavkum35ccix4a5s&dl=0

Thanks alot @akmad It seems going through to the battle.net dashboard window but it comes out as total black - does everyone have the same issue?

yes I have the same problem

di3tc0ke commented 7 months ago

Sorry that the original link stopped working, here's one that should stay up for a while: https://www.dropbox.com/scl/fi/68zr85eh5qfwzvum8jb7w/Battle.net.14494.zip?rlkey=wsv1wv4b3iavkum35ccix4a5s&dl=0

Thanks alot @akmad It seems going through to the battle.net dashboard window but it comes out as total black - does everyone have the same issue?

yes, I had the same.

ajseesink commented 7 months ago

Sorry that the original link stopped working, here's one that should stay up for a while: https://www.dropbox.com/scl/fi/68zr85eh5qfwzvum8jb7w/Battle.net.14494.zip?rlkey=wsv1wv4b3iavkum35ccix4a5s&dl=0

Thanks alot @akmad It seems going through to the battle.net dashboard window but it comes out as total black - does everyone have the same issue?

Check! Same issue here.

WoodJohn commented 7 months ago

For the black window issue, this thread worked for me https://github.com/Whisky-App/Whisky/issues/198#issuecomment-1618979646

Gefrierpunkt commented 7 months ago

I think this may be related to the latest version of Battle.net (build 14542). If you have a previous version of Battle.net that was installed there should be multiple directories under [bottle_dir]/drive_c/Program Files (x86)/Battle.net/ and you can delete (or rename) the Battle.net.14542 directory and then Battle.net should start. It does look like the Battle.net.14542 directory will be recreated and presumably used the next time Battle.net is started so this is just a stopgap solution until others are able to figure out what's going on with the latest version. Note - I did not test this specifically with Whisky as I set up Battle.net on my Mac manually but I was experiencing the same issue with my manual setup and this fixed it.

This does the trick! thx!

This helped getting to the Passwort Prompt without crashing first. Filling in email and Passwort and pressing enter doesn't result in a Login. Battle.net stays idyle without any Failure Message or reaction. Can someone help or has the same issue?

Using:

Whisky 2.2.1
newest Version of battle.net (which doesn't accept a Downgrade)
Latest Version Sonoma 14.1.2

The idea to rename the battle.net folder to "Battle.net.14542" results in the message "go on with the newest version of battle.net" (Mit neuester Version fortfahren). Clicking this message doesn't result in anything else than closing the message window.

Thank you for help!

nathanbeier commented 7 months ago

This helped getting to the Passwort Prompt without crashing first. Filling in email and Passwort and pressing enter doesn't result in a Login. Battle.net stays idyle without any Failure Message or reaction. Can someone help or has the same issue?

Using:

Whisky 2.2.1

newest Version of battle.net (which doesn't accept a Downgrade)

Latest Version Sonoma 14.1.2

The idea to rename the battle.net folder to "Battle.net.14542" results in the message "go on with the newest version of battle.net" (Mit neuester Version fortfahren). Clicking this message doesn't result in anything else than closing the message window.

Thank you for help!

Hi, I had a similar issue. I opted to create a new bottle and get a fresh install of Battle.net. Let Battle.net install like normal, then before launching put the DropBox Battle.net.14494 folder in the Battle.net folder in your drive_c and delete the Battle.net.14542 folder. Then be sure to launch and disable hardware acceleration like normal.

As mentioned, you will need to go in and delete the Battle.net.14542 folder every time you relaunch Battle.net. I hope that helps since I ran into a very similar issue.

akmad commented 7 months ago

I think this may be related to the latest version of Battle.net (build 14542). If you have a previous version of Battle.net that was installed there should be multiple directories under [bottle_dir]/drive_c/Program Files (x86)/Battle.net/ and you can delete (or rename) the Battle.net.14542 directory and then Battle.net should start. It does look like the Battle.net.14542 directory will be recreated and presumably used the next time Battle.net is started so this is just a stopgap solution until others are able to figure out what's going on with the latest version. Note - I did not test this specifically with Whisky as I set up Battle.net on my Mac manually but I was experiencing the same issue with my manual setup and this fixed it.

This does the trick! thx!

This helped getting to the Passwort Prompt without crashing first. Filling in email and Passwort and pressing enter doesn't result in a Login. Battle.net stays idyle without any Failure Message or reaction. Can someone help or has the same issue?

Using:

Whisky 2.2.1

newest Version of battle.net (which doesn't accept a Downgrade)

Latest Version Sonoma 14.1.2

The idea to rename the battle.net folder to "Battle.net.14542" results in the message "go on with the newest version of battle.net" (Mit neuester Version fortfahren). Clicking this message doesn't result in anything else than closing the message window.

Thank you for help!

FYI, my suggestion is not to simply rename the folder. You need to download the previous version (using the link I provided above), delete the folder for the newer version (which is inside the Battle.net folder), and then unzip the older version into the Battle.net folder. This is working for me right now.

Gefrierpunkt commented 7 months ago

This helped getting to the Passwort Prompt without crashing first. Filling in email and Passwort and pressing enter doesn't result in a Login. Battle.net stays idyle without any Failure Message or reaction. Can someone help or has the same issue? Using:

Whisky 2.2.1

newest Version of battle.net (which doesn't accept a Downgrade)

Latest Version Sonoma 14.1.2

The idea to rename the battle.net folder to "Battle.net.14542" results in the message "go on with the newest version of battle.net" (Mit neuester Version fortfahren). Clicking this message doesn't result in anything else than closing the message window. Thank you for help!

Hi, I had a similar issue. I opted to create a new bottle and get a fresh install of Battle.net. Let Battle.net install like normal, then before launching put the DropBox Battle.net.14494 folder in the Battle.net folder in your drive_c and delete the Battle.net.14542 folder. Then be sure to launch and disable hardware acceleration like normal.

As mentioned, you will need to go in and delete the Battle.net.14542 folder every time you relaunch Battle.net. I hope that helps since I ran into a very similar issue.

Yes! this Helps :) Thank You!

Gefrierpunkt commented 7 months ago

I think this may be related to the latest version of Battle.net (build 14542). If you have a previous version of Battle.net that was installed there should be multiple directories under [bottle_dir]/drive_c/Program Files (x86)/Battle.net/ and you can delete (or rename) the Battle.net.14542 directory and then Battle.net should start. It does look like the Battle.net.14542 directory will be recreated and presumably used the next time Battle.net is started so this is just a stopgap solution until others are able to figure out what's going on with the latest version. Note - I did not test this specifically with Whisky as I set up Battle.net on my Mac manually but I was experiencing the same issue with my manual setup and this fixed it.

This does the trick! thx!

This helped getting to the Passwort Prompt without crashing first. Filling in email and Passwort and pressing enter doesn't result in a Login. Battle.net stays idyle without any Failure Message or reaction. Can someone help or has the same issue? Using:

Whisky 2.2.1

newest Version of battle.net (which doesn't accept a Downgrade)

Latest Version Sonoma 14.1.2

The idea to rename the battle.net folder to "Battle.net.14542" results in the message "go on with the newest version of battle.net" (Mit neuester Version fortfahren). Clicking this message doesn't result in anything else than closing the message window. Thank you for help!

FYI, my suggestion is not to simply rename the folder. You need to download the previous version (using the link I provided above), delete the folder for the newer version (which is inside the Battle.net folder), and then unzip the older version into the Battle.net folder. This is working for me right now.

Thank you, it didn't work with the old bottle but with a new one :) Thanks for the provided previous version!

jecc1982 commented 7 months ago

Saw this in the Blizzard forum.

Adding WINE_SIMULATE_WRITECOPY=1 as an environment variable fixes 14542.

https://us.forums.blizzard.com/en/blizzard/t/battlenet-patch-14542-not-working-in-wine/48425/18

EDIT: Wine-GE-Proton released a new version to fix the issue by setting simulate_writecopy to true (see https://github.com/GloriousEggroll/proton-wine/commit/2ad0c4ef188ba570a2a86ec3353e0d37bef00ff3)

johnbayne15 commented 7 months ago

Thanks Akmad for uploading the folder!

I managed to launch Battle.net but when I click "play" D4 never loads. Has anyone experienced this?

Edit: hadn't changed bottle "ESync"

di3tc0ke commented 7 months ago

Saw this in the Blizzard forum.

Adding WINE_SIMULATE_WRITECOPY=1 as an environment variable fixes 14542.

https://us.forums.blizzard.com/en/blizzard/t/battlenet-patch-14542-not-working-in-wine/48425/18

EDIT: Wine-GE-Proton released a new version to fix the issue by setting simulate_writecopy to true (see GloriousEggroll/proton-wine@2ad0c4e)

No luck with the variable. Still black screen. I have to use the delete-folder-method so far.

LW-Ho commented 7 months ago

Same issue.

akeschmidi commented 7 months ago

Same here

sqianglan commented 7 months ago

I am able to 'fix' it by open the battle.net without internet. And enable the internet after the page was partially loaded. Not sure it is the right way or just good luck

BrianJThomas commented 7 months ago

Saw this in the Blizzard forum.

Adding WINE_SIMULATE_WRITECOPY=1 as an environment variable fixes 14542.

https://us.forums.blizzard.com/en/blizzard/t/battlenet-patch-14542-not-working-in-wine/48425/18

EDIT: Wine-GE-Proton released a new version to fix the issue by setting simulate_writecopy to true (see GloriousEggroll/proton-wine@2ad0c4e)

Is there a way to do this in Whisky? I'm assuming the Environment Variables UI shown for each executable is for setting environment variables in the Wine environment rather than for Wine itself. How can we set this flag for Wine?

sirhalos commented 7 months ago

Setting the variable WINE_SIMULATE_WRITECOPY on the Battle.net.exe now does allow me to move past the login screen, but the next screen where it shows the games is now blank, similar to how it is if you forget to turn off hardware acceleration on the battlenet client.

di3tc0ke commented 7 months ago

I am able to 'fix' it by open the battle.net without internet. And enable the internet after the page was partially loaded. Not sure it is the right way or just good luck

Doesn't work in my environment...

AndreyGanichev commented 7 months ago

Saw this in the Blizzard forum.

Adding WINE_SIMULATE_WRITECOPY=1 as an environment variable fixes 14542.

https://us.forums.blizzard.com/en/blizzard/t/battlenet-patch-14542-not-working-in-wine/48425/18 EDIT: Wine-GE-Proton released a new version to fix the issue by setting simulate_writecopy to true (see GloriousEggroll/proton-wine@2ad0c4e)

No luck with the variable. Still black screen. I have to use the delete-folder-method so far.

after spending some hours, i found the following: 1) changing version to 14494 as written above will allow you to pass login screen. 2) if battle net appears black: quit battle net -> go to whisky bottle configuration -> enable(turn on) DXVK 3) restart battle net(now it will be shown) -> go to battle net settings -> disable hardware acceleration -> save and quit battle net 4) go again to whisky bottle configuration -> back disable (turn off) DXVK 5) now both battle net and d4 should run fine

Xuberone commented 7 months ago

Saw this in the Blizzard forum.

Adding WINE_SIMULATE_WRITECOPY=1 as an environment variable fixes 14542.

https://us.forums.blizzard.com/en/blizzard/t/battlenet-patch-14542-not-working-in-wine/48425/18

EDIT: Wine-GE-Proton released a new version to fix the issue by setting simulate_writecopy to true (see GloriousEggroll/proton-wine@2ad0c4e)

How do I install Wine-GE-Proton package into Whisky? Sorry I am a total noob using Whisky for the first time trying to install D4

ermanpehlivan commented 7 months ago

it works for me. I just deleted the new folder and the old version of battle.net is working and I can play now. I also updated the whiskey too.

baslia commented 6 months ago

Same issue here :(

zentavr commented 4 months ago

Saw this in the Blizzard forum.

Adding WINE_SIMULATE_WRITECOPY=1 as an environment variable fixes 14542.

https://us.forums.blizzard.com/en/blizzard/t/battlenet-patch-14542-not-working-in-wine/48425/18 EDIT: Wine-GE-Proton released a new version to fix the issue by setting simulate_writecopy to true (see GloriousEggroll/proton-wine@2ad0c4e)

No luck with the variable. Still black screen. I have to use the delete-folder-method so far.

after spending some hours, i found the following:
1. changing version to 14494 as written above will allow you to pass login screen.

2. if battle net appears black: quit battle net -> go to whisky bottle configuration -> enable(turn on)  DXVK

3. restart battle net(now it will be shown) -> go to battle net settings -> disable hardware acceleration -> save and quit battle net

4. go again to whisky bottle configuration -> back disable (turn off) DXVK

5. now both battle net and d4 should run fine

This workaround works for me. But all the time I need to remove the new folder of Battle.net application

di3tc0ke commented 4 months ago

Here is a weird work around if you can play the game with Battle.net.14494.

Copy everything inside Battle.net.14494, paste them into new Battlenet folder, Battle.net.14589 in my case, start Battlenet app in Whisky, then click Continue with Latest Version button, now it is tricky but press command-option-esc, select wine64-preloader and Force Quite twice. Then Battlenet app launches.

Without this workaround, I had to delete the new Battlenet folder every time after it generated.

fabd commented 3 months ago

Any up to date solution? I am trying to run Diablo II Resurrected. Using the wiki solution for Diablo IV (ie. Battle.Net)

Edit: got past the login screen and downloading D2R by using the 14494 archive kindly shared earlier in the thread.

Peppershaker commented 3 months ago

I was able to get past the login screen with 14494 but it immediately asks me to update battle net. I will then be forced to either update or quit.

Peppershaker commented 3 months ago

Got this working after trying a few more time. Sometimes the app upgrade popup appears slower than others and give me enough time to install the game.

NikolayOG commented 3 months ago

Using 14494 no longer works because battlenet forces you to upgrade to a newer version which is 14766

ajseesink commented 3 months ago

Check. I also just found out battle.net forces you to upgrade to 14766. Cant get D4 to start anymore at this moment.

theeaglesfan005 commented 3 months ago

same for me as well... forcing update to 14766

hahayupgit commented 3 months ago

As far as I know, the last version of Battle.net that worked on Whisky was version 14494. Additionally, a new update with Diablo 4 prevents the game from running at all with Whisky.

AndreyGanichev commented 1 month ago

Hello, has anyone found a new way tp run d4 on macos?

ajseesink commented 1 month ago

Hello, has anyone found a new way tp run d4 on macos?

I run d4 on my macbook pro M1 with crossover. Think it also runs on Parallels.

AndreyGanichev commented 1 month ago

Hello, has anyone found a new way tp run d4 on macos?

I run d4 on my macbook pro M1 with crossover. Think it also runs on Parallels.

How is performance? Before whisky, I've tried on Parallels and performance was very low and it took a lot of space (for windows and d4).

ajseesink commented 1 month ago

Performance is good. Comparable with whisky. I run it in a MacBook Pro M1 Pro with 32 gig memory by the way

AndreyGanichev commented 1 month ago

Thanks a lot. And last question: no problems with last versions of battle net?

Whisky-App / Whisky