| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
only ever using the root part entry.
This eliminates some pointless memory use.
|
| |
|
|
|
|
| |
prim collision status
factor out common SOP physics scene adding code into a common SOP.AddToPhysics() that is the counterpart to the existing RemoveFromPhysics()
|
| |
|
|
|
|
|
|
| |
null then assume it was still not null in later code.
Another thread could come and turn off physics for a part (null PhysicsActor) at any point.
Had to turn off localCopy on warp3D CoreModules section in prebuild.xml since on current nant this copies all DLLs in bin/ which can be a very large number with compiled DLLs
No obvious reason for doing that copy - nothing else does it.
|
| |
|
|
| |
the 'root' part.
|
| |
|
|
| |
notifying client of no build permission
|
| | |
|
| |
|
|
|
|
|
| |
caching.
This adds ScenePresence to IClientAPI.SceneAgent earlier on in the add client process so that its information is available to EventManager.OnNewClient() and OnClientLogin()
Also add a code comment as to why we're caching friend information for child agents.
|
| |
|
|
|
|
|
|
| |
functions require caching for child agents."
We need to cache child agents so that friends object edit/delete permissions will work across boarders on regions hosted by different simulators.
This reverts commit d9f7b8549b3cb9699eb8bd54242d31aac0f8241a.
|
| |
|
|
| |
This reverts commit 964cae4f37120db34d0d3e2f08ab998215237dfd.
|
| | |
|
| |
|
|
|
|
|
|
| |
require caching for child agents.
This allows us to avoid unnecessary multiple calls to the friends service.
All friends functions originate from the root agent and only go to other root agents in existing code.
This also allows us to eliminate complex ref counting.
|
| | |
|
| |
|
|
| |
guarded by an obscure config that no one but me should be using at this point.
|
| |\ |
|
| | |
| |
| |
| | |
Experimental: we'll try switching the root folder from under the viewer.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
[Startup] in OpenSim.ini
On osgrid and other places, I have observed that manually sending appearance updates from the console often relieves grey avatar syndrome.
Despite hunting high and low, I haven't been able to find where this packet is sometimes being lost - it might be a persistent viewer bug for all I know.
Therefore, this experimental setting resends appearance data for everybody in the scene every 60 seconds. These packets are small and the viewer only fetches texture
data if it doesn't already have it.
Default is false.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
maintenance thread will end up running regular jobs that don't need to be in the main scene loop.
The idea is to make the critical main scene loop as skinny as possible - it doesn't need to run things that aren't time critical and don't depend on update ordering.
This will be done gradually over time to try and uncover any issues. Many non-criticial scene loop activities are being launched on separate threadpool threads anyway.
This may also allow modules to register their own maintenance jobs without having to maintain their own timers and threads.
Currently the maintenance loop runs once a second, as opposed to the 89ms scene loop.
|
| | |
| |
| |
| | |
method doc. Rename HeartbeatThread, shuttingdown to conform to code standards.
|
| | |
| |
| |
| | |
Comment out more effectively unused old heartbeat code.
|
| | | |
|
| | |
| |
| |
| | |
Forgot to uppercase the animation name for default animations, since for some reason we store and use them in upper rather than lowercase.
|
| | |
| |
| |
| | |
This has actually been unused since at least 0.7.2 due to earlier changes.
|
| | |
| |
| |
| | |
m_lastUpdate is no longer properly updated and is redundant anyway.
|
| | |
| |
| |
| | |
This was not implemented before the recent changes but should be at some point.
|
| | |
| |
| |
| | |
collection occurs.
|
| | |
| |
| |
| |
| |
| |
| | |
when a frame updates takes longer than twice the desired time
This is controlled via "debug scene updates true|false" on the region console.
Also fix an oversight with "debug scene teleport true|false"
|
| | |
| |
| |
| | |
true|false" command
|
| | |
| |
| |
| |
| |
| | |
scripting true" or other parameters as appropriate.
This is to allow individual switching of scene debug settings and to provide flexibiltiy for additional settings.
|
| | |
| |
| |
| | |
time. Currently commented out.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
analysis and stat accuracy.
Update() now accepts a frames parameter which can control the number of frames updated.
-1 will update until shutdown.
The watchdog updating moves above the maintc recalculation for any required sleep since it should be accounted for within the frame.
|
| | | |
|
| | |
| |
| |
| | |
UserManagementModule where it belongs. No functional changes.
|
| | |
| |
| |
| | |
DisallowForeigners (means what it says) and DisallowResidents (means that only admins and managers can get into the region). This puts the never-completed AuthorizationService to good use. Note that I didn't implement a grid-wide Authorization service; this service implementation is done entirely locally on the simulator. This can be changed as usual by pluging in a different AuthorizationServicesConnector.
|
| | |
| |
| |
| | |
terrain. Default is still pinhead island. I much rather have a flat land in the beginning.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
multiple scripts in the same linkset can cause unnecessary thread aborts.
The first llDie() could lock Scene.m_deleting_scene_object.
The second llDie() would then wait at this lock.
The first llDie() would go on to remove the second script but always abort it since the second script's WorkItem would not go away.
Easiest solution here is to remove the m_deleting_scene_object since it's no longer justified - we no longer lock m_parts but take a copy instead.
This also requires an adjustment in XEngine.OnRemoveScript not to use instance.ObjectID instead when firing the OnObjectRemoved event.
|
| | |
| |
| |
| |
| |
| | |
are still lowercase.
Also convert the estate commands to simply AddCommand() calls so that commands from two different modules can be placed in the same category
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
<category/module>" to display commands in a category.
This is to deal with the hundred lines of command splurge when one previously typed "help"
Modelled somewhat on the mysql console
One can still type help <command> to get per command help at any point.
Categories capitalized to avoid conflict with the all-lowercase commands (except for commander system, as of yet).
Does not affect command parsing or any other aspects of the console apart from the help system.
Backwards compatible with existing modules.
|
| | |
| |
| |
| |
| |
| | |
We can now do this since the entire scene and all objects within it are now successfully gc'd at the end of these tests.
This greatly improves the time taken to run each test (by reducing teardown time, not the time to actually do the test work that we're interested in).
Slightly simplifies config read in Scene constructor to help facilitate this.
|
| | |
| |
| |
| | |
This is another step necessary for the scene to be garbage collected between performance tests
|
| | |
| |
| |
| | |
Scene.PipeEventsForScript()
|
| | |
| |
| |
| |
| |
| |
| |
| | |
allowed to run rather than checking its own prim.
This allows scripts to run in child prims that are outside region boundaries.
This is an interim patch applied from http://opensimulator.org/mantis/view.php?id=5899 though it does not resolve that bug
Thanks tglion!
|
| |/
|
|
| |
TriggerOnSceneObjectLoaded.
|
| | |
|
| |
|
|
|
|
|
|
| |
On the first frame, all startup scene objects are added to the physics scene.
This can cause a considerable delay, so we don't start raising the alarm on scene loop timeouts until the second frame.
This commit also slightly changes the behaviour of timeout reporting.
Previously, a report was made for the very first timed out thread, ignoring all others until the next watchdog check.
Instead, we now report every timed out thread, though we still only do this once no matter how long the timeout.
|
| |
|
|
|
|
|
|
|
|
| |
banlines or freezing on the banline.
This involves
1) On forcible teleport, call m_scene.RequestTeleportLocation() rather than ScenePresence.Teleport() - only EntityTransferModule now should call SP.Teleport()
2) When avatar is being forcibly moved due to banlines, use a 'stop movement' tolerance of 0.2 to requested position rather than 1
This prevents the avatar sometimes being stuck to banlines until they teleport somewhere else.
This aims to fix some problems in http://opensimulator.org/mantis/view.php?id=5822
|
| |\ |
|
| | |
| |
| |
| | |
constructor and never subsequent set to null.
|
| |/
|
|
|
|
| |
potential bad update that places an object at the opposite side of the
origin sim for a moment before actually crossing it. Especially important in
grids like OSG where lag between sims is high.
|
