An update to the texture banding...

Hopefully some other people having this problem can replicate it.

I went to a building contest last night, and there were about 6 of us constantly rezzing in prims and texturing them. In record time, my ATI card started doing its normal "texture banding" brouhaha, making the screen a total mess (and making my table look pink).

Curious, I relogged and went to my building lot, where I make my houses for customers. After a while of rezzing, the screen went all screwy again.

I logged in today, and am currently still logged in, and instead of building, I decided to just start flying around. Oddly enough, I'm having texture problems happen much later.

Is rezzing of prims causing my ATI to mess up?

Could someone else try rezzing a bunch of stuff and correlate it with me?


LF

I'm not sure it's been the same in my experience...I think I've logged in fresh before and noticed it fairly quickly on a *very large texture*. (and I don't think I was really rezzing anything...if so, only a few prims) I'll try and verify that..

I have an ATI Radeon 9500 Pro with the Catalyst 3.9 drivers. After going with the default display settings from the SL 1.1 upgrade and only turning on AGP in addition to the default settings, I have not been having nearly the texture banding issues that I had with SL 1.0. I am at work right now, so I can't tell the exact settings I have turned on. I will repost the settings I am using when I get home.
Even though my video seems to be working well now, I am still hopefully going to get a Geforce FX 5700 for Christmas.

The texture corruption issues on ATI are generally correlated with the number and size of textures that the driver has to manage. Thus, the bug usually correlates to some degree with the amount of time that you're in world, and how many objects and avatars that you have near you.

On a somewhat related note, if you are running Catalyst 3.9, it appears that as long as you have Avatar Vertex Programs turned off (in Preferences/Options), you should usually have less corruption - in particular, the sky and parts of the UI flickering white will go away. It's GL state related, so you'll probably have to restart to fix the problem.

The texture banding issue has been difficult to reproduce in the office - it may be hardware related, but we don't have enough good information to say for certain that that's the case. If anybody who has bad problems with this could experiment with their SMARTGART settings to see if changing them reduces the problem, I would be really interested in knowing!

- Doug

I recently updated my BIOS (which mentioned added support for "bridged AGP cards", whatever that means), updated to cat 3.9, and SL has since been patched.

I haven't noticed it YET (although I definitely might still), but I wasn't able to reproduce it when I just tried.

I've always had Avatar Vertex off since it makes my AV's hair totally bugged. My Smartgart is at AGP 4x with Fast Write on...I'll post a yell here if I notice any corruption tonight.

Ok the Cat and BIOS updates didn't stop it, LF if you wanna get in world some time and experiment with this I'm all for it.

I have an ATI Radeon Mobility 9k (should be almost identical to the regular 9k). When I 'upgraded' to the 3.9 catalysts texture banding occured like mad. I spent all of 10 mins in the game before textures started corrupting. I downgraded back to 3.1 (ATI definately had something there) and had no texture banding.

The only significant differences between 3.9 and 3.1 are:

1. The speed/fluidity. 3.1 gives you much less consistant FPS, and tends to have less fluid camera movement.
   
2. I dunno about clothes movement with ATI, but I didnt notice any with either.
   
3. Textures dont corrupt with 3.1.
   
4. You are liable to crash... or rather, WILL crash at events with many people around or at a place with a LARGE prim concentration with 3.1.
   [/list=a]
   
   ==Chris

Downgrading to 3.1 also locks you out of ANY 3d applications released in the last year or two. Try running Call of Duty or Homeworld 2 on your 3.1 drivers. They simply just don't load up.

LF