The following notes were taken from my audio recording and chat log of the Content Creation User Group (CCUG) meeting held on Thursday, August 20th 2020 at 13:00 SLT. These meetings are chaired by Vir Linden, and agenda notes, meeting SLurl, etc, are are available on the Content Creation User Group wiki page.
Currently, the official viewers remain unchanged from the start of the week:
- Current release viewer version 184.108.40.2066539, dated August 11, promoted August 17, formerly the Arrack Maintenance RC viewer – NEW.
- Release channel cohorts:
- Project viewers:
- Custom Key Mappings project viewer, version 220.127.116.114079, June 30.
- Copy / Paste viewer, version 18.104.22.1683365, December 9, 2019.
- Project Muscadine (Animesh follow-on) project viewer, version 22.214.171.1242999, November 22, 2019.
- Legacy Profiles viewer, version 126.96.36.1990836, September 17, 2019. Covers the re-integration of Viewer Profiles.
- 360 Snapshot project viewer, version 188.8.131.529111, July 16, 2019.
General Viewer Notes
- The Legacy Profiles viewer has been further prevented from making progress due to additional web-side changes that need to be made to enable privacy settings (who can see your feed posts) to work correctly.
- The Mesh Uploader has been integrated with further changes, and is currently being merged up to the current viewer release code base, after which it will go to QA. Providing it passes, it could be appearing as updated RC viewer in week #35. This viewer provides:
- Additional information on meshes at upload, a-la those added to Firestorm (see: Firestorm 6.0.2: Animesh release, February 2019)
- UI improvements to give better information on avatar rigging & related error messaging.
- Improved error messaging overall.
- It will also include various fixes (such as BUG-229032 “[Mesh Uploader] Use Joint Positions Option causes ‘Collapsed Joints/Bones’ for some Files”) that are currently being worked on.
Project Muscadine (Animesh Follow-On)
Currently: offering the means to change an Animesh size parameters via LSL.
- Still officially on hold.
- Will include shape sliders for Animesh – although it should be remembered body shapes and sliders are intended for humanoid avatars, not animals, etc.
Using the JIRA
Complaints were raised about the need to raise Jira bug reports for issues that are “raised in chat”. Simply put:
- Describing an issue (often loosely) in chat – or Voice, which is often the medium for meetings – actually doesn’t mean the issue is captured and recorded. It also doesn’t necessarily mean the issue has been properly described, as those talking about it are not being encouraged to think about the issue in a structured manner or provide illustrations that can better help with understanding precisely where their problem lies.
- The Jira system provides a means by which:
- Information can be captured in a structured manner.
- It can be illustrated.
- It can be updated with further observations, feedback from others, etc.
- It can be referenced, searched and cross-referenced, potentially helping other users understand a problem they are encountering and allowing the Lab to better understand the overall impact of an issue.
- At the end of the day, issues reported by Jira stand a better chance of being fixed at some point that those just chatted about (which likely have a 0% chance).
- Raising Jira reports – Bug or Feature Requests – isn’t actually hard. See:
An attempt to re-evaluate object and avatar rendering costs to make them more reflective of the actual impact of rendering either in the viewer. The overall aim is to try to correct some inherent negative incentives for creating optimised content (e.g. with regards to generating LOD models with mesh), and to update the calculations to reflect current resource constraints, rather than basing them on outdated constraints (e.g. graphics systems, network capabilities, etc).
As of January 2020 ARCTan has effectively been split:
- Viewer-side changes, primarily focused on revising the Avatar Rendering Cost (ARC) calculations and providing additional viewer UI so that people can better visibility and control to seeing complexity.
- Work on providing in-world object rendering costs (LOD models, etc.) which might affect Land Impact will be handled as a later tranche of project work, after the avatar work.
- The belief is that “good” avatar ARC values can likely be used as a computational base for these rendering calculations.
- It now appears that Vir’s work in updating Jelly Dolls will now appear in the ARCTan viewer, when that eventually emerges, but may also (and possibly sooner) appear in a Maintenance RC viewer.
- Overall, ARCTan has been held-up awaiting a fix for an Bake Service issue. Vir believes he now has that fix, and is waiting for it to be deployed to one of the Lab’s internal text grids so he can check to see if it works. Assuming it does work, the fix will be queued for deployment to the main grid and allow performance data gathering to resume.
- Discussions are to resume regarding better UI elements to support information on complexity, etc., that users can understand and use.
- minimum default 15 Land Impact: it is apparently putting some creators off of trying to make Animesh items (notably breedables). It’s been suggested lowering this to 10 LI might help generate greater interest in Animesh creation. Right now, LL haven’t done enough analysis to determine how the figure might conceivably be changed, rather than just making an arbitrary adjustment.
- Bakes on Mesh support: this has been discussed on a number of occasions. There are no plans to provide support for Animesh to use Bakes on Mesh in the foreseeable future, as it requires Animesh to be overhauled to have full inventory support, together with outfit support, and would also require a significant update to the Bake Service to recognise and support Animesh characters.
- Date of next meeting: probably Thursday, September 3rd, 2020.