| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
ice-cream Sunday: the packet itself was hardcoding the size of the region...
|
| |
|
|
|
|
|
| |
draw distance optimization is enabled. Makes terrain editting a lot
snappier.
|
|
|
|
| |
assets associated with foreign users were being missed.
|
|
|
|
| |
Folder Type 8. (Previously we had used Folder Type -1 in one place, and LLClientView didn't even bother changing Folder Type 100 to anything else.)
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
group for *all* the avatars in the scene (not permanently)
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
packet type
Resolves http://opensimulator.org/mantis/view.php?id=6945
|
|
|
|
|
|
| |
the viewer adds a space at the end, which causes searches to fail.
Resolves http://opensimulator.org/mantis/view.php?id=6935
|
| |
|
| |
|
|
|
|
| |
Module to follow.
|
|
|
|
| |
Thanks Garmin.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
udp texture throttle and move it to the task throttle. Since most
viewers are using http textures, the udp texture throttle is holding
onto bw that could be used for more responsive prims updates. See
the documentation for CannibalizeTextureRate in OpenSimDefaults.ini.
Option is disabled by default.
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
OpenSim/Region/CoreModules/Framework/EntityTransfer/EntityTransferModule.cs
OpenSim/Region/Framework/Scenes/SceneBase.cs
OpenSim/Services/Interfaces/IGridService.cs
OpenSim/Services/LLLoginService/LLLoginResponse.cs
(conflicts were debug statements that are commented out in master branch)
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
instead of zeroing it to resolve mouselook camera problems
Addresses http://opensimulator.org/mantis/view.php?id=6892
Thanks to tglion for this spot.
This resolves a recent regression from 17b32b764acd815400d9eb903aaec6dcebd60ac7
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Add new region crossing code to varregion
Conflicts:
OpenSim/Region/CoreModules/Framework/EntityTransfer/EntityTransferModule.cs
OpenSim/Region/Framework/Scenes/ScenePresence.cs
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
- Parts of region crossing code
- New bakes handling code
- Bakes now sent from sim to sim without central storage
- Appearance handling changes
- Some changes to sitting
- A number of unrelated fixes and improvements
|
| |
| |
| |
| |
| |
| | |
Rename 'RegionWorldLocX' to 'WorldLocX' and same for Y and Z.
This keeps the downward compatibility and follows the scheme of 'region'
and 'world' location naming that is happening in the Util module.
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
x/y rot before sending agent updates, instead of before any agent update processing
It turns out that the x/y rot data in mouselook is needed to implement this and to push the avatar against the ground if walking in mouselook.
Doing this in the terse send so that we preserve mouselook rotation information
|
|\ \
| |/ |
|
| |
| |
| |
| | |
Vector3.Zero
|
| |\ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
to wrong position in third-person and mouselook"
Reverting to place on separate branch
This reverts commit ff4e7de7769b7eaa1b4fd3917e59f362b708226a.
|
| |/
| |
| |
| |
| |
| | |
is Vector3.Zero"
This reverts commit 9bdd3dc7de46507b490a2eae5160123a28133d63.
|
| |
| |
| |
| |
| |
| | |
Vector3.Zero
As far as I can see it's valid to change the eye offset even if you aren't changing the at target.
|
| |
| |
| |
| |
| |
| | |
position in third-person and mouselook
We now specify sits as offsets from the root prim, as the viewer expects.
|
|\ \
| |/ |
|
| | |
|
| |
| |
| |
| |
| | |
This records how many packets were indicated to be resends by clients
Not 100% reliable since clients can lie about resends, but usually would indicate if clients are not receiving UDP acks at all or in a manner they consider timely.
|
|\ \
| |/ |
|
| |
| |
| |
| | |
first added a few commits ago
|
| |
| |
| |
| |
| |
| | |
This allows one to monitor the total number of messages resent to clients over time.
A constantly increasing stat may indicate a general server network or overloading issue if a fairly high proportion of packets sent
A smaller constantly increasing stat may indicate a problem with a particular client-server connection, would need to check "show queues" in this case.
|
| |
| |
| |
| | |
Add some debugging logs on region creation to report region size.
|
| |
| |
| |
| |
| | |
compression base computation.
Complete replacement of float[] for terrain heightmap with TerrainData instance.
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
ObjectProperties UDP replies to viewer
Not yet shown that this is used or resolves a bug where not all textures appear on objects with an "XML with textures" upload from singularity 1.8.3
Proper texture entries are actually present and appear properly on relog, but not on select from viewer until at least one face texture is changed.
|
| |
| |
| |
| | |
Appears to be a never used method.
|
| |
| |
| |
| | |
if we sent immediately)
|
|\ \
| |/ |
|
| | |
|
| |
| |
| |
| | |
LLClientView to use same. This passes a terrain info class around rather than passing a one dimensional array thus allowing variable regions. Update the database storage for variable region sizes. This should be downward compatible (same format for 256x256 regions).
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
-- addition of varaible region size in X and Y
-- internal storage of heightmap changed from double[] to short[]
-- helper routines for handling internal structure while keeping existing API
-- to and from XML that adds region size information (for downward compatibility,
output in the legacy XML format if X and Y are 256)
Updated and commented Constants.RegionSize but didn't change the name for compatibility.
|