| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
failing because they are giving an illegal initial position to ScenePresence.MakeRootAgent()
* If we detected an illegal position (x, y outside region bounds or z < 0), then print out the illegal position and substitute an emergency <128, 128, 128> instead
|
| |
|
| |
|
|
|
|
| |
border to a position below it. After teleporting, you can go under the terrain if you like as usual.
|
|
|
|
|
|
|
| |
interesting, but successful way to do it.
* This also takes care of a few error situations that were previously never seen.
|
|
|
|
|
|
|
| |
* User tries to log-in but is already logged in. Userserver will send message to simulator user was in to log the user out there.
* From the UserServer, admin types 'logoff-user firstname lastname message'.
* Some regions may not get the message because they're not updated yet.
|
|
|
|
|
| |
* Added a Non-finite avatar position reset. This will either handle the <0,0,0> avatar gracefully, or send the avatar to 127,127,127 if that also doesn't work. ( I've only been able to reproduce this error once on my development workstation )
|
| |
|
|
|
|
| |
you're a child agent before applying the changes from the grid comms. Doing this to rule it out as a source of a few bugs such as the Zombie bug and the Express Train to 0,0,0 bug.
|
| |
|
|
|
|
|
|
|
| |
check. It seems there may be a race. For me, this patch,
just as it is here, fixes it.
|
| |
|
|
|
|
|
|
|
| |
If the m_controllingClient member if a ScenePresence is
null, that would cause a CTB. This patch fixes 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().
|
| |
|
|
|
|
|
|
|
| |
lookup any time we get it from the server. This should
preventent unwearable appearance.
|
|
|
|
|
|
|
|
|
|
| |
Fix RequestUpdateInventoryItem so that asset changes
generate a new asset, which is needed for editing
appearance to do the right thing. Persistant appearance
seems to work after this, except you need to rebake textures
some times.
|
|
|
|
|
|
|
| |
get saved to the database. There are still issues on wearing things
after a cleared cache that I'm looking at now.
|
|
|
|
|
| |
Fix spelling typo (Thanks ChrisDown for pointing this out)
|
| |
|
| |
|
| |
|
|
|
|
| |
types and null.
|
|
|
|
|
|
|
|
| |
baffles me)
it does make setting appearance in grid stick.
|
| |
|
|
|
|
|
|
| |
prevent his crashes
|
|
|
|
|
|
| |
* This revision also includes a very temporary fix for the fact that NREs are received because of a missing avatar apperance in grid mode
|
| |
|
| |
|
|
|
|
|
|
|
| |
the MSSQL and MYSQL mappers back in under datastores and looking at doing
gid bits for this
|
| |
|
| |
|
|
|
|
|
|
| |
move the appearance sending bits to ScenePresence
|
|
|
|
| |
permissions modules. From Melanie. Thanks Melanie!
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* Down to 65 warnings.
|
|
|
|
|
|
|
|
| |
inaccurate count of neighbors.
* The neighbor count is always lower then the actual number of neighbors unless your region was up the longest.
* The region you're in is un-affected by this, though, you'll get less packet loss, maybe not get logged off immediately when you log in, and possibly see more prim if your internet connection is semi-unreliable.
|
| |
|
|
|
|
| |
(bug #1239).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From Melanie... Thanks Melanie!
.
|
|
|
|
|
|
|
|
| |
them out.
* Fix for Scene.Inventory.cs - It assumes every entity at startup is a SceneObjectGroup. (Actually, this shouldn't have compiled[!] without a warning.)
* Fix for LandManager at startup - it assumes there's a land channel when perhaps there isnt. (Bug that needs another refactor to fix. [Mike - I've assigned a ticket to you about this])
|
|
|
|
|
| |
*Moved OnSignificantClientMovement to where it is supposed to be - SceneEvents and not ScenePresence
|
|
|
|
|
|
|
|
|
| |
seen in one of the crashes of mantis 1163
* It's not impossible that this could lead to deadlock where sessions simply appear to freeze, even though the region console still responds.
* If this is the case, please file a mantis
|
|
|
|
| |
sitting on an object.
|