| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
The only times when ParentGroup might be null is during regression tests (which might not be a valid thing) and when scene objects are being constructed from the database.
At all other times it's not possible for a SOP not to have a SOG parent.
|
|
pointless duplication of identical values
|
|
This does a tiny bit to reduce code complexity, memory requirement and the cpu time of pointlessly setting this field to the same value in every SOP
|
|
BestAvatarResponsiveness prioritizer.
|
|
and currently used for all of an avatars attachments by the other
policies. Also changed the way items are pulled from the update queues
to bias close objects even more.
|
|
per Melanie's very good suggestion. The immediate queue is
serviced completely before all others, making it a very good
place to put avatar updates & attachments.
Moved the priority queue out of the LLUDP directory and
into the framework. It is now a fairly general utility.
|
|
initialized scene presence. Not sure why we are dumping updates
to a client that isn't there yet...
|
|
a warning. There appears to be a race condition on slow logins
that attempts to prioritize before the scene presence is fully
initialized.
|
|
|
|
improved networking performance.
Reprioritization algorithms need to be ported still. One is
in place.
|
|
|
|
improved networking performance.
Reprioritization algorithms need to be ported still. One is
in place.
|
|
improved networking performance.
Reprioritization algorithms need to be ported still. One is
in place.
|
|
|
|
|
|
|
|
|
|
By the time a scheduled update is triggered, a sog may have been removed from the scene. This change prevents NullReferenceExceptions in these situations.
|
|
before it can be updated
|
|
policy
|
|
before child prims.
This was originally a fix for huds, since child prims fail to display if the viewer doesn't receive the root prim update first.
However, on the advice of jhurliman, this has been done for all objects, both ordinary and attachments.
The separate mechanism in LLClientView which prevents child prim updates being sent out first is still present temporarily.
This is a foreport of the equivalent fix in 0.6.9-post-fixes, though that was for attachments only.
|
|
update priority policy
|
|
Prioritizer.cs
* Simplified the interest management code to make it easier to add new policies. Prioritization and reprioritization share code paths now
* Improved the distance and front back policies to always give your avatar the highest priority
|
|
deprioritizes
static prims, creating a hierarchy as follows:
0 == own avatar < other avatars < pysical prims < static prims
For a child agent, simply acts like FrontBack
|
