The bug happens when your client is trying to rebake your avatar's textures and you're doing something with the window (minimizing, switching windows, etc). Since we use the screenbuffer for our dynamic textures, its unavoidable that this would result in a bad bake. Unfortunately there isn't an easy way to detect this case either.
The long-term solution is to change our dynamic texture system to use off-screen buffers for texture readbacks. While not requiring a complete re-write of the avatar baking system, this is non-trivial to do. I've already written a shorter-term solution, which is to draw a black rectangle over the relevant area of the window to prevent the UI from appearing on the bake. I can port this over to snowglobe later this week if there is interest in testing this out. "Rebake textures" should still trigger an upload of your avatar's baked textures. Is there sufficient reason to believe that we're using cached versions (whether server or client-side) of the bakes even when you manually specify "rebake textures"? -Nyx Argent Stonecutter wrote: > Even if you can't figure out how to fix this one... how about making > "Rebake Textures" work without having to go into appearance and select > a modifiable wearable first? > _______________________________________________ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/SLDev > Please read the policies before posting to keep unmoderated posting privileges > _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges
