| Commit message (Collapse) | Author | Files | Lines |
|---|
|
asynchronously to reduce hold up in the IN UDP packet processing loop.
This is already being done for the initial object data send.
|
|
it's live before sending other data.
This means that avatar/appearance data of other avatars and scene objects for a client will be sent after the ack rather than possibly before.
This may stop some avatars appearing grey on login.
This introduces a new OpenSim.Framework.ISceneAgent to accompany the existing OpenSim.Framework.ISceneObject and ISceneEntity
This allows IClientAPI to handle this as it can't reference OpenSim.Region.Framework.Interfaces
|
|
If sp becomes null right after we've checked or created it, then behaviour down the line is going to be wrong anyway.
So instead retain the check/create ScenePresence reference and use this.
|
|
|
|
comparing against an object rather than a string
|
|
success = true on success rather than false
|
|
of code to do password checks, etc., instead of copy/pasting this code into every method
|
|
It makes far more sense anyway to use TryGetRootScenePresence().Scene, in common with the rest of the code
This method could also return any scene for child or root agents, depending in which order the scenes happened to lie in the list
|
|
structure so that logout on unexpired packets isn't retriggered, causing the same exception
|
|
This allows someone with access to this command on the XMLRPCAdmin interface to teleport an avatar to an arbitrary region and/or position.
|
|
|
|
|
|
It appears that this is entirely unnecessary since the poll http handlers are dealt with on a separate code path.
|
|
url for all users
This meant that if a user exited the region, the UploadTexture handler would be effectively removed for everyone, causing subsequent failures.
This hopefully resolves the recent UploadTexture LLSD problems
This was a regression in 5640f2e (Thu Dec 1 23:24:15 2011 +0000)
|
|
the UploadBakedTexture cap asynchronously."
This is a possible cause of the dramatic upswing in "Unable to upload... No handler registered for LLSD requests..."
Needs more investigation.
This reverts commit 1854c52ea3c60d0a47f9793a7f5ec405e15489ca.
|
|
|
|
UUID for each bake type and whether the simulator can find it.
|
|
than accidentally doing nothing
|
|
|
|
send" command for a chosen avatar as well as all
|
|
"appearance send" console command
|
|
Add OpenSim.Region.Capabilities.Handlers.Tests.dll into test suite
|
|
of OSHttpRequest/OSHttpResponse.
This is required for the substitution of different HTTP servers or the newer HttpServer.dll without having to commit to a particular implementation.
This is also required to write regression tests that involve the HTTP layer.
If you need to recompile, all you need to do is replace OSHttpRequest/OSHttpResponse references with IOSHttpRequest/IOSHttpResponse.
|
|
|
|
whole asset length, return HTTP PartialContent instead of NotFound
NotFound is obviously wrong, and this change stops viewer 3.2.2 (and v probably earlier) complaining in the log about missing textures that are actually present.
We still return PartialContent even if the range requested is a superset of the data range as per httpd's behaviour
https://issues.apache.org/bugzilla/show_bug.cgi?id=51878
Viewer 3.2.2 and very probably earlier appear happy with this.
Whether fixing this NotFound bug has any practical effect apart from resolve viewer log messages is unknown.
|
|
wide use will have to wait a few releases. So the sims are still calling GET for now.
|
|
|
|
|
|
since they don't do anything useful.
|
|
stage and then at Scene.AddClient()
|
|
This required an option to be added to NullRegionData via ConnectionString for it to act as a non-static instance, so that regression tests (which only load this class once) don't get hopeless confused and complex to compensate.
Normal standalone operation unaffected.
|
|
|
|
dictionary rather than AgentCircuitManager.AgentCircuits directly in "show circuits" to avoid enumeration exceptions
|
|
|
|
We are returning the actual number of 'sides', not the maximum index number.
Also minor format corrections.
|
|
Meshs are handeled as sculpts but can have up to 8 faces (SL restriction the collada format can handle even more). The patch enables all LSL function that adressing faces to behave correct. Like llGetNumberOfSides(); llSetLinkPrimitiveParamsFast(); llSetPrimitiveParams(); llSetColor();
Signed-off-by: marc <mare@sounddog.net>
|
|
It might be inefficient, but there are collisions every frame if the avatar is walking/standing on the ground or a prim surface
|
|
called continuously even where there are no collisions
|
|
|
|
HandleAgentUpdate().
There's no point doing this if it's being called via PhysicsCollisionUpdate
|
|
causes avatars to never reach the correct animation after some actions.
This reverts to situation where animation updates are made each frame on SP.PhysicsCollisionUpdate (though a packet is only sent if the anim actually changes).
m_updateCount was not being update on various avatar state changes, causing the correct animations to never be sent.
Always setting in HandleAgentUpdate() is not enough since the avatar is continually sending AgentUpdate packets.
One would need to identify all the conditions under which animations need to play out and set m_updateCount appropriately in SP.HandleAgentUpdate()
|
|
than duplicating it with m_movementAnimation
|
|
asking for a new determination
|
|
|
|
DetermineMovementAnimation() for better code readability
|
|
processed if we're dealing with a child ScenePresence.
Neither of these can have any effect on child agents
Now leaving warning about trying to set animation on a child agent active. Might temporarily pop up now and again.
|
|
where such requests are ignored.
|
|
constructor.
Comment was right - it is indeed useless since SP always starts off as child and TrySetMovementAnimation screens out child SP
|
|
UploadBakedTexture cap asynchronously.
This prevents a possible race condition where the client would be told all baked textures had updated before they were in the asset service.
The client would then trigger a set appearance which, after a delay, would send the avatar appearance out to other clients.
The race condition seems unlikely because of this delay but it's still possible.
Might help with grey avatar appearances.
|
|
|
