Larian Studios
Posted By: BugMeNot Not working with Yosemite - 18/10/14 09:51 PM
Upgraded to Yosemite and it's not loading at all for me. The preload screen comes up with the Divinity logo and hangs there for a few minutes then goes away.

Also, I can't explain how frustrating it is that:

1. You don't have support for an operating system that ought to have been available for you to test before it went public.

2. Your stinking forums don't even allow me to sign up to create an account so I had to go to bugmenot.com to get one.
Posted By: Raze Re: Not working with Yosemite - 19/10/14 03:32 AM

The game should work with Yosemite. A couple people have reported issues with the game after upgrading from Mavericks, though.

Work on officially supporting Yosemite started on or before the gold master release, and those involved were using the betas before then.

One person reported an issue recently creating an account with Chrome or Safari. If that is the case for you, try a different browser, if available, or email me (raze@larian.com, or the support address below) with your desired user name and I can set up an account for you with a temporary password (you would be asked to change it when first logging in).


Please email supportdos@larian.com, with a description of the problem and your system specs. I'm not sure if Yosemite moved anything around, but in Mavericks you could use 'system report' from the 'about this mac' apple menu item or the 'system information' app (utilities folder).

Also, please perform the following steps and include that information:

1. Verify your Steam game cache (if applicable)
2. Launch Activity Monitor
3. Start Game and get into a freeze state
4. Now Alt-Tab back to Desktop and check Activity Monitor. What do you see? How much CPU does the game consume?
5. Double click on the Divinity - Original Sin process and press 'Sample' button. Wait until Sampler is finished
6. Save sample output using 'Save' button
Posted By: jpfranco Re: Not working with Yosemite - 19/10/14 10:15 PM
Same issue here. Upgraded from Mavericks and now I get the spinning beach ball of death on the game menu screen as soon as I hover over any of the buttons. At this point there is no way to click on any of the buttons so I just end up force quitting the app.

I verified the steam cache and found no issues. These are my system specs:
[code]
Model Name: MacBook Pro
Model Identifier: MacBookPro6,2
Processor Name: Intel Core i5
Processor Speed: 2.4 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 3 MB
Memory: 8 GB
Processor Interconnect Speed: 4.8 GT/s
Boot ROM Version: MBP61.0057.B0F
SMC Version (system): 1.58f17
Serial Number (system): W8016351AGU
Hardware UUID: 80B8AF39-374E-59A8-8BC9-49EFE96CBA12
Sudden Motion Sensor:
State: Enabled
[/code]

My video card is the following: NVIDIA GeForce GT 330M 256 MB (Which, by the way, crashes like crazy on Win 8/bootcamp. The card is known to be defective, but DOS is the only game I've tried that actually crashes the display driver while playing, so if you could manage to get a try/catch in there somewhere I'd be very grateful :hahaha:)

Also, I checked the process on activity monitor and the game seems to be using 100%. This is the output from the sampler:

[code]Sampling process 825 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling Divinity - Original Sin (pid 825) every 1 millisecond
Process: Divinity - Original Sin [825]
Path: /Users/jp/Library/Application Support/Steam/SteamApps/common/Divinity - Original Sin/Divinity - Original Sin.app/Contents/MacOS/Divinity - Original Sin
Load Address: 0x1000
Identifier: com.larian.dos
Version: 1.0.177.0 (1.0.177.0)
Code Type: X86
Parent Process: ??? [1]

Date/Time: 2014-10-19 14:58:04.546 -0700
OS Version: Mac OS X 10.10 (14A389)
Report Version: 7
Analysis Tool: /usr/bin/sample
----

