| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
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
|
| | |
|
| |
|
|
| |
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
|
| | |
|
| |
|
|
| |
This has been handled by WebFetchInvDescHandler.Fetch() for some time.
|
| |
|
|
| |
conversion rather than the arrays in TaskInventoryItem
|
| |
|
|
|
|
| |
Scene.GetNearestAllowedPosition()
At least on ODE, this wasn't doing any harm but there wasn't any point to it either
|
| |
|
|
|
|
| |
not just root ones.
Also adds scene name and client type (root|child) to logged information.
|
| |
|
|
|
|
|
| |
desintation sim has no active script engines.
This involves getting IScene.RequestModuleInterfaces() to return an empty array (as was stated in the method doc) rather than an array containing one null entry.
Callers adjusted to stop checking for the list reference being null (which never happened anyway)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
57956c4b-ff2e-4fc1-9995-613c6256cc98>: Invalid character 'O' in input string messages
These are just the result of an attempt to canonicalize received messages - it's not important that we constantly log them.
Also finally get the deregister grid service message working properly
|
| |
|
|
|
|
| |
regeneration.
Maptile storage appears orthogonal to region registration
|
| |
|
|
|
|
|
| |
scripts from the appdomain in XEngine.
All the other actions (script state save, etc.) still occur.
This makes shutdown where there are many scripts vastly quicker.
|
| |
|
|
|
|
|
| |
own private m_localID property but leaving get to return the then unset PhysicsActor.LocalId!
Instead, just have both subclasses use the PhysicsActor.LocalID property.
This restores collision functionality that fell away in 45c7789 yesterday
|
| |
|
|
| |
changes, just cleanup
|
| |
|
|
| |
read lock
|
| |
|
|
| |
This is <thread-name> (<region-name>)
|
| |
|
|
| |
EventManager.OnMakeRootAgent event since this is on the critical path for transfer of avatars from one region to another.
|
| |
|
|
| |
As far as I can see, the SCS is only now used for informing neighbours of up/down status and possibly sending child agent updates and close requests
|
| |
|
|
| |
All this is now being handled through IEntityTransferModule and SimulationService instead, and has been for some time.
|
| |
|
|
| |
not being used any more - it's now IEntityTransferModule and SimulationService instead
|
| |
|
|
|
|
|
|
| |
FriendsModule.FetchFriendslist() asychronously.
Executing this asynchronously allows a race condition where subsequent friends fetches hit a cache that FetchFriendsList() had not yet populated.
Changing this to synchronous may improve issues where a user does not see friends as online even though they are.
I don't believe synchronous is a problem here, but if it is, then a more complicated signalling mechanism is required. Locking the cache isn't sufficient.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |/
|
|
|
|
| |
stop a NullReferenceException being thrown if an HG IM is sent to a simulator running multiple regions
This is an attempt to address http://opensimulator.org/mantis/view.php?id=5791
|
| |
|
|
| |
ScenePresenceSitTests
|
| | |
|
| | |
|
| |
|
|
| |
with other sitting code.
|
| |
|
|
|
|
|
| |
ground and solid again when it stands.
This is to avoid http://opensimulator.org/mantis/view.php?id=5783 when a collision with a ground sitting avatar causes that avatar to automatically stand and sometimes not be able to move
A better solution may be to keep gound sitting avatars solid but remove their collision status. However, this requires some physics code work.
|
| | |
|
| |
|
|
|
|
|
| |
the avatar if prim with no sit target was out of sitting range.
Now, no movement occurs.
Note that you can still sit on a prim with an explicit sit target from any distance, as was the case before.
|
