Viewer compatibility

← Back to docs · Integration architecture · Architecture

Current viewer compatibility status, updated as live testing progresses.

Supported viewers

ViewerLoginIn-worldStatus
Aurora ViewerYesPartialFirst connected 2026-11-14
Firestorm (OpenSim build)YesWorkingTested 2026-11-14
LibreMetaverse botYes10/10 steps on a fresh regionAutomated test client

Groups

Groups are off by default; turn them on with [Groups] Enabled = true (see the configuration reference). The region talks to the grid's groups service, which welkin-robust provides. These behaviours come from the code and its tests, not from a live viewer run.

Working:

  • Group data is sent at login, so the viewer shows the avatar's groups with their real names.
  • The active group appears in AgentDataUpdate.
  • A viewer can create a group, join one, leave one, update a group's info and activate a group. The region replies with the viewer's usual reply messages and refreshes the avatar's group state after a change.
  • A viewer can open a group's profile and read its member list, its roles, the titles the avatar may pick, and which members hold which role. Members see the whole list. An avatar that is not a member sees only the members who hold a role with the MemberVisible power (bit 50 of the role powers), as OpenSimulator does; if the Everyone role has that power, every member is visible.
  • Member lists and role-member lists go out in several replies, each kept to a budget of about 1000 bytes, so a large group does not overflow a UDP packet.
  • A member with the right to invite can invite another avatar to the group. The region stores the invitation in the groups database, so it survives a restart, and sends the invitee an instant message. The invitee can accept, which adds them to the group and refreshes their group state, or decline. A refused invitation shows the inviter "Unable to invite that agent (no permission, or already a member)." The region logs a failed invitation lookup.
  • If you test invitations with a LibreMetaverse bot, note that LibreMetaverse declines a group invitation unless the bot's GroupInvitation handler sets Accept. An earlier failure reported as "accept does not add the member" was the test harness; accepting on the server works.
  • The group founder holds the Owner role only, not Owner and Officer both.
  • Members can manage the group from the viewer's group window: create, update and delete roles (including their powers), assign members to roles or remove them, change the avatar's own title, set whether the avatar accepts group notices, and eject a member. An ejected member's viewer drops the group, and a request from an avatar that is not allowed to make the change is refused with an alert message.

How it differs from OpenSimulator:

  • The region refuses a join request for a group with closed enrollment and shows the viewer "This group is not open for enrollment." OpenSimulator does not check this and relies on the viewer to hide the Join button. This is a deliberate improvement.
  • Every group handler acts for the authenticated avatar of the connection and never reads the agent ID that a packet claims, so one avatar cannot create, join, leave or change groups in another avatar's name.
  • GroupPowers in the login group data is an 8-byte big-endian binary value, the same encoding OpenSimulator uses.
  • The region makes its calls to the groups service without holding the session lock, and runs each group request in its own task. A slow or hung groups service therefore does not stall the region's packet loop or the avatar's other traffic; a test with a hung service covers this. The connector times out a request after 15 seconds and a connection attempt after 5 seconds, and speaks the XML protocol that ROBUST's groups service uses.

Who may do what: the grid groups service (welkin-services) checks each change against the powers of the roles the requesting avatar holds. The region relays the request using the authenticated avatar as the requester. An avatar with no role in the group has no powers, so its requests are refused.

ActionPower required
Create a roleCREATE_ROLE
Update a roleCHANGE_ACTIONS
Delete a roleDELETE_ROLE
Update group info (charter, fee, enrollment)CHANGE_ACTIONS
Assign or remove another member's roleASSIGN_MEMBER, or ASSIGN_MEMBER_LIMITED, which also requires holding the role being assigned or removed; group owners always pass
Eject a memberEJECT, unless the avatar ejects itself
InviteINVITE; the region also limits the inviter to offering the Everyone role or a role the inviter holds
Send a noticeSEND_NOTICES

Choosing the avatar's own active role (its title) needs no power, but the avatar must hold the role it selects. If it does not, the groups service refuses and the viewer shows the alert "Unable to update group title."

