| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
closed on teleport, don't unnecessarily resend all avatar and object data about that region.
|
|
|
|
|
|
| |
neighbour) don't resend all the initial avatar and object data again.
This is unnecessary since it has been received (and data continues to be received) in the existing child connection.
|
|
|
|
|
|
|
| |
SP.WaitForUpdateAgent() with a triggered event instead.
Rapid polls are more expensive than triggered events (several polls vs one trigger) and may be problematic on heavily loaded simulators where many threads are vying for processor time.
A triggered event is also slightly quicker as there is no maximum 200ms wait between polls.
|
|
|
|
| |
This is already going to be correctly set by WaitForUpdateAgent() earlier on in that method, which is always called where a callback to the originating region is required.
|
|
|
|
| |
for better accuracy and consistency with other similar parameters
|
|
|
|
|
|
|
| |
updates except to originator
For experimental purposes.
Also corrects a previous bug where each terse update sent was counted rather than each set of terse updates to agents.
|
|
|
|
|
|
| |
Allows experiments in manually reducing updates under heavy load.
Activated by "debug scene set client-upd-per" console command.
In a simple test, can send as few as every 4th update before observed movement starts becoming disturbingly rubber-banded.
|
|
|
|
|
|
|
| |
tolerances on the fly.
This is done via "debug scene set client-pos-upd, client-rot-upd, client-vel-upd".
For testing purposes.
|
|
|
|
|
|
|
|
|
|
|
| |
appear both on the avatar AND as in-world objects.
Another manifestation of this bug is that after a Hypergrid teleport, when you click on one of the avatar's attachments the object doesn't show its name. This means that the viewer knows the attachment is there, but the simulator does not.
The problem was caused by treating Hypergrid teleports as if they're Logins (because the teleport flag ViaLogin is enabled).
This may fix: http://opensimulator.org/mantis/view.php?id=7238
This may fix: http://opensimulator.org/mantis/view.php?id=7220
|
|
|
|
|
|
| |
hasn't completed yet
This caused the client to stop responding, and even the simulators to have problems. The solution is to disallow crossing before the previous cross has completed.
|
|
|
|
| |
was an inconsistency in the scope between opening and closing child agents in neighboring regions. For opening (in EnableChildAgents), the region's DrawDistance was being used; for closing (in IsOUtsideView) , the viewer's (SP) DrawDistance was being used. This fixes this inconsistency, therefore eliminating bugs observed in TPs between, at least, neighboring varregions.
|
|
|
|
|
|
|
| |
HG gods are not safe at this point. It's better to disallow this until
they can be made safe.
This reverts commit e86c765be3b0d94c94ff1c5f15a3949ecc857627.
|
| |
|
|
|
|
| |
Still has problems with child avatars.
|
| |
|
|
|
|
| |
ScenePresence.SendTerseUpdateToAllClients() which is extremely helpful when investigating presence update triggers.
|
|
|
|
|
|
| |
in a root prim, the focus should remain on the root prim.
Matches behaviour just tested on the Linden grid.
|
|
|
|
| |
camera-at value, rather than replace.
|
|
|
|
| |
child prim with camera-eye set
|
|
|
|
|
|
| |
prim does not, use the root prim offsets.
This matches behaviour just tested on the Linden Lab grid.
|
|
|
|
|
|
|
|
| |
prims moved camera/focus to wrong position.
For non-root prim, eye offsets now need to be made relative to root prim if either camera-at or camera-eye are set.
Probably a regression since November 2013 when all sits were made relative to root prim to match viewer expections (and fix other bugs).
Addresses http://opensimulator.org/mantis/view.php?id=7176
|
| |
|
|
|
|
|
|
|
|
|
|
| |
anywhere in neighbouring regions.
This was due to a silent uint overflow in ScenePresence.UpdateChildAgent() corrupting child agent positions
when the child agent was in a region with a greater x or y map co-ord than the root agent region
Probably introduced in beeec1c.
This still will not function properly with very high region map co-ords (in the millions) but other parts of the code don't handle this properly anyway.
Looks to address http://opensimulator.org/mantis/view.php?id=7163
|
|
|
|
|
|
| |
currently being used as a flag to orchestrate destination simulator threads on teleport.
If not reset, it's possible that teleports back and forth between simulators may not restart scripts in attachments.
|
|
|
|
|
|
|
| |
to restart attachment scripts before the source simulator's SP.UpdateAgent() thread had added them.
This commit changes the order of code so that attachments are re-added before the CompleteMovement() thread is released.
Relates to http://opensimulator.org/mantis/view.php?id=7148
|
|
|
|
| |
recent patch bc969a6b
|
|
|
|
| |
non-megaregion paths in ScenePresence.MoveToTarget() by recent patch bc969a6b
|
|
|
|
|
|
|
|
|
|
| |
of the LL grid.
This uses an offset of 0.05 on the up vector of the sit orientation, after extensive analysis on
http://opensimulator.org/mantis/view.php?id=7096 and https://wiki.secondlife.com/wiki/Talk:LlSitTarget
This supersedes the previous adjustment in 5b73b9c4 which had been wrongly applied.
The maximum change is about 0.1 with a maximum height avatar.
This patch is all Aleric's work - I am applying manually in order to add these additional notes
|
| |
|
|
|
|
| |
Signed-off-by: Robert Adams <misterblue@misterblue.com>
|
|
|
|
| |
When an avatar is in their home grid, their name appears as "First Last". In other grids the name appears as "First.Last @grid.example.com". However, viewers have a bug and they don't always show the new name. We use a trick (changing the Group Title briefly) in order to make the viewers show the new name. This is only done after a Hypergrid teleport.
|
|
|
|
| |
(this time with the right code change)
|
|
|
|
|
|
|
| |
turns fixes llDetectedPos(), llGetLinkPrimitiveParams() and similar functions.
Add regression test for this case.
In relation to http://opensimulator.org/mantis/view.php?id=7043
|
|
|
|
|
|
|
|
| |
to the physics engine.
This operation was accidentally removed while in the middle of improving
the computation of the avatar height. This is a temp fix until the real
solution is added.
|
|
|
|
| |
part.AddSittingAvatar already does this.
|
|
|
|
|
|
| |
instead of two independent structures that do exactly the same thing
m_sittingAvatars code also already properly handles locking to avoid races.
|
|
|
|
|
|
|
|
|
| |
an exception, and a second recross would stop the user moving until relog
Also fixes an issue where sitting avatar counts became inaccurate after any cross.
Part of the problem was due to cloning code using MemberwiseClone() but not resetting certain collection structures.
Adds regression test for this case.
In relation to http://opensimulator.org/mantis/view.php?id=7050
|
|
|
|
|
|
| |
(which has a 1-minute timeout)
Resolves http://opensimulator.org/mantis/view.php?id=6945
|
|
|
|
|
|
| |
Recent versions of Firestorm and Singularity have started sending the viewer name in the 'Channel' field, leaving only their version number in the 'Viewer' field. So we need to search both of these fields for the viewer name.
This resolves http://opensimulator.org/mantis/view.php?id=6952
|
|
|
|
| |
main frame loop anyway and has the potential to race that thread.
|
|
|
|
|
|
|
|
| |
change, not just those outside the usual tolerances.
This is to allow small adjustments of less than 0.05m in functions such as llSetPrimitiveLinkParams() to work
This is another fix for http://opensimulator.org/mantis/view.php?id=7044
Extends regression test for this case.
|
|
|
|
|
| |
Fix odd "cannot cross into banned parcel" viewer error message when crossing
into non-existant region. Proper permission failure messages are now returned.
|
|
|
|
|
|
|
| |
belongs to no group (UUID.Zero)
This was trigger the XmlRpcGroups errors described in http://opensimulator.org/mantis/view.php?id=6986
Introduced in commit 5b73b9c4 (Wed Dec 11 01:39:56 2013)
|
|\ |
|
| |
| |
| |
| | |
Locking attachments then launching script instances on a separate thread will not work, attachments will simply be unlocked and vulnerable to race conditions.
|
| |
| |
| |
| | |
occur no matter which branch of the conditional is executed
|
|\ \
| |/ |
|
| | |
|
| |\ |
|
| | |
| | |
| | |
| | | |
small window for race conditions on duplicate CompleteMovement calls
|