Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0011680Dwarf FortressTechnical -- Generalpublic2021-01-26 16:442021-01-28 17:06
Assigned Tolethosor 
PlatformMacbook ProOSBig SurOS Version
Product Version0.47.04 
Target VersionFixed in Version 
Summary0011680: Game window is blank on macOS 11
DescriptionAs soon as I launch the game there are several error messages which can be resolved by giving permissions in the security and privacy section of system preferences. After attempting to launch DF several times it will eventually open the .exe, however the screen is completely white and the game is unviewable. I am able to hear music and even interact with the game (I can tell since pressing esc skips the opening cutscene and the music changes).
Steps To Reproduce1. Launch the df exec file.
2. Grant permissions and exceptions as needed in the security and privacy section of system preferences.
3. Eventually, the exec file will open the .exe.
4. Game audio will work and the game is seemingly able to be interacted with, however the no visual aspects of the game will load.
TagsNo tags attached.
Attached Files

- Relationships
related to 0006031confirmedFootkerchief Playing window is drawn in the top left corner of the application window (on Macbook Pro w/ Retina) 
related to 0010052acknowledgedlethosor DF uses 57% in PRINT_MODE:2D with 640x300 window, over 100% when maximized 
has duplicate 0011794resolvedlethosor DF launches to white screen on macOS 

-  Notes
Ziusudra (reporter)
2021-01-26 23:31 [^]

Specifically, "On macOS 11 (Big Sur) and above, if you see a blank white window when starting the game, you will need to change [PRINT_MODE:2D] to [PRINT_MODE:STANDARD] in init.txt."
lethosor (manager)
2021-01-28 17:06

I'm surprised that this wasn't reported on here already - thanks for the report!

As Ziusudra mentioned, changing the PRINT_MODE setting to STANDARD should fix this. 2D has had several issues on recent versions of macOS, like 0006031 and 0010052, so changing the default to STANDARD would fix all of those.

Implementation notes: STANDARD is currently the default on the parser side (i.e. it will parse unrecognized values like "PRINT_MODE:FOO" as "PRINT_MODE:STANDARD") but 2D is in the default init.txt. I'm not sure if other platforms have issues with STANDARD that would warrant different defaults - 0003480 is pretty old, for instance.

- Issue History
Date Modified Username Field Change
2021-01-26 16:44 C7703 New Issue
2021-01-26 18:01 C7703 Issue Monitored: C7703
2021-01-26 18:01 C7703 Issue End Monitor: C7703
2021-01-26 23:31 Ziusudra Note Added: 0040882
2021-01-28 15:38 lethosor Summary Game Is Unplayable => Game window is blank on macOS 11
2021-01-28 17:06 lethosor Note Added: 0040887
2021-01-28 17:06 lethosor Assigned To => lethosor
2021-01-28 17:06 lethosor Status new => confirmed
2021-01-28 17:06 lethosor Relationship added related to 0006031
2021-01-28 17:06 lethosor Relationship added related to 0010052
2021-08-11 12:15 lethosor Relationship added has duplicate 0011794

Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker