Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Macbook] Bug - Dota 2 Ring Master update. (Intel core MacOS Sonoma Version 14.6.1 (23G93)) #21129

Open
akashsinghkunwar opened this issue Aug 23, 2024 · 46 comments

Comments

@akashsinghkunwar
Copy link

image

image

This comes after opening game dota 2 on mac

@akashsinghkunwar
Copy link
Author

image

@Donubu
Copy link

Donubu commented Aug 23, 2024

The same problem with iMac intel (Ventura).

Trying with -sw command, the problem persist.

@akashsinghkunwar
Copy link
Author

image

@akashsinghkunwar akashsinghkunwar changed the title Macbook Bug - Dota 2 Ring Master update. (Intel core MacOS Sonoma Version 14.6.1 (23G93)) [Macbook] Bug - Dota 2 Ring Master update. (Intel core MacOS Sonoma Version 14.6.1 (23G93)) Aug 23, 2024
@zeda96
Copy link

zeda96 commented Aug 23, 2024

Can relate. Having the same issue. Mac mini M1, Sonoma 14.6.1

@usefree
Copy link

usefree commented Aug 23, 2024

Apple M3 Pro, os 14.6.1 (23G93) with latest update available, same error 24 during launch

@cavadoge
Copy link

same here, Apple M1, os 13.5.1 (22G90), game worked fine before latest update, now crashed mid game and app won't restart

@derderian7
Copy link

same here on MacBook Air M1, OS 14.3.1 (23D60)

@ThePetrovich1337
Copy link

ThePetrovich1337 commented Aug 23, 2024

same here on MacBook Pro 15 Intel (2017)
Ventura 13.6.9 (22G830)
lobby and error

@Psychopath28
Copy link

same thing i also send the screenshot of the error

@wooodswu
Copy link

same thing! macbook air M1, macOS: version 14.6.1(23G93) error 24

@mylaluna
Copy link

same here on M1

@Vanness-au
Copy link

the same problem ,where can we report this bug?

@Oliveride
Copy link

Same problem. MacOS Sonoma.

@Rian199
Copy link

Rian199 commented Aug 23, 2024

Same here M1 Macbook Pro 2020 MacOS 14.2

@Soarrre
Copy link

Soarrre commented Aug 23, 2024

Same here Mac Mini M2 Sonoma 14.5

@FlorianWendelborn
Copy link

Related to ValveSoftware/Dota-2#2784

@tatarrr95
Copy link

m3 pro, Sonoma, same problem

@FlorianWendelborn
Copy link

Possible workaround here: ValveSoftware/Dota-2#2784 (comment)

@thiagoigfraga
Copy link

same on m1

1 similar comment
@some1ask
Copy link

same on m1

@shaba5h
Copy link

shaba5h commented Aug 23, 2024

same on m2

@ldzslv
Copy link

ldzslv commented Aug 23, 2024

me too

@svvdevell
Copy link

svvdevell commented Aug 23, 2024

Yes,really crashed sometimes

  1. First init after update dota
  2. Second after ACCEPT the game,but after app crashed and banned me
    Macbook M1 and the last MacOS

@alexandremoraesoliveira

Can't play Dota 2 with my friends anymore !! This is unacceptable !! Help Us Steam!! MacMini M1 macOS Sonoma 14.6.1

@lizilong007
Copy link

The same problem with MacBookPro intel (Catalina 10.15.7).

@pwan895
Copy link

pwan895 commented Aug 24, 2024

same on macos version 15 public beta.

@pwan895
Copy link

pwan895 commented Aug 24, 2024

please fix it, thanks!

@hlt7777777
Copy link

me too

@davidblus
Copy link

+1

@zeda96
Copy link

zeda96 commented Aug 24, 2024

Current Work around for this is

Click Ok on the error code
You will get a dialogue box,
Click Reopen
Continue playing the game

I was able to play 3-4 turbo games this morning. Works fine.

