| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
|
|
|
|
|
|
| |
Fixes: Undo, T-pose of others on login, modifiedBulletX works again, feet now stand on the ground instead of in the ground, adds checks to CombatModule. Adds: Redo, Land Undo, checks to agentUpdate (so one can not fall off of a region), more vehicle parts. Finishes almost all of LSL (1 function left, 2 events).
Direct flames and kudos to Revolution, please
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|\ |
|
| |\ |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |/
|/| |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
| |
callers can use it
|
|
|
|
|
|
|
|
|
|
| |
When an object was deleted, the remove script instance call was aggregating the scripting events as normal.
This would queue a full update of the prim before the viewer was notifed of the deletion of that prim (QuitPacket)
On some occasions, the QuitPacket would be sent before the full update was dequeued and sent.
In principle, you would think that a viewer would ignore updates for deleted prims. But it appears that in the Linden viewer (1.23.5),
a prim update that arrives after the prim was deleted instead makes the deleted prim persist in the viewer. Such prims have no properties
and cannot be removed from the viewer except by a relog.
This change stops the prim event aggregation call if it's being deleted anyway, hence removing the spurious viewer-confusing update.
|
| |
|
|
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
|
|
|
|
| |
CRs cleaned from patch
Signed-off-by: Melanie <melanie@t-data.com>
|
|
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
|
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
|
|
|
|
| |
Applied with whitespace cleanup
Signed-off-by: Melanie <melanie@t-data.com>
|
|
|
|
|
|
| |
Revert "[PATCH] Adds llCollisionFilter"
This reverts commit eab2b4c6a96cd5b2a0f079f27a9c2ac15273d3f0.
|
|
|
|
| |
Thank you, Revolution. Applied with minor changes.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
pass script state and assembly again properly. Reintroduce respecting tht
TrustBinaries flag. Changes the interregion protocol! No version bump
because it was broken anyway, so with a version mismatch it will simply
stay broken, but not crash. Region corssing still doesn't work because
there is still monkey business with both rezzed prims being pushed across
a border and attached prims when walking across a border. Teleport is
untested by may work.
|
|
|
|
| |
normally again.
|
|
|
|
| |
one fixes the situation where the object on the server is moving but no updates are being sent.
|
|
|
|
|
|
| |
AttachPoint
* LLClientView.CreateImprovedTerseBlock() now uses AttachPoint and does the proper high-low swap (this should fix disappearing attachment pieces)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* Change the PhysicsCollision callback for objects to send full contact point information. This will be used to calculate the collision plane for avatars
* Send the physics engine velocity in terse updates, not the current force being applied to the avatar. This should fix several issues including crouching through the floor and walking through walls
|
| |
|
|
|
|
|
|
|
| |
default region, any region" before giving up
* Hip offset should have been added not subtracted (it's a negative offset). This puts avatar feet closer to the ground
* Improved duplicate checking for terse updates. This should reduce bandwidth and walking through walls
|
|
|
|
|
|
| |
drifting prims/avatars
* Added contacts_per_collision to the ODE config section. This allows you to reduce the maximum number of contact points ODE will generate per collision and reduce the size of the array that stores contact structures
|
|
|
|
| |
avoid floating away forever until a key is pressed (deviates from SL behavior in a hopefully good way)
|
|
|
|
| |
mitigate some of the rubberbanding issues while we are sending incorrect time dilation values
|
| |
|
|
|
|
|
|
| |
in faster than the surrounding scene
* Adds duplicate tracking for SceneObjectParts and ScenePresences to avoid sending out duplicate ImprovedTerseObjectUpdate packets
|
|
|
|
|
|
|
|
|
|
| |
Parallel. This is quite possibly the source of some deadlocking, and at the very least the synchronous version gives better stack traces
* Lock the LLUDPClient RTO math * Add a helper function for backing off the RTO, and follow the optional advice in RFC 2988 to clear existing SRTT and RTTVAR values during a backoff
* Removing the unused PrimitiveBaseShape.SculptImage parameter * Improved performance of SceneObjectPart instantiation * ZeroMesher now drops SculptData bytes like Meshmerizer, to allow the texture data to be GCed * Improved typecasting speed in MySQLLegacyRegionData.BuildShape()
* Improved the instantiation of PrimitiveBaseShape
|
|
|
|
| |
avoiding locking and copying the list each time it is accessed
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
packets to fill in the data more accurately and avoid allocating memory that is immediately thrown away
* Changed the Send*Data structs in IClientAPI to use public readonly members instead of private members and getters
* Made Parallel.ProcessorCount public
* Started switching over packet building methods in LLClientView to use Util.StringToBytes[256/1024]() instead of Utils.StringToBytes()
* More cleanup of the ScenePresences vs. ClientManager nightmare
* ScenePresence.HandleAgentUpdate() will now time out and drop incoming AgentUpdate packets after three seconds. This fixes a deadlock on m_AgentUpdates that was blocking up the LLUDP server
|
| |
| |
| |
| | |
implements a simple distance prioritizer based on initial agent positions. Re-prioritizing and more advanced priority algorithms will follow soon
|
| |
| |
| |
| |
| |
| |
| |
| | |
so it is clear who/what the broadcast is going to each time
* Removed two redundant parameters from SceneObjectPart
* Changed some code in terse update sending that was meant to work with references to work with value types (since Vector3 and Quaternion are structs)
* Committing a preview of a new method for sending object updates efficiently (all commented out for now)
|
|\ \
| |/ |
|
| | |
|
|\ \
| |/ |
|
| | |
|