| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
This can always be retrieved via the LLUDPClient and is so done in various places already.
|
| |
|
|
|
| |
This may well come back in the future when this subinterface is actually used but it currently isn't and I feel the name was poor.
Everything uses IClientAPI.RemoveEndPoint which also returned the full endpoint rather than just the ip address.
|
| |
|
|
| |
IClientAPI.RemoteEndpoint.
|
| |
|
|
|
|
|
| |
names in OpenSim.ini.example to AllowedClients and BannedClients to match long-existing settings in [LoginService]
Also changes separator from comma to bar to match existing [LoginService] config features.
Divergence of config names for identical facilities in different places makes for an unnecessarily confusing user experience.
|
| |
|
|
|
| |
Also change to use standard table formatting
"show circuits" and "show connections" console commands are very similar but access different data structures.
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
SOG and SOP. Should have no functionality changes.
|
| |/
|
|
| |
Also moves into own method.
|
| |
|
|
|
|
|
| |
constructing fresh copies.
The encodings are thread-safe and already used in such a manner in other places.
This isn't done where Byte Order Mark output is suppressed, since Encoding.UTF8 is constructed to output the BOM.
|
| |
|
|
|
| |
This is only currently meant for use by regression tests that don't have any issues if XEngine is started up quickly, since no other operations will be occuring simultaneously.
Therefore, this is not yet documented externally.
|
| |
|
|
| |
since the infrastructure no longer fails if this module isn't present, at least on the tested codepaths
|
| |
|
|
| |
This currently only does a relatively crude check for a ScriptState node in the serialized xml
|
| |
|
|
| |
currently only checks for the presence of script items, not for started scripts
|
| |
|
|
|
|
|
| |
avatar to sit in the position given if no sit target was set.
Previous behave was that the second avatar could not sit.
This matches behaviour observed on the LL grid.
|
| |
|
|
| |
and SOP.RemoveSittingAvatar()
|
| |
|
|
|
| |
This reverts commit c8f0d476d2f775ba4d7afca12eeff527b46bb8e2.
On reconsideration, I think this is less readable since immediately following code still sets SitTargetAvatar directly
|
| | |
|
| |
|
|
|
|
| |
rather than creating a new copy
There are no issues with side-effects since this is a struct.
|
| |
|
|
|
|
|
| |
property rather than being repeated in SP.
This also makes the detection in SP.FindNextAvailableSitTarget() and SendSitResponse() identical.
Previously they varied slightly (SendSitResponse didn't check for an older type of invalid quaternion) but the practical effect is most probably zero.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
avatars rather than throwing an exception.
Extends sitting avatar regression tests to test new sitters information
|
| |
|
|
|
|
| |
the known item with script state still in the script engine and then remove the scripts.
This is to fix a regression starting from 5301648 where attachments had to start being deleted before persistence in order to avoid race conditions with hud update threads.
|
| |
|
|
|
|
|
| |
second to finish normally before forcibly aborting.
This is to avoid the worst of the problems in mono 2.6, 2.10 where an aborted thread does not always release all its locks.
This very short grace period is identical to the existing behaviour when a script is removed from the scene.
|
| |
|
|
|
|
|
| |
another avatar in the scene.
Very useful in serious game/environment scenarios where its only allowed for trusted creators.
Threat level Severe
|
| | |
|
| |
|
|
|
|
| |
This prevents a stack overflow where a get position on the avatar will refer to the attachment which will in turn refer back to the avatar.
This required recording of all sitting avatars on a prim which is done separately from recording the sit target avatar.
Recording HashSet is null if there are no sitting avatars in order to save memory.
|
| |
|
|
| |
is only complete for a particular region at a time
|
| | |
|
| |
|
|
|
| |
This was causing 2 copies of the module to be created for each scene.
Probably no bad consequences other than a small waste of memory (both for the module and for the warp3D renderer it loaded)
|
| | |
|
| |
|
|
| |
draw the eye
|
| |\ |
|
| | |\
| | |
| | |
| | |
| | |
| | | |
Cleanup preceeding major work. No major functional changes.
Collisions reported to simulator more efficiently.
BulletSim binaries updated using a more recent version of Bullet (v2.80-r2527).
|
| | | |
| | |
| | |
| | |
| | | |
the simulator in batches.
More comments.
|
| |/ /
| |
| |
| |
| | |
This is always done later on in SceneGraph.AddSceneObject() if the call hasn't failed due to sanity checks.
There's no other purpose for this method to exist and it's dangerous/pointless to call in other conditions.
|
| | |
| |
| |
| | |
a few commits ago in 43a2da9
|
| |/ |
|
| |
|
|
| |
the scene graph
|
| |
|
|
|
| |
This patch trims leading and trailing spaces from NPC chat and
suppresses the sending of empty chat strings on open chat channel 0.
|
| |
|
|
| |
Allow NPCS to touch obects.
|
| |
|
|
|
|
| |
Scene.AddObject()
Only IncomingCreateObject() needs these checks. General object adding does not need to perform crossing perm checks
|
| |
|
|
| |
AttachObject() for better code comprehension
|
| | |
|
| |
|
|
|
|
| |
timer setting.
This is to help detect situations where thread timeout warnings are being generated because of general machine issues rather than deadlock, network or other problems.
|
| |
|
|
|
|
| |
messages from concurrent logins. Also adds destination resolution debug log message showing region endpoint.
Adding endpoint to the log helps to find issues where the region external host information has been wrongly configured
|
| |
|
|
| |
I can't see that these present any real hazard to sim functioning.
|
| | |
|
| |
|
|
|
|
|
| |
This works like osForceAttachToAvatar() but allows an object to be directly specified from the script object's inventory rather than forcing it to be rezzed in the scene first.
Still only attaches objects to the owner of the script.
This allows one to bypass the complicated co-ordination of first rezzing objects in the scene before attaching them.
Threat level high.
|