An avatar's list of groups is kept current: if the slow login fetch of group data finishes after a newer change, such as creating a group, the region drops the stale list instead of sending it, so the viewer does not show the old set of groups. The region tracks this per avatar and forgets it at logout.

Group notices work (send, store, delivery and list), except notice attachments, which are not supported yet. Group proposals and votes are out of scope: they belong to a separate OpenSimulator module that has no service support in welkin-robust, and the approved design leaves them out.

Group chat: members can chat in a group's chat session from the viewer.

  • Starting the session (instant message dialog 15) adds the avatar to the group's chat roster if it is a member. The region answers through the event queue with ChatterBoxSessionStartReply, as OpenSimulator's groups messaging module does, and sends ChatterBoxSessionAgentListUpdates when someone joins, is added or leaves, so the viewer's participant list stays current.
  • A message (dialog 17) goes to the members currently in the roster. The sender must be in the roster or be a member of the group. Leaving the session is dialog 18. The roster is held in memory and an entry counts as current for 30 seconds.
  • The dialog numbers are pinned by a test. An earlier version used the wrong numbers for session start, send and drop (17, 20 and 14).
  • With groups turned off, the region refuses group chat and notice instant messages instead of handling them.

Hardening:

  • The region refuses instant messages of dialog 3 (group invitation) and 33 (notice attachment accepted) when a viewer sends them. Only the server creates those, so a client-sent copy is a forgery. This stops one avatar from sending another a fake invitation.
  • Group packets from one avatar run one at a time, in the order they arrive, through a queue that holds 64 packets. Packets beyond that are dropped with a warning, and the queue is cleared at logout. Role updates, role changes and group name requests process at most 64 entries per packet.

Limits to know about:

  • Groups are grid-only. Hypergrid avatar IDs are not supported.
  • There is no notice handling yet (a planned milestone). A group with closed enrollment can be joined only by accepting an invitation.
  • Only SQLite has been used, as with the rest of Welkin.
  • The tests ran in process against the groups router, not against a launched welkin-robust binary, so the full path from a viewer to a running grid is unverified.

Firestorm session (2026-11-14)

Tested with the Firestorm OpenSim build against a local Welkin grid (ROBUST + one region). Commits 053b903 through cfd4cae cover all work described below.

Login and connection

  • XMLRPC and LLSD login (Firestorm sends XMLRPC, LibreMetaverse 3.x sends LLSD)
  • Circuit establishment (UseCircuitCode, CompleteAgentMovement, RegionHandshake)
  • PacketAck processing (server clears acked packets)
  • Region handle formula: ((loc_x * 256) << 32) | (loc_y * 256)
  • ROBUST config separation (robust.toml for grid DB, welkin.toml for region DB)

Movement and navigation

  • WASD movement with walk, run and fly transitions
  • Map and minimap via MapLayer cap (POST and GET)
  • Local teleport via map
  • Cross-region teleport via EntityTransferModule (FSM flow, distance validation up to 4095m)
  • Region crossing with child agent handoff
  • Hypergrid teleport via gatekeeper resolution and UserAgentService verification
  • Sit and stand on objects

Object interaction

  • Permission enforcement on 14 object mutation handlers via DefaultPermissionsModule: ObjectDelete, MultipleObjectUpdate, ObjectName, ObjectDescription, ObjectShape, ObjectPermissions, ObjectSaleInfo, ObjectExtraParams, ObjectGroup, ObjectOwner, ObjectLink, ObjectDelink, ObjectDuplicate, ObjectDuplicateOnRay. Denied mutations log a warning and skip the operation.
  • Object persistence wired into region heartbeat (every 60 ticks) and graceful shutdown
  • Object creation (ObjectAdd with FullObjectUpdate broadcast)
  • Object editing: move, rotate and scale via MultipleObjectUpdate
  • ObjectSelect, ObjectDeselect
  • Touch events: ObjectGrab, ObjectGrabUpdate, ObjectDeGrab
  • Property editing: name, description, shape, permissions, sale info, extra params
  • RezObject, DeRezObject
  • ObjectLink, ObjectDelink, ObjectDuplicate
  • llSetPrimitiveParams/llGetPrimitiveParams with 90+ PRIM_* constants (shape, texture, color, glow, flex, light, sculpt)
  • llSetLinkPrimitiveParams/llSetLinkPrimitiveParamsFast
  • Vehicle dynamics: llSetVehicleType plus 6 vehicle functions with 46 VEHICLE_* constants and type presets (car, boat, airplane, balloon, sled)
  • llRezObject/llRezAtRoot with inventory validation and rez channel
  • Attachments: llAttachToAvatar, llDetachFromAvatar, llAttachToAvatarTemp with 38 ATTACH_* constants
  • Position and rotation targets: llTarget, llRotTarget with at_target/not_at_target events

