Page 1 of 1

[15.x] Crash during loading on macOS

Posted: Mon May 01, 2017 10:25 am
by nymfact
Hello.

The game crashes while loading on all 0.15.x versions. 0.14 stable works fine.
Similar to this issue: viewtopic.php?f=7&t=45772&p=263175
It starts loading, gets to ~40% and "Cropping Bitmaps ...", then crashes and generates a log.
I tried with --max-texture-size 4096, 2048 and 1024, still crashes at the same point, but as you can see from the logs I attached, it creates more "atlas bitmap" before crashing than without the argument.

Edit: downloaded the release from the website to test if it was related to Steam, but still the same problem.

Re: [15.x] Crash during loading on macOS

Posted: Sat May 27, 2017 10:39 pm
by posila
Hi, we have enabled some more logging in graphics library we use in 0.15.13. Could you please post log from the latest experimental version?

Re: [15.x] Crash during loading on macOS

Posted: Sat Jun 03, 2017 9:09 pm
by knutaldrin
I have exactly the same bug, posting my log from 15.18.

Re: [15.x] Crash during loading on macOS

Posted: Mon Jun 05, 2017 10:42 am
by knutaldrin
Hi.

This seems to be caused by a config settings from 0.14 saying "video-memory-usage=high". Changing it to "medium" fixed the issue.
Apparently, the game seems to not check how much memory is available on the machine, and thus crashes.

Re: [15.x] Crash during loading on macOS

Posted: Fri Jun 23, 2017 11:43 pm
by dgw
Yep, I reported this upon first upgrading from 0.14 to 0.15 on my MacBook Pro and manually editing the config file to use less video memory fixed it. viewtopic.php?f=23&t=48397

Re: [15.x] Crash during loading on macOS

Posted: Mon Jun 26, 2017 7:22 pm
by Rseding91
We attempt to detect video memory but some graphics cards (notably ones on Mac OSs) don't give useful numbers and or crash instead of returning failure when trying to create the atlas images.

It's a known problem that we hope will be addressed by updating the game to use newer versions of Open GL (on non-windows) and DirectX (on windows).

Until then setting the video memory usage to a lower value is the official way of fixing it.