Lumiya, the go-to Second Life / Open Sim client for Android by Alina Lyvette, updated on Wednesday, October 19th, although it’s taken me a few days to get around to blogging about it.
Version 3.1.2 contains a single up-front change, but it’s one users are liable to appreciate: the ability to save chat and IM logs to their Google drive.
To do so, two things are required:
An active Google account with access to Google drive (no surprises there).
Download and install the Lumiya Cloud Plugin on the devices(s) you use with Lumiya.
Log-in to Lumiya and go to Settings via the menu (top left icon) and select Chat and Messages.
Tap Save chat history to Google Drive to enable it.
Setting Lumiya to save chat and IM logs to your Google Drive
A pop-up is displayed for your Google account (not your Second Life account). If you have more than one Google account, you may be asked to enter the details of the account you wish to associate with Lumiya.
Selecting your Google account
Providing you have selected the Google account you wish to use, tap Add Account.
A further pop-up is displayed asking you to allow the Lumiya Cloud Plugin service to access your Google drive in order to save and retrieve chat and IM log files.
Providing you’re happy, tap Allow.
Granting the cloud app permission to save and retrieve your chat and IM logs
And that’s it. You only need to do this once per device, you don’t have to do it for each of your SL accounts if you have more than one. When you log in to Second Life, your chat and IM histories will be available, and saved automatically.
If you ever want to revert to saving your histories directly onto your device, simply go to Menu (top left) > Settings > Chat and Messages and uncheck Save chat history to Google Drive.
Feedback
This is a handy update for Lumiya, offering a single location for chat and IM logs which could be especially useful for those who may use Lumiya on more than one device (e.g. a Tablet and a smartphone), as it removes discontinuities in saving logs locally – although obviously, you’ll have to use the Lumiya Cloud Plugin to associate each device with your Google account / drive.
And if Google Drive isn’t your thing? Then you can continue to save your logs directly to the storage on your device. Simples!
This summary is published every Monday, and is a list of SL viewer / client releases (official and TPV) made during the previous week. When reading it, please note:
It is based on my Current Viewer Releases Page, a list of all Second Life viewers and clients that are in popular use (and of which I am aware), and which are recognised as adhering to the TPV Policy. This page includes comprehensive links to download pages, blog notes, release notes, etc., as well as links to any / all reviews of specific viewers / clients made within this blog
By its nature, this summary presented here will always be in arrears, please refer to the Current Viewer Release Page for more up-to-date information.
Official LL Viewers
Current Release version: 4.1.1.320331 (dated October 4th), promoted October 10th – no change
Cool VL viewer Stable branch updated to version 1.26.18.30 and the Experimental branch updated to version 1.26.19.32, both on October 29th (release notes).
Mobile / Other Clients
Littlesight updated to version 2.0.0 on October 29th – New user interface.
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 the Hippotropolis Campfire Circle. and chaired by Vir Linden. For details on the meeting agenda, please refer to the Bento User Group wiki page.
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.
Eye sizing issue: as Bento allows mesh eyes to be affected by the eye size slider, they can suddenly appear to resize when seen on the that viewer (r), compared to how they appear on a non-Bento viewer (l)
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.
Benches: because even an elephant needs the occasional sit down. Medhue Simoni’s stunning Bento elephant avatar
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.
Other Items
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).
The Skeleton
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.
Next Meeting
The next Bento meeting will likely be Thursday, November 10th, 2016, as November 3rd clashes with the Lab’s monthly internal meeting.
A panoramic image of Holly Kai Park’s events pavilion, captured in the news 360-degree snapshot viewer – click on the image to view in 360 via Flickr, and see my article here
Server Deployment
The RC deployment in week #42 introduced a bug, so there was no Main (SLS) channel deployment on Tuesday, October 25th.
The three RC all received the same server maintenance package, comprising: a fix for the bug introduced in week #42 – see BUG-40735 “Paying an object with [slgaming] in the object name (most skill game machines) fails on the RC 16.10.14.320687”; two fixes for issues with the new llSit function for Experiences, and additional internal updates.
SL Viewer
360 Snapshot Viewer
The new 360-degree snapshot project viewer arrived on Wednesday, October 26th, with the release of the first iteration of the project viewer, version 4.1.2.320965. There is an accompanying wiki page for the viewer, and I have a hands-on look.
Other than this, the viewer pipeline remains as per my TPV Developer meeting summary of October 21st:
Current Release version: 4.1.1.320331 (dated October 4), promoted October 10 – formerly the VLC media plug-in for Windows RC
Release candidates:
Project Bento RC (avatar skeleton extensions), version 5.0.0.320815, dated October 20th
Maintenance RC viewer, version 4.1.2.320804 dated October 20th
Project viewers:
None.
Obsolete platform viewer version 3.7.28.300847 dated May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.
Aditi Weekend Issues
Some people trying to access Aditi, the beta grid, encountered problems over the weekend of the 22nd / 23rd October after a database for that grid failed. As Aditi doesn’t have either the same level of redundancy or the same urgency of repair that Agni (the main grid) has, the database didn’t get sorted out until Monday, October 24th.
On Wednesday October 26th Linden Lab announced the release of the 360o snapshot viewer, which I’ve had the good fortune to be able to play with for the last week.
The viewer is still very much under development, and has been released as project viewer with a number of caveats against it as development continues. Essentially, it allows you to take a set of images (6 in total) of the location around your camera, and then produce these as a scrollable 360o view – you can see the results in action on this sample page. Just click drag on an image to manually scroll around it.
The viewer is available via the Alternative Viewers wiki page as project viewer, with documentation on the wiki. As noted there are some caveats concerning it, which need to be kept in mind:
The 360o capture operates all around your field of view simultaneously. This can lead to conflicts with the viewer’s Interest List, so that objects which may be “behind” your camera position may not be properly rendered, etc. To avoid this, always pan your camera around (or turn your avatar around if you are taking a picture from your avatar’s position) to completely view the scene and allow things to initially load, before taking a shot.
The current viewer saves the resulting image to your local disk as a zip file. You’ll need to set-up your own local web host in order to view them (or if you have your own website, you could set one up there). Again, this will be changing as the project develops
However, even in this format, once you are viewing an image, you can download it in a 2:1 aspect ratio suitable for upload to Flickr for sharing with friends and viewing in 360o.
As I’ve covered three of the 360o camera HUDs available in Second Life, I’m offering the rest of this article as a walk-through in using the new viewer and viewing your photos.
Note – these instructions apply to Windows, I don’t have access to a Mac to provide guidelines for that platform.
Setting Your Viewing Environment
Before taking your photos, you’ll need – for the time being at least – to set-up a simply local web server. Callum Linden has made this relatively easy.
Download Python from the Python website. You can select to install either Python 3.5.x (latest) or Python 2.7.x (the Lab uses Python 2.7 as a point of reference).
When installing Python, make sure you add the installation to your Windows path.
If you are installing Python 3.5.x, simply check the box in the installer
If you are installing Python 2.7, click the Advanced button in the installer, scroll down the list of customisable options and set Add Python .EXE to Path to Will be installed on local hard drive.
If you are familiar with Mercurial, you can clone the existing web framework via the link given in the wiki page. I found going the ZIP file route easier.
Unzip the web viewer files to a location on your hard drive.
When you have unzipped the web viewer package, you should have a folder looking like this – note the SHOTS folder, this is where you’ll be wanting to save your snapshot sets (Windows environment)
Using the Viewer
When you have downloaded and installed the 360o snapshot viewer, proceed as follows:
Position your avatar / camera at the centre of the area you wish to photograph. If you are using your avatar, not that you should “hide” it via removing all attachments and alpha-masking, or by using something like a “vanish” gesture.
Note that you can positioning your camera for a 360o snapshot simply by positioning your camera (e.g. using ALT-zoom or by flycamming).
Make sure you freeze the clouds in order to assist the image “stitching” process, and to avoid visual discontinuities in the finished image. Use Menu > World > Environment Editor >Sky Presets > Edit Presets. You should also avoid using Depth of Field.
Set your preferred windlight / time of day setting.
Turn your camera / avatar slowly around in a circle to view everything in the field of view around it, and allow everything to render.
Open the Snapshot floater and click on the 360 option – not that although this displays the filter options for snapshot, the filter effects are not currently captured when taking 360o shots.
When you are ready, Click Save to save the image set – you will be prompted to save a ZIP file to your hard drive.
Navigate to the location where you unzipped the web viewer files (above) and then save the ZIP file (with a suitable file name) in the SHOTS folder.
This summary is published every Monday, and is a list of SL viewer / client releases (official and TPV) made during the previous week. When reading it, please note:
It is based on my Current Viewer Releases Page, a list of all Second Life viewers and clients that are in popular use (and of which I am aware), and which are recognised as adhering to the TPV Policy. This page includes comprehensive links to download pages, blog notes, release notes, etc., as well as links to any / all reviews of specific viewers / clients made within this blog
By its nature, this summary presented here will always be in arrears, please refer to the Current Viewer Release Page for more up-to-date information.
Official LL Viewers
Current Release version: 4.1.1.320331 (dated dated October 4th), promoted October 10th – no change
Cool VL viewer Stable branch updated to version 1.26.18.29 and the Experimental branch updated to version 1.26.19.31, both on October 22nd (release notes).