Re: [opensource-dev] 'justabouteverything' (STORM-1921, STORM-1928, STORM-1927)

[Adam Moss]

This branch
https://bitbucket.org/tofu_linden/just-about-everything2
and the independent fix branches of which it is comprised
https://bitbucket.org/tofu_linden/better-ssao4
https://bitbucket.org/tofu_linden/faster-dof
https://bitbucket.org/tofu_linden/vwr-29175-fog-fixes
... have been updated relative to the latest changes in
viewer-development-materials, for the benefit of TPVs (& LL if ever starts
caring again).

To recap, these offer better quality and faster depth-of-field effect,
better quality screen-space ambient occlusion, and unbroken haze, fog and
atmospherics on water and fullbright faces.

Cheers,
--Adam / 'Tofu'

On 29 June 2013 21:38, Adam Moss  wrote:

> Ditto now with:
> https://bitbucket.org/tofu_linden/just-about-everything2
> Updated to the latest viewer-release (w/materials).
>
> Cheers,
> --Adam
> 'Tofu Buzzard'
>
>
> On 10 March 2013 16:30, Adam Moss  wrote:
>
>> I've put ALL of my finished rendering fixes and speedups on this one
>> branch:
>> https://bitbucket.org/tofu_linden/justabouteverything
>>
>> It's all been reviewed.  I've put it in one place based on third-hand
>> information that merging the fixes together with viewer-development was
>> hard (it was truly trivial - hmm!)
>>
>> It's based on the latest viewer-development.
>>
>> I'd appreciate if it could be taken upstream or whatever.
>>
>> Cheers,
>> --Adam
>> 'Tofu Buzzard'
>>
>>
>
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

[opensource-dev] The Current Outfit Folder and you!

[Nyx Linden]

As we’ve been rolling out Server Side Appearance, a few reports have
been coming in about specific users having issues with the current outfit
folder. The good news is that very few users are reporting serious issues.
The bad news is that it looks like some viewers are not handling the COF
quite correctly. To help narrow down the possible issues below is a list of
how the COF should be handled, please take some time and look over the
following behaviors to make sure your viewer performs in a way that is
compatible with the standards defined by the secondlife viewer. This list
shows how our viewer handles the COF, which defines the protocol that is
compatible with the Second Life service. As long as these guidelines are
followed, your viewer should be compatible with other installed viewers and
with the Server Side Appearance system. If you deviate substantially from
this protocol, it could interfere with our ability to provide normal and
expected functionality. As always if you have any questions or concerns
regarding the appearance system, please do not hesitate to reach out to me
directly.

Keep reading to the end to get additional information on details of future
releases from the Sunshine team!


   1.

   There should be only one folder of type ‘FT_CURRENT_OUTFIT’.
   1.

  The ‘Current Outfit’ folder should be the special type
  ‘FT_CURRENT_OUTFIT’. There should be only one such folder, its
name should
  be ‘Current Outfit’ and it should be a child of the root inventory folder.
  2.

  Please verify the following items in your viewer:
  1.

 Verify that there is not a code path for the end user to create or
 delete this folder.
 2.

 Verify that no code path would allow this folder to be duplicated,
 automatically or by user interaction
 3.

 Verify that no code path exists that would allow this folder to be
 moved out of the root of the inventory.
 4.

 Verify that this folder will only be created on login, and only if
 it does not already exist.
 5.

 Verify that no code path can rename this folder.
 2.

   The current outfit folder (COF) is the authoritative source for what the
   user should be wearing
   1.

  Everything the user should be wearing should have a link in the COF.
  2.

  This should be kept up to date at all times (not just login/logout),
  in case of viewer crashes
  3.

  The contents of the COF should be what is loaded and worn for the
  avatar on login.
  4.

  Please verify the following:
  1.

 Verify that all clothing, body part, and attachments that a user
 should be wearing have a link in the current outfit folder
 2.

 Verify that on changing outfits, this remains true once all
 network operations resolve
 3.

 Verify that the avatar’s appearance is read from the COF and
 loaded appropriately on login, without modification, except
if the COF was
 left in a bad state.
 1.

Note that inventory changes are most likely to fail during
times of heavy network usage - this includes login.
3.

   All links in the COF should be “valid” links when at all possible.
   1.

  “Valid” links make a reference to an existing item in the user’s
  inventory tree.
  2.

  Links can be presented as broken if they refer to an item in the
  library, an item that has been deleted, or cannot be properly
fetched, but
  viewers should avoid creating these links if possible
  3.

  Please verify the following:
  1.

 When a user wears an item from the library or from an object’s
 inventory, it is copied into their inventory, and a link is
created to the
 newly created instance.
 2.

 Links are not copied to the COF or worn if they are broken.
 3.

 The user has sufficient feedback to see which links are broken.
 4.

   The COF should maintain a ‘valid’ appearance
   1.

  A valid appearance requires exactly one link to each type of body
  part: shape, skin, hair, eyes.
  2.

  Clothing and attachments can be added up to the normal limits defined
  in the latest release viewer.
  3.

  Verify the following:
  1.

 Verify that there is no code path that will result in multiple
 body parts of the same type  being linked in the COF simultaneously
 2.

 Verify that even when an outfit is replaced, body parts will not
 be removed unless they are being immediately replaced. Do not
assume the
 replacement outfit necessarily has all body parts.
 3.

 Verify that the viewer will not allow more total attachments than
 the Linden release viewer allows.
 4.

 Verify that the viewer will not allow more clot

Re: [opensource-dev] Viewer branches and their repositories

[Oz Linden (Scott Lawrence)]

On 2013-07-18 05:20 , Henri Beauchamp wrote:

>See
>https://wiki.secondlife.com/wiki/Linden_Lab_Official:Viewer_Source_Repositories

Ah, yes, thank you... What about putting a link to that page on the
https://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers
page ?...

The alternate viewers page is for people who want to download and run 
viewers, not develop them, so I don't think it's appropriate.


I did add a link from the primary wiki page on getting viewer source: 
https://wiki.secondlife.com/wiki/Get_source_and_compile


--
*Scott Lawrence* | /Director of Open Development/
Skype ozlinden  | Second Life Oz Linden 



Linden Lab| Makers of Shared Creative Spaces 
SECOND LIFE  | PATTERNS 
 | CREATORVERSE  | 
DIO  | VERSU 
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges