HUD prims vanishing on llSetTexture

When I call llSetTexture, HUD prims will randomly vanish (though not delink, just not render)

Is anyone seeing this as well?

- I have highlight transparent on, but it's not highlighting as alpha/transparent, just invisible / not rendered.
- I can edit the prim and I get a blue outline, but no again .. no transparent highlighting.
- When I drop the HUD the vanished prim re-appears with the correct texture. I have no change events or anything like that.
- When I edit the prim I can see the correct texture in the texture box.

It kind of makes HUDs rather undependable for something critical, but perhaps there is an LSL workaround or maybe I am doing something weird that causes this bug.

Let me know if you're seeing something similar.

Thanks,

Iron.

Hmm, I noticed something very similar, but not while calling llSetTexture, but while actually manually changing the texture for a hud I was working on a few days ago. As I changed the texture the piece would "dissappear" in the same manor you describe, only to reappear as I dropped or reattached it... I just bug reported it and did my best to work around it, but I can verify that I was having the same problem.

possible workaround - if this involves just a few texture swaps - like an on/off button for example, if to use texture offset?
ie: make your texture have all the states you want to diplay, then just slide it around.

You stole that idea from Me Max.. Dangit! Mine!

I have actually had the same problem with prims looking like they derez temporarily whenever the texture on the prim is updated in some way. I just assumed it was a bug they are working on. I haven't really looked into it too much.

This is a known bug... I see it in some of my builds, not HUDs though. Usually the prims reappear after a few seconds, so it's only marginally annoying. If they stay away forever until you drop the HUD attachment, you should bug-report that... the lindens may not know about it.

I've also noticed this both on HUDs and rezzed inworld. One way to get the prims to reapear is force an update of some kind to the root prim. Anything that makes SL resend the info on the root will work; changing textures, alpha, etc. If your changing the texture via script, wait about .1 seconds, then send a message to the root and have it change in someway. Not the best, but it works.

What sort of changes are required to the root? Does it have to be a texture change to the root?

heheh.. i would have hit on it eventually - it's a css web trick
me just slow
perhaps a licensing fee?
I'll give you .01$L for each device i sell that uses it

Same here, smooth, looped animated texture on droid tracks, when I stop the animation the tracks prims vanish and reappear after an uncomfortably long pause.

Did someone submit the bug report yet?

I demand at least .05$L.. Don't be trying to low ball me!

I'm not sure of everything that would cause an update to the root, but I've had to work around the disapearing prim in two of my products. The first is a category based vendor, the buttons would sometimes disapear after putting the product image on them, so I just waited .2 seconds after setting the buttons before changing the main display, which was root, and never had a button say gone afterward.

The second product was my HUD radar, which has buttons that I alpha in and out to reduce screen clutter. Not all the buttons would come back, so I forced a 1% change in the alpha of the root after the buttons were brought back. Again, I had to wait around .2 seconds before the change, or some buttons would still be missing.

If it's possible, try making the root a prim that's hidden inside/behind the object, then chaging texture or alpha after a short delay.

Well, this is nice. SL v1.8.1 broke my workaround, now the root prim is disappearing.

I have noticed this happening with simple color changes as well on one of my HUDs. It's usually only in very laggy areas like clubs though.

I've noticed this happening with llSetColor(), llSetTexture(), llOffsetTexture(), & llSetPrimativeParams() it's been driving me nutty. It seems to happen more frequently when there are multiple actions on a prim but I have seen it happen less frequently with just a single llSetTexture() call. This is not hud related it happens in inworld rezzed objects too. This has been a known bug but it seems to gotten some legs and have gotten worse with the past upgrades.

Bump - Still having this problem with a hud I'm working on, looks like it might be tied to llSetTexture, randomly/almost sporadically instead of setting the appropriate texture, about 80% of the hud pieces become invisible >_<

I concur. Bump.

Has someone posted this under technical issues yet? Or reported the bug?

i've reported a related bug with fullbright & huds, as this is related.