Jump to content

Ai Austin

  • Content Count

  • Joined

  • Last visited

Community Reputation

25 Excellent

About Ai Austin

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As Theresa said the Bakes button has appeared for texture selection for avatar attached items since BoM was introduced. Since the Love Me Render release candidate this bake button also appears to allow items rezzed in world to be textured with BoM so when worn they have BoM applied. The Love Me Render #4 release candidate became the default viewer a week or two ago. Its now a drop down menu chooser rather than a radio button. See https://jira.secondlife.com/browse/BUG-227553 Firestorm EEP Beta incorporated the Love Me Render #4 code from LL from Firestorm 6.4.10.
  2. @Maitimo glad your mesh content still works. Ruth2's (unrigged) mesh elf ears still work with BoM too. But I hope the restriction to not allow BoM texturing on prim (and scuplt perhaps) parts in attachments is removed so it behaves as it was up to 6.4.6. Current viewers do not work for me with flexi-prim tails 🙂 I can live without allowing BoM texturing on HUD elements, though would like to know the reason for that restriction. @Kyle Lindenpointed us at a JIRA entry but I don't have permission to view it to see the rationale. https://jira.secondlife.com/browse/DRTVWR-501
  3. The fix is in LL viewers from 6.4.7 up to current version. Its also already in Firestorm Beta test versions now including the current FS6.4.10 EEP Beta Wulfie. And rightly the FS team have said we should address this via the SL JIRA and Linden Lab as we can't have rendering look different between the official viewer and Firestorm or it would just not work for everyone and make BoM content rendering consistent.
  4. Thanks @Dan Linden I will tidy up the description. Sorry for the edits I made in a stream yesterday, they all appeared as separate items in the issue timeline! .I could not work out a better way to ask for the JIRA to be reopened. Also @Gabriele Graves and @Maitimo I just tried to attach a simple mesh item, which I THINK is unrigged.. and it DOES texture correctly when set to a BoM face. So you may be in luck with your mesh item attachments even though the fix back in May seemed to require isRiggedMesh()
  5. Hopefully @Dan Lindenwill reopen BUG-229508 so people can relate their use cases there. Dan... the issue is not about the temporary server bakes issue. https://jira.secondlife.com/browse/BUG-229508
  6. Current released Firestorm is 6.3.9 and an EEP Beta version 6.4.5.. and those will work fine as they both predate the change made at LL viewer 6.4.7. But that change is now incorporated into the version being prepared as the next Firestorm release. The change was incorporated into Firestorm in May 2020. See https://vcs.firestormviewer.org/phoenix-firestorm/changeset/b654330f51dea8d5b6b3afd0440a10b2f623bcdd
  7. Check it out in the latest viewer Gabriele. I did not test unrigged mesh attachments myself. I was testing prim attachments, and while investigating attached also a simple sculpt to show that was also was not now being rendered with BoM. The related classic avatar parts though are still hidden if you texture any face of any attached part even if its a prim, a sculpt or in a HUD. So things are in a bit of a broken state at the moment anyway. I was just going on the code change which indicates the change was from allowing anything attached to the avatar to a tighter restriction that for Bo
  8. I would say it should allow that if the creator or user wishes to apply a BoM texture to those. Elf Ears for example might be attached and not necessarily be rigged mesh.
  9. Yes Tazzie, things works fine when you mix classic clothing, tattoos, normal worn attachments that are normally textured (mesh or prim based) and even alpha masks (so long as you select a suitable alpha mode for the mesh that is BoM textured). My use case though is different... its an attachment that I want to apply a BoM texture to (in the case of the tail a part of the lower texture) but where the attachment includes a prim element rather than all the attachment being all (rigged) mesh. In fact anything attached to the avatar that you want rendered with a BoM texture that is not (rigg
  10. Here is an image of a flexi-prim tail attached to an avatar showing the skin tone from BoM as it worked in LL viewers up to 6.4.6 (and Firestorm viewers up to 6.4.5) alongside how it now appears with the (yellow LOWER) fall back coloured texture when seen in LL viewers from 6.4.7 to the current versions (6.4.10) and Firestorm 6.4.10 Beta.
  11. Can I raise an Issue on the types of attached items that can render with a BoM texture... I appreciate this may have been discussed back in April and May 2020 and have been looking back to try to find the reasons that @Vir Lindenmade a change between 6.4.6 and 6.4.7 to limit the BoM textures to be applied to only rigged mesh worn on the avatar and to exclude HUDs. Previously the behaviour was just to check it was an avatar attached item of any type. The change means that prim (and sculpt) parts of worn attachments no longer are rendered with BoM and fall back to the coloured backup textures. T
  12. Its also being reported in Firestorm 6.4.10 Beta as a major bug. But as noted in this Forum, the issue is actually one of the LL core code "fixes" from the Love Me Render #4 changes. The LL folks attempted to fix an issue and have made things worse for many use vases for people trying to use EEP. See https://jira.firestormviewer.org/browse/FIRE-30410
  13. @Vir Linden I wonder if you can get whoever looks after the Wiki to update the UUIDs for the BAKES channels/fallback textures to the up to date ones... and add the extra 5 added BAKES? https://wiki.secondlife.com/wiki/Internal_Textures
  14. More UUIDs and fallback textures would be a bit of overkill don't you think? Better if it can be done to have a (one bit boolean) flag (default "on" for compatibility) to let you turn off alpha hiding of the relevant part.
  15. @Vir Linden can you point us at the JIRA number? I was not sure which seemed to be related to this issue.
  • Create New...