| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | | |
|
| |/
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
absurd 3m vertical jump to better match what you would see in Second
Life and be more in line with what users would expect.
|
| |
|
|
| |
(sqrt(2)) rather than doing it multiple times on every move.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
the same time.
Have to lock m_MeshToTriMeshMap as property is static and with more than one region two scene loops could try to manipulate at the same time.
|
| | |
|
| |
|
|
|
|
|
| |
was not active
Unfortunately, the OnLoginsEnabled event is currently only guaranteed to fire if the RegionReady module is active.
However, we can instantiate the AuthorizationService in the module RegionLoaded method since by this time all other modules will have been loaded
|
| |
|
|
|
|
| |
scripts in a region.
Addresses http://opensimulator.org/mantis/view.php?id=5940
|
| | |
|
| |
|
|
| |
the Basic one and the HG one, so that we can do everything that needs to be done for HG ACLs to work without interfering with the vanilla opensim. For the moment, it finds foreign users who have left a trace in the region, e.g. an object. This makes it possible to ban/IM/etc these users using the regular avatar picker. TODO: contact the UAS directly given a name of the form First.Last @foo.com.
|
| |
|
|
| |
UserManagementModule where it belongs. No functional changes.
|
| |\ |
|
| | |
| |
| |
| |
| | |
This allows one to get description data for a given prim inventory item.
Thanks MarcelEdward and GuduleLapointe!
|
| |/
|
|
| |
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.
|
| |\ |
|
| | |
| |
| |
| | |
These can start with ; # or //
|
| | |
| |
| |
| |
| |
| | |
of execution time.
This is to make the report clearer and less confusing.
|
| | |
| |
| |
| | |
This is for the top scripts report.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
measurement period and an idealised frame time.
The previous lines-per-second measurement used for top scripts report was inaccurate, since lines executed does not reflect time taken to execute.
Also, every fetch of the report would reset all the numbers limiting its usefulness and we weren't even guaranteed to see the top 100.
The actual measurement value should be script execution time per frame but XEngine does not work this way.
Therefore, we use actual script execution time scaled by the measurement period and an idealised frame time.
This is still not ideal but gives reasonable results and allows scripts to be compared.
This commit moves script execution time calculations from SceneGraph into IScriptModule implementations.
|
| |/
|
|
| |
being found or not, because the UI is horribly confusing -- places profile is always "loading..." whether the region exists or not.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
from region modules. The LSL translator is extended to generate the
modInvoke format of commands for directly inlined function calls.
A region module can register a function Test() with the name "Test".
LSL code can call that function as "Test()". The compiler will translate
that invocation into modInvoke("Test", ...)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
redefine the encoding of HG URLs because the viewer messes them up. Examples of what works and doesn't work:
- secondlife://ucigrid00.nacs.uci.edu|8002/128/128 <-- works throughout the viewer
- secondlife://http|!!ucigrid00.nacs.uci.edu|8002+Test+Zone+1/128/128 <-- works throughout the viewer
- secondlife://http|!!grid.sciencesim.com!grid!hypergrid.php+Yellowstone01+74/128/128 <-- works throughout
- secondlife://http%3A%2F%2Fucigrid00.nacs.uci.edu%3A8002%20UCI%20Central%201/128/128 <-- works in chat, but not as URLs in the webkit
|
| | |
| |
| |
| | |
This reverts commit e5612553ce57b6e36cfa59db8450473099054da1.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
needed.
Revert "Revert "Hack around https://jira.secondlife.com/browse/VWR-28570""
This reverts commit 5a9560db288a25799c93a3ecbd3544931149fa2a.
|
| | |
| |
| |
| | |
This reverts commit 697ac7fd9de244cb3b25ff8576838fd323b257c3.
|
| | |
| |
| |
| | |
This reverts commit 10731732b4d40ec9d9e7a21f406a3d2b5dfc1075.
|
| |\ \
| |/ |
|
| | | |
|
| | |
| |
| |
| | |
false in both if/else branches
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
to release locks, resulting in a crippled simulator.
This seems to be a particular problem with ReaderWriterLockSlim, though other locks can be affected as well.
It has been seen to happen when llDie() is called in a linkset running more than one script.
Alleviation here means supplying a ScriptInstance.Stop() timeout of 1000ms rather than 0ms, to give events a chance to complete.
Also, we check the IsRunning status at the top of the ScriptInstance.EventProcessor() so that another event doesn't start in the mean time.
Ultimately, a better solution may have to be found since a long-running event would still exceed the timeout and be aborted.
|
| | | |
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
it more understandable as to what it is and what it does (hold a thread pool work item for a waiting of in-progress event)
Also add other various illustrative comments
|
| | |
| |
| |
| | |
scripts do that, and that fails the whole thing.
|
| |\ \
| |/ |
|
