| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
| |
CheckForBorderCrossing the right way.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
baked texture caching when crossing region boundaries.
Needs further investigation.
Revert "Stop sending the viewer its own AvatarAppearance packet."
This reverts commit 92039f295d7fe66bf1a09b29483f9057e395839e.
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| | |
The viewer warns in the log if it receives this.
Stopping this doesn't appear to have adverse effects on viewer 1 or viewer 3 - the viewer gets its own appearance from body parts/clothes and self-baked textures.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
AvatarFactoryModule from AppearanceInfoModule so that it can be used in debug (inactive).
Further filters "debug packet <level>" to exclused [Request]ObjectPropertiesFamily if level is below 25.
Adjust some method doc
Minor changes to some logging messages.
|
| | |
| |
| |
| | |
These were entirely unused.
|
| |/
|
|
| |
a little bit.
|
| |
|
|
|
|
| |
BEGIN] to [SCENE] because that's where the message happens.
Also changed the instantiation of a vector object to be done only once instead of every time we receive a position update.
|
| |
|
|
|
|
| |
when we've already passed size information to the avatar at PhysicsScene.AddAvatar()
Eliminate some copypasta for height setting in OdeCharacter
|
| |
|
|
|
|
| |
Stop hiding RemoveAvatar failure, add log messages when characters are removed through defects or re-added unexpectedly.
Add commented out log lines for future use.
Use automatic property for PhysicsActor for better code readability and simplicity
|
| |
|
|
| |
IsColliding
|
| |
|
|
| |
in favour of IClientAPI.ISceneAgent.IsChildAgent instead.
|
| | |
|
| |
|
|
|
| |
The only caller is the LLUDP stack and this has to validate the UDP circuit itself, so we know that it exists.
This allows us to eliminate another null check elsewhere and simplifies the method contract
|
| | |
|
| |
|
|
|
|
| |
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
|
| |
|
|
| |
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()
|
| | |
|
| |
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
| |
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
|
| |
|
|
| |
EventManager.OnMakeRootAgent event since this is on the critical path for transfer of avatars from one region to another.
|
| |
|
|
| |
not being used any more - it's now IEntityTransferModule and SimulationService instead
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
|
|
| |
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.
|
| |
|
|
|
|
|
| |
list last week.
This means that if the avatar is within 10 meters of the selected target, it sits on it immediately without walking.
Existing autopilot outside this range will be disabled in a later commit
|
| | |
|
| | |
|
| |
|
|
| |
animation being run after the scripted one.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
properly.
|
| | |
|