Slow updates coming through in MBs and KBs by valvo, so hang in there folks.

@tesazangetzu
Copy link

me too, the same problem macOS 2015 12.4, in the morning play 3 o 4 games...

@fabcairo
Copy link

I have the same problem with MacBook M3 Pro (Sonoma 14.6.1)

@thangible
Copy link

omg been more than a day
image

@dberkay34
Copy link

dberkay34 commented Aug 24, 2024

Hello,
I used to have the same problem. It's probably a cloud error meaning that the cloud files are not transferred or processed as needed. Here is what I did:

1 - Turn on Steam
2- Instead of directly clicking the game to play, please do right click and see the "properties"
3- Go for "Installed Files"
4- Click "Browse"
5- Click "Game"
6- Click "Bin"
7- Click "osx64"
8- Click "dota2.app"

By doing this You're supposed to not have the same bug now.
This is what I did and it worked.


Possible Reasons for the Issue

  1. Steam Integration Errors:

When starting the game directly through Steam, there may be integration issues between the Steam client and the game itself. This can stem from problems with updating game files, cloud synchronization, or other Steam-related issues.

  1. Updates and Cloud Synchronization:

During game updates or cloud synchronization, some files might be missing or corrupted, which can lead to various errors when starting the game.

  1. Corruption of Game Files:

Some parts of the game files might be corrupted, causing the game to not function properly. Launching the game directly through the application file might bypass some of these corruptions.

Reasons for Launching the Game Directly via dota2.app

  1. Direct Execution of Game Files:

Clicking directly on the dota2.app file bypasses some of Steam's high-level integrations and launches the game directly. This might temporarily help you avoid integration issues and cloud synchronization errors with Steam. This method starts the game using all its files directly, avoiding any errors introduced by the Steam client.

  1. Bypassing Steam Update and Synchronization Issues:

If there are issues with game file updates or cloud synchronization, starting the game directly via dota2.app might bypass these issues. This is often due to the Steam client making an error during a particular update or synchronization process.

General Solutions

  1. Update and Restart Steam:

Update the Steam client and restart it. Updates often help resolve existing bugs.

  1. Verify Game Files:

On Steam, use the option to verify the integrity of game files. Right-click the game, select "Properties" > "Local Files" > "Verify Integrity of Game Files." This will re-download any missing or corrupted files.

  1. Check Steam Cloud Synchronization:

Ensure that Steam Cloud synchronization is functioning correctly. This generally ensures that saved data for the game is synchronized properly.

  1. Check Access Permissions:

Check and adjust the game’s access permissions if necessary. On macOS, some permissions might prevent applications from working correctly.

My Thoughts on The Issue

I am not an expert, and unless Steam shares its source code, it can be quite difficult to determine where the problem originates. At this point, there should be no anger against Steam on not sharing the codes, because no game company would share such information due to the risk of theft or copying. However, I just want to share a few things I have noticed on my own.

The issue is likely caused by some files that are incorrectly, incompletely transferred, or not transferred from the cloud to the local storage.

My issue is as follows: when a team's base tower is destroyed and the game ends, the screen shuts down by itself. Additionally, this self-shutdown also occurs when trying to watch replays of the games I have played previously.

Screenshot 2024-08-24 at 12 37 24

To address the possibility that the error might be caused by some unintegrated files mentioned above, I tried the "Verify Integrity of Game Files" option, but it actually exacerbated the problem. After trying this option, the connection to the cloud was lost, and the game switched to offline mode after being unable to find a coordinator for a certain period of time.

Screenshot 2024-08-24 at 13 37 21 Screenshot 2024-08-24 at 14 10 36 Screenshot 2024-08-24 at 14 11 51 Screenshot 2024-08-24 at 14 13 33