Inventory

  • Inventory panel with full folder tree (16 categories)
  • Inventory caps: FetchInventoryDescendents2, FetchInventory2, FetchLib2, CreateInventoryCategory
  • Baked texture upload (UploadBakedTexture cap, two-phase, stored in ROBUST)
  • Inventory creation idempotency guard
  • Inventory offers between users

Communication

  • Chat send and receive (ChatFromViewer routed through ChatModule)
  • Instant messaging with full dialog dispatch (20+ message types)
  • Group messaging
  • Friendship management (offer, accept, decline, terminate)
  • ViewerEffect relay to other clients
  • UUIDNameRequest
  • ScriptDialogReply
  • llHTTPRequest with 25-pending throttle, config parsing, response channel
  • llRequestURL/llRequestSecureURL/llReleaseURL for inbound HTTP caps from scripts
  • llEmail/llGetNextEmail with 20s rate limiting and email queue
  • llGetNotecardLine/llGetNumberOfNotecardLines via dataserver events
  • llRequestAgentData with DATA_* constants via dataserver events

Avatar and presence

  • Avatar name resolution from ROBUST UserAccountService via RemoteAccountsConnector (POST METHOD=getaccount); falls back to "Unknown User" if unreachable. The reply nests the account data one level down, under <result type="List">, and the region reads the tag at any depth; an earlier version read only direct children, so every avatar name came back as "Unknown User"
  • Avatar profile viewing
  • Multi-user presence (new users see existing avatars)
  • AgentUpdate and ViewerEffect flowing
  • 53 region modules loaded
  • 20 NPC functions: osNpcCreate/Remove, osNpcMoveToTarget, osNpcSit/Stand/Touch, osNpcSay/Shout/Whisper, osNpcPlayAnimation/StopAnimation, osNpcSaveAppearance/LoadAppearance
  • osTeleportAgent/osTeleportOwner
  • osGetAvatarList, osKickAvatar, osForceOtherSit
  • osSetSpeed/osGetSpeed with per-avatar speed multiplier
  • SetDisplayName cap

Estate administration

  • EstateOwnerMessage dispatch with 11 sub-commands (setregioninfo, setregionterrain, restart, estateaccessdelta, simulatormessage and others)
  • FreezeUser: freeze/unfreeze target avatar with alert
  • EjectUser via TeleportFailed, remove presence, optional ban
  • GodUpdateRegionInfo for god-mode region settings
  • RequestRegionInfo with full RegionInfo reply

Physics

  • Rapier physics step running at 11ms (90fps)
  • Collision events (collision_start, collision, collision_end) flowing to scripts with per-frame diffing
  • Terrain heightfield collision via Scene::set_terrain()

World and environment

  • osSetDynamicTextureURL/osSetDynamicTextureData for runtime texture rendering
  • osSetRegionWaterHeight, osSetRegionSunSettings, osSetSunParam/osGetSunParam
  • osGetCurrentSunHour
  • osSetTerrainHeight/osGetTerrainHeight, osSetTerrainTexture/osSetTerrainTextureHeight
  • osTerrainFlush, osSetWindParam/osGetWindParam
  • osGetSimulatorMemory (reads /proc/self/status VmRSS)
  • osGetRegionSize, osGetRegionStats, osRegionNotice

