| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
to 1 from 3
This is one step towards reducing hud glitches on region crossing, since the viewer fails to display prims if it receives child full updates before the root prim full update
This commit also introduces a mechanism in LLClientView to stop child attachment updates ever going out before the root one
This is a very temporary mechanism and will be commented out when the next step of the fix (to give root prims higher udpate priority) is committed
This code is a foreport from the equivalent changes in 0.6.9-post-fixes
|
| |
|
|
|
|
| |
* Bug fix in TPs across neighboring regions: bug was introduced when getting rid of crashed sessions.
|
|
|
|
| |
a group of prims.
|
|
|
|
|
| |
This is going to be the right behaviour in all cases, I should think.
This means that avatars in region when an oar is loaded do not lose their attachments
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
| |
stored in regionsettings. Upon generation of a new tile image, the old one is deleted. Tested for SQLite and MySql standalone.
* Fixed small bug with map search where the local sim regions weren't found.
|
|
|
|
|
|
| |
home and position info in the presence service. WARNING: I violated a taboo by deleting 2 migration files and simplifying the original table creation for Presence. This should not cause any problems to anyone, though. Things will work with the new simplified table, as well as with the previous contrived one. If there are any problems, solving them is as easy as dropping the presence table and deleting its row in the migrations table. The presence info only exists during a user's session anyway.
BTW, the Meshing files want to be committed too -- EOFs.
|
|
|
|
| |
proper field in AgentCircuitData instead
|
| |
|
|
|
|
| |
carried along
|
| |
|
|
|
|
|
| |
helper into Scene, since that is less evil than exposing m_storageManager
to the public.
|
| |
|
| |
|
|
|
|
|
|
| |
is fully rezzed and all scripts in it are instantiated. This ensures that link
messages will not be lost on rez/region crossing and makes heavily scripted
objects reliable.
|
| |
|
|
|
|
| |
AttachmentsModule
|
|
|
|
| |
Signed-off-by: dahlia <dahliaTrimble@gmail.removeme.com>
|
|
|
|
|
| |
This allows scripts to set WindLight parameters for clients connecting
to a region. Currently, this is only supported by the Meta7 viewer.
|
|
|
|
| |
used on first run and not only later.
|
|
|
|
|
| |
* Changed the null check back in estate manager setup but fixed the case for an existing account being found
* Implemented SetPassword() in the SimianGrid auth connector
|
|
|
|
| |
and a misleading error message (in grid mode it tries to get a user, not create one)
|
|
|
|
| |
can't prompt for estate owner in unit tests
|
|
|
|
|
|
|
| |
of a region and joining it to an existing estate or creating a new estate,
as well as creating an estate owner if in standalone, and assigning estate
owners. In Grid mode, existing users must be used. MySQL ONLY!!!! so far, as
I can't develop or test for either SQLite or MSSQL.
|
|
|
|
|
| |
defaults. Adding code to facilitate estate creation / managemment as part of
first time start up
|
|
|
|
| |
Scene and SceneGraph. This was the only change in this patch to keep it isolated from other recent changes to the same set of files.
|
|
|
|
| |
GetAvatars have been removed to consolidate locking and iteration within SceneGraph. All callers which used these to then iterate over presences have been refactored to instead pass their delegates to Scene.ForEachScenePresence(Action<ScenePresence>).
|
|
|
|
|
|
| |
eliminating option to return the actual list. Callers can now either request a copy of the array as a new List or ask the SceneGraph to call a delegate function on every ScenePresence. Iteration and locking of the ScenePresences now takes place only within the SceneGraph class.
This patch also applies a fix to Combat/CombatModule.cs which had unlocked iteration of the ScenePresences and inconsistent try/catch around the use of those ScenePresences.
|
| |
|
|
|
|
| |
AttachmentsModule
|
|
|
|
| |
AttachmentsModule
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|\ |
|
| |
| |
| |
| | |
need to rationalize method names later
|
| | |
|
|/
|
|
|
|
| |
CheckForSignificantMovement()
* Removed a lock on "return m_neighbours.Count" in GetInaccurateNeighborCount(). Dictionary<>.Count by itself does not benefit from locking
|
|
|
|
|
|
|
|
| |
root prim until right clicked (or otherwise updated).
The root cause of this problem was that multiple ObjectUpdates were being sent on attachment which differed enough to confuse the client.
Sometimes these would eliminate each other and sometimes not, depending on whether the scheduler looked at the queued updates.
The solution here is to only schedule the ObjectUpdate once the attachment code has done all it needs to do.
|
|
|
|
| |
be rewritten, because they are doing agent manipulations in the wrong way, so they're fairly meaningless.
|
|
|
|
| |
this needs more testing, but everything is there.
|
|\
| |
| |
| | |
into presence-refactor
|
| |\
| | |
| | |
| | | |
This brings presence-refactor up to master again
|
| | | |
|
|/ /
| |
| |
| | |
CreatorID, it doesn't modify database backends or OAR files to support storing/loading it
|