0009555: Vanilla game simply will not start on MacOS ElCapitan

Notes
(0034636) Detros (manager) 2016-02-11 02:17	Maybe try to check 0007389, "freetype missing on OS X; causes crashes when entering fullscreen and/or starting DF" and it's connected reports. Also, when updating versions you have created a new folder, haven't you? Because overwriting some old raws with new ones can lead to just any wild behaviour.

(0034660) jeturcotte (reporter) 2016-02-14 10:48	Sorry; On the latter matter, as indicated in the description, this is stark naked pure vanilla. No modifications whatsoever. Even just one second after download to entire new df folder, it fails to start. And this wasn't the case on the immediately previous version .05; and no changes have occurred on my system between the two. Took a quick vid of my experience: https://youtu.be/tNUtJWWqlEw [^] ... and, again, the only error mentioned in the logs (should'a taped that, I guess) is: Unrecognized Announcement Token: TRAVEL_ADVISORY

(0034679) jeturcotte (reporter) 2016-02-16 03:27	update; after a question from tarn, I checked, and this problem DOES exist for vanilla .05 as well... there's something about the init files that has ceased to be compatible with modern osx, or vice versa. When I drop the inits (and corresponding art files) that I've been using for so long back in, poof... .06 works fine. In fact, yeah... on a hunch I tried something, since this used to be an annoyance in the past and I always just do immediately whenever upgrading to a new version of DF. [PRINT_MODE:2D] It used to be this would cause the screen to be really small and inhabit a 1/4 quadrant in the upper left corner of the total DF window... so I did some reading and, ages ago, set it to [PRINT_MODE:STANDARD] instead... and have been habitually leaving it like that ever since. Now, this is the difference between it starting up and not starting up, instead. Not sure what that means internally.

(0034978) lethosor (manager) 2016-04-04 13:41 edited on: 2016-04-04 13:42	Sounds like another duplicate of 0002624. Updating SDL should do the trick if you really want to use 2D for some reason.

Issue History
Date Modified	Username	Field	Change
2016-02-10 19:31	jeturcotte	New Issue
2016-02-11 02:17	Detros	Note Added: 0034636
2016-02-14 10:48	jeturcotte	Note Added: 0034660
2016-02-16 03:27	jeturcotte	Note Added: 0034679
2016-04-04 13:41	lethosor	Note Added: 0034978
2016-04-04 13:41	lethosor	Relationship added	duplicate of 0002624
2016-04-04 13:41	lethosor	Status	new => resolved
2016-04-04 13:41	lethosor	Resolution	open => duplicate
2016-04-04 13:41	lethosor	Assigned To	=> lethosor
2016-04-04 13:42	lethosor	Note Edited: 0034978	View Revisions