Second Life Project Notice Viewer version 184.108.40.2063211 – July 8 – From the release notes: (paraphrasing) A new Notifications floater separates incoming notifications into; System, Transactions, Invitations, and Group notices. This provides a better way to view, interact with, prioritize, and manage incoming notices, especially for busy residents.
The Lindens are giving a special thank you to Aki Shichiroji for initial feature design on this feature.
This is a PROJECT Viewer, so now is the time to provide feedback. If you deal with a lot of notifications in your use of SL, this is the time for you to try this viewer and provide your input on how it works and what may need to change. Be sure you include your use case that supports your recommended change.
Whirly Fizzle and Jessica Lyon like this feature… both are sane users that I class in the power user group. So, I consider theirs a decent endorsement of the feature.
You may know that how avatar game damage is reported and when it is scored is incoherent. At this point the Lindens are working on fixing it. That means how it works now is not exactly what was intended.
People have noticed that in the recent Linden viewers damage is accumulated while in safe no damage areas. In some of those areas damage accruing is not being reported. An avatar just surprisingly is teleported home because of damage sustained with no clue what is happening.
Third Party Dev’s think parts of the interest list are broken. The interest list tells the viewer what to download and render. It has a priority system so that the things nearest you and in your field of view download and render first. That has not been working so well in recent releases.
However, to fix the problem the Lab needs to see cases of the problem and to have the steps needed to reproduce the problem. That they are not seeing the problem tells us something about their use of Second Life.
We use SL more than they do, so we are more likely to run into the problem. Thus we need to provide the information. Getting the Lindens to spend more time in SL searching for a nebulous problem takes away from productive work time.
One of the big problems to solve in determining where to start looking for the problem is learning whether interest list messages are not being sent, failing to arrive, or being poorly handled by the viewer verses whether the asset downloads are failing and slowing the render process. On screen either would look about the same, I think. So, I think this moves the problem search into the geeks realm.
BUG-7084 – Prim properties visually revert to an earlier state since Interesting.
BUG-9487 – Avatar Shapes failing to load e.g. (Missing/corrupt shape in inventory). In this one it looks like the shape asset is being corrupted. But, it is unclear whether the asset is corrupted during editing in a laggy region (unlikely) or the local inventory pointer or cached copy of the item is being corrupted.
To fix the problem reliable steps to reproduce the problem are needed. When the steps are not reliably consistent it is almost always because some factor is being missed/omitted.
*If you contribute to the JIRA on this attachment issue make sure you can reproduce the problem in the RC Big Bird Viewer. Reproducing it in any other viewer is not really helpful. If you report the problem in the Firestorm JIRA THEN use Firestorm.