| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
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
|
