Opened 11 years ago

Closed 10 years ago

#2245 closed defect (fixed)

Render failure on Mac OS X 10.9

Reported by: Tom Brewe Owned by:
Priority: Must Have Milestone: Alpha 15
Component: Core engine Keywords: rendering mac mavericks
Cc: Patch:

Description (last modified by Tom Brewe)

I upgraded to the newest OS X. The Alpha 14 Build does run, I see the Start display and match-setup perfectly. But in the actual game all is black, besides territory borders. No units or terrain are rendered.

I am using a "Macbook Pro 5,1" with the NVIDIA GeForce 9400M.

Attachments (2)

Bildschirmfoto 2013-10-31 um 21.17.57.png (149.7 KB ) - added by Tom Brewe 11 years ago.
mainlog.html (64.4 KB ) - added by Tom Brewe 11 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 by Tom Brewe, 11 years ago

Description: modified (diff)

comment:2 by Tom Brewe, 11 years ago

Tried both graphic cards in the laptop (9400M and 9600 GT). Same problem for both. See screenshot.

comment:3 by Tom Brewe, 11 years ago

Ok further testing: On 10.8 I enabled several graphic settings in my local.cfg. I tried to turn them on/off individually and could identify smoothlos = true as the problem. Having all other whizzbang-graphics on, but smoothlos to false, no rendering problem occurs.

See especially lines 473 and 716ff.

Version 1, edited 11 years ago by Tom Brewe (previous) (next) (diff)

by Tom Brewe, 11 years ago

Attachment: mainlog.html added

comment:4 by wraitii, 10 years ago

Milestone: BacklogAlpha 16

comment:5 by historic_bruno, 10 years ago

Is this still broken in A15? There have been a few minor changes to the shaders and renderer since A14, not intending to fix this bug, but it's possible.

comment:6 by Echelon9, 10 years ago

A15 works fine for me here on a Mavericks OS X 10.9 laptop, using a NVIDIA GeForce 9600M GT and NVIDIA GeForce 9400M.

comment:7 by historic_bruno, 10 years ago

Milestone: Alpha 16Alpha 15
Resolution: fixed
Status: newclosed

I will mark the reported issue as fixed in A15 then, reopen if that's not the case.

Note: See TracTickets for help on using tickets.