As a solution, I uninstalled Steam from my computer, re-downloaded it from the website, and instead of directly clicking "Play", and without "verifying," I right-clicked, went to "Properties," and accessed the folder where the game is locally stored, as I mentioned above. By doing this, I ran the game using the files already present on my computer instead of those that could not be transferred or were incorrectly transferred from the cloud, and I did not encounter the same error again. Additionally, I can now watch replays, meaning the game does not shut down immediately when I click the "Watch Replay" button.

You can also check whether the issue has been resolved by observing the following: When the game starts, it is completely normal for it to display "game mode on." However, if it also shows a warning such as "access Steam...", this indicates that access to Steam is ongoing, which means the same cloud-related issue may occur again. This warning appeared when the game was closing on its own, but after running Dota from my local computer using dota2.app, I did not receive this "access" warning, and the game ran very well without the same bug.

Screenshot 2024-08-24 at 14 24 09 Screenshot 2024-08-24 at 14 24 52

@6u5haman
Copy link

Its either we should stop running Dota on potato computers or Valve should stop hiring potato employees

@emanuel-oprea
Copy link

Same issue with the game crashing at the end of the game, probabily it can't load the game review screen
M3 Max - Sonoma 14.6.1

@6u5haman "We don't need QA, devs have unit tests and e2e tests and all the automatic stuff... " No more QA, bugs are the future

@lKutts
Copy link

lKutts commented Aug 24, 2024

M1 Mac mini here, Sonoma 14.6.1, same thing.

@zeda96
Copy link

zeda96 commented Aug 25, 2024

Hello, I used to have the same problem. It's probably a cloud error meaning that the cloud files are not transferred or processed as needed. Here is what I did:

1 - Turn on Steam 2- Instead of directly clicking the game to play, please do right click and see the "properties" 3- Go for "Installed Files" 4- Click "Browse" 5- Click "Game" 6- Click "Bin" 7- Click "osx64" 8- Click "dota2.app"

By doing this You're supposed to not have the same bug now. This is what I did and it worked.

Possible Reasons for the Issue

  1. Steam Integration Errors:

When starting the game directly through Steam, there may be integration issues between the Steam client and the game itself. This can stem from problems with updating game files, cloud synchronization, or other Steam-related issues.

  1. Updates and Cloud Synchronization:

During game updates or cloud synchronization, some files might be missing or corrupted, which can lead to various errors when starting the game.

  1. Corruption of Game Files:

Some parts of the game files might be corrupted, causing the game to not function properly. Launching the game directly through the application file might bypass some of these corruptions.

Reasons for Launching the Game Directly via dota2.app

  1. Direct Execution of Game Files:

Clicking directly on the dota2.app file bypasses some of Steam's high-level integrations and launches the game directly. This might temporarily help you avoid integration issues and cloud synchronization errors with Steam. This method starts the game using all its files directly, avoiding any errors introduced by the Steam client.

  1. Bypassing Steam Update and Synchronization Issues:

If there are issues with game file updates or cloud synchronization, starting the game directly via dota2.app might bypass these issues. This is often due to the Steam client making an error during a particular update or synchronization process.

General Solutions

  1. Update and Restart Steam:

Update the Steam client and restart it. Updates often help resolve existing bugs.

  1. Verify Game Files:

On Steam, use the option to verify the integrity of game files. Right-click the game, select "Properties" > "Local Files" > "Verify Integrity of Game Files." This will re-download any missing or corrupted files.

  1. Check Steam Cloud Synchronization:

Ensure that Steam Cloud synchronization is functioning correctly. This generally ensures that saved data for the game is synchronized properly.

  1. Check Access Permissions:

Check and adjust the game’s access permissions if necessary. On macOS, some permissions might prevent applications from working correctly.

My Thoughts on The Issue

I am not an expert, and unless Steam shares its source code, it can be quite difficult to determine where the problem originates. At this point, there should be no anger against Steam on not sharing the codes, because no game company would share such information due to the risk of theft or copying. However, I just want to share a few things I have noticed on my own.

The issue is likely caused by some files that are incorrectly, incompletely transferred, or not transferred from the cloud to the local storage.

