Update, May 23rd: version 22.214.171.1246444 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 – 126.96.36.1996444 – 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 – 188.8.131.524882 – featuring a number of bug fixes and improvements.The viewer was actually a replacement for an earlier Maintenance RC, version 184.108.40.2064646, 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 220.127.116.114882 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.
On Friday, February 3rd, Linden Lab released the latest Maintenance RC viewer – version 18.104.22.1683359 – which brings with it another round of updates and fixes, together with a couple of new features requested by users, one of which could prove popular for creators and builders: the ability to select default folders for saving uploads.
Also for builders, the RC includes some long-awaited fixes to the build floater / objects when building. Several other niggles people have had with the viewer are also fixed with this update, making it a handy set of improvements to have.
The following is not intended as an in-depth review of the RC, but is intended to highlight the core changes.
Custom Folders for Uploads
With Maintenance RC 22.214.171.1243359 users can now select their own preferred inventory folders into which uploads – images / textures, sounds, animations and mesh models are saved by default (rather than having all textures + images go to Textures for example).
To set a custom folder for an upload type:
Go to Inventory and right-click on the desired folder.
Select Use As Default For. This opens a sub-menu of upload types (shown on the right).
Click on the type of upload you wish to always save to that folder.
Note that this only applies to uploads: images / textures, mesh models, etc., received via transfer will still go to the their “default” folders.
So, for example, an animation passed to you in-world by someone else will still go to your Animations folder, regardless of any custom destination you have set for animation uploads.
You can also review which custom folders you have set at any time via Preferences > Uploads, a new tab in the preferences floater. This list updates dynamically as you select / change custom locations for your uploads.
Other Requested Fixes / Updates
There are several other oft-requested updates are also included in the RC:
A long-term and understandable annoyance among role-players / combat players is that a change made by the Lab some time ago meant that the Damage icon would not show in parcels that were damage-enabled. This has now been reverted.
The issue of the Sun sometimes appearing to jump around rather than moving incrementally has been fixed.
The Block list has been updated so that the last name on the list once again displays correctly, and a tally has been added to show number of avatars / objects blocked, and total limit (see right).
Avatars should now correctly display after a fresh inventory fetch.
Changes in wearables should now properly save.
Build / Edit Improvements
The following build / edit fixes and improvements have also been made to the viewer:
Repeats per meter value is now correctly saved.
An object created when a linkset is open is now shown in the linkset list.
Select Face will now show selection for all faces until such time as an individual face is selected.
The contents of any object worn from the ground should now correctly update.
The Script Debug Floater should now be useful once more.
Other Updates and Improvements
The release notes for the viewer also draw attention to the following updates:
Hanging texture downloads have been cleaned-up for better performance (via contribution from Ansariel Hiller).
Viewer Login will no longer save password when it is not supposed to.
Beacons will once more show when in Mouselook.
Teleport location selected from World Map no longer omits Z value.
Grid selection short cut at login is fixed.
Crash Fixes in LLPanelEditWearable::isDirty(), LLFloaterIMContainer::visibleContextMenuItem(), opening many scripts.
/displayname and /completename no longer change when toggling “View Display Names”.
Link added to Events in World menu.
Full details on the viewer updates, included a list of resolved MAINT JIRAs can be found in the viewer release notes and download page. Note that as they are MAINT (LL internal), not all of the JIRAs may be open to public view.
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.
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.