Economy

  • MoneyModule trait with SampleMoneyModule
  • Economy data packets (EconomyData, MoneyBalance)
  • XML-RPC endpoints: /currency.php, /landtool.php
  • LSL money functions: llGiveMoney, llTransferLindenDollars, llSetPayPrice
  • DTL/NSL currency proxy mode
  • Gloebit REST client

Scripting pipeline (verified end-to-end)

Viewer script uploads use a two-step protocol: the viewer POSTs LLSD metadata to UpdateScriptAgent, which returns a one-shot uploader URL with state: "upload". The viewer then POSTs raw LSL source to that URL; the server compiles it, loads it into the VM, and returns state: "complete". Upload tokens are single-use (replay returns 404). Direct raw-text POST still works for bot tests and automation.

Script-to-scene change propagation: llSetPos, llSetRot, llSetScale and llSetText changes in ScriptContext flow back to SceneObjectPart after each scheduler tick, with terse ObjectUpdate broadcast for transform changes and full ObjectUpdate for hover text changes. Threshold-based diffing (0.001) prevents unnecessary broadcasts.

The bot test validates the full scripting chain: rez a prim, upload LSL, confirm state_entry fires llSay, send ObjectGrab, confirm touch_start fires llSay. The bot test has 10 steps (login, region connect, chat send, chat echo, movement, rez prim, script upload, script alive, touch event, logout). The bot test passes 10/10 on a fresh region; on a region that already holds objects from earlier runs the touch step can fail. The cause is under investigation; probably the test picks a stale prim.

Known limitations

  • Terrain edits made in the viewer: see Terraforming for what is and is not supported
  • Avatar animations on Aurora Viewer (needs AgentAnimation packet)

Not yet user-tested

These features are implemented and code-verified but have not been validated by a user in a live viewer session:

  • Local teleport between regions
  • A 10-minute soak test on either viewer: no completed run is on record
  • Reconnection after viewer restart
  • Full Firestorm re-test after the chat/map/stub fixes

Known viewer messages

These are Firestorm-internal warnings that appear with an empty inventory and do not indicate server bugs:

  • "Could not put on outfit" (no clothing items in inventory)
  • "Could not load settings" (no viewer settings in inventory)

Parcels

These behaviours come from the region code and its tests; they are not yet confirmed in a live viewer session.

  • A viewer will not let an avatar fly in a region unless it receives a parcel with the AllowFly flag. The region now sends ParcelProperties when an avatar enters and in reply to every ParcelPropertiesRequest. It sends the data both over UDP and through the event queue, because modern viewers read it from the event queue.
  • The region has one parcel that covers the whole region: local ID 1, named "Your Parcel", owned by the estate owner, with room for 15,000 prims and OpenSimulator's default parcel flags (flying allowed).
  • Land management is not implemented. Parcels cannot be divided, joined, edited, sold or bought, and the other parcel requests (ParcelInfoRequest, ParcelDwellRequest and the access list requests) are not handled.

Instant messages

  • The region no longer forwards the sender's circuit session ID to the recipient of an instant message. That ID is a secret of the sender's connection, and the recipient's viewer had been able to read it. The relayed message now carries a nil session ID.
  • The session ID of a person-to-person conversation is the XOR of the two agents' IDs, which is how viewers compute it, so both viewers file the messages in the same conversation.

Terraforming

These behaviours come from the region code and its tests, including round-trip tests of the terrain encoder against the viewer's decoding algorithm; they are not yet confirmed in a live viewer session.

  • A viewer's ModifyLand request edits the scene's terrain, and the changed patches are sent to every connected viewer as LayerData. The region no longer sends a flat 21 m terrain.
  • The six brushes ported from OpenSimulator are flatten, raise, lower, smooth, noise and revert. A single click paints a round brush; viewers send the brush radius in the extended block, and older viewers send only a 1, 2 or 4 m size index. A dragged rectangle over the whole region applies the same action to the whole area, as OpenSimulator's flood brushes do. An area edit limited to one parcel is not supported yet and does nothing.
  • The terrain encoder follows the Second Life LayerData format: a discrete cosine transform per 16 by 16 patch, zigzag ordering and quantisation. The region is 16 by 16 patches. Updates are split into packet-sized payloads, and the transform uses lookup tables.
  • A request is applied only if the requesting avatar may edit terrain (can_edit_terrain). Requests with NaN or infinite values, or absurd ones, are dropped whole; see the terraforming security review.
  • Edited terrain is saved on the backup timer in OpenSimulator's terrain format and loaded again at start; see the configuration reference.
  • Each avatar can send one terrain edit every 20 ms, as in OpenSimulator. Requests that arrive sooner are dropped.
  • Golden test vectors generated by OpenSimulator 0.9.3.0 check the encoder: 17 match byte for byte and 2 are checked by decoding only.

