| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| |\ |
|
| | |
| |
| |
| | |
(though this is also effectively done by physics at the moment)
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
| |
HGInventoryAccessModule where it belongs. They need to exchange some events, so added those to EventManager. Those events (TeleportStart and TeleportFail) are nice to have anyway.
|
| | |
|
| |
|
|
| |
purpose; it's an historical record of what works and what doesn't wrt manipulating inventory at the viewer. I'll remove the unused code in a subsequent commit, but wanted to place it in history. The uncommented code works.
|
| |
|
|
|
|
|
|
| |
null then assume it was still not null in later code.
Another thread could come and turn off physics for a part (null PhysicsActor) at any point.
Had to turn off localCopy on warp3D CoreModules section in prebuild.xml since on current nant this copies all DLLs in bin/ which can be a very large number with compiled DLLs
No obvious reason for doing that copy - nothing else does it.
|
| |
|
|
| |
heavy SendBulkInventoryUpdate message. Waiting for Melanie to finish the light-weight version of that message.
|
| |
|
|
| |
hack away from ScenePresence. This is better but it still doesn't restore the inventory upon arrival.
|
| |
|
|
| |
guarded by an obscure config that no one but me should be using at this point.
|
| |
|
|
| |
creations and getting contacted from other grids. Incoming HyperGrid teleports can also be restricted to local users.
|
| |
|
|
| |
Experimental: we'll try switching the root folder from under the viewer.
|
| |
|
|
| |
scripts do that, and that fails the whole thing.
|
| |
|
|
|
|
| |
potential bad update that places an object at the opposite side of the
origin sim for a moment before actually crossing it. Especially important in
grids like OSG where lag between sims is high.
|
| | |
|
| |
|
|
| |
concurrent uses of the same TCP connection, and even of the connections to the same server. So let's stop doing it. This patch makes movement much smoother when there are lots of neighbours.
|
| |
|
|
| |
Uri.ToString() drops the port when it's port 80.
|
| |
|
|
|
|
| |
cf73afec356eed30e169be3ce71edad89b4fdb37
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
| |
|
|
| |
region Scenes and Modules. Changed existing modules to use it instead of assuming that foreign = null account.
|
| |
|
|
| |
on get_agent_home in UAS.
|
| | |
|
| |
|
|
|
|
|
|
| |
into a region that does not exist. This is particularly problematic for
physical objects where the velocity continues to move them out of the
region causing an infinite number of failed region crossings. The patch
forces an object that fails a crossing to be non-physical and moves it
back into the starting region.
|
| |
|
|
| |
passing the entire agent with attachs in one big message we don't necessarily need to wait for confirmation. The callback sometimes is problematic and it adds delay to the process. (2) Z velocity sent to the viewer = 0. This is an heuristic; the Z velocity usually is negative, and it makes the viewer move the avie down. This only matters while the agent is in transit and therefore not being physically simulated by neither region. As soon as the receiving region receives CompleteMovement from the viewer, the position and velocity get corrected.
|
| |
|
|
| |
in other regions, as opposed to <128, 128, 70>
|
| | |
|
| |
|
|
|
| |
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.
|
| |
|
|
| |
where such requests are ignored.
|
| |
|
|
| |
packet per prim. More to come as we change to make use of this.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
UpdateFlag is now referenced/used only within SOP and SOG. Outsiders are
using ScheduleFullUpdate, ScheduleTerseUpdate or ClearUpdateSchedule on
SOP consistently now. Also started working toward eliminating those
calls to ScheduleFullUpdate, ScheduleTerseUpdate or ClearUpdateSchedule
from outside SOP in favor of just setting properties on SOP and let SOP
decide if an update should be scheduled. This consolidates the update
policy within SOP and the client rather than everywhere that makes
changes to SOP. Some places forget to call update while others call it
multiple times, "just to be sure".
UpdateFlag and Schedule*Update will both be made private shortly.
UpdateFlag is intended to be transient and internal to SOP so it has
been removed from XML serializer for SOPs.
|
| |
|
|
| |
than calling SOP.OffsetForNewRegion
|
| |
|
|
|
|
| |
ways to access the list/dictionary of child regions and locking was
inconsistent. There are now public properties which enforce locks.
Callers are no longer required to create new copies of lists.
|
| |
|
|
| |
which called IsInTransit=true which called m_inTransit=true. Also removed NotInTransit().
|
| | |
|
| |
|
|
| |
doesn't prevent the actual teleport.
|
| |
|
|
|
|
|
|
| |
actually has an impact.
The code in question is over three years old and just be catching an inconsistency rather than being wholly necessary.
This commit still carries out the check and prints all the previous log warnings but a 'failure' no longer prevents avatar region crossing or teleport, and it doesn't give the client the error message.
This will have some kind of impact on http://opensimulator.org/mantis/view.php?id=5672
|
| |
|
|
|
| |
This method wasn't actually doing anything since dropped attachments retain a PCode of 9.
Also, behaviour of dropped attachments in other places appears to be that they persist after avatar logout rather than get deleted.
|
| |
|
|
| |
It's never possible for SOG to have no RootPart, except in the first few picosends of the big bang when it's pulled from region persistence or deserialized
|
| | |
|
| |
|
|
|
|
|
| |
The approach here, as in other parts of OpenSim, is to return a copy of the list rather than the attachments list itself
This prevents callers from forgetting to lock the list when they read it, as was happening in various parts of the codebase.
It also improves liveness.
This might improve attachment anomolies when performing region crossings.
|
| |
|
|
| |
pointless duplication of identical values
|
| |
|
|
| |
agent
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
rather than just saying "destination not found"
Instead of performing the 4096 check when the region is linked (and subsequently removing the link), leave the link in place and perform the check in the entity transfer module
This allows us to explicitly tell the hypergridder why the teleport failed (region out of range).
It also allows people on regions that are within range (on a large source grid) to teleport.
The Check4096 config parameter in the [GridService] section is replaced by a max_distance paramter in a new [EntityTransfer] section in OpenSimDefaults.ini
Since the parameter is in OpenSimDefaults.ini no action needs to be taken unless you want to increase this limit. It could also be decreased.
The check is being made in the base entity transfer module, since I believe the viewer problem occurs both on extremely large grids and while hypergridding.
|
| |
|
|
| |
instead keep track of which map blocks each client has seen in the region, and reset exactly those when the client closes.
|
| |
|
|
| |
and reset only exactly the map blocks that had regions in them. WARNING: this fetches all the regions from the Grid service, so there is a chance that this is a really bad idea in large grids. Pushing it for testing.
|
| | |
|
| | |
|
