| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
would make the non-physical prim phantom rather than part of the physics object.
On region restart, the whole object would become physical as expected.
Observed behaviour from elsewhere is that all prims in a new linkset should take on the status of the root prim.
Add regression test for this behaviour.
|
| |
|
|
| |
methods directly rather than through Scene may allow race conditions.
|
| |
|
|
| |
Signed-off-by: nebadon <michael@osgrid.org>
|
| |
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
the 'root' part.
|
| |
|
|
|
|
| |
ContainsPart method and remove method duplication.
HasChildPrim is also misleading since the 'root' prim can also be returned.
|
| |
|
|
|
|
|
|
|
|
|
| |
measurement period and an idealised frame time.
The previous lines-per-second measurement used for top scripts report was inaccurate, since lines executed does not reflect time taken to execute.
Also, every fetch of the report would reset all the numbers limiting its usefulness and we weren't even guaranteed to see the top 100.
The actual measurement value should be script execution time per frame but XEngine does not work this way.
Therefore, we use actual script execution time scaled by the measurement period and an idealised frame time.
This is still not ideal but gives reasonable results and allows scripts to be compared.
This commit moves script execution time calculations from SceneGraph into IScriptModule implementations.
|
| |
|
|
| |
http://opensimulator.org/mantis/view.php?id=5404
|
| |
|
|
|
|
| |
exception and constant complaints in v3 viewers).
Aims to address http://opensimulator.org/mantis/view.php?id=5878
|
| |
|
|
|
| |
This illustrates that references to Scene, SOG, etc. are not currently being released when a stress test ends (or at regression test end in general).
This means even the current stress tests take much more memory than they need, a problem that will have to be addressed.
|
| |
|
|
| |
Pickup the max physical prim size in Scene to make it uniform since adding code to get default size from the OpenSim*.ini.
|
| |
|
|
| |
This will show details about a part with the given uuid if it's found.
|
| |
|
|
| |
same grid don't have the publisher as owner.
|
| |
|
|
|
| |
rotating physical objects. This does not use physics. Currently the rate
of change is determined as 1 / (PI * Strength).
|
| |
|
|
| |
temponrez flag
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
created in that client session, or if no other action has been performed on the object.
There were two problems here:
1) On object group update, we looked for the group is the IClientAPI group cache rather than in the groups service. This fails to groups created newly in that session
2) On object group update, we weren't setting the HasGroupChanged flag. This meant that the change was not persisted unless some other action set this flag.
This commit fixes these issues and hopefully addresses http://opensimulator.org/mantis/view.php?id=5588
This commit also moves HandleObjectGroupUpdate() to the GroupsModule from the Scene.PacketHandlers.cs file
|
| |
|
|
| |
GetGroupByPrim() rather than retrieving GetEntities() and inspecting the entire list
|
| |
|
|
| |
These were entirely unused.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
prim update to only triple queuing. Existing method was:
1. Schedule prim for update, adding to scene update list
2. Update on SOGs during heartbeat queues update onto each SceneViewer
3. Update on SPs during heartbeat queues update onto each IClientAPI
4. ProcessEntityUpdates queues updates into UDP send stack
Now the SceneViewer has been eliminated so updates are scheduled at any
time and then put onto the IClientAPI priority queues immediately during
SceneGraph.UpdateObjectGroups.
|
| |
|
|
| |
properties packet sends and so one part is not telling a different part what to do. That should be up to the SOG to manage permissions on its parts and notify clients when one of them changes.
|
| |\ |
|
| | | |
|
| |/
|
|
| |
terse update
|
| |
|
|
| |
packet per prim. More to come as we change to make use of this.
|
| | |
|
| |
|
|
| |
numbered properly even when sets are linked to sets.
|
| |
|
|
|
|
| |
from previous commit which sort out which iterator is used are left
intact. A discussion is needed as to what constitutes an avatar vs a
ScenePresence.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
the 3 iteration functions so more of them are using the correct
iteration for the action they are performing. The 3 iterators that seem
to fit all actions within OpenSim at this time are:
ForEachAvatar: Perform an action on all avatars (root presences)
ForEachClient: Perform an action on all clients (root or child clients)
ForEachRootClient: Perform an action on all clients that have an avatar
There are still a dozen places or so calling the old
ForEachScenePresence that will take a little more refactoring to
eliminate.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
UpdateFlag is now referenced/used only within SOP and SOG. Outsiders are
using ScheduleFullUpdate, ScheduleTerseUpdate or ClearUpdateSchedule on
SOP consistently now. Also started working toward eliminating those
calls to ScheduleFullUpdate, ScheduleTerseUpdate or ClearUpdateSchedule
from outside SOP in favor of just setting properties on SOP and let SOP
decide if an update should be scheduled. This consolidates the update
policy within SOP and the client rather than everywhere that makes
changes to SOP. Some places forget to call update while others call it
multiple times, "just to be sure".
UpdateFlag and Schedule*Update will both be made private shortly.
UpdateFlag is intended to be transient and internal to SOP so it has
been removed from XML serializer for SOPs.
|
| |
|
|
| |
We always use SOP.Rotation instead
|
| |
|
|
| |
than calling SOP.OffsetForNewRegion
|
| | |
|
| | |
|
| |
|
|
|
| |
SP still has an implementation but this is now just a public method on SP rather than an abstract one in EntityBase.
No point making the code more complex until it actually needs to be,
|
| |
|
|
| |
are only sent to affected clients.
|
| |
|
|
| |
This is moved into ScenePresence for now as a general facility
|
| |
|
|
|
|
| |
reflect what it actually does
This also makes it consistent with some other methods that send data to the client.
|
| |
|
|
|
|
|
| |
SOG.ClearPartAttachmentData() is called.
Even though we don't use these on rez they are still present after an unlink, after which selecting them causes various viewers to crash
Hopefully really does address http://opensimulator.org/mantis/view.php?id=5664
|
| |
|
|
| |
It's never possible for SOG to have no RootPart, except in the first few picosends of the big bang when it's pulled from region persistence or deserialized
|
| | |
|
| |
|
|
| |
stored in the root part's state field.
|
| |
|
|
| |
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
|
| |
|
|
| |
AttachmentsModule.DetachSceneObjectToGround() and remove redundant code
|
| |
|
|
| |
AttachmentsModule.DetachSingleAttachmentToInv()
|
