Game Development Community

Graphics bug on OS X 10.5.7

by David Menefee · in Torque Game Engine Advanced · 05/26/2009 (12:35 am) · 5 replies

Hi all

I just upgraded my 17" Macbook Pro to OS X 10.5.7, and am now seeing some spectacular problems with terrain rendering:

www.sophicarts.com/Picture6.png
and

www.sophicarts.com/Picture7.png
My configuration:

Model Name: MacBook Pro 17"
Processor Name: Intel Core 2 Duo
Processor Speed: 2.33 GHz
Memory: 3 GB
Chipset Model: ATY,RadeonX1600
VRAM (Total): 256 MB

I see no obvious problems in the system console log or in the game log. I am convinced that this is the result of upgrading my OS, since the problem only appeared afterward. Has anyone else seen this?

Also, this only happens when the camera is moving, and the rendering triangles change rapidly while it does move.

#1
05/26/2009 (12:55 am)
I haven't upgraded anything to 10.5.7 yet internally, but I do know that the VMware guys have advised that users with ATI macs not upgrade to 10.5.7, so I'm willing to bet there's something seriously futzed in the driver that affects us too.
#2
05/26/2009 (5:38 pm)
I have a spare Mac book 17 i can test on . I will update that to 10.5.7 in the next few days and see what i can see.


My main machine is a unibody 17 " in , which will be updated this week . That has a Nvdia chip set however . I will test on that as well and post here
#3
05/26/2009 (10:59 pm)
Well, I upgraded my home machine (MBP w/GeForce 8600M) and didn't notice anything going wrong with our demos. That's not to say everything is fine and rosy (our demos actually don't hit a surprising amount of the engine), but at least it's not exploding horrifically. Hopefully in the next couple of days I'll get a chance to upgrade the computers at work (iMac w/X1600 and iMac/HD2600) and evaluate the damage.
#4
05/27/2009 (11:08 am)
Alex: if your X1600 has problems, that would seem to reinforce the idea that it's a problem with the ATI driver... If so, I hope Apple fixes it soon!
#5
06/02/2009 (11:09 am)
I haven't tested the X1600 yet, but the HD2600 exhibits the same issue. Hooray for Apple!

No idea when, or even if, I'll have a workaround. Some of the bugs are just so nasty there's not a lot mortal non-driver programmers can do.