DiskDoctor

Another with the same issue here. Mac Pro (tower), single 2560x1440 monitor. Can't use CMD+F to get out of fullscreen - it does flicker when I use that command and I can see the game when it flickers, but then goes black again. I had a similar issue with Cities: Skylines, another Unity game, last week. I was able to get around it there by using the CMD+F shortcut > setting my screen resolution in the game options while in windowed mode (which then would cause the black screen) > quitting the game with CMD + Q > when I relaunched it would load at the correct resolution I set within the game options. If I want to play in windowed mode I basically have to go through all of that in reverse. console.log output - The repeating capture/release is probably me hitting CMD+F. 3/26/15 6:25:19.823 PM PillarsOfEternity[11615]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.2 instead of 10.10.2. Use NSProcessInfo's operatingSystemVersion property to get correct system version number. Call location: 3/26/15 6:25:19.823 PM PillarsOfEternity[11615]: 0 CarbonCore 0x00007fff97969d9b ___Gestalt_SystemVersion_block_invoke + 113 3/26/15 6:25:19.823 PM PillarsOfEternity[11615]: 1 libdispatch.dylib 0x00007fff890f9c13 _dispatch_client_callout + 8 3/26/15 6:25:19.823 PM PillarsOfEternity[11615]: 2 libdispatch.dylib 0x00007fff890f9b26 dispatch_once_f + 117 3/26/15 6:25:19.823 PM PillarsOfEternity[11615]: 3 CarbonCore 0x00007fff979123ca _Gestalt_SystemVersion + 987 3/26/15 6:25:19.823 PM PillarsOfEternity[11615]: 4 CarbonCore 0x00007fff97911fb7 Gestalt + 144 3/26/15 6:25:19.823 PM PillarsOfEternity[11615]: 5 PillarsOfEternity 0x000000010072c4ad _ZN14AnimationEvent8TransferI17RemapPPtrTransferEEvRT_ + 952925 3/26/15 6:25:19.823 PM PillarsOfEternity[11615]: 6 PillarsOfEternity 0x0000000100722a1b _ZN14AnimationEvent8TransferI17RemapPPtrTransferEEvRT_ + 913355 3/26/15 6:25:23.441 PM WindowServer[240]: Display 0x1a49c438 captured by conn 0x29f23 3/26/15 6:25:28.134 PM WindowServer[240]: Display 0x1a49c438 released by conn 0x29f23 3/26/15 6:25:28.153 PM WindowServer[240]: Display 0x1a49c438 captured by conn 0x29f23 3/26/15 6:25:35.655 PM WindowServer[240]: Display 0x1a49c438 released by conn 0x29f23 3/26/15 6:25:35.677 PM WindowServer[240]: Display 0x1a49c438 captured by conn 0x29f23 3/26/15 6:25:35.968 PM WindowServer[240]: Display 0x1a49c438 released by conn 0x29f23 3/26/15 6:25:35.981 PM WindowServer[240]: Display 0x1a49c438 captured by conn 0x29f23 3/26/15 6:25:36.347 PM WindowServer[240]: Display 0x1a49c438 released by conn 0x29f23 3/26/15 6:25:36.360 PM WindowServer[240]: Display 0x1a49c438 captured by conn 0x29f23 3/26/15 6:25:36.649 PM WindowServer[240]: Display 0x1a49c438 released by conn 0x29f23 3/26/15 6:25:36.661 PM WindowServer[240]: Display 0x1a49c438 captured by conn 0x29f23 3/26/15 6:25:36.950 PM WindowServer[240]: Display 0x1a49c438 released by conn 0x29f23 3/26/15 6:25:36.962 PM WindowServer[240]: Display 0x1a49c438 captured by conn 0x29f23 3/26/15 6:25:37.253 PM WindowServer[240]: Display 0x1a49c438 released by conn 0x29f23 3/26/15 6:25:37.264 PM WindowServer[240]: Display 0x1a49c438 captured by conn 0x29f23 3/26/15 6:25:37.555 PM WindowServer[240]: Display 0x1a49c438 released by conn 0x29f23 3/26/15 6:25:37.569 PM WindowServer[240]: Display 0x1a49c438 captured by conn 0x29f23 3/26/15 6:25:38.824 PM WindowServer[240]: Display 0x1a49c438 released by conn 0x29f23 Unity > Player.log has a lot of this sort of thing in it: Switching to 2560x1440 fullscreen Could not find requested mode. (Filename: Line: 104) Switching to 2560 x1440 failed! Trying second best guess. Switching to 2048x1152 fullscreen Could not find requested mode. (Filename: Line: 104) Switching to 2560 x1440 failed! Trying second best guess. Switching to 1920x1080 fullscreen Could not find requested mode. (Filename: Line: 104) Switching to 2560 x1440 failed! Trying second best guess. Switching to 1600x1200 fullscreen Could not find requested mode.