Aurora Viewer session (2026-11-14)

First viewer connection to Welkin. No recording or log of this session is on record, so treat the notes below as unverified. Aurora uses a non-standard LLUDP flag layout: ZEROCODED=0x80, ACK=0x10 (swapped vs the Linden Lab specification). The server handles both layouts via the aurora-msg crate. Aurora connects via XMLRPC login on port 8002 using the --loginuri flag for grid selection.

Connection sequence

Login, circuit established, region handshake, terrain data, avatar appearance, event queue, presence registered. The full sequence completes without manual intervention.

Working

  • XMLRPC login on port 8002
  • Circuit and region handshake
  • 256 terrain patches rendered (flat terrain, height 21.0)
  • Avatar visible with wearables and name display
  • EventQueue (LLSD long-poll, 25s timeout)
  • Minimap (CoarseLocationUpdate at 3s interval)
  • Ping keepalive
  • Camera rotation
  • Capabilities HTTP
  • 9 region modules loaded

Soak test

No completed soak test is on record. An earlier note here claimed a clean 10-minute Aurora run at 60 fps, but no log or recording supports it, so the claim was removed. Treat long-session stability as untested.

Known gaps

  • GetDisplayNames returns 404 (not yet implemented, non-critical)
  • Avatar animations (T-pose, needs AgentAnimation packet)
  • Movement (needs position update echo)
  • Textures (asset service schema bug at time of test)

Inventory objects and attachments

These behaviours come from the region code and its end-to-end tests with real grid services; they are not yet confirmed in a live viewer session.

Taking and returning objects (DeRezObject): the region saves the object to inventory, as an asset and an inventory item, before it removes the object from the scene. The permissions module must allow the action.

  • Take and Take copy put the item in the folder the viewer chose, or the Objects folder if it chose none.
  • Delete puts the item in Trash when the owner deletes it, and in Lost and Found when someone else does.
  • Return puts the item in the owner's Lost and Found.
  • The item's permissions follow OpenSimulator's rules: the owner keeps the object's permissions, and anyone else gets them cut down to the next-owner permissions.

Buying an object (ObjectBuy): the region checks the sale and, if it passes, puts the object in the buyer's inventory in the folder the buyer chose, and sends the new item to the buyer's viewer. These behaviours come from the code and its tests, not a live viewer run.

  • The sale type and price in the request must match the object. The region refuses an object that is not for sale, a request whose sale type differs from the object's, and a request whose price differs from the object's price.
  • A copy sale gives the buyer a copy and the object stays in the scene. An original sale moves the object itself: it is saved into the buyer's inventory and removed from the scene. Contents sales are not supported and are refused.
  • When the region refuses a purchase, the buyer sees the alert "Unable to buy: ." (for example "not for sale" or "price changed"), and the region logs the refusal.
  • No money moves. The sample economy charges nothing, so a purchase is free whatever the price.

Attachments: an attachment is an object worn by an avatar.

  • Viewers see a worn object in ObjectUpdate with the avatar as its parent, the attachment point swapped into the position the viewer expects, and the inventory item ID it came from. Attached objects leave the physics engine.
  • The region handles wearing an inventory object, one or several at a time, attaching an object that lies in the world (a copy goes into inventory first, so it can be taken off again), detaching to inventory, and dropping to the ground.
  • An avatar can wear up to 38 attachments, as in OpenSimulator. The viewer's append flag (0x80) adds to what is worn at a point instead of replacing it. When the viewer names no point, the region picks the last point the object used, or the left hand.
  • When an avatar logs out, times out or is ejected, the region saves each attachment into its inventory item and removes it from the scene and from every viewer.
  • The region checks that an attach can succeed before it copies a world object into inventory, so a failed attach does not leave a stray inventory copy.
  • The region remembers what each avatar wears in the grid's avatar service, in one _ap_<point> entry per attachment point, and wears the same items again at the avatar's next login.