My issue is as follows: when a team's base tower is destroyed and the game ends, the screen shuts down by itself. Additionally, this self-shutdown also occurs when trying to watch replays of the games I have played previously.

Screenshot 2024-08-24 at 12 37 24 To address the possibility that the error might be caused by some unintegrated files mentioned above, I tried the "Verify Integrity of Game Files" option, but it actually exacerbated the problem. After trying this option, the connection to the cloud was lost, and the game switched to offline mode after being unable to find a coordinator for a certain period of time.

Screenshot 2024-08-24 at 13 37 21 Screenshot 2024-08-24 at 14 10 36 Screenshot 2024-08-24 at 14 11 51 Screenshot 2024-08-24 at 14 13 33
As a solution, I uninstalled Steam from my computer, re-downloaded it from the website, and instead of directly clicking "Play", and without "verifying," I right-clicked, went to "Properties," and accessed the folder where the game is locally stored, as I mentioned above. By doing this, I ran the game using the files already present on my computer instead of those that could not be transferred or were incorrectly transferred from the cloud, and I did not encounter the same error again. Additionally, I can now watch replays, meaning the game does not shut down immediately when I click the "Watch Replay" button.

You can also check whether the issue has been resolved by observing the following: When the game starts, it is completely normal for it to display "game mode on." However, if it also shows a warning such as "access Steam...", this indicates that access to Steam is ongoing, which means the same cloud-related issue may occur again. This warning appeared when the game was closing on its own, but after running Dota from my local computer using dota2.app, I did not receive this "access" warning, and the game ran very well without the same bug.

Screenshot 2024-08-24 at 14 24 09 Screenshot 2024-08-24 at 14 24 52

Great stuff friend! Enjoyed reading through - will be trying out the new dota2.app method but regardless, even on normally opening the app, game works fine for me. It just quits right when loaders are loading. (poor English, sorry)

As for seeking out source code from Steam, I don't think any of us are expecting this level of resolution. We patiently wait and let valve do its thing - that's the best we can do. In terms of priority pipeline, I am sure MacOS is somewhere high on the list but not the highest.

They will squash one bug at a time. Hopefully all good before TI.

Cheers!

@fschai89
Copy link

hello dota 2 dev? you guys sleeping?

@mylaluna
Copy link

Hello, I used to have the same problem. It's probably a cloud error meaning that the cloud files are not transferred or processed as needed. Here is what I did:

1 - Turn on Steam 2- Instead of directly clicking the game to play, please do right click and see the "properties" 3- Go for "Installed Files" 4- Click "Browse" 5- Click "Game" 6- Click "Bin" 7- Click "osx64" 8- Click "dota2.app"

By doing this You're supposed to not have the same bug now. This is what I did and it worked.

Possible Reasons for the Issue

  1. Steam Integration Errors:

When starting the game directly through Steam, there may be integration issues between the Steam client and the game itself. This can stem from problems with updating game files, cloud synchronization, or other Steam-related issues.

  1. Updates and Cloud Synchronization:

During game updates or cloud synchronization, some files might be missing or corrupted, which can lead to various errors when starting the game.

  1. Corruption of Game Files:

Some parts of the game files might be corrupted, causing the game to not function properly. Launching the game directly through the application file might bypass some of these corruptions.

Reasons for Launching the Game Directly via dota2.app

  1. Direct Execution of Game Files:

Clicking directly on the dota2.app file bypasses some of Steam's high-level integrations and launches the game directly. This might temporarily help you avoid integration issues and cloud synchronization errors with Steam. This method starts the game using all its files directly, avoiding any errors introduced by the Steam client.

  1. Bypassing Steam Update and Synchronization Issues:

If there are issues with game file updates or cloud synchronization, starting the game directly via dota2.app might bypass these issues. This is often due to the Steam client making an error during a particular update or synchronization process.

