| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
created in that client session, or if no other action has been performed on the object.
There were two problems here:
1) On object group update, we looked for the group is the IClientAPI group cache rather than in the groups service. This fails to groups created newly in that session
2) On object group update, we weren't setting the HasGroupChanged flag. This meant that the change was not persisted unless some other action set this flag.
This commit fixes these issues and hopefully addresses http://opensimulator.org/mantis/view.php?id=5588
This commit also moves HandleObjectGroupUpdate() to the GroupsModule from the Scene.PacketHandlers.cs file
|
|
|
|
| |
in other regions, as opposed to <128, 128, 70>
|
| |
|
|
|
|
|
|
|
|
| |
in the same thread rather than on another one.
The caller is already an async thread from LLClientView so this doesn't hold up the client.
However, launching on a separate thread does remove the effect of m_setAppearanceLock
This was potentially allowing two different SetAppearance threads to interfere with each other, though this probably rarely happens, if at all.
|
| |
|
|
|
|
| |
Haven't been able to resolve issue where attachments are removed by the viewer on relog on a localhost
|
|
|
|
| |
It appears that this is entirely unnecessary since the poll http handlers are dealt with on a separate code path.
|
|\ |
|
| | |
|
|/
|
|
|
|
|
|
| |
of OSHttpRequest/OSHttpResponse.
This is required for the substitution of different HTTP servers or the newer HttpServer.dll without having to commit to a particular implementation.
This is also required to write regression tests that involve the HTTP layer.
If you need to recompile, all you need to do is replace OSHttpRequest/OSHttpResponse references with IOSHttpRequest/IOSHttpResponse.
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
bots between neighbouring regions.
Not yet enabled since there is a bug where the initial cross will work but all subsequent movements on the receiving simulator appear to fail.
|
|
|
|
|
|
|
| |
SendCreateChildAgent" message
This is misleading since a simulator will call this method before successfully trying remote regions.
Also comments out spammy "[SIMULATION]: Stream handler called" AgentHandlers messages for now.
|
| |
|
|
|
|
|
|
| |
after printing out the error, since this method is invoked by users.
Still throwing the exception on the stream method since this invoked programatically
|
|
|
|
| |
putting out a useful complaint message if we haven't for some reason
|
|
|
|
| |
Recent issues in http://opensimulator.org/mantis/view.php?id=5794 were not related to HG friends
|
| |
|
| |
|
|
|
|
| |
user's homeurl
|
|
|
|
| |
This is <thread-name> (<region-name>)
|
|
|
|
| |
This also adds time since started to "show threads". Unfortunately these two changes got mixed in.
|
|
|
|
|
|
|
|
| |
This might help with
[USER AGENT CONNECTOR]: new connector to ()
[USER AGENT CONNECTOR]: Unable to contact remote server for GetServerURLs
[USER AGENT CONNECTOR]: Malformed Uri : Argument cannot be null.
Parameter name: uriString
|
| |
|
|
|
|
| |
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
|
|
|
|
| |
RecacheFriends() to reflect their intended function
|
|
|
|
| |
better reflect its actual function
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
structs are so not passed by reference (and they're immutable!)
|
| |
|
|
|
|
|
|
| |
relationship.
Rename IFriendsModule.AddFriend() to AddFriendship()
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
HGFriendsModule.GetOnlineFriends() then spit out a warning rather than failing on the String.Substring().
This is to progress http://opensimulator.org/mantis/view.php?id=5789
|
|
|
|
|
|
| |
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
|
|
|
|
| |
packet per prim. More to come as we change to make use of this.
|
|
|
|
|
|
| |
from previous commit which sort out which iterator is used are left
intact. A discussion is needed as to what constitutes an avatar vs a
ScenePresence.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the 3 iteration functions so more of them are using the correct
iteration for the action they are performing. The 3 iterators that seem
to fit all actions within OpenSim at this time are:
ForEachAvatar: Perform an action on all avatars (root presences)
ForEachClient: Perform an action on all clients (root or child clients)
ForEachRootClient: Perform an action on all clients that have an avatar
There are still a dozen places or so calling the old
ForEachScenePresence that will take a little more refactoring to
eliminate.
|
|\ |
|
| |\ |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| |/ / |
|