Call graph:
2127 Thread_39552 DispatchQueue_1: com.apple.main-thread (serial)
+ 2127 start (in libdyld.dylib) + 1 [0x935276d9]
+ 2127 NSApplicationMain (in AppKit) + 2082 [0x987ef4d0]
+ 2127 -[NSApplication run] (in AppKit) + 907 [0x98805f6c]
+ 2127 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit) + 186 [0x988137a1]
+ 2127 _DPSNextEvent (in AppKit) + 2663 [0x988146e2]
+ 2127 AEProcessAppleEvent (in HIToolbox) + 55 [0x99b014b1]
+ 2127 aeProcessAppleEvent (in AE) + 313 [0x9871692a]
+ 2127 dispatchEventAndSendReply(AEDesc const*, AEDesc*) (in AE) + 44 [0x98716a37]
+ 2127 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) (in AE) + 583 [0x9874a8c2]
+ 2127 _NSAppleEventManagerGenericHandler (in Foundation) + 211 [0x95e23264]
+ 2127 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] (in Foundation) + 451 [0x95e2346f]
+ 2127 __76-[NSAppleEventManager setEventHandler:andSelector:forEventClass:andEventID:]_block_invoke (in Foundation) + 118 [0x95e23937]
+ 2127 -[NSObject performSelector:withObject:withObject:] (in libobjc.A.dylib) + 84 [0x949cd119]
+ 2127 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] (in AppKit) + 277 [0x988180ca]
+ 2127 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] (in AppKit) + 827 [0x988187fd]
+ 2127 -[NSApplication _sendFinishLaunchingNotification] (in AppKit) + 239 [0x9881c048]
+ 2127 -[NSApplication _postDidFinishNotification] (in AppKit) + 365 [0x9881c358]
+ 2127 -[NSNotificationCenter postNotificationName:object:userInfo:] (in Foundation) + 92 [0x95e023c4]
+ 2127 _CFXNotificationPost (in CoreFoundation) + 3713 [0x917fb3f1]
+ 2127 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ (in CoreFoundation) + 20 [0x9191a6e4]
+ 2127 __57-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke (in Foundation) + 50 [0x95e144a3]
+ 2127 ??? (in Divinity - Original Sin) load address 0x1000 + 0x3359 [0x4359]
+ 2127 BaseApp::OnIdle() (in libGameEngine.dylib) + 274 [0xce9012]
+ 2127 BaseApp::MakeFrame() (in libGameEngine.dylib) + 81 [0xce9f31]
+ 2127 BaseApp::DrawFrame(rf::Renderer*) (in libGameEngine.dylib) + 40 [0xce9c08]
+ 2127 rf::RenderFrame::Draw() (in libRenderFramework.dylib) + 60 [0xb8237c]
+ 2127 ls::ShadowStage::Do() (in libGameEngine.dylib) + 1632 [0xbeec10]
+ 2127 ??? (in Divinity - Original Sin) load address 0x1000 + 0xcc098 [0xcd098]
+ 2127 glClear (in libGL.dylib) + 28 [0x9a3c2e97]
+ 2127 glClear_Exec (in GLEngine) + 208 [0x945d6b9b]
+ 2127 gleUpdateDrawFramebufferState (in GLEngine) + 553 [0x946cc4b0]
+ 2127 gldUpdateDrawFramebuffer (in libGPUSupport.dylib) + 158 [0xef381df]
+ 2127 gldReadTextureData (in GeForceTeslaGLDriver) + 904614 [0x4832208c]
+ 2127 gldReadTextureData (in GeForceTeslaGLDriver) + 603880 [0x482d89ce]
+ 2127 gldReadTextureData (in GeForceTeslaGLDriver) + 601428 [0x482d803a]
+ 2127 gldReadTextureData (in GeForceTeslaGLDriver) + 673792,673772,... [0x482e9ae6,0x482e9ad2,...]
2127 Thread_39563 DispatchQueue_2: com.apple.libdispatch-manager (serial)
+ 2127 _dispatch_mgr_thread (in libdispatch.dylib) + 52 [0x932373a2]
+ 2127 _dispatch_mgr_invoke (in libdispatch.dylib) + 245 [0x9323773f]
+ 2127 kevent64 (in libsystem_kernel.dylib) + 10 [0x900228d2]
2127 Thread_39584
+ 2127 thread_start (in libsystem_pthread.dylib) + 34 [0x962f0f0e]
+ 2127 _pthread_start (in libsystem_pthread.dylib) + 162 [0x962f2e45]
+ 2127 _pthread_body (in libsystem_pthread.dylib) + 138 [0x962f2ecf]
+ 2127 _NSEventThread (in AppKit) + 283 [0x98987874]
+ 2127 CFRunLoopRunInMode (in CoreFoundation) + 123 [0x918624fb]
+ 2127 CFRunLoopRunSpecific (in CoreFoundation) + 390 [0x91862696]
+ 2127 __CFRunLoopRun (in CoreFoundation) + 1529 [0x91862ef9]
+ 2127 __CFRunLoopServiceMachPort (in CoreFoundation) + 214 [0x91863ae6]
+ 2127 mach_msg (in libsystem_kernel.dylib) + 68 [0x9001aad0]
+ 2127 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x9001ba2e]
2127 Thread_39585
+ 2127 thread_start (in libsystem_pthread.dylib) + 34 [0x962f0f0e]
+ 2127 _pthread_start (in libsystem_pthread.dylib) + 162 [0x962f2e45]
+ 2127 _pthread_body (in libsystem_pthread.dylib) + 138 [0x962f2ecf]
+ 2127 mt_ThreadedMTEntry (in MultitouchSupport) + 76 [0x993e130b]
+ 2127 CFRunLoopRun (in CoreFoundation) + 129 [0x91925071]
+ 2127 CFRunLoopRunSpecific (in CoreFoundation) + 390 [0x91862696]
+ 2127 __CFRunLoopRun (in CoreFoundation) + 1529 [0x91862ef9]
+ 2127 __CFRunLoopServiceMachPort (in CoreFoundation) + 214 [0x91863ae6]
+ 2127 mach_msg (in libsystem_kernel.dylib) + 68 [0x9001aad0]
+ 2127 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x9001ba2e]
2127 Thread_39586: IOPollingHelperThread
+ 2127 thread_start (in libsystem_pthread.dylib) + 34 [0x962f0f0e]
+ 2127 _pthread_start (in libsystem_pthread.dylib) + 162 [0x962f2e45]
+ 2127 _pthread_body (in libsystem_pthread.dylib) + 138 [0x962f2ecf]
+ 2127 SteamThreadTools::CThread::ThreadProc(void*) (in libtier0_s.dylib) + 222 [0xe8430c4]
+ 2127 CatchAndWriteMiniDumpForVoidPtrFn (in libtier0_s.dylib) + 35 [0xe83e752]
+ 2127 CatchAndWriteMiniDumpExForVoidPtrFn (in libtier0_s.dylib) + 87 [0xe83e729]
+ 2127 CatchAndWriteMiniDump_Impl(CatchAndWriteContext_t&) (in libtier0_s.dylib) + 214 [0xe83e642]
+ 2127 CatchAndWriteContext_t::Invoke() (in libtier0_s.dylib) + 159 [0xe83ec29]
+ 2127 SteamThreadTools::CThread::ThreadExceptionWrapper(void*) (in libtier0_s.dylib) + 16 [0xe843150]
+ 2127 OSXHelpers::CIOPollingHelper::Run() (in steamclient.dylib) + 41 [0xf8e9181]
+ 2127 CatchAndWriteMiniDumpForVoidPtrFn (in libtier0_s.dylib) + 35 [0xe83e752]
+ 2127 CatchAndWriteMiniDumpExForVoidPtrFn (in libtier0_s.dylib) + 87 [0xe83e729]
+ 2127 CatchAndWriteMiniDump_Impl(CatchAndWriteContext_t&) (in libtier0_s.dylib) + 214 [0xe83e642]
+ 2127 CatchAndWriteContext_t::Invoke() (in libtier0_s.dylib) + 159 [0xe83ec29]
+ 2127 OSXHelpers::CIOPollingHelper::RealRun() (in steamclient.dylib) + 277 [0xf8e92a7]
+ 2127 kevent (in libsystem_kernel.dylib) + 10 [0x900228b6]
2127 Thread_39588: TextureStreamerThread
+ 2127 thread_start (in libsystem_pthread.dylib) + 34 [0x962f0f0e]
+ 2127 _pthread_start (in libsystem_pthread.dylib) + 162 [0x962f2e45]
+ 2127 _pthread_body (in libsystem_pthread.dylib) + 138 [0x962f2ecf]
+ 2127 ??? (in libCoreLib.dylib) load address 0xdd8000 + 0xae105 [0xe86105]
+ 2127 ls::ThreadBridgeEventWorker::DoWork() (in libCoreLib.dylib) + 479 [0xdec32f]
+ 2127 ls::ThreadEvent::Wait(unsigned int) (in libCoreLib.dylib) + 189 [0xe76b2d]
+ 2127 semaphore_timedwait_trap (in libsystem_kernel.dylib) + 10 [0x9001ba82]
2127 Thread_39589: DeviceDiscovery
+ 2127 thread_start (in libsystem_pthread.dylib) + 34 [0x962f0f0e]
+ 2127 _pthread_start (in libsystem_pthread.dylib) + 162 [0x962f2e45]
+ 2127 _pthread_body (in libsystem_pthread.dylib) + 138 [0x962f2ecf]
+ 2127 ??? (in libCoreLib.dylib) load address 0xdd8000 + 0xae105 [0xe86105]
+ 2127 ??? (in Divinity - Original Sin) load address 0x1000 + 0x674be1 [0x675be1]
+ 2127 ls::ThreadEvent::Wait(unsigned int) (in libCoreLib.dylib) + 189 [0xe76b2d]
+ 2127 semaphore_timedwait_trap (in libsystem_kernel.dylib) + 10 [0x9001ba82]
2127 Thread_39592
+ 2127 thread_start (in libsystem_pthread.dylib) + 34 [0x962f0f0e]
+ 2127 _pthread_start (in libsystem_pthread.dylib) + 162 [0x962f2e45]
+ 2127 _pthread_body (in libsystem_pthread.dylib) + 138 [0x962f2ecf]
+ 2127 ??? (in Divinity - Original Sin) load address 0x1000 + 0xb435c [0xb535c]
+ 2127 pthread_cond_wait$UNIX2003 (in libsystem_pthread.dylib) + 71 [0x962f71d1]
+ 2127 _pthread_cond_wait (in libsystem_pthread.dylib) + 726 [0x962f3b06]
+ 2127 __psynch_cvwait (in libsystem_kernel.dylib) + 10 [0x90021516]
2127 Thread_39593
+ 2127 thread_start (in libsystem_pthread.dylib) + 34 [0x962f0f0e]
+ 2127 _pthread_start (in libsystem_pthread.dylib) + 162 [0x962f2e45]
+ 2127 _pthread_body (in libsystem_pthread.dylib) + 138 [0x962f2ecf]
+ 2127 ??? (in Divinity - Original Sin) load address 0x1000 + 0x51ee3 [0x52ee3]
+ 2127 semaphore_wait_trap (in libsystem_kernel.dylib) + 10 [0x9001ba6a]
2127 Thread_39611
+ 2127 thread_start (in libsystem_pthread.dylib) + 34 [0x962f0f0e]
+ 2127 _pthread_start (in libsystem_pthread.dylib) + 162 [0x962f2e45]
+ 2127 _pthread_body (in libsystem_pthread.dylib) + 138 [0x962f2ecf]
+ 1992 ??? (in Divinity - Original Sin) load address 0x1000 + 0x8c964 [0x8d964]
+ ! 1992 semaphore_wait_trap (in libsystem_kernel.dylib) + 10 [0x9001ba6a]
+ 134 ??? (in Divinity - Original Sin) load address 0x1000 + 0x8c95a [0x8d95a]
+ ! 132 ??? (in Divinity - Original Sin) load address 0x1000 + 0x4c253 [0x4d253]
+ ! : 132 ??? (in Divinity - Original Sin) load address 0x1000 + 0x3ce66 [0x3de66]
+ ! : 132 ??? (in Divinity - Original Sin) load address 0x1000 + 0x900b6 [0x910b6]
+ ! : 88 ??? (in Divinity - Original Sin) load address 0x1000 + 0x90194 [0x91194]
+ ! : | 84 ??? (in Divinity - Original Sin) load address 0x1000 + 0x8fbfd [0x90bfd]
+ ! : | + 62 ??? (in Divinity - Original Sin) load address 0x1000 + 0xb9fa9 [0xbafa9]
+ ! : | + ! 55 ??? (in Divinity - Original Sin) load address 0x1000 + 0xbfe1b [0xc0e1b]
+ ! : | + ! : 55 ??? (in Divinity - Original Sin) load address 0x1000 + 0xbe898 [0xbf898]
[/code]
Posted By: Raze Re: Not working with Yosemite - 20/10/14 03:04 AM

