| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
this for debugging purposes, rather than before it actually starts to do this.
|
|
|
|
| |
name of user and the region they are in
|
|
|
|
| |
bypass close checks.
|
| |
|
|
|
|
|
|
|
| |
into the 3-parameter AddNewSceneObject() method instead of always hardcoding true.
This doesn't affect any core OpenSimulator code since all callers were passing true anyway
But it allows region modules to create objects that are never persisted.
|
| |
|
|
|
|
| |
xengine to spit out some useful information and continue to save other script states
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
connection string as [AssetService].
This is necessary because commit 8131a24 (Tue Mar 27 10:08:13 2012) started passing the config section name rather than hardcoding "AssetService"
This meant that the HG external-facing asset service tried to read ConnectionString from [HGAssetService] rather than [AssetService].
On SQLite, not finding this meant that it fell back to [DatabaseService], which is set for OpenSim.db rather than Asset.db.
Therefore, all external asset requests returned null.
Solution taken here is to create an [HGAssetService] section with the same ConnectionString as [AssetService].
This bug does not affect normal MySQL/MSSQL config since they use the [DatabaseService] connection string anyway.
Addresses http://opensimulator.org/mantis/view.php?id=6200, many thanks to DanBanner for identifying the exact problem commit which was very helpful.
This was a regression from OpenSimulator 0.7.3.1 which did not contain this bug.
|
|
|
|
|
|
|
|
|
|
| |
prevents malloc heap corruption seen under Ubuntu 10.04.1 and 11.04 - probably a libcairo issue
In testing, it appears that if multiple threads dispose of separate GDI+ objects simultaneously,
the native malloc heap can become corrupted, possibly due to a double free(). This may be due to
bugs in the underlying libcairo used by mono's libgdiplus.dll on Linux/OSX. These problems were
seen with both libcario 1.10.2-6.1ubuntu3 and 1.8.10-2ubuntu1. They go away if disposal is perfomed
under lock.
|
|
|
|
|
|
| |
avatar would base its gain calculation on the previous avatar's gain, instead of the original input gain
This is similar to commit d89faa which fixed the same kind of bug in TriggerSound()
|
|
|
|
|
| |
This is to resolve a reported issue in http://opensimulator.org/mantis/view.php?id=6232
Here, the land management module is using OpenSim.Framework.Cache (the only code to currently do so apart from the non-default CoreAssetCache).
|
|
|
|
|
|
|
|
|
| |
race condition checks.
This is to allow a second attempt to remove an avatar even if "show connections" shows them as already inactive (i.e. close has already been attempted once).
You should only attempt --force if a normal kick fails.
This is partly for diagnostics as we have seen some connections occasionally remain on lbsa plaza even if they are registered as inactive.
This is not a permanent solution and may not work anyway - the ultimate solution is to stop this problem from happening in the first place.
|
|
|
|
| |
now conforms to the behaviour in SL.
|
|
|
|
|
|
|
| |
passing the original ThreadWatchdogInfo structure.
This is to avoid the possibility of misleading reporting if a watchdog update outraces an alarm.
Should address any remaining issues from http://opensimulator.org/mantis/view.php?id=6012
|
|
|
|
| |
StackOverflowExceptions during script conversion/compilation (e.g. on Windows 64-bit)
|
|
|
|
|
|
| |
instead.
This is more useful if compilation fails due to an uncatchable exception since we know what was being compiled.
|
| |
|
| |
|
|
|
|
| |
This is to avoid false positives when the machine is under heavy load whilst starting up.
|
| |
|
| |
|
|
|
|
| |
thread has retreived it after checking whether the NPC exists.
|
| |
|
| |
|
|
|
|
| |
command
|
|
|
|
|
|
| |
This was working in 0.7.2 but was accidentally removed from 0.7.3.
The --publish option for "save oar" will now save oars stripped of parcel owner information as well as scene object info.
Please use the --publish option if you want to publish oars that may be later loaded by others to the same grid from which they were saved.
|
| |
|
|\ |
|
| |
| |
| |
| | |
last commit 205f2326
|
| | |
|
| |
| |
| |
| | |
collisions on objects that don't care are not reported up.
|
|/
|
|
|
|
| |
Add interface 2 enhancements to BSCharacter.
Modify AddForce and SetForce to use the new Bullet interface.
More DetailLog statements for character.
|
|
|
|
|
|
| |
DelayBeforeAppearanceSave into [Appearance] section from [Startup] config section so that all appearance settings are in the same place and not in the startup bucket.
All these settings are in OpenSimDefaults.ini only. If you are using them then please adjust your OpenSim.ini
|
|
|
|
| |
functional change.
|
|
|
|
| |
VectorRenderModule inside its own context, rather than disposing of the old font before using it as a prototype for the new.
|
|\ |
|
| |
| |
| |
| | |
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
|/
|
|
|
|
|
|
|
|
| |
[Startup] to [Appearance] config section.
Add description and default of false (as before) to OpenSimDefaults.ini
If set to true, this config switch will resend avatar appearance information (a small amount of UUID data, not the baked textures themselves) to other avatars in the sim every 60 seconds.
For me, this has helped with situations where avatars appear persistently grey - the LL viewer sometimes did not appear to request assets the first time the appearance data was sent.
However, this switch will not help with other appearance failure situations (e.g. failure to bake assets).
This setting is experimental but will not have any significant impact on the simulator if turned to true.
|
|
|
|
| |
FromFolderID, FromItemID and to reflect that it's a SOP ID rather than a SOG ID.
|
|
|
|
| |
is already its default value as it's a struct.
|
|
|
|
| |
scheduling terse updates will not (and does not) update shape information in the viewer
|
|
|
|
|
|
| |
timed-out
The bug manifested as follows: a large world was saved. All the assets were found. But for some unknown reason, the timeout timer was restarted. So after 1 minute it closed the Archive Writer, because it didn't receive any more assets during that minute. That caused the OAR to become corrupted because ArchiveWriteRequestExecution.Save() was still running.
|
| |
|
|
|
|
| |
trying to find a corrupted memory problem. Update DLL and SO.
|
| |
|
| |
|
|
|
|
|
|
|
| |
textures.
The convention is that if an object implements IDiposable() the code must explicitly call Dispose() or call it via the using statement.
This may be particularly important for GDI+ objects since they encapsulate native code entities.
|
|\ |
|
| | |
|