Game Development Community

OSX Only Problems

by Charlie Sibbach · in Torque Game Engine · 01/13/2009 (10:59 pm) · 3 replies

I'm working with my lead artist, who lives about 2000 miles away, and he reports to me that on his OSX machine, the engine does all sorts of very bad things that I've never seen before, on OSX 1.4, Linux, and Windows builds of TGE1.5. He says (and has sent screen shots) of objects that get rendered only halfway and/or with big sections removed, and that the game has some kind of memory or cycle leak, such that it will lock up in about 5 minutes of play. The strangest part of these reports is that it is only happening about 50% of the time!

I've poured through the console logs, looking for any hint- and there's nothing. We have nearly identical Macbook Pros (his slightly newer)- only substancial difference is he's on 10.5 and I'm on 10.4, and I'm building the game on 10.4. None of these problems have appeared on any other platform, and I build on all three daily. There has been NO sign of this on my Tiger mac. He's going to build the game on 10.5 tomorrow, we'll see if that makes any difference (it would sure make me have to bite the bullet and upgrade), but my gut tells me that's a 50-50 shot at best. Anybody else experienced anything like this?

#1
01/14/2009 (10:08 am)
If he has a nVidia 8600M GT graphic card, a chunk of them can become unfonctionnal because of a flaw in the production process (a bad glue is degenrating over time and heat).

So, his graphic card can become partly dysfunctional.

Hope it is just that (because it's the easiest thing to fix).

Nicolas Buquet
www.buquet-net.com/cv/
#2
01/15/2009 (6:55 pm)
Charlie:

I've been coding on my MacPro and porting to my Windows and Linux machines and have had no problems with TGE 1.5.2+Afx 1.2. Testing on multiple Macs, I've had no rendering issues, only network problems that were things I needed to fix. FYI I've compiled on 10.4 and 10.5 with no problems. Would lead me to suspect a hardware/driver issue...
#3
01/17/2009 (5:19 pm)
Looks like compiling the game on 10.5 solved the problems. Now we have other ones, but it might be stuff I know about and can see on my side.