Thanks. BTW, you can now use UBBCode; there are restrictions on new accounts to discourage spam.


To the OP;
If you were getting a 'fatal error' from the forum after clicking on submit when trying to register, try again; it should work now.
Posted By: Stauff1138 Re: Not working with Yosemite - 20/10/14 07:59 AM
Dear Yosemite users

Yes, we're aware of this issue and yes, we've been testing this stuff using Yosemite beta. But we've never seen such issues.. It's an Apple bug straight and clear. Right now I don't have anything encouraging for you right away but I will keep you posted. Our goal is definitely to get D:OS working fine on Yosemite, so please don't panic, we will get to it.

Update:

Affected lock-up systems

GeForce 9400
GeForce 320M 256 MB of DDR3 SDRAM shared with main memory
GeForce 8600M GT
GeForce GT 330M

All those systems suffer from same Apple bug. We will get the hardware and will look at that.
Posted By: Stauff1138 Re: Not working with Yosemite - 21/10/14 12:31 PM
The issue has been addressed. Game will be working fine with the next update.
Posted By: jpfranco Re: Not working with Yosemite - 22/10/14 03:22 AM
Awesome. I'll wait for the update then, thanks.
Posted By: nerakhon Re: Not working with Yosemite - 22/10/14 03:13 PM
Hi, this is great news as I am under exactly the same trouble. Any ETA on the patch release? I mean rough like next month, next week, tomorrow :D ... thanks a lot!
Posted By: Raze Re: Not working with Yosemite - 23/10/14 01:01 AM