General Solutions

  1. Update and Restart Steam:

Update the Steam client and restart it. Updates often help resolve existing bugs.

  1. Verify Game Files:

On Steam, use the option to verify the integrity of game files. Right-click the game, select "Properties" > "Local Files" > "Verify Integrity of Game Files." This will re-download any missing or corrupted files.

  1. Check Steam Cloud Synchronization:

Ensure that Steam Cloud synchronization is functioning correctly. This generally ensures that saved data for the game is synchronized properly.

  1. Check Access Permissions:

Check and adjust the game’s access permissions if necessary. On macOS, some permissions might prevent applications from working correctly.

My Thoughts on The Issue

I am not an expert, and unless Steam shares its source code, it can be quite difficult to determine where the problem originates. At this point, there should be no anger against Steam on not sharing the codes, because no game company would share such information due to the risk of theft or copying. However, I just want to share a few things I have noticed on my own.

The issue is likely caused by some files that are incorrectly, incompletely transferred, or not transferred from the cloud to the local storage.

My issue is as follows: when a team's base tower is destroyed and the game ends, the screen shuts down by itself. Additionally, this self-shutdown also occurs when trying to watch replays of the games I have played previously.

Screenshot 2024-08-24 at 12 37 24 To address the possibility that the error might be caused by some unintegrated files mentioned above, I tried the "Verify Integrity of Game Files" option, but it actually exacerbated the problem. After trying this option, the connection to the cloud was lost, and the game switched to offline mode after being unable to find a coordinator for a certain period of time.

Screenshot 2024-08-24 at 13 37 21 Screenshot 2024-08-24 at 14 10 36 Screenshot 2024-08-24 at 14 11 51 Screenshot 2024-08-24 at 14 13 33
As a solution, I uninstalled Steam from my computer, re-downloaded it from the website, and instead of directly clicking "Play", and without "verifying," I right-clicked, went to "Properties," and accessed the folder where the game is locally stored, as I mentioned above. By doing this, I ran the game using the files already present on my computer instead of those that could not be transferred or were incorrectly transferred from the cloud, and I did not encounter the same error again. Additionally, I can now watch replays, meaning the game does not shut down immediately when I click the "Watch Replay" button.

You can also check whether the issue has been resolved by observing the following: When the game starts, it is completely normal for it to display "game mode on." However, if it also shows a warning such as "access Steam...", this indicates that access to Steam is ongoing, which means the same cloud-related issue may occur again. This warning appeared when the game was closing on its own, but after running Dota from my local computer using dota2.app, I did not receive this "access" warning, and the game ran very well without the same bug.

Screenshot 2024-08-24 at 14 24 09 Screenshot 2024-08-24 at 14 24 52

Thank you for sharing your solution. I have a few launch options for the game. Is there a way to run these options when launching the game directly?

@yunot
Copy link

yunot commented Aug 26, 2024

Hello, I used to have the same problem. It's probably a cloud error meaning that the cloud files are not transferred or processed as needed. Here is what I did:

1 - Turn on Steam 2- Instead of directly clicking the game to play, please do right click and see the "properties" 3- Go for "Installed Files" 4- Click "Browse" 5- Click "Game" 6- Click "Bin" 7- Click "osx64" 8- Click "dota2.app"

By doing this You're supposed to not have the same bug now. This is what I did and it worked.

Possible Reasons for the Issue

  1. Steam Integration Errors:

When starting the game directly through Steam, there may be integration issues between the Steam client and the game itself. This can stem from problems with updating game files, cloud synchronization, or other Steam-related issues.

  1. Updates and Cloud Synchronization:

During game updates or cloud synchronization, some files might be missing or corrupted, which can lead to various errors when starting the game.

  1. Corruption of Game Files:

Some parts of the game files might be corrupted, causing the game to not function properly. Launching the game directly through the application file might bypass some of these corruptions.

Reasons for Launching the Game Directly via dota2.app

  1. Direct Execution of Game Files:

