On Friday, October 13th, the Lab promoted their “Moonshine” release viewer, version 220.127.116.119115 to de facto release status. This viewer brings some new options to the official viewer, as well as including a range of improvements and bug fixes.
The code name for the viewer is described thus: “Moonshine was originally a slang term used to describe high-proof distilled spirits usually produced illicitly, without government authorisation. In recent years, however, moonshine has been legalized in various countries and has become a term of art. Legal in the United States since 2010, moonshine is defined as ‘clear, unaged whiskey’. This deploy is filled with a jigger of crash fixes, a splash of translation fixes and a kick that will make you say ‘I can’t feel my face any more!'”
In terms of the updates, probably the most visible is the new Worn tab within the Inventory floater. Those who have used third-party viewers like Firestorm will be familiar with this: it presents a list of items your avatar is currently wearing, defined by the folders in which the items are located.
In addition, the scroll zone associated with the inventory floater (and the Marketplace floater) has been improved, and the inventory filter options (My Inventory > Gear menu > Show filters) have two new options:
Created by me, Created by others
Search by Name, Description, Creator, UUID.
The viewer includes the ability to increase the cache size to up to 9.75 GB in size, and cache performance has been improved. This work is all part of on-going viewer infrastructure work, which with this viewer includes changes to reduce the rate at which log-in retries are attempted.
As I’ve reported in my weekly SL project updates, the rate at which these login retries were being carried out could cause a detrimental impact on services when the grid was experiencing issues; it is an update TPVs have been asked to adopt as soon as they can.
Also included in this release as a part of the infrastructure updates is a general clean-up of the log-in code.
In addition to the above, the viewer includes a range of UI behaviour improvements and bug fixes, all of which are listed in the release notes.
I’ve not had the opportunity to use this viewer extensively, but performance-wise and in terms of the length of time I have been using it, the performance easily matches previous releases when running on my main system. In terms of the updates, the increased cache size could prove beneficial to those able to take advantage of it, and who use either an SSD or who can make use of a RAM drive on their system.
Overall, another useful viewer update from the Lab, with a good range of resolved issues and fixed bugs.
Updated July 7th: to include information on easy embedding in WordPress.
Linden Lab has recently made two updates to the 360-degree snapshot project viewer, which I’ve been meaning to review for the last couple of weeks.
On June 19th, version 18.104.22.1686488 of the viewer was issued, which included image processing updates, and which included offering the viewer in both 32-bit and 64-bit Windows flavours. Then, on June 29th, the viewer was further updated to version 22.214.171.1246743 (at the time of writing the current version), which largely saw the viewer brought up to parity with the current release viewer.
The core functional changes to the viewer in both of these updates is the removal of the need for manual post-processing via zip file download and a web back-end provided by the Lab (see my original hands-on of the initial release of the viewer for more). Instead, the viewer is intended to process the image and provide the necessary meta-date to allow automatic playback on most 360-degree image sharing sites.
I’ve so far tested the viewer on Flickr and a number of 360-degree photo sharing sites such as VRchive. The latter appear to work as expected, Flickr requires 360-images uploaded from the viewer to be manually tagged from within Flickr in order to work. This is a minor inconvenience – but would be smarter if the metadata allowed for auto-tagging of the images as equirectangular, as can be done with other 360-imaging tools. A JIRA has been raised on this.
In the meantime, here’s a look at taking photos with the viewer, and getting them working on Flickr.
The 360-degree photo option is fully integrated into the snapshot floater, and when selected will disable all other options and will only allow you to save images to your local hard drive. Note that if you set any other options (e.g. check the Interface option or setting a filter) prior to checking the 360-degree snapshot option, this will result either in the viewer reverting to taking a “normal” snapshot, or ignoring the filter when processing as a 360-degree image.
Before taking a shot, you should do a little preparation first:
Position your avatar / camera at the centre point of the image you wish to capture (you can “hide” your avatar using a full body alpha or something like a “vanish” animation if you don’t want it appearing in the shot). Use ALT-cam or flycamming to position the camera if you want your avatar to appear in the image, but not at its centre.
Use Menu > World > Environment Editor >Sky Presets > Edit Presets to set your desired Windlight and use the Clouds tab to freeze the clouds. Avoid the use of Depth of Field.
Turn your camera / avatar slowly around in a circle to see everything in the snapshot field of view, allowing everything to render as you do so.
When you’re ready to take your shot, click on Save to Disk on the snapshot floater and set your preferred image size:
Small – 1024×512
Medium – 2048×1024
Large – 4096×2048
Save your snapshot to the location of your choice on your hard drive. You can now upload it to your preferred 360-degree image sharing website.
Displaying In Flickr
If you are uploading to Flickr, remember to manually set the equirectangular tag in the image page, and then refresh the page. The image should reload and display in 360-degree format.
Displaying in WordPress
WordPress has a beta 360 photo and video processor allowing users to embed 360-degree images into their posts. However, in the case of images, this requires the .JPG file extension to be used. Currently the snapshot viewer uses .JPEG. However, once the extension has been changed, images should work fine.
To embed a 360 image, upload it to your WordPress media library (or similar on-line storage – but not a photo sharing website), making sure it has the .JPG extension. Then within your blog post, add the following shortcode between square braces (i.e. [ and ]) in either the Visual or Text editor:
vr url=path-to-photo.jpg view=360
This should result in the image being displayed so that it can be clicked on an manually scrolled, as per the image below:
As noted, 360-degree snapshots should auto-play on any photo sharing sites such as VRchive which parse uploads to ensure they are in the required equirectangular ratio (information on using VRchive can be found in this blog here).
Whether or not the viewer can be set so that the metadata allows Flickr to auto-recognise the 360-degree images as such, and simply play them without manual tagging remains to be seen. But as noted, it’s not a major inconvenience of not (after all, who of us here doesn’t fiddle with images post upload to Flickr?). As it is, this is a definite step up for the viewer in managing 360-degree images, and I’d certainly be interested in hearing from anyone as to how it works with Facebook.
One other point to note as well is that at the moment, the 360-degree snapshot project viewer is not compatible with format used for 360-degree images on SL Places Pages. However, the latter will be revised to support displaying images captured by the viewer at some point in the future.
Update, May 23rd: version 126.96.36.1996444 of this viewer is now the release version of the official viewer.
On Friday, May 12th, 2017, Linden Lab issued a new Maintenance release candidate viewer – now version – 188.8.131.526444 – featuring a number of bug fixes and improvements.
In particular the viewer includes updates to reflect the revised region / parcel access controls now deployed to the main grid. It also includes improvements to inventory management and purging Trash, and a range of other improvements and updates as well as numerous bug fixes.
As per usual, this is not intended to be an in-depth review of the viewer, but rather to highlight some of the new / updated features and an overview based on the release notes.
Region / Parcel Access Controls
The new region / parcel access controls are paired with a server-side update first announced in April, and the first part of which was deployed to the LeTigre server RC channel on Wednesday, May 17th. Until these server-side updates are deployed grid-wide, this particular set of changes in the view may not function on all regions.
In short, the new controls mean that when a region holder / manager explicitly set a region for open access by visitors (via the Region / Estate floater), parcel holders on the region will no longer be able to override the setting at the parcel level and create ban lines around their parcel. They will, however, still be able to use their parcel ban list or deploy security orbs or similar (assuming the use of the latter is allowed under any covering covenant).
This means that with this viewer, both the Estate tab in the Region / Estate floater has been updated, and the behaviour of the Access tab in the About Land floater has changed.
In the case of the Estate tab in the Region / Estate floater, the check box Allow Public Access has been removed, and a new option, Parcel Owners Can Be More Restrictive, has been added (see below).
By default, Parcel Owners Can Be More Restrictive is checked, which means that as the updated settings are deployed server-side, parcel owners should see no difference in behaviour for their parcels unless an estate holder / manager opts to make changes at the estate level (as shown in the image above).
Should the option be unchecked, the estate holder / manager making the change will receive a model warning that they are about to make a change that could affect parcel settings in the estate.
Should they go ahead and APPLY the change, two further things will happen:
Parcel owners will receive a new system notification for every parcel in the region they hold which has been affected by the change (below).
Any previously active banlines around affected parcel will be removed, and parcel owners will no longer be able to set parcel access restrictions via About Land > Access, as the options to do so will be greyed out (as shown below).
If a region which previously allowed parcel holders to set their own access restrictions is set to public access (by unchecking Parcel Owners Can Be More Restrictive and clicking APPLY), and then is reverted again (by checking Parcel Owners Can Be More Restrictive and clicking APPLY), all parcels on the region will revert to the access settings applied to them before any changes to region access were made at the estate level.
On Thursday, March 23rd, 2017, Linden Lab issued a new Maintenance release candidate viewer – 184.108.40.2064882 – featuring a number of bug fixes and improvements.The viewer was actually a replacement for an earlier Maintenance RC, version 220.127.116.114646, which was withdrawn after it was noted it lacked some of the expected improved functionality.
In particular, this RC viewer brings some additional options for managing Avatar Complexity (aka Jelly Dolls), gives us a new option for checking the Grid Status page and offers a number of other nice nips-and-tucks to the viewer, as well as resolving a series of bugs.
As is my usual approach the following is not intended as an in-depth review of the RC, but is intended to highlight the core changes.
Avatar Complexity Rendering Updates
There are several improvements to avatar complexity, which are outlined below.
The Options for how you render an avatar have been updated to Default (i.e. in accordance with your avatar complexity threshold setting); Always (i.e. always render the selected avatar) or Never (i.e. permanently render them as a grey imposter). These options have also been moved to a sub-menu on the right-click Avatar context menu (shown on the right).
Also, and following Firestorm’s lead, whatever setting you select for an avatar will now persist across all log-ins for the viewer, until either reset or your settings are cleared by a clean install or similar.
Finally, the viewer gets two new options for Avatar Complexity, located on the Preferences > Graphics tab. The first is a check box, Always Render Friends, which is pretty much self-explanatory: when checked your friends will always fully render, regardless of your Avatar Complexity threshold.
The second is an Exceptions button, which adds a further level of complexity control for how other avatars – including your Friends – are rendered in your view.
Using Avatar Rendering Exceptions
Clicking the Exceptions button opens a new floater, Avatar Render Settings, shown below left. This comprises a people filter for the list of names recorded on the floater (which is obviously blank when first opened), together with a + (add) button.
Clicking + will display a pop-up with two options:
Always Render A Resident
Never Render a Resident
Clicking on either of these will open the Choose Resident floater, shown above right. You can then use the Search, or Friends or Near Me tabs to select an avatar or avatars, adding them to the list on the floater. Clicking OK will add them to the Avatar Render Settings panel. The avatars will also be rendered in accordance with whichever option you used to launch the selection process (Always render or Never render).
You can also update how any avatar in your Exceptions list is displayed.
To do this, simply open the list floater via Preferences > Graphics > Exceptions, locate the name of the avatar in question (use the filter if you have a lot of avatars in your exceptions), and right-click on the avatar’s name.
This displays a sub-menu of rendering options, with the currently selected option indicated by a tick. Click on either of the other two options to change it. Note that “Default” will remove the avatar’s name for your exceptions list and display them in-world in accordance with your overall Avatar Rendering Complexity setting.
Grid Status Display Toolbar Button
Maintenance RC 18.104.22.1684882 adds a new Grid Status toolbar button to the viewer. This can be accessed via Me -> Toolbar or by right-clicking your toolbar to select Toolbar Buttons. Either of these routes will open your Toolbox floater. You can then drag the Grid Status button to the toolbar location of your choice (left, right or bottom of your screen) where it will be displayed.
Clicking on the button will open the Grid Status page in the viewer’s built-in browser, regardless of your Preferences setting for how web content is to be displayed.
In addition to the above, this RC viewer also includes the following improvements:
Inventory Offer messages now display the name of the object being offered to another avatar
Library items can now be worn via a right-click context menu, and not just drag & drop
The Snapshot floater will now remember what you did last, and open with that mode next time (until you next relog)
You can now see and change the type of block (Voice / Text / Particles) from within the block list in People floater
LLTextBox message lines will extend along with the length of the message now.
The release notes provides the following list of bug fixes with this release:
Some builds wouldn’t link to release notes. Now they do.
Other minor UI tweaks and adjustments
Removed several instances of legacy People API usage, thanks to Ansariel Hiller.
Inventory floater was missing UI for spawning new Inventory floaters. So now you can do it even if you don’t know the Ctrl+*Shift*+*I* shortcut.
Build floater used to hide behind other floaters due to wrong Z-priority. Not no more!
Appearance editor didn’t “Save as” as well as it should have, but now does.
Avatar animations wouldn’t play after several operations with editing and wearing objects, but do now.
Closing inventory window used to leave an orphaned context menu.
Active listings folder stayed active after everything was cut from it. We don’t need that confusion.
Teleport offers and Eject messages will show complete name when that’s what you’ve chose to see.
You can now remove friends even when you’re in a Groups floater looking at Members list.
I’ve not driven this viewer for more than an hour thus far, so cannot give any feedback on performance / stability. In terms of the improved features, making Avatar Complexity settings persist between log-ins is a welcome addition to the viewer. Both the Always Render Friends check box and the Exceptions options are also nice additions. .
The Grid Status button is also a handy addition, and should provide help for those of us wanting to know what is going on with the grid (when suspecting something might be wrong), but who get a little annoyed at having to manually visit the grid status page in order to do so.