Game won't launch (OSX)
nerdcore9
Member Posts: 7
I've put many hours in to the game and out the blue it will not launch. I have always used steam without problems. Now the game seems to launch for a moment and then shuts down. I got a few error messages when it started, but cannot reproduce them.
Things I have tried:
reinstall
verify game files using steam
Renaming the folder in Documents
I could really use some help. It's been quite frustrating because I cannot seem to create an account for Beamdog's support system.
Things I have tried:
reinstall
verify game files using steam
Renaming the folder in Documents
I could really use some help. It's been quite frustrating because I cannot seem to create an account for Beamdog's support system.
0
Comments
Here is part of one of the error messages I grabbed.
Path: /Users/USER/Library/Application Support/Steam/*/Baldur's Gate - Enhanced Edition.app/Contents/MacOS/Baldur's Gate - Enhanced Edition
Identifier: com.beamdog.baldursgateenhancededition
Version: 2.3.67.3 (2036703)
Code Type: X86-64 (Native)
Parent Process: launchd [204]
Responsible: Baldur's Gate - Enhanced Edition [460]
User ID: 502
Date/Time: 2017-01-20 21:36:11.144 -0500
OS Version: Mac OS X 10.9.5 (13F1911)
Report Version: 11
Anonymous UUID: 78347491-6659-B493-4521-26FA89D9560C
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.beamdog.baldursgateenhancededition 0x000000010c8af1e8 __ARCLite__load() + 2
1 libobjc.A.dylib 0x00007fff937cc500 load_images + 78
2 dyld 0x00007fff676b2f53 dyld::notifySingle(dyld_image_states, ImageLoader const*) + 249
3 dyld 0x00007fff676bfa8f ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 289
4 dyld 0x00007fff676bf936 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 54
5 dyld 0x00007fff676b31da dyld::initializeMainExecutable() + 189
6 dyld 0x00007fff676b64ca dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 2269
7 dyld 0x00007fff676b227b dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 477
8 dyld 0x00007fff676b205e _dyld_start + 54
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x00007fff793d3908 rbx: 0x00006000001fd608 rcx: 0x00007f956180c040 rdx: 0x00000000a1a1a1a1
rdi: 0x000000010cb74808 rsi: 0x00007fff8b664abf rbp: 0x00007fff539b1200 rsp: 0x00007fff539b11a8
r8: 0x0000000000000044 r9: 0x00007fff539b1000 r10: 0x0000600000074680 r11: 0x00007fff793ce810
r12: 0x0000000000000001 r13: 0x000000010c8af1e6 r14: 0x00006000001fd600 r15: 0x000000010cb74808
rip: 0x000000010c8af1e8 rfl: 0x0000000000010246 cr2: 0x000000010c8af1e6
Logical CPU: 1
Error Code: 0x00000000
Trap Number: 6
Aaron
FWIW I am also on OSX 10.9.5
http://steamcommunity.com/discussions/forum/2/143388132204079990/
My suggestion would be to find the folder the game is installed in and then cut and paste it somewhere else on your computer. Then run the game.
I'm running OSX 10.8.5, and everything appeared to be working properly until my Steam client automatically updated on Friday, the 20th.
At this stage the only thing I can think of would be to sign up for the Steam beta (Settings -> Account -> Beta participation). Hopefully Steam can get a fix out quickly.
If I manually go to the directory where the actual application is (/Applications/Baldur's Gate - Enhanced Edition/Game Data/00777 in my case), I can try to start the application by hand.
This gives me an error about Rosetta being required.
However, if I delve even further in (/Applications/Baldur's Gate - Enhanced Edition/Game Data/00777/Baldur's Gate - Enhanced Edition.app/Contents/MacOS), I can find executable Baldur's Gate - Enhanced Edition which I can launch. This has the downside of having totally wrong resolution and what not.
So I think Beamdog has made some mistake in packaging the application. It should be easy to fix if this just got to their attention.