diff options
author | ruslantproductengine <ruslantproductengine@lindenlab.com> | 2015-01-07 02:04:03 +0200 |
---|---|---|
committer | ruslantproductengine <ruslantproductengine@lindenlab.com> | 2015-01-07 02:04:03 +0200 |
commit | bb3517c24e77e7fdea915a8a57326e10e8261d7c (patch) | |
tree | 4f7e91b21d3dd876d063981b0b62319935541d1e /indra/win_crash_logger | |
parent | dbafa3c358f24c9dec0c6e9b5fc92880e6f0e0dd (diff) |
MAINT-4773 FIXED Some transparent textures are rendered as white.
This bug fix related also to MAINT-4092. In 4092 sometimes when we
don't have information about the texture during the setup the materail
(LLVOVolume::setTEMaterialParams()), we should substitute the material with
disabled "diffuse alpha mode" (for detail in cases see MAINT-4092 JIRA ticket
comment).
This bug fix cover the case when after the loading texture we have all
information about alpha mode, and in this case we should restore diffuse
alpha mode if need.
In short: now we always believe that information about the material is valid
(LLVOVolume::setTEMaterialParams()).
Of course before setup it we check information about texture (if it possible)
, if texture is not exist in database or not 32 bit depth (for diffuse) we
made changes.
But in all other cases (if we can't receive information about texture)
we remeber this case in mWaitingTextureInfo multimap.
When information about texture will be available we get it in:
LLVOVolume::notify AboutCreatingTexture()
or
Volume::notifyAboutMissingAsset()
and again, we recheck it and if need change (substitute)
the material parameters.
I suppose that this solution is better than was before.
If this patch will be accepted
, I think that MAINT-4092 should be rechecked again.
Diffstat (limited to 'indra/win_crash_logger')
0 files changed, 0 insertions, 0 deletions