Clicking directly on the dota2.app file bypasses some of Steam's high-level integrations and launches the game directly. This might temporarily help you avoid integration issues and cloud synchronization errors with Steam. This method starts the game using all its files directly, avoiding any errors introduced by the Steam client.

  1. Bypassing Steam Update and Synchronization Issues:

If there are issues with game file updates or cloud synchronization, starting the game directly via dota2.app might bypass these issues. This is often due to the Steam client making an error during a particular update or synchronization process.

General Solutions

  1. Update and Restart Steam:

Update the Steam client and restart it. Updates often help resolve existing bugs.

  1. Verify Game Files:

On Steam, use the option to verify the integrity of game files. Right-click the game, select "Properties" > "Local Files" > "Verify Integrity of Game Files." This will re-download any missing or corrupted files.

  1. Check Steam Cloud Synchronization:

Ensure that Steam Cloud synchronization is functioning correctly. This generally ensures that saved data for the game is synchronized properly.

  1. Check Access Permissions:

Check and adjust the game’s access permissions if necessary. On macOS, some permissions might prevent applications from working correctly.

My Thoughts on The Issue

I am not an expert, and unless Steam shares its source code, it can be quite difficult to determine where the problem originates. At this point, there should be no anger against Steam on not sharing the codes, because no game company would share such information due to the risk of theft or copying. However, I just want to share a few things I have noticed on my own.

The issue is likely caused by some files that are incorrectly, incompletely transferred, or not transferred from the cloud to the local storage.

My issue is as follows: when a team's base tower is destroyed and the game ends, the screen shuts down by itself. Additionally, this self-shutdown also occurs when trying to watch replays of the games I have played previously.

Screenshot 2024-08-24 at 12 37 24 To address the possibility that the error might be caused by some unintegrated files mentioned above, I tried the "Verify Integrity of Game Files" option, but it actually exacerbated the problem. After trying this option, the connection to the cloud was lost, and the game switched to offline mode after being unable to find a coordinator for a certain period of time.

Screenshot 2024-08-24 at 13 37 21 Screenshot 2024-08-24 at 14 10 36 Screenshot 2024-08-24 at 14 11 51 Screenshot 2024-08-24 at 14 13 33
As a solution, I uninstalled Steam from my computer, re-downloaded it from the website, and instead of directly clicking "Play", and without "verifying," I right-clicked, went to "Properties," and accessed the folder where the game is locally stored, as I mentioned above. By doing this, I ran the game using the files already present on my computer instead of those that could not be transferred or were incorrectly transferred from the cloud, and I did not encounter the same error again. Additionally, I can now watch replays, meaning the game does not shut down immediately when I click the "Watch Replay" button.

You can also check whether the issue has been resolved by observing the following: When the game starts, it is completely normal for it to display "game mode on." However, if it also shows a warning such as "access Steam...", this indicates that access to Steam is ongoing, which means the same cloud-related issue may occur again. This warning appeared when the game was closing on its own, but after running Dota from my local computer using dota2.app, I did not receive this "access" warning, and the game ran very well without the same bug.

Screenshot 2024-08-24 at 14 24 09 Screenshot 2024-08-24 at 14 24 52

Thx @dberkay34 .This workaround works for M2 Mac as well, but if I want to use some built-in options (like in-game FPS counter), is there a way to solve it?

@yevsa
Copy link

yevsa commented Aug 27, 2024

the issue is fixed

@ldzslv
Copy link

ldzslv commented Aug 28, 2024

the issue is fixed

what is a solution?

@ADSkor
Copy link

ADSkor commented Aug 30, 2024

the issue is fixed

No, it's not. Still present!

@yevsa
Copy link

yevsa commented Sep 7, 2024

Try verify integrity cache. It did not help at first but on Aug 27 patches fixed crashes for me. No longer happening. M1 Pro

@winterdl
Copy link

turn off bluetooth

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests