| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
it actually does
|
| |
|
|
|
|
| |
other modules can capture IM messages and do custom handling of them. As just attaching to Client IM events doesn't really support this, as they would still get routed through the normal process and could give back errors.
|
|
|
|
|
|
|
|
| |
usable. Applied with formatting changes, please don't introduce
K&R style indentations into OpenSim
Fixes Mantis #3190
|
| |
|
|
|
|
|
|
|
|
| |
required file system objects are not present in the test harness.
This makes the main code ignore the failure, therefore the test succeeds.
Not elegant and maybe a unit test guru has a better way. Marked as a TODO
|
| |
|
| |
|
|
|
|
| |
calling from the outside are public
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
since this is useful in a variety of situations
* Comment out one oar test since I think somehow the two save tests are causing the occasional test failures
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The attached patch implements osGetDrawStringSize that looks like:
vector osGetDrawStringSize(string contentType, string text, string
fontName, int fontSize)
in LSL. It is meant to be used in conjunction with the osDraw*
functions. It returns accurate information on the size that a given
string will be rendered given the specified font and font size.
This allows for nicely formatted and positioned text on the generated
image.
|
|
|
|
|
|
|
| |
Known issue: after TP, the self client doesn't see the animations going, but others can see them. So there's a bug there (TPs only, crossings seem to be all fine).
Untested: did not test animation overriders; only tested playing animations from the viewer.
|
|
|
|
| |
which still don't have the new appearance management code.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* This is done on the inventory archiver module directly rather than Scene.EventManager - the module seems the more appropriate location
|
|
|
|
|
|
|
|
| |
and dropped nonths ago, because it is required to get smooth region
crossings with AO running. Without it, in some corner cases, anims will
continue to run in an unstoppable state.
|
|
|
|
| |
happen: "[PHYSICS]: trying to change capsule size, but the following ODE data is missing - Shell Body Amotor". That warning occurred in MakeRoot, because of the call to SetSize, immediately after making the avie physical.
|
|
|
|
|
|
|
|
|
| |
properties as before
- prefix private variables with m_ in AssetBase.cs
- related to Mantis #3122, as mentioned in
https://lists.berlios.de/pipermail/opensim-dev/2009-February/005088.html
- all services will likely need to be upgraded after this commit
|
|
|
|
| |
user service/server. Appearance is now sent by the user service/server along with all other loginparams. Regions don't query the user service for appearance anymore. The appearance is passed along from region to region as the avie moves around. And, as before, it's stored back with the user service as the client changes the avie's appearance. Child agents have default appearances that are set to the actual appearance when the avie moves to that region. (as before, child agents are invisible and non-physical).
|
|
|
|
|
|
| |
* This is always available at Scene.CommsManager.AssetCache
|
| |
|
|
|
|
|
| |
Fixes Mantis #3170
|
|
|
|
| |
when it's 0.
|
|
|
|
| |
doesn't interfere with the unit tests.
|
|
|
|
| |
now. The flying status was temporarily being ignored, which caused the avie to drop sometimes -- there was a race condition. In the process it also fixes that annoying bug in basic physics where the avie would drop half-way to the ground upon region crossings (SetAppearance was missing). Additionally, a lot of child-agent-related code has been cleaned up; namely child agents are now consistently not added to physical scenes, and they also don't have appearances. All of that happens in MakeRoot, consistently.
|
|
|
|
| |
regions going up & down while avies are logged in (mantis #2701, perhaps? maybe not). This is the bug mentioned 2 commits ago. If this proves to work well in OSGrid, there's a lot of old code cleaning to do.
|
|
|
|
| |
entirely maintained, although it will have to be revisited soon, because it's buggy.
|
|
|
|
|
|
| |
* This was the cause of teleport tests interfering with each other
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
world map module
|
| |
|
|
|
|
| |
substantially changed because of the callback from region B triggered by the client.
|
|
|
|
| |
remoting for agent movements. WARNING: This breaks region crossing compatibility with previous versions.
|
|
|
|
| |
warnings. Fix some m_log declarations.
|
|
|
|
| |
cloned (regions on the same instance) and when it doesn't (regions on different instances).
|
| |
|
|
|
|
|
|
|
|
| |
of ScenePresence and into SceneCommunicationService, where it should be (next to RequestTeleportToLocation). No changes in the crossing mechanism itself, yet. But this change opens the way to doing crossings as slowly as it needs to be, outside the simulator Update loop.
Note: weirdnesses may occur!
|
| |
|
|
|
|
| |
made in earlier code
|
|
|
|
|
|
| |
* This simplifies callers in most cases - CachedUserInfo is already handling the rest of the fetch inventory work anyway
|
| |
|
|
|
|
| |
StandaloneTeleportTests when we add RESTInterregionComms module to the ScenePresenceTests.
|
| |
|