PBR issue on some faces of some Mesh items (#5% of items not compatible)
Ophelatex Demonia
As a designer, I have made a hud to apply all PBR or BP parameters on faces of some items with one hud and one click only, and that includes 10 K textures and 2.5 K materials.
In PBR, some faces of my Mesh items can't be set with a material, they "stay" in BP.
Issue is reproductible on about 10% of faces on about 5% or Mesh items.
Have you heard about that ?
Is it planned to be fixed ?
I can show you inworld if you need more info and/or some Mesh items to see what happens.
I use Firestorm.
I have the same issue with all versions of Firestorm for about one year.
Yours,
ophelatex.demonia
designer and manager of DomiNation & Lilith shop (https://marketplace.secondlife.com/stores/230382)
Log In
Rheia Silvercloud
While my suggestion might seem bothersome, perhaps test to see if this occurs in the standard Linden Labs viewer. Firestorm is a third-party viewer not run by or coded by Linden Labs, and, at best, they could only (much like yourself) ask the Firestorm team to look into this. If it is, however, an issue in the underlying Linden Labs code, (which is the reason for my suggestion above), means that Linden Labs can then look into what is causing it and also post up a bounty to solve the issue, which would then trickle down to all other Third Party Viewers.
Dawn Enchantment
My partner and I are having related issues with pbr and BP, when you go into edit, the last thing you were doing, either pbr or BP, becomes the override, so if you mix pbr textures on one object, the other in your viewer is ignored, you must go into edit and switch to the right texture. It becomes one or the other. It seems you can't mix textures. One rock for instance has a pbr texture, the other is BP, depending on whether you were last in a pbr texture or a bp texture in the viewer. I am on the latest FS release
Rheia Silvercloud
Dawn Enchantment Pardon me copying and pasting what I said above, but:
While my suggestion might seem bothersome, perhaps test to see if this occurs in the standard Linden Labs viewer. Firestorm is a third-party viewer not run by or coded by Linden Labs, and, at best, they could only (much like yourself) ask the Firestorm team to look into this. If it is, however, an issue in the underlying Linden Labs code, (which is the reason for my suggestion above), means that Linden Labs can then look into what is causing it and also post up a bounty to solve the issue, which would then trickle down to all other Third Party Viewers.