Posted September 08, 2024
I just bought and installed the game using GOG Galaxy and after the initial long verification time, the game now crashes every time I run it. I am running it directly, not through GOG Galaxy.
What I found odd is the crash indicated it was running the "X86-64 (Translated)" version which means it's using Rosetta 2, but it shouldn't be since that's not checked in the Info window.
Now here's the more interesting thing. If I go into the app content folder (Baldur's Gate 3.app/Contents/MacOS) and run the "Baldur's Gate 3" it immediately crashes, but if I run "Baldur's Gate 3 GOG" the game opens and works fine.
As such it seems like the app is running the wrong executable. I have no idea why though. Any ideas on how to get the app to launch normally?
Edit:
I ended up renaming the "Baldur's Gate 3" file that causes the came to crash as "Baldur's Gate 3.bad" and then copied the "Baldur's Gate 3 GOG" to "Baldur's Gate 3", effectively replacing the executable that crashes with the one that runs. I can now run the app normally, but I find it odd that I need to do that as basically anyone with an Apple Silicon Mac shouldn't be able to run the application without crashing if the exec is bad.
What I found odd is the crash indicated it was running the "X86-64 (Translated)" version which means it's using Rosetta 2, but it shouldn't be since that's not checked in the Info window.
Now here's the more interesting thing. If I go into the app content folder (Baldur's Gate 3.app/Contents/MacOS) and run the "Baldur's Gate 3" it immediately crashes, but if I run "Baldur's Gate 3 GOG" the game opens and works fine.
As such it seems like the app is running the wrong executable. I have no idea why though. Any ideas on how to get the app to launch normally?
Edit:
I ended up renaming the "Baldur's Gate 3" file that causes the came to crash as "Baldur's Gate 3.bad" and then copied the "Baldur's Gate 3 GOG" to "Baldur's Gate 3", effectively replacing the executable that crashes with the one that runs. I can now run the app normally, but I find it odd that I need to do that as basically anyone with an Apple Silicon Mac shouldn't be able to run the application without crashing if the exec is bad.
Post edited September 08, 2024 by morac2