The following notes and audio were taken from the weekly Bento User Group meeting, held on Thursday, October 27th at 13:00 SLT at the Bento User Group wiki page.. and chaired by Vir Linden. For details on the meeting agenda, please refer to the
Note that this update is not intended to offer a full transcript of the meeting, nor does it present the discussion points in chronological order. Rather, it represents the core points of discussion, grouped together by subject matter were relevant / possible, whilst maintaining the overall context of the meeting.
General Project Status
Work continues on Bento bug fixes. As a result of the Bento code being available in a pre-release version of Firestorm, the number of reported issues with legacy content have increased (see BUG-40672). There are two issue in particular the Lab have been looking at:
- The previously reported issues of some mesh content having latent “bad” joint positions which were previously overlooked by the viewer, but which are now taken into account under Bento, leading to avatar deformation (see my update #30 for more on this)
- An issue related to the eye joints now being scaled by the eye size slider, which can result in existing mesh eyes appearing to bug out of avatar’s heads when viewed in the Bento viewer. The easiest way to fix this is to reset the eye slider to the default 50 value.
Outside of these problems – which are still being looked at (see below), there is at least one bug (initially noted with Haste Coy products and also reported on BUG-40672), which should have a fix in the next Bento RC update, and a crash issue which also should be fixed in the next update.
If anyone is encountering issues with existing content when using the Bento viewer, they should report their problems via the JIRA (BUG-40672) so the Lab can look at things.
Legacy Content Deformation Issue
There has still been no decision on how to handle the “werewolf deformation” issue, which now extends to about three creators, and may extend beyond werewolf models. There have been suggestions on forking rendering behaviour by something like upload date, so that if an item was uploaded prior to date X, then it is handled as “non-Bento”; if uploaded after date X, it is handled with Bento in mind.
A problem here is setting an arbitrary date may not actually solve anything. Bento has been around for over a year, with content creators working on it for the last several months at least, during which time other creators have been creating / updating and uploading non-Bento content. So, determining which is which by date likely won’t work.
That said, if there is a large amount of legacy content impacted by the viewer change, it still might be preferable to set a date and have Bento content creators re-upload their work to be on the “right side” of that date, rather than trying to get legacy content creators to re-upload. This is because some creators may not already be around and / or some may have used mesh creation kits which don’t have the necessary .DAE file for them to modify.
A further complication here is that any impact of the viewer behaviour change may simply be negated by creators of older avatar models updating to Bento models, to which their customers subsequently update.
No Modify Shapes
The eye issue mentioned above once again raised concerns around users employing shapes that do not have modify permissions. Such shapes prevent the use of the appearance sliders, so even apparently “easy fix” issues, such as adjusting the eye size slider, may not be applicable.
This particular issue sparked a lengthy conversation about using the (currently non-obvious in the official viewer) XML shape exporter coupled with additional code to more easily export a shape’s XML file, which could then be re-imported with a check box to ensure the default 50 setting for things like the eye size sliders.
One problem here, as Vir pointed out is that users who are unaware of unfamiliar with using the shape sliders likely aren’t going to be enamoured with the idea of exporting an appearance XML file, creating a shape and then importing the appearance XML data against that shape, even though some TPVs have, with the Lab’s approval, sought to make this easier.
There is also the problem that creators may object to users being given the ability to export / import shape data, as it effectively bypasses the permissions system, allowing anyone to take shape data and use it as they please. However, given there is already a TPV methodology available, to assist with shape data import which has been given the nod by the Lab, Vir will take the matter back to the office for further discussion.
The more direct solution might be for creators to indicate that Bento avatar meshes require the use of a modifiable shape (either supplied with the mesh or which the user can create and edit).
Vir highlighted the fact that while different terms are used, there are technically three types of joints in the avatar skeleton: bones, the “standard joints” for rigging to; collision volumes, as used by things like fitted mesh; and attachment points, which have most of the properties of joints, hence why some creators started rigging and animating to them, even though this was never an intended use.
The next Bento meeting will likely be Thursday, November 10th, 2016, as November 3rd clashes with the Lab’s monthly internal meeting.
- Project Bento testing page (wiki)
- Avatar body size (wiki)
- Bento Skeleton Guide (wiki)
- Project Bento user group page
- Project Bento discussion forum
- Project Bento coverage in this blog (including weekly user group meeting updates)