| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Port from Avination
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
& box
|
| |
|
| |
|
| |
|
|
|
|
| |
scheduling terse updates will not (and does not) update shape information in the viewer
|
|
|
|
| |
SOG and SOP. Should have no functionality changes.
|
|
|
|
| |
and SOP.RemoveSittingAvatar()
|
|
|
|
|
| |
This reverts commit c8f0d476d2f775ba4d7afca12eeff527b46bb8e2.
On reconsideration, I think this is less readable since immediately following code still sets SitTargetAvatar directly
|
| |
|
|
|
|
|
|
|
| |
property rather than being repeated in SP.
This also makes the detection in SP.FindNextAvailableSitTarget() and SendSitResponse() identical.
Previously they varied slightly (SendSitResponse didn't check for an older type of invalid quaternion) but the practical effect is most probably zero.
|
|
|
|
|
|
| |
avatars rather than throwing an exception.
Extends sitting avatar regression tests to test new sitters information
|
|
|
|
|
|
| |
This prevents a stack overflow where a get position on the avatar will refer to the attachment which will in turn refer back to the avatar.
This required recording of all sitting avatars on a prim which is done separately from recording the sit target avatar.
Recording HashSet is null if there are no sitting avatars in order to save memory.
|
|
|
|
| |
instead of attachmentpoint magic numbers.
|
|
|
|
| |
object UUID rather than local id, since UUID doesn't potentially vary between simulator starts.
|
|
|
|
|
|
|
|
| |
point. HUDs attachment points are private.
Change SOP.SendFullUpdateToClient() and SoundModule.PlayAttachedSound() to use this rather than different magic number formulations.
This also corrects a bug in PlayAttachedSound() where the code assumed that all attachment points over 30 were HUDs.
It appears this is no longer true with Neck and Root (Avatar Center)
|
| |
|
|\ |
|
| |
| |
| |
| | |
loads roots before children like MySQL does.
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
reordered.
This was because the parts in scene objects were sometimes not serialized in link order.
This is perfectly fine since the parts still have the right link numbers, but an extra fix to adjust for this
had not been done in the SerialiserModule methods that OAR loading used.
Add regression test for same.
Addresses http://opensimulator.org/mantis/view.php?id=5948, http://opensimulator.org/mantis/view.php?id=5749
|
|
|
|
|
|
| |
SetPhysicsAxisRotation()
sop.PhysActor can currently become null at any time.
|
|
|
|
|
|
|
|
| |
rather than setting phantom.
This was an oversight when removing some race conditions from PhysicsActor setting recently.
Regression tests extended to probe this code path.
Extending regression tests required implementation of a BasicPhysicsPrim (there was none before). However, BasicPhysics plugin is still of no current practical use other than to fill in as a component for other parts of regression testing.
|
|
|
|
| |
non-physical
|
| |
|
|
|
|
|
|
| |
ever using the root prim one, store on SOG instead.
This reduces pointless memory usage.
|
|
|
|
|
|
| |
only ever using the root part entry.
This eliminates some pointless memory use.
|
| |
|
|
|
|
|
|
|
|
| |
or attachments.
Return relative position to root prim rather than 0,0,0.
Should fix same issue with llGetLocalPos()
http://opensimulator.org/mantis/view.php?id=5951
|
|
|
|
|
|
| |
prim collision status
factor out common SOP physics scene adding code into a common SOP.AddToPhysics() that is the counterpart to the existing RemoveFromPhysics()
|
|
|
|
|
|
|
|
| |
null then assume it was still not null in later code.
Another thread could come and turn off physics for a part (null PhysicsActor) at any point.
Had to turn off localCopy on warp3D CoreModules section in prebuild.xml since on current nant this copies all DLLs in bin/ which can be a very large number with compiled DLLs
No obvious reason for doing that copy - nothing else does it.
|
| |
|
|
|
|
|
|
| |
http://opensimulator.org/mantis/view.php?id=5893
Signed-off-by: nebadon <michael@osgrid.org>
|
|
|
|
|
|
|
|
|
|
|
| |
update when scene objects have been deleted.
At least on mono 2.6.4, running GC.Collect() is not guaranteed to force gc of all objects when run in the same method where those objects had references.
Therefore, GC.Collect() is now being done in the per-script teardown of ObjectTortureTests.
In addition, scene loop update is being run after garbage collection in order to clean out the viewer update list of scene objects in the SceneGraph.
These measures mean that scene objects/parts are now garbage collected after a test run if deleted from the scene, resulting in a much better memory usage report (though probably still not very accurate).
However, deletion takes a very long time - what's really needed is to find out now why the entire scene isn't being GC'd by this measure.
This change hasn't yet been applied to the other stress tests.
|
|
|
|
| |
This is not valid in the case of BasicPhysics which can return a null PhysicsActor (though I think it should really return a do-nothing PhysicsActor).
|
|
|
|
| |
triggering events on a potentially null Scene
|
|\ |
|
| |
| |
| |
| | |
texEntry) for region modules
|
| |
| |
| |
| |
| | |
rotating physical objects. This does not use physics. Currently the rate
of change is determined as 1 / (PI * Strength).
|
| |
| |
| |
| | |
location of the user's UAS. This corrects an earlier design which had some cases pointing to the profile server. WARNING: CONFIGURATION CHANGES in both the sims (*Common.ini) and the Robust configs (Robust.HG.ini). Please check diff of the example files, but basically all vars that were pointing to profile should point to the UAS instead and should be called HomeURI.
|
| | |
|
| |
| |
| |
| | |
early access to changed parameters.
|
|/
|
|
| |
module access.
|
|
|
|
| |
external as a property
|
|
|
|
|
|
|
|
|
| |
boolean setting in the OpenSim.ini config [Startup] section.
Naturally, default is true.
When set to false, "phantom" flags on prims can be set as usual but all prims remain phantom.
This setting is for test purposes.
This switch does not affect the collision of avatars with the terrain.
|