Game Development Community

Mac Terrain rendering glitches?

by Sean OBrien · in Torque Game Engine Advanced · 06/27/2009 (1:34 am) · 4 replies

First off, this is an Intel iMac, ATI Radeon 2600HD, OS X 10.5.7 ... so hurray for the "world famous" (cough) ATI drivers.

Now, what happens is that the terrain is sporadically covered with what appear to be untextured polys (?) subject to a few conditions:
  • This only affects Torque but it occurs with every demo and every build with 1.8.0 and 1.8.1. Other OpenGL demos, etc don't do anything like this.
  • This only happens to the terrain -- every single other object, emitter, effect, and surface is perfectly fine, textured, lit, etc.
  • The glitches are STATIC when strafing and/or flying but OSCILLATE very quickly when rotating the camera even a little bit.
  • Resetting the camera position/orientation produces exactly the same pattern — i.e. it's repeatable and deterministic.
  • The terrain IS properly rendered when the "near field" (high rez?) ground texture is applied to the close up area (like the TGEA walkthrough demo).
  • It appears as though a long-duration emitter/explosion — long enough to throw light on the terrain — will cause the area lit to be properly rendered until the effect fades.
Here are a few shots:
gaia.ecs.csus.edu/~obriens/glitch1.jpggaia.ecs.csus.edu/~obriens/glitch2.jpggaia.ecs.csus.edu/~obriens/glitch3.jpg
At first I suspected a bad shader or some other corrupted file until I went through and tried all of the engine builds in all of the project folders for both of the versions (total of 9 different executables in 6 different projects). As only one or two of these share resources, it's obviously impossible for a single corrupt file to be the cause of all of this. Furthermore, I just dl'd the 1.8.1 version, unpacked it and whammo -- same exact problem. (As I said before, hurray ATI drivers...)

I have folded in the corrections for the black texturing issue and read up on the mip-map workaround. I also noticed that the console shows that the flag for both "needsExplicitGenerateMipmap" and "HD2600DepthBufferCopy" are set to 0. Again, not entirely sure they should be set or not but noticed it was there.

#1
06/27/2009 (5:31 am)
Not a help necessarily but a sharing of information. I haven't experienced this problem in any of the demos or template files.

I'm running
System: iMac Intel 3ghz duo
Vid Card: NVIDIA GeForce 8800 GS

Could be the drivers :)

Sorry I can't be of much more help.
#2
06/28/2009 (12:18 am)
Considering the sheer number of ... um, "comments" Apple is receiving about 10.5.7 I wouldn't be surprised if the drivers were at fault. What I don't understand is, how do other programs work around these issues? And it's not like the entire image is messed up -- it's only the terrain and only in this one particular manner. Very odd.

Here's hoping 10.6.x has better drivers and T3D (once I can make enough cookies for bake sales! hehehe) will prove immune to these odd quirks.
#3
06/28/2009 (1:50 am)
I do not have these artifacts on my Mac book pro with 10.5.7. HOwever it has an Nvidia chip

I will try and test on my older mac book which has an ATI chip.

I would hazard a guess however that this is driver related.
#4
07/08/2009 (2:52 pm)
I see similar terrain rendering problems with 1.8.1 on my MacBook Pro, Core Duo (not Core 2 Duo), ATI card.