Avatar movement and physics

These behaviours come from the region code and its tests; they are not yet confirmed in a live viewer session.

  • Avatars stand on the real terrain. The avatar movement code and the physics engine read one terrain source, so an avatar and a dropped prim agree on where the ground is. A standing avatar's centre sits 1.0 m above the ground.
  • A walking avatar can jump. Pressing jump (the UP_POS control while walking) gives an upward speed of 5.0 m/s, about 1.3 m of height. An avatar that is in the air, including one that stops flying, falls under gravity of 9.80665 m/s^2 (OpenSimulator's standard value) to a terminal speed of 54 m/s and lands on the terrain. A flying avatar cannot go below the ground.
  • Each avatar keeps its vertical velocity between updates, and the region sends it to viewers. Jump and fall are integrated in fixed 0.02 s sub-steps, so jump height does not depend on how often the viewer sends AgentUpdate.
  • A walking avatar that is in the air plays the JUMP animation while it rises and the FALLDOWN animation while it falls. The region counts an avatar as airborne when it is not flying and is more than 0.1 m above its standing height. On the ground, holding the crouch control plays CROUCH, or CROUCHWALK when the avatar is also moving. The region logs each animation change (control flags, flying state and animation) at info level, which helps when you diagnose a flying problem.
  • Physical prims move under the Rapier physics engine. The region copies the simulated position and motion back into the scene and sends terse updates to viewers, including a final update with zero velocity when an object comes to rest. When a script or an edit moves an object, the move is pushed into the physics engine so the collider follows.
  • The terrain collider is built at the full region size and orientation. An earlier version covered only 1 m by 1 m and was transposed, so objects fell through the ground.
  • Script physics commands reach the physics bodies; see the script engine page.

Scene delivery and object creation

These behaviours come from the region code and its tests (including a UDP round trip that parses the sent datagrams); they are not yet confirmed in a live viewer session.

  • When a viewer arrives, the region sends it every object already in the scene. The root prim and every linkset child are sent as full object updates, in batched ObjectUpdate packets, with their sound fields and texture entry.
  • ObjectAdd builds the new prim from the shape the viewer sends: prim code, state, scale, rotation, and every path and profile field (curve, begin, end, scale, shear, twist, taper, revolutions, skew, radius offset, hollow). A tube, torus or hollow prim made in the viewer keeps its shape. The state value is also copied into the last attach point, as OpenSimulator does. The texture entry is left empty, so the prim uses the default plywood texture.
  • A full object update, for example after a script changes a sound, sends the root and every linkset child, batched. It no longer sends the root alone.
  • Rezzing an object from inventory (RezObject) fetches the inventory item and its asset, reads the object XML, gives every part a new ID, and sets the owner to the rezzing avatar and the permissions from the item. The permissions module must allow the rez. Coalesced objects are not supported yet.
  • All three paths build their updates through one function in scene_sync.rs, so a prim looks the same whichever path sent it.

Capabilities

42 capability route entries implemented:

CapStatus
AgentPreferencesWorking
AvatarPickerSearchWorking
ChatSessionRequestWorking
CopyInventoryFromNotecardWorking
CreateInventoryCategoryWorking
DispatchRegionInfoWorking
EnvironmentSettingsWorking (GET and POST)
EstateChangeInfoWorking
EventQueueGetWorking (25s long-poll)
FetchInventory2Wired to ROBUST xinventory
FetchInventoryDescendents2Wired to ROBUST xinventory
FetchLib2Working
GetDisplayNamesWorking
GetMeshProxied to ROBUST asset service
GetMesh2Proxied to ROBUST asset service
GetTextureProxied to ROBUST asset service
GroupMemberDataWorking
HomeLocationWorking
LandResourcesWorking
MapLayerWorking (POST and GET)
MeshUploadFlagWorking
NewFileAgentInventoryWorking
RegionInfoWorking
RemoteParcelRequestWorking
SearchStatRequestWorking
ServerReleaseNotesWorking
SetDisplayNameWorking
SimConsoleAsyncWorking
SimulatorFeaturesWorking
UpdateAgentInformationWorking
UpdateAgentLanguageWorking
UpdateGestureAgentInventoryWorking
UpdateGestureTaskInventoryWorking
UpdateNotecardAgentInventoryWorking
UpdateNotecardTaskInventoryWorking
UpdateScriptAgentTwo-step LLSD upload (like bake textures); raw POST fallback for bots
UpdateScriptTaskWorking
UploadBakedTextureTwo-phase, stores in ROBUST
ViewerAssetWorking (all asset type query params: texture_id, bodypart_id, clothing_id, etc.)
ViewerMetricsWorking
ViewerStatsWorking

Protocol notes

  • Firestorm and Aurora use different login codecs: Firestorm sends XMLRPC, LibreMetaverse 3.x sends LLSD. Both are supported.
  • Aurora swaps the ZEROCODED and ACK flag bits in the LLUDP header. Welkin detects and handles both layouts.
  • Terrain is sent as real LayerData: a DCT, zigzag and quantised encoding of the heightfield, in packet-sized payloads (see Terraforming). The flat-terrain shortcut (range 0, offset 21.0) is gone.

Sound protocol

Sound messages follow OpenSimulator's behaviour:

  • AttachedSound carries flags 0, or QUEUE (0x10) for llPlaySound with queueing on.
  • SoundTrigger goes only to avatars inside the prim's sound radius; a radius of 0 is treated as 100 m.
  • PreloadSound goes to avatars inside twice the sound radius.
  • A looping or stopped sound is carried in a full ObjectUpdate for the root prim, so avatars who enter the region later hear the loop. STOP is flag 0x20.
  • A prim that has a saved sound comes back from a restart looping, with the LOOP flag set and a radius of 100 m. The saved data does not keep the loop flag or the radius, so the region restores both for any prim with a sound.

See the script engine page for the LSL side.

Commits

HashDescription
053b903Firestorm login fixes (real_id, inventory root, buddy list)
9d82a90Remove chat stub, fix MapBlockRequest, fix ChatFromViewer routing
6f04835Remove 21 log-only stub handlers (-297 lines)
f4ec89fAgentSetAppearance handler (orange cloud fix)
3d927aeMovement, teleport and object creation support
079f043Firestorm session completion (sit/stand, profiles, multi-user)
8da4f35 .. eb634b0Object interaction: editing, properties, rez, link, duplicate
3b7c2d8 .. 368e61dModule activation: 9 to 53 region modules
c6834aa .. afdecf9Viewer messaging: IM dispatch, groups, friends, effects
dcc3e8b .. cc9520aCurrency: MoneyModule, economy packets, Gloebit client
14d769fInfrastructure builtins: llHTTPRequest, llSetPrimitiveParams, vehicle, email, attachments, targets, notecard reading
1dd130219 new HTTP capability handlers (42 total routes)
fa8de4dEstate admin, cross-region teleport, region crossing, HG teleport
cfd4caePhysics verification, 20 NPC functions, os* teleport, dynamic textures, 100+ os* functions
e94f119Register LSL builtins on VM so scripts actually execute (ScriptContext wiring)
c707f3bBot test: script upload, execution and touch interaction (10 steps)
56d05a3ViewerAsset: support all asset type query params (bodypart_id, clothing_id, etc.)
3d68f07UpdateScriptAgent: two-step LLSD upload protocol (fixes viewer-initiated uploads)
f94dacdObject persistence wired into region heartbeat and shutdown (85+30 field mappings)
69f0db4Permission enforcement on 14 object mutation handlers
58e5d0aAvatar name resolution from ROBUST, script-to-scene change propagation