Posted April 10, 2018
DISCLAIMER: The text below was copy-pasted from my correspondence with GOG.com support. They offered me a refund (which I declined since I play this game on my other OS X devices) then suggested that I reach out for the devs on my own, since the support agents aren't allowed "to act as middlemen between me and the devs"
My game version is v1.06. I'm on OS X 10.11.6 and I'm using a third-party graphics card (Nvidia GeForce GTX 750Ti) with Nvidia's so-called web drivers (no Apple drivers are available for this graphics card) After launch, the game spawns a full-screen blank window and all I'm getting is an endlessly spinning beach ball of death. The game process eats up 100% CPU usage and becomes marked as "unresponsive" in the process explorer app. It doesn't even create a folder in ˜/Libraries/Application Support/" like most Unity games do, so I can't provide you with an output log. When I manually launch the main game binary (WTWTLW.app/Contents/MacOS/WTWTLW) from within the .app with a Terminal command, the game prints virtually no output to the console except for a "SIGTERM 9 KILLED" message when I kill the process. There's a thread on Steam forums regarding a similar issue on Windows, but OS X doesn't have that option that supposedly fixes it.
https://steamcommunity.com/app/447120/discussions/0/1694917906653075640/
I also tried using the "opensnoop" console utility to see which files the game process tries to access, create or modify upon launch. It appears that it does not read or write to ~/Libraries/Application Support but does progress until it attempts to play the opening movie.
My own research led me to the conclusion that the game uses a very wacky method for modesetting -- should it default to window mode and minimum possible resolution upon its first launch, this could possibly resolve the issue.
I still can play this game on my portable devices running OS X and I have zero problems with Intel's integrated graphics like HD4000 or HD4600. I just can't run it on my main computer, which is very frustrating.
Nvidia GPU families like Maxwell, Kepler and Pascal are not supported by OS X out of the box, but Nvidia does release their own custom driver packages with a ripe and full-fledged support for these GPUs.
Where the Water Tastes Like Wine is my first game out of a multitude I played on my main computer that failed to start. Lots of other Unity-based games work flawlessly, as well as graphics-intensive apps like Everspace or Warhammer Total War. So it's not a graphics driver issue -- upon running into this problem with WTWTLW, I checked twice that I could run some demanding games with my current setup. I did some test runs both with Metal and OpenGL-reliant apps.
I have my own reasons to abstain from upgrading to 10.12.6 or 10.13.4 but if someone (like one of the devs) confirms this can resolve issue, I'll upgrade.
My game version is v1.06. I'm on OS X 10.11.6 and I'm using a third-party graphics card (Nvidia GeForce GTX 750Ti) with Nvidia's so-called web drivers (no Apple drivers are available for this graphics card) After launch, the game spawns a full-screen blank window and all I'm getting is an endlessly spinning beach ball of death. The game process eats up 100% CPU usage and becomes marked as "unresponsive" in the process explorer app. It doesn't even create a folder in ˜/Libraries/Application Support/" like most Unity games do, so I can't provide you with an output log. When I manually launch the main game binary (WTWTLW.app/Contents/MacOS/WTWTLW) from within the .app with a Terminal command, the game prints virtually no output to the console except for a "SIGTERM 9 KILLED" message when I kill the process. There's a thread on Steam forums regarding a similar issue on Windows, but OS X doesn't have that option that supposedly fixes it.
https://steamcommunity.com/app/447120/discussions/0/1694917906653075640/
I also tried using the "opensnoop" console utility to see which files the game process tries to access, create or modify upon launch. It appears that it does not read or write to ~/Libraries/Application Support but does progress until it attempts to play the opening movie.
My own research led me to the conclusion that the game uses a very wacky method for modesetting -- should it default to window mode and minimum possible resolution upon its first launch, this could possibly resolve the issue.
I still can play this game on my portable devices running OS X and I have zero problems with Intel's integrated graphics like HD4000 or HD4600. I just can't run it on my main computer, which is very frustrating.
Nvidia GPU families like Maxwell, Kepler and Pascal are not supported by OS X out of the box, but Nvidia does release their own custom driver packages with a ripe and full-fledged support for these GPUs.
Where the Water Tastes Like Wine is my first game out of a multitude I played on my main computer that failed to start. Lots of other Unity-based games work flawlessly, as well as graphics-intensive apps like Everspace or Warhammer Total War. So it's not a graphics driver issue -- upon running into this problem with WTWTLW, I checked twice that I could run some demanding games with my current setup. I did some test runs both with Metal and OpenGL-reliant apps.
I have my own reasons to abstain from upgrading to 10.12.6 or 10.13.4 but if someone (like one of the devs) confirms this can resolve issue, I'll upgrade.