AFAIK probably next week.
Posted By: nerakhon Re: Not working with Yosemite - 23/10/14 10:19 AM
Thanks for the info, so I'll look forward to getting back to playing.
Posted By: RoxPonys Re: Not working with Yosemite - 11/11/14 08:33 PM
Not working for me :'(.
I was on Mavericks and i updated a few weeks ago, but i got Divinity yesterday. I downloaded it and it doesn't work...
I mean i see the logo, then it's loading and it freeze to the menu like this : [url=http://uprapide.com/image/876797-screen-shot-2014-11-11-at-21][img]http://uprapide.com/images/invite/screen-shot-2014-11-11-at-21.png[/img][/url] (I did not change the opacity, it's what it's looks like, and strange, the preview show the picture but not the post.) And the music continue. So the only thing i can do is force quit it because it doesn't respond.
I really hope you can help me with it.

Hardware Overview:

Model Name: MacBook Pro
Model Identifier: MacBookPro5,3
Processor Name: Intel Core 2 Duo
Processor Speed: 2,8 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 6 MB
Memory: 8 GB
Bus Speed: 1,07 GHz
Boot ROM Version: MBP53.00AC.B03
SMC Version (system): 1.48f2

If the image does not appear, copy this : http://uprapide.com/image/876797-screen-shot-2014-11-11-at-21
Posted By: Raze Re: Not working with Yosemite - 11/11/14 08:52 PM

