| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
nothing rather than throwing an error.
Resolves http://opensimulator.org/mantis/view.php?id=7311
|
|
|
|
| |
indepedently, so that it can be seen in "show threads" and stats
|
|
|
|
|
|
|
|
| |
rather than a persistent thread with sleep.
This is to see if an inaccuracy in sleep times under load is responsible for increase in frame times even when there is spare time still available.
Can currently only be activated by setting "debug scene set update-on-timer true".
Can be switched between timer and thread with sleep updates whilst the scene is running.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
It's WIP in that a dialog builder is on it's way. For now, the XML needs to
be handmade.
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
appearance refresh is active.
Corresponds to ResendAppearnceUpdates setting in [Appearance] in OpenSim.ini
This was originally implemented to alleviate cloud appearance problems but could be too expensive with large numbers of avatars.
|
|
|
|
|
|
|
| |
tolerances on the fly.
This is done via "debug scene set client-pos-upd, client-rot-upd, client-vel-upd".
For testing purposes.
|
|
|
|
| |
f6f7585
|
|
|
|
|
|
|
|
| |
reprioritization distance to be changed on the fly.
This governs when child agent position changes are sent to neighbouring regions.
Corresponding config parameter is ChildReprioritizationDistance in [InterestManagement] in OpenSim.ini
For test purposes.
|
|
|
|
|
|
|
|
|
|
|
|
| |
queues")"
Fixes http://opensimulator.org/mantis/view.php?id=7280
It can't be done this way because the stats data needs to show up on the console at all log levels, not just debug.
But this means setting it to log at fatal, which is not appropriate for this stuff in the log.
I understand the desire but this has to be done some other way, perhaps by (yet another) config parameter.
Also, this was already being done with the ClientStatsReport but that also should be done in another way, I think.
This reverts commit 5d534127663899cd5592c865b1d00855fce25854.
|
|
|
|
| |
is being throttled due to past poor performance.
|
| |
|
|
|
|
| |
thanks Ai Austin for pointing this out.
|
|
|
|
| |
New property created to specify how many days to keep files for. Off by default, also made sure only oar files will be removed.
|
| |
|
|
|
|
| |
this with a warning.
|
|
|
|
| |
don't try to extract materials data rather than throw an exception
|
|
|
|
| |
Signed-off-by: Michael Cerquoni <nebadon2025@gmail.com>
|
|
|
|
|
|
| |
messages instead of a warning message.
Same justification as earlier commit 996a6c2. These are not warnings but should still be visible to the user at any log level.
|
|
|
|
| |
when sending group messages, not just those after get group members and get presence status, as applicable
|
|
|
|
|
|
|
|
|
| |
that of the groups module.
This is to allow us to get useful information on messaging without being overwhelmed by the rest of groups debug.
Enabled with [Groups] DebugMessagingEnabled = true in config (default false)
Or "debug groups messaging verbose true|false on the console" (similar to existing groups setting).
Done for both xmlrpc and V2 groups.
|
|
|
|
|
|
|
|
| |
notice with XmlRpcGroups messaging did not appear in the user's inventory.
This was because the "session ID" when the message template was copied was always replaced with the group ID, whereas a notice requires this to be the notice ID.
Instead just copy the "session ID" as is - other callers already have this set properly so replacing with group ID was redundant anyway.
Relates to http://opensimulator.org/mantis/view.php?id=7037
|
|
|
|
|
|
|
|
| |
handle notices to offline users directly as known undeliverable messages rather than discarding or attempting delivery.
Offline notices can still be controlled with the [Messaging] ForwardOfflineGroupMessages setting.
Looks to address more of http://opensimulator.org/mantis/view.php?id=7037
Only for Flotsam now for testing, but if approach works should be possible with core offline notices as well.
|
| |
|
|
|
|
| |
GroupsMessagingModule.ProcessMessageFromGroupSession()
|
| |
|
|
|
|
|
|
|
|
| |
NPCs would be seen by other viewers.
It appears that at least Singularity 1.8.5 (but probably others) rely on attachment FromItemIDs being different to display more than one.
This commit resolves this by generating random IDs instead of always using UUID.Zero for NPCs.
Resolves http://opensimulator.org/mantis/view.php?id=7110
|
|
|
|
| |
Extends basic physics to allow av movement on a varregion (basic physics is only really useful for regression test purposes).
|
| |
|
|
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
|
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
|
|
|
| |
PrimLimitsModule.CanObjectEnter() when we know for sure that we need them.
|
|
|
|
|
|
|
|
| |
was failing, with the object returning to its original position.
Root cause was that PrimLimitsModule was not properly handling the case where the parcel it was asked to check was outside the current region's bounds.
If this is the case, we can abort the check since the receiving region will perform it.
Added a regression test for this case.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
| |
or trailing whitespace between comma separate module combinations.
|
|
|
|
|
|
|
|
| |
use for fetching group data to be different from im.fromAgentID
This is because xmlrpcgroups currently always checks visibility for the requesting agent ID (unlike Groups v2, which can accept UUID.Zero)
But group notice IMs have a from agent which is the group rather than the sending agent.
Further addresses http://opensimulator.org/mantis/view.php?id=7037
|
|
|
|
|
|
|
|
| |
group chat to avoid timeout issues when sending messages to large groups.
Only implementing for XmlRpcGroups initially to test.
May require MessageOnlineUsersOnly = true in [Groups] to be effective.
In relation to http://opensimulator.org/mantis/view.php?id=7037
|
| |
|
|
|
|
|
|
|
| |
This commit eliminates all of the 'border' class and list code and replaces
it with testing if in the current region.
Impacts: can make a mega-region out of varregions of the same size; and
mega-region combinations must be rectangular (not square but rectangular)
|
|
|
|
| |
XmlRpcGroupsServiceConnector error
|
|
|
|
|
|
|
| |
llRezAtRoot except that the start parameter is a Json string that will
be unpacked into a json store identified by the objects uuid. This
makes a much more expressive (and simpler) way of passing initial
parameters to a rezzed object.
|
|
|
|
| |
is intended for use in region modules and is not exposed to scripts.
|
|\ |
|
| | |
|
|\ \ |
|
| | | |
|