| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
echo back the maturity that it sent
Without this change, attempts to change the maturity rating in the viewer's Preferences don't work.
|
| | |
|
| |
|
|
|
|
|
| |
parameter 'TerrainGroundPlane' which defaults to -500.
BulletSim had assumed altitudes never went negative but that is not true. The
ground plane is just a safety net so things wouldn't fall to infinity.
|
| |
|
|
| |
from 2227f51b to run
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Per http://wiki.secondlife.com/wiki/Tips_for_Creating_Heightfields_and_Details_on_Terrain_RAW_Files#Notes_for_Creating_Height_Field_Maps_for_Second_Life
terrain heights up to 508 are possible on the LL grid (and were available on previous releases of OpenSimulator).
The obvious way to allow both this and equivalent -z values, is to rewiden the internal terrain height storage from short to int.
The memory tradeoff is most noticeable on the maximum 8192x8192 var region (equiv to 1024 normal regions), where it adds 128mb to resident use (128k on a normal region)
This is still better than the double used in previous releases.
This does not affect physics or data storage since they already use float and double respectively.
This may not be the final solution if we actually want to sacrifice -z, >327 or something else.
Relates to http://opensimulator.org/mantis/view.php?id=7076
|
| |
|
|
|
|
| |
config option, LogOverloads, to log when a thread pool overload occurs.
This option defaults to "True" because the logging data is useful for
diagnosing threading issues.
|
| |
|
|
| |
This fixes the issue of "Show in Search" seeming resetting at random.
|
| |\ |
|
| | |
| |
| |
| | |
because now JsonRpcRequest() returns an error result instead of throwing an exception
|
| | |
| |
| |
| | |
both the Simulators and Robust
|
| |/
|
|
| |
permissive, where the permissions of the children prims' inventory items were not changed. As a consequence, we couldn't control some of the objects imported via HG and OARs even in god mode.
|
| | |
|
| |
|
|
| |
of 0 from previous commit cb1f28
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
of the LL grid.
This uses an offset of 0.05 on the up vector of the sit orientation, after extensive analysis on
http://opensimulator.org/mantis/view.php?id=7096 and https://wiki.secondlife.com/wiki/Talk:LlSitTarget
This supersedes the previous adjustment in 5b73b9c4 which had been wrongly applied.
The maximum change is about 0.1 with a maximum height avatar.
This patch is all Aleric's work - I am applying manually in order to add these additional notes
|
| |
|
|
| |
simulator cache)
|
| |
|
|
| |
This commit also contains other changes, but they're all just for clarity. The only actual behavior change is to avoid Posting local assets.
|
| |
|
|
| |
because it's Obsolete.
|
| | |
|
| |
|
|
|
|
| |
Previously, if the movement speed was below 0.05/sec then it didn't work correctly.
Fixes http://opensimulator.org/mantis/view.php?id=7117
|
| |
|
|
| |
pre-truncate the description of dynamic textures.
|
| |
|
|
|
|
|
|
| |
status of friends, so they continued to appear Offline.
This happened because these notifications (the UDP packets) can only be sent to Root Agents. But the notifications were done in OnClientLogin(), at which point the client is still a Child Agent. Since a FireAndForget is used, it became a race condition as to whether the packets would be sent before or after the client became a Root Agent.
To fix this, we now only send the notifications once the client becomes a Root Agent for the first time.
|
| |
|
|
| |
Signed-off-by: Robert Adams <misterblue@misterblue.com>
|
| |
|
|
| |
value
|
| |
|
|
| |
group for *all* the avatars in the scene (not permanently)
|
| |
|
|
| |
much as they wanted even if the parcel's permissions had since been changed to disallow rezzing
|
| |
|
|
| |
object in the parcel even if the flag "Create Objects by Group" was disabled
|
| |
|
|
|
|
| |
parcel has a Group set; it doesn't have to be *deeded* to the group
Also some cleanup of the use of Group ID's (with no change to functionality).
|
| | |
|
| |
|
|
| |
Gatekeeper URI (which is used with Regions); not the Home URI (which is used with Users)
|
| |
|
|
|
|
|
|
| |
objects in the world.
This was originally changed in an attempt to make vehicles work better
but the effect was not that large and it causes avatars to float
above the terrain.
|
| |
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
| |
possible
|
| | |
|
| |
|
|
|
|
|
|
| |
completely inoperative.
This means the presence info may be out of date by up to 20 seconds, but this avoids scripts potentially triggering constants requests to user accout and presence info services.
Relates to http://opensimulator.org/mantis/view.php?id=7088 though I fixed in a different way.
Adds regression test for this case.
|
| |
|
|
|
| |
This adjustment makes a default, shoeless avatar stand properly on a prim
for the various heights (0% to 100% in the appearance adjustment).
|
| |
|
|
| |
land. The objects that are sold together with the parcel of land need to fulfill the following preconditions: owned by the current parcel owner, not set to a group, transferrable. This feature does not work for group owned parcels or land bought by a group.
|
| |
|
|
| |
When an avatar is in their home grid, their name appears as "First Last". In other grids the name appears as "First.Last @grid.example.com". However, viewers have a bug and they don't always show the new name. We use a trick (changing the Group Title briefly) in order to make the viewers show the new name. This is only done after a Hypergrid teleport.
|
| |
|
|
| |
referrer)
|
| |
|
|
| |
says "Teleport failed", so adding "Teleport refused" is redundant.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
could not be found" to the client. This happened on both success and failure.
On successful teleports this error wasn't actually shown to the user. But on failed teleports this error could hide the true cause of the failure. For example, attempting to use a Landmark that's more than 4095 regions away would result in two warnings appearing in the viewer: "Region too far" and "Destination could not be found". The second message hid the first one, so it wasn't obvious to the user what is actually the problem.
|
| |
|
|
|
|
| |
entering the grid.
This can affect which region to use. E.g., returning users may be allowed to enter any region, whereas users from other grids will have to enter a gateway region. Previously per-user decisions were only made later, but by then it's too late to change which region the user enters.
|
