Uploaded image for project: 'Firestorm'
  1. Firestorm
  2. FIRE-13904

Texture Thrashing when WowMeh HUD is worn.

    Details

    • Type: Documentation
    • Status: Closed
    • Priority: Major
    • Resolution: Out of Scope
    • Affects Version/s: Phoenix Firestorm 4.6.5, Phoenix Firestorm 4.6.6
    • Fix Version/s: None
    • Component/s: Rendering
    • Environment:
    • SL Avatar Name:
      HUGSaLOT Vakyrie
    • Reported In:
      Firestorm 4.6.6.41108 QA

      Description

      The textures on the walls in my home keep re-rezzing repeatedly. It appears blurry, then partly rezzed, then back to all blurry again and repeats indefinatly. If i right click on the walls the rez fully, and it stops but only for a minute and it starts over again.

      Some surfaces will remain blurry, while others will go into a re-rezing loop. this only seem to apply to basic prim objects, not sculpts, nor mesh, and my avatar's skin, attachments, and HUDs were fine.

      The normal workaround was to disable HTTP texture gets, but that didn't work for me. Disabling them still caused the textures to re-rez in a loop.

      Clearing texture cache and having HTTP textures off resulting almost no textures rezzing. After putting it back on and allowing texture to rez, still result in this looping re-rezzing.

      I have teleported around to different regions and saw the same texture re-rezzing looping issue i saw in my home.

      I'm using two different windows 8.1 PCs that show this behavor. Both with Nvidia cards using the same current WHQL drivers. One PC is using the x64 build, the other is on the x86 version of FS (build 41108) and they both report my video card models properly.

      Also my log files are also attached as requested by the beta group when we spoke about this.

      EDIT (Whirly): Im going to add a list here of repro HUDs (or objects) that we have found to easily trigger texture thrashing. The WowMeh HUD is by no means the only culpret here.

      Repro Object Where to get it Other info...
      WowMeh HUD https://marketplace.secondlife.com/p/WowMeh-Mesh-Body/5288361 Many 1024 textures, Hud uses over 300MB memory
      ToddleeDoo avatar HUD https://marketplace.secondlife.com/p/Cute-Bytes-ToddleeDoo/3702051 Often seen causing this problem by FS support
      The shops HUD - StyleMode (v.151b) http://maps.secondlife.com/secondlife/The%20Shops/115/131/4 HUD is free. Reported to cause thrashing in SUP-13894
      1. Hugsie-Firestorm.log
        210 kB
        HUGSaLOT Valkyrie

        Issue Links

          Activity

          Hide
          ansariel.hiller Ansariel Hiller added a comment -

          The usual thing: Too many textures around:

          2014-05-31T08:04:43Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 0.3 sBoundTextureMemoryInBytes 403091616 sTotalTextureMemoryInBytes 467307040 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:44Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 0.5 sBoundTextureMemoryInBytes 419807732 sTotalTextureMemoryInBytes 484023240 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:44Z INFO: newview/llviewerdisplay.cpp(232) : display_stats: FPS: 58.90
          2014-05-31T08:04:44Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 0.8 sBoundTextureMemoryInBytes 423473652 sTotalTextureMemoryInBytes 487693512 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:45Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 1.0 sBoundTextureMemoryInBytes 425259508 sTotalTextureMemoryInBytes 489561288 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:45Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 1.3 sBoundTextureMemoryInBytes 425455092 sTotalTextureMemoryInBytes 490084552 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:46Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 1.5 sBoundTextureMemoryInBytes 425143796 sTotalTextureMemoryInBytes 490428616 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:46Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 1.8 sBoundTextureMemoryInBytes 425144820 sTotalTextureMemoryInBytes 491740360 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:47Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 2.0 sBoundTextureMemoryInBytes 425406964 sTotalTextureMemoryInBytes 492002504 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:47Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 2.3 sBoundTextureMemoryInBytes 425366260 sTotalTextureMemoryInBytes 491962824 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:48Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 2.5 sBoundTextureMemoryInBytes 425127668 sTotalTextureMemoryInBytes 491723208 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:48Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 2.8 sBoundTextureMemoryInBytes 425549300 sTotalTextureMemoryInBytes 493521096 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:49Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 3.0 sBoundTextureMemoryInBytes 425305844 sTotalTextureMemoryInBytes 493277640 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:49Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 3.3 sBoundTextureMemoryInBytes 424273652 sTotalTextureMemoryInBytes 492245448 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:50Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 3.5 sBoundTextureMemoryInBytes 425114356 sTotalTextureMemoryInBytes 494396872 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:50Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 3.8 sBoundTextureMemoryInBytes 424401652 sTotalTextureMemoryInBytes 493684168 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:51Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 4.0 sBoundTextureMemoryInBytes 424008436 sTotalTextureMemoryInBytes 493290952 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:51Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 4.3 sBoundTextureMemoryInBytes 421599988 sTotalTextureMemoryInBytes 490849736 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:52Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 4.5 sBoundTextureMemoryInBytes 421567220 sTotalTextureMemoryInBytes 490849736 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:52Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 4.8 sBoundTextureMemoryInBytes 418126580 sTotalTextureMemoryInBytes 487409096 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:53Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 5.0 sBoundTextureMemoryInBytes 417798900 sTotalTextureMemoryInBytes 487081416 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          2014-05-31T08:04:53Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 5.3 sBoundTextureMemoryInBytes 412023540 sTotalTextureMemoryInBytes 480273864 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768
          

          You should reduce textures in your home. We can't do anything about creators dumping lots of 1024x1024 pixel textures on everything.

          Show
          ansariel.hiller Ansariel Hiller added a comment - The usual thing: Too many textures around: 2014-05-31T08:04:43Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 0.3 sBoundTextureMemoryInBytes 403091616 sTotalTextureMemoryInBytes 467307040 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:44Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 0.5 sBoundTextureMemoryInBytes 419807732 sTotalTextureMemoryInBytes 484023240 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:44Z INFO: newview/llviewerdisplay.cpp(232) : display_stats: FPS: 58.90 2014-05-31T08:04:44Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 0.8 sBoundTextureMemoryInBytes 423473652 sTotalTextureMemoryInBytes 487693512 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:45Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 1.0 sBoundTextureMemoryInBytes 425259508 sTotalTextureMemoryInBytes 489561288 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:45Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 1.3 sBoundTextureMemoryInBytes 425455092 sTotalTextureMemoryInBytes 490084552 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:46Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 1.5 sBoundTextureMemoryInBytes 425143796 sTotalTextureMemoryInBytes 490428616 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:46Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 1.8 sBoundTextureMemoryInBytes 425144820 sTotalTextureMemoryInBytes 491740360 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:47Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 2.0 sBoundTextureMemoryInBytes 425406964 sTotalTextureMemoryInBytes 492002504 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:47Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 2.3 sBoundTextureMemoryInBytes 425366260 sTotalTextureMemoryInBytes 491962824 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:48Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 2.5 sBoundTextureMemoryInBytes 425127668 sTotalTextureMemoryInBytes 491723208 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:48Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 2.8 sBoundTextureMemoryInBytes 425549300 sTotalTextureMemoryInBytes 493521096 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:49Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 3.0 sBoundTextureMemoryInBytes 425305844 sTotalTextureMemoryInBytes 493277640 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:49Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 3.3 sBoundTextureMemoryInBytes 424273652 sTotalTextureMemoryInBytes 492245448 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:50Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 3.5 sBoundTextureMemoryInBytes 425114356 sTotalTextureMemoryInBytes 494396872 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:50Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 3.8 sBoundTextureMemoryInBytes 424401652 sTotalTextureMemoryInBytes 493684168 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:51Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 4.0 sBoundTextureMemoryInBytes 424008436 sTotalTextureMemoryInBytes 493290952 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:51Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 4.3 sBoundTextureMemoryInBytes 421599988 sTotalTextureMemoryInBytes 490849736 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:52Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 4.5 sBoundTextureMemoryInBytes 421567220 sTotalTextureMemoryInBytes 490849736 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:52Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 4.8 sBoundTextureMemoryInBytes 418126580 sTotalTextureMemoryInBytes 487409096 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:53Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 5.0 sBoundTextureMemoryInBytes 417798900 sTotalTextureMemoryInBytes 487081416 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 2014-05-31T08:04:53Z INFO: newview/llviewertexture.cpp(555) : LLViewerTexture::updateClass: new bias 5.3 sBoundTextureMemoryInBytes 412023540 sTotalTextureMemoryInBytes 480273864 sMaxBoundTextureMemInMegaBytes 384 sMaxTotalTextureMemInMegaBytes 768 You should reduce textures in your home. We can't do anything about creators dumping lots of 1024x1024 pixel textures on everything.
          Hide
          hugsalot HUGSaLOT Valkyrie added a comment -

          this wasn't a problem before 41108. It's not as if i added one too many textures to my home today. My home has been unchanged for months with out issues. Same with all the other places I'm seeing this problem now with this build, as it's not the land owners problem.

          I do have my texture memory set to 384m, I'll set it to 512m and see if that helps.. but I've had it at 384mb for years.
          ((time passes))
          The 512mb setting seems to have fixed it. Odd was never a problem before and I'm using a 1Gb video card.

          ok i fixed it. \o/

          Show
          hugsalot HUGSaLOT Valkyrie added a comment - this wasn't a problem before 41108. It's not as if i added one too many textures to my home today. My home has been unchanged for months with out issues. Same with all the other places I'm seeing this problem now with this build, as it's not the land owners problem. I do have my texture memory set to 384m, I'll set it to 512m and see if that helps.. but I've had it at 384mb for years. ((time passes)) The 512mb setting seems to have fixed it. Odd was never a problem before and I'm using a 1Gb video card. ok i fixed it. \o/
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Clematide Oyen was also complaining about this problem in Beta testers group and she said the same, that the previous QA build did not do this.
          It could be just coincidence, but maybe not....
          Lets not close this one just yet and see if anymore beta tester complaints come in about increased texture thrashing on this build.

          Show
          whirly.fizzle Whirly Fizzle added a comment - Clematide Oyen was also complaining about this problem in Beta testers group and she said the same, that the previous QA build did not do this. It could be just coincidence, but maybe not.... Lets not close this one just yet and see if anymore beta tester complaints come in about increased texture thrashing on this build.
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Turns out Clematide is wearing the Wowmeh avatar HUD currently and she was not wearing this while testing the previous QA build.
          Support have seen several instances of this Wowmeh HUD triggering severe texture thrashing on the 4.6.5 release.

          Hugs, you dont happen to also be wearing the Wowmeh HUD do you?

          Show
          whirly.fizzle Whirly Fizzle added a comment - Turns out Clematide is wearing the Wowmeh avatar HUD currently and she was not wearing this while testing the previous QA build. Support have seen several instances of this Wowmeh HUD triggering severe texture thrashing on the 4.6.5 release. Hugs, you dont happen to also be wearing the Wowmeh HUD do you?
          Hide
          ansariel.hiller Ansariel Hiller added a comment -

          Where can I get that HUD?

          Show
          ansariel.hiller Ansariel Hiller added a comment - Where can I get that HUD?
          Hide
          whirly.fizzle Whirly Fizzle added a comment - - edited

          Here Ans: https://marketplace.secondlife.com/p/WowMeh-Mesh-Body/5288361

          Theres a demo but I cant remember if the demo comes with the HUD.

          Clementine was instantly fixed after removing her Wowmeh HUD.
          Whirls has the full Wowmeh avatar too so Im going to leave this HUD on & do some testing.

          Show
          whirly.fizzle Whirly Fizzle added a comment - - edited Here Ans: https://marketplace.secondlife.com/p/WowMeh-Mesh-Body/5288361 Theres a demo but I cant remember if the demo comes with the HUD. Clementine was instantly fixed after removing her Wowmeh HUD. Whirls has the full Wowmeh avatar too so Im going to leave this HUD on & do some testing.
          Hide
          whirly.fizzle Whirly Fizzle added a comment - - edited

          Hmm this is interesting.
          I am not seeing any texture thrashing issues when wearing the Wowmeh HUD at my default setting of 512MB for video memory, the BIAS never goes above zero, BUT if I lower video memory to 250-300MB, as soon as I attach the Wowmeh HUD, the Bias quickly shoots up to 5 and thrashing immediately starts. Removing the HUD and thrashing instantly stops and BIAS goes quickly down to zero.
          100% repeatable - each time I add the HUD in the same session, BIAS shoots up to 5 and thrashing starts.

          Im pretty sure you should be able to repro this easily Ans.
          I am also testing on a fairly empty region, not texture rich at all. So I suspect even on the default 512 video memory setting, after a few TP's around texture rich regions, this will likely reproduce.
          I'll test that

          Show
          whirly.fizzle Whirly Fizzle added a comment - - edited Hmm this is interesting. I am not seeing any texture thrashing issues when wearing the Wowmeh HUD at my default setting of 512MB for video memory, the BIAS never goes above zero, BUT if I lower video memory to 250-300MB, as soon as I attach the Wowmeh HUD, the Bias quickly shoots up to 5 and thrashing immediately starts. Removing the HUD and thrashing instantly stops and BIAS goes quickly down to zero. 100% repeatable - each time I add the HUD in the same session, BIAS shoots up to 5 and thrashing starts. Im pretty sure you should be able to repro this easily Ans. I am also testing on a fairly empty region, not texture rich at all. So I suspect even on the default 512 video memory setting, after a few TP's around texture rich regions, this will likely reproduce. I'll test that
          Hide
          ansariel.hiller Ansariel Hiller added a comment - - edited

          The demo has the HUD apparently. Is uses over 300MB of memory

          And since HUDs always load with discard level 0, means textures fully load...

          Show
          ansariel.hiller Ansariel Hiller added a comment - - edited The demo has the HUD apparently. Is uses over 300MB of memory And since HUDs always load with discard level 0, means textures fully load...
          Hide
          hugsalot HUGSaLOT Valkyrie added a comment -

          Oh yes was using a Wowmeh HUD since i was in the middle of trying to edit an outfit for my new body shape. However like i said in my post last night, increasing memory size to 512Mb solved it for me. I used to have it at 384Mb for some years assuming it would help render lag.

          Looks like using this HUD and video card memory set under 512Mb is the culprit.

          Show
          hugsalot HUGSaLOT Valkyrie added a comment - Oh yes was using a Wowmeh HUD since i was in the middle of trying to edit an outfit for my new body shape. However like i said in my post last night, increasing memory size to 512Mb solved it for me. I used to have it at 384Mb for some years assuming it would help render lag. Looks like using this HUD and video card memory set under 512Mb is the culprit.
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Ha! Dammit.
          I'm beginning not to be quite so in love with my Wowmeh lol.
          Thanks Hugs - good to know the new build isn't the culpret anyway.

          I'll edit the title & link this to the general texture thrashing issue.
          I'd like to leave this issue open for now - LL have an upcoming change which will allow a larger video memory setting and testing how this change behaves with the evil HUD worn would be a wise thing to do.

          For reference: viewer-tiger: https://bitbucket.org/lindenlab/viewer-tiger/commits/8425f76bbb1de290c9c4956a2e0579d4a05a0112
          Note that currently this commit actually causes worse texture thrashing, but I'm sure this will be fixed - see https://jira.secondlife.com/browse/BUG-6207 ([Tiger] Increased texture thrashing problem on viewer-tiger).

          Show
          whirly.fizzle Whirly Fizzle added a comment - Ha! Dammit. I'm beginning not to be quite so in love with my Wowmeh lol. Thanks Hugs - good to know the new build isn't the culpret anyway. I'll edit the title & link this to the general texture thrashing issue. I'd like to leave this issue open for now - LL have an upcoming change which will allow a larger video memory setting and testing how this change behaves with the evil HUD worn would be a wise thing to do. For reference: viewer-tiger: https://bitbucket.org/lindenlab/viewer-tiger/commits/8425f76bbb1de290c9c4956a2e0579d4a05a0112 Note that currently this commit actually causes worse texture thrashing, but I'm sure this will be fixed - see https://jira.secondlife.com/browse/BUG-6207 ( [Tiger] Increased texture thrashing problem on viewer-tiger).
          Hide
          alexxyes Cassandra Hastings added a comment -

          Wouldnt be possible for the maker of wowmeh to redo the HUD so it wont cause thrashing textures? I never seen such a HUD to cause so many problems.

          Show
          alexxyes Cassandra Hastings added a comment - Wouldnt be possible for the maker of wowmeh to redo the HUD so it wont cause thrashing textures? I never seen such a HUD to cause so many problems.
          Hide
          whirly.fizzle Whirly Fizzle added a comment - - edited

          Well, that would be an ideal solution yes. Though it would be nice if the viewer was able to handle icky content such as this better too.
          The WowMeh isn't the only HUD that does this. The Toddleedoo avatar HUD is another one famous for causing the same problem. The popularity of the Wowmeh is causing this to become a rather popular problem recently though.

          Show
          whirly.fizzle Whirly Fizzle added a comment - - edited Well, that would be an ideal solution yes. Though it would be nice if the viewer was able to handle icky content such as this better too. The WowMeh isn't the only HUD that does this. The Toddleedoo avatar HUD is another one famous for causing the same problem. The popularity of the Wowmeh is causing this to become a rather popular problem recently though.
          Hide
          hugsalot HUGSaLOT Valkyrie added a comment -

          The Wowmeh HUD isn't necessary to wear. It's only needed it to change clothes, skins, etc. The body mesh wearable is amazing and hot, but you do not need to wear the HUD 24/7. Sexy Ginn did send a message to the maker of Wowmeh about this issue.

          Show
          hugsalot HUGSaLOT Valkyrie added a comment - The Wowmeh HUD isn't necessary to wear. It's only needed it to change clothes, skins, etc. The body mesh wearable is amazing and hot, but you do not need to wear the HUD 24/7. Sexy Ginn did send a message to the maker of Wowmeh about this issue.
          Hide
          whirly.fizzle Whirly Fizzle added a comment -

          Soft Linden just filed a LL JIRA about the WowMeh HUD problem:
          https://jira.secondlife.com/browse/BUG-6242 - Provide an informative warning when a user has a render-heavy set of HUDs

          Show
          whirly.fizzle Whirly Fizzle added a comment - Soft Linden just filed a LL JIRA about the WowMeh HUD problem: https://jira.secondlife.com/browse/BUG-6242 - Provide an informative warning when a user has a render-heavy set of HUDs
          Hide
          bit mcmillan bit mcmillan added a comment -

          I'm WowMeh and ToddleeDoo creator and i'm aware about this issue.
          I'd ask for help in the Support Group inworld when i released the first ToddleeDoo version with this HUD.
          I didn't get a clear answer, but i noticed that the large amount of skins and clothes textures is what it cause this issue.

          There is a simple and effective work around: ToddleeDoo as long as WowMeh HUD are Modify and - according to instructions - for those users with difficulties on loading these HUD is suggested to "hack" it: simply rezz it on ground and unlink all the non-used buttons, specifically, noone needs to carry on everyday, 24 and more skins.

          So just feel free to customize your HUDs....

          Show
          bit mcmillan bit mcmillan added a comment - I'm WowMeh and ToddleeDoo creator and i'm aware about this issue. I'd ask for help in the Support Group inworld when i released the first ToddleeDoo version with this HUD. I didn't get a clear answer, but i noticed that the large amount of skins and clothes textures is what it cause this issue. There is a simple and effective work around: ToddleeDoo as long as WowMeh HUD are Modify and - according to instructions - for those users with difficulties on loading these HUD is suggested to "hack" it: simply rezz it on ground and unlink all the non-used buttons, specifically, noone needs to carry on everyday, 24 and more skins. So just feel free to customize your HUDs....
          Hide
          ansariel.hiller Ansariel Hiller added a comment -

          Question: Why does a small button need a 1024x1024 pixel texture that is using up 4MB of texture memory? Using a small 32x32 or 64x64 pixel texture would be sufficient.

          Show
          ansariel.hiller Ansariel Hiller added a comment - Question: Why does a small button need a 1024x1024 pixel texture that is using up 4MB of texture memory? Using a small 32x32 or 64x64 pixel texture would be sufficient.
          Hide
          bit mcmillan bit mcmillan added a comment - - edited

          It actually contain the body textures (in the case of skins) and clothes textures (in clothes): users can just drop their textures on it (and touch) and the HUD apply them to the body.
          For default it contain a lot features and options useful for everyone, but most don't actually need to change skin every 10 minutes, or the same for custom clothes.
          The UI textures are very small and optimized indeed.
          The HUD is modify: users can unlink all the buttons not needed, resize or recolor, as long as link appliers or like that: it just needed to reset the main script once your customization is done.

          Show
          bit mcmillan bit mcmillan added a comment - - edited It actually contain the body textures (in the case of skins) and clothes textures (in clothes): users can just drop their textures on it (and touch) and the HUD apply them to the body. For default it contain a lot features and options useful for everyone, but most don't actually need to change skin every 10 minutes, or the same for custom clothes. The UI textures are very small and optimized indeed. The HUD is modify: users can unlink all the buttons not needed, resize or recolor, as long as link appliers or like that: it just needed to reset the main script once your customization is done.
          Hide
          siliconrose Laura Bondi added a comment -

          Honestly the workaround proposed by bit mcmillian is not really useful for normal users that could even be unable to rezz and edit things inworld. I admit that the HUD may contain several very large textures (skin textures in WowMeh are HD) but if they are inside the prim inventory they won't have effects inworld and then they can't be the cause of the bug. The problem is just for the texture applyed to the prims and there is not a real reason because large textures should be applied to buttons or prim faces in a HUD. Just cut a 256x256 piece of the skin you have to show (or make a 256x256 copy of the nails texture) and apply it to the buttons. This will hopefully fix the problem. My HUDs usually won't even have textures in the hidden faces or not shown buttons (clear faces) and are texturized only when shown. Anyway also if I agree that people doesn't need to keep worn the WowMeh HUD, in some situations they need to do (when preparing for getting naked in example) and it is not really nice to get undressed while everything around you (your partner too) is blurring and reloading continuously.

          Show
          siliconrose Laura Bondi added a comment - Honestly the workaround proposed by bit mcmillian is not really useful for normal users that could even be unable to rezz and edit things inworld. I admit that the HUD may contain several very large textures (skin textures in WowMeh are HD) but if they are inside the prim inventory they won't have effects inworld and then they can't be the cause of the bug. The problem is just for the texture applyed to the prims and there is not a real reason because large textures should be applied to buttons or prim faces in a HUD. Just cut a 256x256 piece of the skin you have to show (or make a 256x256 copy of the nails texture) and apply it to the buttons. This will hopefully fix the problem. My HUDs usually won't even have textures in the hidden faces or not shown buttons (clear faces) and are texturized only when shown. Anyway also if I agree that people doesn't need to keep worn the WowMeh HUD, in some situations they need to do (when preparing for getting naked in example) and it is not really nice to get undressed while everything around you (your partner too) is blurring and reloading continuously.
          Hide
          ansariel.hiller Ansariel Hiller added a comment -

          Closing as out of scope. It's not fixable by the viewer if a creator adds lots of high resolution textures to HUDs that will eat up all the texture memory of the viewer.

          Show
          ansariel.hiller Ansariel Hiller added a comment - Closing as out of scope. It's not fixable by the viewer if a creator adds lots of high resolution textures to HUDs that will eat up all the texture memory of the viewer.
          Hide
          whirly.fizzle Whirly Fizzle added a comment -
          Show
          whirly.fizzle Whirly Fizzle added a comment - https://bitbucket.org/andreykproductengine/hud-notifier/commits/f1d8241496a15b859cbf0472edc90518d3161b73 MAINT-4124 Warnin user about render-heavy set of HUDs

            People

            • Assignee:
              Unassigned
              Reporter:
              hugsalot HUGSaLOT Valkyrie
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: