| Commit message (Collapse) | Author | Files | Lines |
|---|
|
Adds handlers for the reclaim land functionality,
plus all needed permissions checks.
|
|
|
|
OnRequestMapBlocks event (and handler), as when a client sends a map block request it also sends what layer it wants it for 0,1,2. It will always send two requests, one of them being for layer 2 (the overlay layer) and the other one either 0 or 1 depending on the tab that is selected in the client worldmap window. We should also be sending what layer the reply is for in IClientAPI.SendMapBlock (current always set to 0). That will come in next part (most likely at the weekend).
|
|
World->Region/Estate. Then on the Estate tab, at the lower right hand corner, clicking the 'Add' button and picking an avatar.
* It only persists across reboots for the mySQL datastore currently.
* Currently have stubs in the other datastores.
|
|
plugin. This makes it easy for developers to experiment with alternative communication protocols
|
|
Implements terrain bake from Region/Estate dialog and
respects estate settings during terraforming
|
|
|
|
something else
|
|
same instance.
* Only generates a new maptile after a refresh interval
* Maptile names have the UnixTimeSinceEpoch that they were generated and the regionUUID they're from, so you can know which ones are no longer necessary.
* Updates RegionInfo, so backup your /bin/Region/*.xml files.
|
|
* Implemented a hack so regions beyond the 10,000m range will show the map without having to click on the map before they'll start to show. The hack shows regions around the one you're in, but it won't show the one you're in.. you still need to click on the map to get that (not sure why yet). Additionally, the map still only shows pictures for regions that are hosted on the same instance (no change).
|
|
override the default method of calculating how many prims a parcel can have.
|
|
|
|
interesting, but successful way to do it.
* This also takes care of a few error situations that were previously never seen.
|
|
|
|
the client thread terminating when creating a new script.
|
|
commit
|
|
warning for debugging purposes
|
|
up the resources
|
|
* Ignoring it on reload as of yet
|
|
removes a lock on every SendPacketTo call, which was shown to have
good performance benefits by the IBM China Research Lab.
|
|
|
|
unmolested
* These are only thrown on client shutdown anyway
* This stops the console (harmlessly) spewing stack traces when a client logs off
|
|
actually be all that tricky to try better clean up on a client thread crash. Haven't actually implemented
this, though
|
|
|
|
fails by catching the exception in AuthUser() instead of letting it propogate out of the thread
|
|
mono. Need to sort that out with DJ shortly.
|
|
Set udp flags correctly to prevent "Socket forcibly closed by host"
errors.
|
|
|
|
Dropping.' message
|
|
must remember to nant clean
* Hook all server startups into base opensim server startup method
|
|
|
|
* Now all servers respond to the "show version" command on the console
|
|
- volume doesn't change with a new llLoopSound(same sound, new volume);
- SendFullUpdateToClients sends 0's in all sound related fields when
there's no sound on the prim, thereby improving the amount of data being
sent out on these prims (fixes zeropack)
- Removed some code duplication between llStartSound, llLoopSound and llParticleSystem() calls
|
|
|
|
llLoopSound sends out one packet to clients in view, so it doesn't work anymore
when clients enter later on, or the prim is modified in any way.
Solution: Stored sound data on prim, send full update instead.
llStartSound and llLoopSound now accept both LLUUIDs to a sound as well as object
inventory sound names. llStopSound clears prim data and sends full update.
|
|
duplication causing 2-3 duplicates depending on the UDP connection quality. This also eliminates duplicated chat, etc.
* It's verbose currently since this is new. You'll see: [CLIENT]: Warning Duplicate packet detected X Dropping. After this is sufficiently tested we'll remove that m_log.info line.
|
|
that creates the event handler chain ready to hook by script engines
|
|
prims
* no user functionality yet
|
|
|
|
however you can use it to help find out what scripts are causing your simulator to cry.
* Access it from the Estate tools/Debug tab.
|
|
|
|
* If the agent throttle byte array is unexpectedly empty, then log a warning and drop the packet
|
|
There's some oddness with the parcel counts, but if you can get past the oddness, you can return objects under an owner that you have permission to return.
|
|
* If user is in the same sim with you, they'll get an inventory update, if not.... oh well, they'll have to clear their cache potentially before they'll see it.
|
|
finding out which region a new avatar was logging in to; the same problem
occurred when the client/avatar logged out. the reason was mani-fold:
- Scene.AddNewClient(...) would call SubscribeToClientEvents(client)
which would subscribe to all client events and then call
TriggerOnNewClient(...) BEFORE the ScenePresence object had even been
created and added. i've moved the TriggerOnNewClient() call to the
end of Scene.AddNewClient()
- Scene.AddNewClient(...) is called with child == true; a later call
to ScenePresence.MakeRootAgent() will turn child to false. When
OnNewClient is triggered, child is still true, causing IRCBridgeModule's
FindClientRegion to ignore the ScenePresence of the new avatar.
i've changed IRCBridgeModule to still use OnNewClient and also OnLogout
and OnConnectionClosed but only to signal that the avatar has logged on
(logged off respectively). to track whether an avatar has actually entered
a region i've added EventManager.OnMakeRootAgent (complementing
OnMakeChildAgent).
also, i've cleaned up the internal IRCModule code a bit. currently it
still uses IClientAPI.SendChatMessage() which replicates the code in
ChatModule, that needs to be changed to use TriggerOnChatFromWorld().
|
|
Nothing huge, but the new button code for producing
a new script does well, but the script will not allow
for name change once created. It reverts back to new script.
|
|
packets in rapid fire as quickly as possible. The terrain data sending is now done in a threadpool worker thread over ~10 seconds with a thread.sleep between each packet sending. this hasn't been tested thoroughly, so it might not actually help with the atom bomb terrain (missing patches) but its a simple thing to revert if it makes things worse for anyone.
10 seconds is roughly the time between the region handshake completing and you being in world where you can see your avatar. So normally the terrain still should have loaded by time you get in the region, although it is possible that sometimes you might see the very end of the terrain load just after you arrive.
|
|
|
|
information from Scene to OpenSimMain
* This also means the operating system info will show up in the region console (and hence the logs)
|
|
|
