| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
From: Sean Dague <sdague@gmail.com>
|
|
|
|
|
| |
From: Sean Dague <sdague@gmail.com>
|
|
|
|
|
| |
From: Sean Dague <sdague@gmail.com>
|
| |
|
|
|
|
|
| |
Fixes Mantis #3006
|
| |
|
|
|
|
| |
teleport is being directed rather than just its position
|
|
|
|
|
| |
* Updates LibOMV to r2362
|
|
|
|
|
|
|
| |
* Since this is a db change, as always I strongly recommend that you backup your database before updating to this revision
* Haven't touched MSSQL in case I get it wrong - looking for some kind soul to take care of this.
|
|
|
|
|
|
| |
asset server doesn't check for the existence of this parameter since
r2744.
|
| |
|
| |
|
|
|
|
| |
getting the object moving.
|
|
|
|
|
|
|
| |
non-phantom from phantom.
Fixes Mantis #1883
|
| |
|
|
|
|
| |
useless, but sometimes problematic (mantis #2999). Initial tests indicate that this call is not necessary. Let's see if this stands in the wild.
|
|
|
|
|
|
| |
Fixes Mantis #3002
|
|
|
|
|
|
|
|
|
| |
teleport unit test with checks that the scene presence disappeared from sceneA and appeared in
sceneB
* However, I'm not convinced that the actual process in the test completely reflects reality, and a lot of stuff had to be rigged up (which should get resolved over time)
|
| |
|
|
|
|
|
|
|
| |
linked hypergrid region's real location is within 4096,4096 map spaces of its "local" location. If it is outside of that range ( so it wouldn't be possible to teleport to it) then it ignores it and doesn't create a link.
See the hypergrid wiki page for more details.
|
|
|
|
|
|
|
|
|
|
| |
from a xml file.
Console Command: link-mapping <StartXloc> <StartYloc>.
This results in only the last two digits of any of the locations defined in the xml file being used, and those 0-99 values being added to the StartXloc and StartYloc figures.
For more infomation, see the email on the mailing list and the soon to be added instructions on the wiki's hypergrid page.
Also made the Secion Names in xml file case insensitive.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
locking periods changed.
* Added an additional lock in GetScenePresences()
* Changed ForEachClient to use GetScenePresences() instead of the main ScenePresences dictionary, so that there is no need to lock.
|
| |
|
| |
|
|
|
|
|
|
| |
* Does not yet check results.
|
| |
|
|
|
|
| |
loading. So that certain links in the file will be ignored. See the wiki's hypergrid page for details (in about a hour).
|
|
|
|
|
|
|
|
|
| |
Although its currently still activated by using console command: link-region <URI of xml file> , the uri should be able to be a local file path or a http uri. I'm adding details of the format of the xml file to the wiki's hypergrid page.
TODO: Add a initial startup option for setting the uri and making it autoload it.
Add support for scanning the xml file to check that its own region(s) aren't in the list, and if they are, ignoring them. This would allow setting up "virtual link/grid lists" on webservers, that people can add their own regions to and also point those regions to those same lists, so they load the other region's data.
Add support for automapping of those region/link lists.
|
|
|
|
| |
Mantis #2908. Thanks Teravus for the suggestions :)
|
|
|
|
|
|
|
|
| |
* There appears to be a bug on mono 1.9.1 (and maybe later), where sometimes the async wait will be signalled even though that async callback has not executed
* This change may make it slightly better but it's difficult to tell (it definitely still occurs)
* Also this patch closes the wait handle explicitly, as recommended in the MSDN docs. This doesn't have any impact on the bug though
|
|
|
|
|
|
|
|
| |
notifications that won't actually lead to a client connection (because they are from a neighbouring teleport
target that needs to trigger a child seeds adjustment on a child agent that has been kept around)
|
|
|
|
|
| |
From: Arthur Rodrigo S Valadares <arthursv@linux.vnet.ibm.com>
|
|
|
|
|
|
|
|
| |
'new user notifications' that have existing scene presences
* The position will be reset if the connection turns out to be a root one, and since the client is already authenticated another authentication will not occur anyway
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
enabled it
* In fact, it would only be activated if there was no [Communications] section at all (which would be the case for most people with existing region setups unless they
specifically added it in
* This fix means that enabling inter-region rest comms is now the default
|
|
|
|
|
|
|
| |
* This fixes MSSQL for user friends lookups
* Thanks StrawberryFride
|
| |
|
|
|
|
|
|
|
|
| |
Multiple spaces or leading/trailing spaces when specifying the prims
to connect should no longer cause problems.
|
|
|
|
| |
locks of SceneGraph ScenePresences introduced in 7982, this was making TPs not close the agent in the departing region due to locking. That locking problem seemed to occur only in Linux/mono -- I suspect a mono bug here.
|
|
|
|
|
|
| |
to also transmit and use a Z coordinate.
|
|
|
|
|
| |
* This ensures that the user will be logged off successfully by a properly permissioned user server
|
|
|
|
|
| |
* Added a path for all sessionids to be logged off when a region secret is provided. (helps log-off dead agents).
|
|
|
|
|
|
| |
* CapsUtil.GetRandomCapsObjectPath(); contains a / and the regionInfo.httpServerURI contains a / so that makes
* response.SeedCapability = regionInfo.httpServerURI + CapsUtil.GetCapsSeedPath(capsPath); contain two "//" leading to a seed caps path definition like //CAPS/f7ba4238-ec86-4a2b-b3f6-4d9b56070000/, which is wrong
|
|
|
|
|
| |
From: Arthur Rodrigo S Valadares <arthursv@linux.vnet.ibm.com>
|
| |
|
| |
|
| |
|