| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| |
| |
| |
| | |
Still has problems with child avatars.
|
| |
| |
| |
| |
| |
| | |
[Terrain]SendTerrainUpdatesByViewDistance=true.
This tracks which patches have been sent to each client and outputs the
patches as the avatar moves.
|
|/
|
|
|
|
| |
Specifically, StoreEstateSettings was not being used anywhere; instead EstatSetting.Save was being called, but that method is a trigger to the DB-layer code directly, which, besides being wrong, was making it impossible to replace the service with a remote connector.
Also added more packing/unpacking code.
|
|
|
|
|
|
| |
erroneous information.
Also, added conversion of EstateSettings from/to key-value pairs in preparation for robust net work connectors.
|
|\ |
|
| | |
|
| |
| |
| |
| | |
ScenePresence.SendTerseUpdateToAllClients() which is extremely helpful when investigating presence update triggers.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
RawVelocity update threshold for now in BSCharacter.UpdateProperties().
For some reason as yet unidentified (feedback?) a threshold above 0.4 here causes the RawVelocity to move between a lower and upper bound rather than remaining constant.
The RawVelocity increased until it triggered the threshold update, at which point it started to decrease until it again triggered the threshhold update.
This delta-v was enough to exceed the checks in ScenePresence.SendTerseUpdateToAllClients() and produce jittery avatar flight because of the fluctuating velocity.
With a threshold of 0.4 (or 0, as with ODE), the RawVelocity remains constant in BulletSim and so avatar flight becomes mostly smooth - remaining occasional glitches appear to be a result of errors in distance extraploation.
There are no obvious problems with commenting out the threshold.
Misterblue, if this is wrong or I've missed some subtlety here, please feel free to revert and/or correct.
The same considerations may or may not apply to object velocity updates.
|
| |
| |
| |
| | |
required. This preserves API compatibility for external modules using this function.
|
| |
| |
| |
| | |
which logs every request it receives.
|
| |
| |
| |
| |
| |
| | |
bitmap generation in WorldMapModule throw an exception on next startup.
This commit replaces the hardcoded region sizes in WorldMapModule.GenerateOverlay() with numbers pulled from m_scene.RegionInfo
|
| |
| |
| |
| | |
producing Debug or Release binaries
|
| |
| |
| |
| | |
other assembly versions
|
| | |
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| | |
configs
This is to fix an issue since recent commit fbcb763 where these are no longer removed automatically.
OpenSim.*.config was already not appending these newlines
|
| | |
|
| |
| |
| |
| | |
the issue with different AppDomain BaseDirectory in local and Jenkins test runs
|
| |
| |
| |
| |
| |
| | |
out to console to get a handle on what's going wrong.
Does not fail for me locally and I failed to notice this test was failing on Jenkins.
|
| |
| |
| |
| |
| |
| | |
commit 1fa3a6f
This was hidden in continuous integration because of another regression test issue.
|
| | |
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| | |
step updates and collisions. This is an attempt to fix a crash reported
by Justin when doing high velocity teleports.
|
|/
|
|
| |
send the SW-most corner of the varregions; the other areas, when clicked, would result a blue circle, meaning that the viewer didn't know about those areas. This is still not quite right, as all the areas appear to be in the same coordinates, but it's good enough for now.
|
| |
|
|\ |
|
| | |
|
|/
|
|
| |
are not found locally.
|
| |
|
|
|
|
| |
permissions according to the permissions of the items in the object
|
|
|
|
|
|
| |
and the standard subfolders of "Calling Cards".
(If we don't create them now then they'll be created later by the viewer, but why wait.)
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
script.
This is probably due to changes in the layout of the generated script preamble (using statements etc, ) in c8afc852 (Jan 17 2013).
Re-enabled existing regression test that exercises at least one case of this.
|
| |
| |
| |
| |
| |
| | |
yet enabled.
This reveals the position map problems and will make the fix (and subsequent continual checking) easier.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
than on every single log.
Compiling every time is unnecessary since Regex is thread-safe.
|
| |
| |
| |
| | |
RegexOptions.SingleLine
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
MessageTransferModule.SendGridInstantMessageViaXMLRPCAsync() whilst preserving retry lookup behaviour.
This is based on heavily mikemig's original patch in http://opensimulator.org/mantis/view.php?id=7149
but instead of exiting after the first IM delivery failure to presence information retrieved from the presence service
it will retry the lookup until the result matches the previous lookup.
This is to deal with the case where the agent is sent an IM whilst they are teleporting.
|
| |
| |
| |
| |
| |
| | |
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 and the root prim has no corresponding value set, then also set the root prim.
This matches behaviour just tested on the Linden Lab grid.
|
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
| |
| |
| |
| | |
chat
|