| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
I forgot that m_post is being set inconsistently between non-explicit and explicit ragets
|
|
|
|
| |
specified as well.
|
|
|
|
| |
Original commit is ff4e7de7
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
TestRepeatSameDrawContainingImageReusingTexture() and TestRepeatSameDrawContainingImage() if localhost has a webserver set up.
Use 0.0.0.0 instead of localhost
|
|
|
|
|
|
| |
position in third-person and mouselook
We now specify sits as offsets from the root prim, as the viewer expects.
|
|
|
|
|
|
| |
again as "non-shared"
Addresses http://opensimulator.org/mantis/view.php?id=6860
|
|
|
|
|
|
| |
syntax error
This was the case before any of the recent changes
|
| |
|
| |
|
|
|
|
|
|
| |
take a single integer, generate a syntax error on LSL script compile rather than an exception later on.
This applies to events changed, collision, collision_start, collision_end, on_rez, run_time_permissions, sensor, touch, touch_start, touch_end
|
|
|
|
|
|
|
| |
and timer LSL events generate a syntax error if inappropriately given arguments.
This matches behaviour seen on the LL grid and a previous change for state_entry.
These are all the events which should take no arguments
|
| |
|
|
|
|
|
|
|
| |
(UUID)null
Patch from http://opensimulator.org/mantis/view.php?id=6843
Thanks Kira.
|
|
|
|
| |
Thanks to Kira for this patch from http://opensimulator.org/mantis/view.php?id=6845
|
|
|
|
|
|
| |
console the full details of that parcel.
Using "land show" without a land ID still outputs a summary of parcels in the region
|
|
|
|
|
|
|
| |
Objects statistic by 1 instead of by the number of prims removed.
Unlike LL, OpenSimulator currently uses this stat to record the number of prims in the physics simulation, even when they are at rest.
Added regression test for this case.
|
|
|
|
|
|
| |
state_entry() generates a syntax error.
Same for other events to follow at a later date.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
generate syntax error as seen on the LL grid
This is done through the parser and so generates the same syntax error message if any parameters are wrongly specified for this event.
We were already enforcing event names in the parser.
This is only for state_entry so far as an initial test of the approach - appears to work correctly.
|
|
|
|
| |
j2kDecodeCache folder should be cleared after updating to this revision so that sculpts containing alpha can be re-decoded and successfully meshed.
|
| |
|
| |
|
|
|
|
| |
first added a few commits ago
|
|
|
|
| |
UploadBakedTextureModule
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
particle system functionality. Note that this does *not* complete required server side changes for implementing the new particle system
|
|
|
|
| |
rate that is currently only displayed if LogLevel >=1 in [AssetCache] config
|
| |
|
|\ |
|
| | |
|
|/
|
|
|
|
| |
[Startup] section.
These are long unused but confusingly will be seen in the [Startup] section on a "config save".
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
| |
static objects.
Reorder collision flag setting code for terrain to fit pattern used elsewhere.
|
|
|
|
| |
Signed-off-by: teravus <teravus@gmail.com>
|
|
|
|
| |
(The changes weren't visible before because updates to attachments aren't sent while the attachment is selected.)
|
|
|
|
|
|
|
|
|
|
|
| |
the vehicle buoyancy if the vehicle is above its hover height.
This is a known misfeature of this vehicle flag which has been accepted
since it would break too many implementations. The problem is noticed
when creating a jetski-like vehicle that jumps over sand bars. A boat
normally is configured with neutral buoyancy and hovering at water
height. When it jumps the sandbar, it needs to have gravity applied
to get back to water level.
|
|
|
|
| |
Previously only the first object in the Coalesced Object was rezzed. Now all the objects are rezzed.
|
| |
|
| |
|
| |
|
|
|
|
| |
* Break out common BasicDOSProtector code into separate class.
|
|
|
|
|
|
|
|
|
| |
HTTP Server handlers. XMLRPC Handler, GenericHttpHandler and <Various>StreamHandler
* Applied the XmlRpcBasicDOSProtector.cs to the login service as both an example, and good practice.
* Applied the BaseStreamHandlerBasicDOSProtector.cs to the friends service as an example of the DOS Protector on StreamHandlers
* Added CircularBuffer, used for CPU and Memory friendly rate monitoring.
* DosProtector has 2 states, 1. Just Check for blocked users and check general velocity, 2. Track velocity per user, It only jumps to 2 if it's getting a lot of requests, and state 1 is about as resource friendly as if it wasn't even there.
|
|
|
|
| |
shout-range, at the request of Singularity dev Liru-Dargon
|