David E

I have the same problem on an Intel MacBook Pro, running the "Universal" Avernum 4 v1.1. A bug fix (or workaround) would be most appreciated, and I am also curious as to what in particular is the cause of this problem (is it an incompatibility in the Intel OS X implementation of a particular graphics framework/API?)...