| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
Fixes: Undo, T-pose of others on login, modifiedBulletX works again, feet now stand on the ground instead of in the ground, adds checks to CombatModule. Adds: Redo, Land Undo, checks to agentUpdate (so one can not fall off of a region), more vehicle parts. Finishes almost all of LSL (1 function left, 2 events).
Direct flames and kudos to Revolution, please
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
|
|
| |
These patch should allow people using systems that do not have their locale set to En_US or similar to use OpenSim without suffering effects such as being a million miles up in the air on login.
The problem was caused by parsing strings without forcing that parse to be En_US (hence different decimal and digit group symbols were causing problems).
Thanks very much to VikingErik for doing the legwork on this fix and phacelia for spotting it in the first place.
|
| |
|
|
|
|
|
| |
This resolves the problem where eyes and hair would turn white on standalone configurations
When a client receives body part information, for some insane reason or other it always ends up uploading this back to the server and then immediately re-requesting it.
This should have been okay since we stored that asset in cache. However, the standalone asset service connector was not checking this cache properly, so every time the client made the request for the asset it has just loaded it would get a big fat null back in the face, causing it to make clothes and hair white.
This bug did not affect grids since they use a different service connector.
|
| |
|
|
| |
code. No functional changes
|
| |
|
|
|
|
|
|
|
|
| |
When an object was deleted, the remove script instance call was aggregating the scripting events as normal.
This would queue a full update of the prim before the viewer was notifed of the deletion of that prim (QuitPacket)
On some occasions, the QuitPacket would be sent before the full update was dequeued and sent.
In principle, you would think that a viewer would ignore updates for deleted prims. But it appears that in the Linden viewer (1.23.5),
a prim update that arrives after the prim was deleted instead makes the deleted prim persist in the viewer. Such prims have no properties
and cannot be removed from the viewer except by a relog.
This change stops the prim event aggregation call if it's being deleted anyway, hence removing the spurious viewer-confusing update.
|
| | |
|
| | |
|
| |
|
|
|
| |
will be honored now, while allowed groups will not. This requires additional
groups module integration work
|
| |
|
|
| |
The new methods are still not in IClientAPI, so some work remains to be done.
|
| |
|
|
| |
Signed-off-by: Melanie <melanie@t-data.com>
|
| |
|
|
|
|
| |
Provisionally applied to fix the naming. Signatures are still subject to change.
Signed-off-by: Melanie <melanie@t-data.com>
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Applied with change: Changed spelling to Summary (from Summery)
Signed-off-by: Melanie <melanie@t-data.com>
|
| | |
|
| | |
|
| |
|
|
| |
profiles
|
| | |
|
| | |
|
| |
|
|
|
|
| |
packet to be processed asynchronously or not.
* Make several packets not asynchronous (such as AgentUpdate). In theory, all fast returning packet handling methods should not be asynchronous. Ones that wait on an external resource or a long held lock, should be asynchronous.
|
| | |
|
| |
|
|
| |
specific limitation, it moves to the Linden Specific client handler.
|
| |
|
|
|
|
| |
See http://opensimulator.org/mantis/view.php?id=4356
Thanks Revolution
I performed a subsequent probable bug fix in this patch
|
| | |
|
| |
|
|
| |
handler delegates.
|
| | |
|
| |
|
|
| |
line switch.
|
| | |
|
| |
|
|
| |
handler delegate
|
| |
|
|
| |
of of that giant 5000 line switch, ProcessInPacket.
|
| | |
|
| |
|
|
| |
delegates
|
| |
|
|
| |
on prim should work fine again.
|
| |
|
|
|
|
| |
AttachPoint
* LLClientView.CreateImprovedTerseBlock() now uses AttachPoint and does the proper high-low swap (this should fix disappearing attachment pieces)
|
| | |
|
| | |
|
| |
|
|
|
|
| |
packet. This is a limitation of LLUDP, nothing we can really do about it
* Marking CoarseLocationUpdate as *not* zerocoded. Zerocoding can only save space when a packet contains three or more contiguous zeroes, and will use more space if it contains single zeroes randomly scattered through the packet (which is what you see when you send a long list of UUIDs)
|
| | |
|
| |
|
|
|
| |
Applied with major changes. Core functionality commented pending review
for possible rights escalation. No user functionality yet.
|
| |
|
|
|
| |
now 6, as before, item limit is 5. This should avoid most, if not
all, oversized packets.
|
| |
|
|
| |
for InventoryDescendents to the proper way
|
| | |
|
| |
|
|
| |
number of items per packet to 5 to prevent asserts
|
| | |
|
| |
|
|
|
|
|
| |
InventoryDescendents packet. Testing has shown that UDP inventory now
works flawlessly and, unlike CAPS inventory, doesn't download the entire
agent inventory on start. Neither does it incessantly re-request folder
NULL_KEY. Therefore, I have disabled CAPS inventory.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
packet is a mess and shouldn't be used at all (in favor of the event queue message)
* Clean up the way we send AvatarGroupsReply packets, including clamping the group name and group title
|