The GeForce 9600M GT is known to have this problem, and will be included in the list of cards that need the fix in a future game update (along with the GT 120).

You should be able to get the game working by using the following command in the Terminal:

defaults write com.larian.dos ShaderBasedClear -bool true


BTW, UBBCode is disabled for new accounts, to try to discourage spam (no clickable links). You can now use UBBCode, and will not need to use captchas to post, etc.
Posted By: RoxPonys Re: Not working with Yosemite - 11/11/14 09:02 PM
Ok thx, im checking if it works.
Posted By: RoxPonys Re: Not working with Yosemite - 11/11/14 09:03 PM
Wow Great! Lagy but working. Thx
Posted By: Glorfy Re: Not working with Yosemite - 17/12/14 05:11 PM
Hello!

Have the same issue with preload screen.

Here is my configuration:

OS X 10.10.1 (14B25)
Model Name: iMac
Model Identifier: iMac14,2
Processor Name: Intel Core i5
Processor Speed: 3,2 ГГц
Memory: 8 GB

NVIDIA GeForce GT 755M

Have to use bootcamp :(
Posted By: Raze Re: Not working with Yosemite - 17/12/14 09:23 PM

Did you try the defaults command above in the Terminal?
Posted By: Stauff1138 Re: Not working with Yosemite - 18/12/14 07:38 AM
NVIDIA GeForce GT 755M?? It's a recent video card. There should be zero problems with it. Can you please elaborate on the issue you're experiencing.
Posted By: ElectricCraze Re: Not working with Yosemite - 18/04/15 06:35 PM
Hey I was wondering if I could run the game.
I am running Yosemite 10.10 on a macbook air 11 inch mid 2013.
I have a 1/3 Ghz Intel Core i5
Memory is 4gb 1600 MHz DDR3
Startup disk is Macintosh HD
Graphics: Intel HD Graphics 5000 1536 MB

I am about to buy the game on GOG.com.
Of course, there is a 30 day refund time, but just wondering.
Posted By: Raze Re: Not working with Yosemite - 18/04/15 09:22 PM

The minimum required CPU is a 2.4GHz dual core, though I have seen reports of the game running on CPUs as low as 2.0GHz. One person reported crashes on startup with a 1.7GHz CPU, but in that case the GPU was also below spec (and a PC). Stauff1138 may have an idea if or how well it may run.

The next update should include some multithreading optimizations to take better advantage of multi-core CPUs, but I don't know if that would be enough to help with a 1.3GHz CPU.
Posted By: ElectricCraze Re: Not working with Yosemite - 19/04/15 05:37 AM
AWwwwhhh maaan frown
Posted By: ElectricCraze Re: Not working with Yosemite - 19/04/15 05:57 AM
After some research I discovered that my laptop is a piece of worthless s@#$. Well, so long gaming community. Nice game though, it looked really cool! And thanks for the help!
Posted By: ElectricCraze Re: Not working with Yosemite - 19/04/15 06:19 AM
Did some research, found out that I have been playing minimum 2.5GHz Duo Core (e.g Gear Up, Star Trek Online, Tropico 5) games on my laptop for ages. And they seemed to run pretty smoothly.

But I do need your expert opinion.
Posted By: Raze Re: Not working with Yosemite - 19/04/15 06:54 AM

I'll check with Stauff1138...
Posted By: ElectricCraze Re: Not working with Yosemite - 19/04/15 10:34 AM
Found out that the i5 1.3 core is about as good as the 2.5GHz. A little less.
1298 to 1391
Posted By: Raze Re: Not working with Yosemite - 19/04/15 06:38 PM

It would depend on how mutithreaded the application was, as to whether or how much more cores would compensate for a lower speed.
Posted By: ElectricCraze Re: Not working with Yosemite - 19/04/15 06:39 PM
How multithreaded is Original Sin then?
Posted By: ElectricCraze Re: Not working with Yosemite - 20/04/15 12:36 PM
Welp, still gonna buy it on steam. Otherwise I will just have to wait till the next update.
Posted By: ElectricCraze Re: Not working with Yosemite - 20/04/15 07:54 PM
Completely working! No long loading screens, and awesome gameplay! Really thanks for all the the help and support! You really did a great job! I will recommend it to all of my friends!
Posted By: Raze Re: Not working with Yosemite - 20/04/15 08:06 PM

Thanks for the update. At least if the GPU is above minimum it seems the game doesn't need much in terms of CPU.
© Larian Studios forums