| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
| |
used by the TestRezCoalescedObject() regression test.
This structure matches the existing one for SceneObjects and will allow code to be reused by the uuid gatherer, other tests, etc.
Test is not yet fully implemented due to a bug in rezzing coalesced objects where they all get the same name as the item.
Only one object should get the same name as the item, which appears to be the one selected last when the the objects were coalesced in the first place.
This bug will be addressed shortly.
|
|
|
|
| |
populating the local id scene object index instead of each part's local id
|
|
|
|
| |
well as Entities
|
|
|
|
|
|
|
|
| |
prim (e.g. a SOG with 3 prims would have the action executed three times).
To do this, a new SceneObjectGroupsByFullID index in SceneGraph which just index's prims by their root part UUID, in order to avoid the inefficiency of filtering existing lists.
Existing callers to SceneGraph.ForEachSOG() did not fail due to the multiple per SOG action executions - they were probably just much less efficient.
Code suggests that no callers expected ForEachSOG() to execute actions on sog multiple times
|
|
|
|
| |
are indexing each part's UUID, not just the root part.
|
| |
|
| |
|
|
|
|
|
| |
anything) and clean up the code in AddNewClient (so Appearance only
gets assigned once, not three times).
|
|
|
|
|
|
| |
used by a 3rd party region module and contains non-obvious attachment specific code
There are no functional changes. UpdateAttachmentPosition() is adapted to the new approach of only saving attachment state on logout
|
|
|
|
| |
a sitting avatar should have it's offset position added to the scene object, not its absolute position
|
|
|
|
|
|
|
| |
save properly, as will the results of a resizer script working. Attachment
positions are no longer saved on each move, but instead are saved once on
logout. Attachment script states are saved as part of the attachment now
when detaching.
|
| |
|
|
|
|
|
|
| |
troubleshooting. It MUST be combined with e.StackTrace, or e.ToString() must
be used.
Fix one more instance of that cr.p
|
| |
|
|
|
|
| |
MapAndArray collection
|
|
|
|
| |
being migrated to AttachmentsModule
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
script state enum to reflect recent changes.
|
| |
|
|
|
|
|
|
| |
Scene.UpdatePrimPosition() and move into AttachmentsModule
This allows region modules to change attachment positions.
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Resolve merge conflicts
Conflicts:
OpenSim/Region/Framework/Scenes/SceneGraph.cs
|
| |
| |
| |
| | |
sticking around
|
|/
|
|
| |
conditions in linking and unlinking
|
|
|
|
|
|
|
|
| |
and move into SceneGraph.AddNewSceneObject()
The new SceneGraph method is more consumable by region modules that want to extract objects from inventory and add them to the scene in separate stages.
This change also reduces the number of redundant client updates scheduled when an object is rezzed directly by a script or region module
This code does not touch direct rez by a user
|
| |
|
| |
|
| |
|
|
|
|
| |
used, but made for a very mispleading read of the code in the callers.
|
|
|
|
|
|
|
| |
nonworking ownership assignment in SOG, which messed things up before.
No longer trust the client to send the ID of the person something is copied
as, since it allows to run a script with someone else's permissions. Properly
adjust inventory ownership and perms.
|
| |
|
|
|
|
|
|
| |
isn't present in the presence dictionary
the code to do this was there but was being circumvented by newmap[agentID] before the check actually took place
|
|
|
|
| |
list of all locations fresh for every scene presence on every frame, we will instead compute the list once every 50 frames and send to all connected presences at that time. Also, we only add 60 items to the list when there are more than 60 presences in the scene. For 1000 users, this change yields a 99.8% reduction in list processing and a 98% reduction in network bandwidth for coarse locations.
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
that uuid is already in the scene
this means that we don't perform pointless work
|
|
|
|
|
|
| |
successfully adding an object rather than true, in defiance of its method documentation
This meant that the returns were inconsistent - false would be returned both for various scene object failure conditions (e.g. root part was null) and if the object was successfully added.
|
|
|
|
| |
now only be for simultaneous add/removes of scene presences from the scene.
|
| |
|
|
|
|
|
|
| |
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
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
need to rationalize method names later
|