| Commit message (Collapse) | Author | Files | Lines |
|---|
|
disposed no matter what
|
|
Store() no matter what
|
|
sometimes look to start attachment scripts before ETM.HandleIncomingSceneObject() had added them.
Probably a regression since ghosts branch merge on Nov 26 2014
|
|
|
|
|
|
This provides no obvious benefit as far as I can tell but has a definite cost in keep script strings in memory for the entire simulator session.
|
|
their own or as attachments) with AppDomainLoading = false would create the new state in the source region area rather than the dest.
This was beause the code was finding the script DLL compiled for the source region as everything is in the same appdomain and using this as the location for the destination script state, etc.
This resolves the regression by passing the proper destination separately from the DLL retrieved.
Probably a regression since commit d7b92604 (11 July 2014).
Added regression test for this case.
At least partly addresses http://opensimulator.org/mantis/view.php?id=7278
|
|
could complete but see OnRezScript() insert a new job and complete before it set m_CurrentCompile = null
If the above happened, it would mean the new script would not compile until some script was added for compilation.
|
|
m_CompileDict to avoid a rare but not impossible race condition.
|
|
RecordAssetUuids() to AddForInspection() as this properly describes what both of these methods do.
|
|
times on each cached asset once, not for every reference.
|
|
like UUIDGatherer, so we can deal with future cases where the dictionary may already be pre-populated.
|
|
|
|
access violation if another thread is operating on the file at the same time.
Resolves one issue from http://opensimulator.org/mantis/view.php?id=7271
|
|
UpdateFileLastAccessTime() method for imminent reuse.
|
|
updating access time.
The majority of updates won't be for anything currently writing and any sharing exception from an actual clash can be caught and ignored anyway.
|
|
even being set. Region parameters come from Scene.RegionInfo instead.
|
|
region with its parameters rather than 2
|
|
config change (a rare situation), then explicitly log this for debug purposes.
|
|
controlled at runtime with the command "debug xengine log <level>", as with similar commands.
If log level is 1 then every script load is logged.
This means the <logger name="OpenSim.Region.ScriptEngine.XEngine"> section in OpenSim.exe.config is no longer needed to avoid log spam on regions with many scripts and can be removed.
|
|
writing the linemap.
The previous error report of already exists is inaccurate since existing files do get overwritten.
|
|
streams in the script engine even if exceptions are thrown.
|
|
|
|
clear. Add 'InternalScheduleRebuild() CHange rebuild code to call InternalScheduleRebuild() rather than ForceRebuild() to limit the scope of the changes made by the linkset.
|
|
are not Incomplete and not waiting for assets. Change BSPrimLinkable to use AllPartsComplete.
|
|
waiting for assets to load.
|
|
BSPrim.Incomplete flag based on rebuild flags to say when an object is being rebuilt.
|
|
DoOnRezScriptQueue()(and now the scene name).
|
|
error and always set m_CurrentCompile = null
Setting m_CurrentCompile = null in the finally block reduces the risk that an exception could permanently stop any future scripts compiling until the simulator is restarted.
If an exception is seen from this then please report and further changes to fix the bug or improve compiling reliability can be made.
|
|
m_ScriptFailCount as set in XEngine.DoOnRezScriptQueue()
|
|
calling ZeroMotion in SetPhysicalProperties() at all
SetPhysicalProperties is only called when adding a new character so it looks like there is no existing data to reset anyway.
|
|
convert the m_log.DebugFormat() call back to the original DetailLog call
|
|
crossings without degrading the walk cross experience (neither of which have been that great anyway).
|
|
ETM.CrossAgentIntoNewRegionMain() since this has already been performed by SP.CheckForBorderCrossing()
|
|
when avatar enters the new region.
This commit addresses the following issues were causing velocity to be set to 0 on the new region, disrupting flight in particular
* Full avatar updates contained no velocity information, which does appear to have some effect in testing.
* BulletSim was always setting the velocity to 0 for the new BSCharacter. Now, physics engines take a velocity parameter when setting up characters so we can avoid this.
This patch applies to both Bullet and ODE.
|
|
Urls in UMM if the initial request fails, possibly due to the home URL not being present
Instead, the failure information is effectively added to the memory cache (so no persistence over simualtor sessions).
A future improvement may be to invalidate negative cache results after some time has passed in case the failure was transient.
Looks to resolve http://opensimulator.org/mantis/view.php?id=7382
|
|
This has not been maintained for more than 2 years, is unimplemented for newer features (e.g. built-in groups) and has no core developers using it.
If somebody fixes these issues then it could be reinstated.
|
|
console as it is unused/ignored, at least in core.
|
|
creator data
|
|
reflect its location (UMM not Scene) and add the user name and ID.
|
|
|
|
thread and run work in the jobengine from Watchdog to a WorkManager class.
This is to achieve a clean separation of concerns - the watchdog is an inappropriate place for work management.
Also adds a WorkManager.RunInThreadPool() class which feeds through to Util.FireAndForget.
Also switches around the name and obj arguments to the new RunInThread() and RunJob() methods so that the callback obj comes after the callback as seen in the SDK and elsewhere
|
|
|
|
on any teleport within a foreign grid after the first.
Bug was introduced in ghosts branch commit 69abade
|
|
loglevel, in common with similar commands.
|
|
when [Startup] section is not present (though this is extremely unlikely).
|
|
disabled for testing purposes if necessary.
|
|
inside Watchdog.RunJob() (renamed from RunWhenPossible) and generalize them.
|
|
avatars collide. This is true by default.
This is implemented with a new collision type (PhantomToOthersAvatar) to potentially allow colliding and non-colliding avatars to be present in the same scene.
So there is no provision yet for giving avatars different collision types.
This commit replaces the temporary change in commit f3eaa6d8 where avatars would never collide when using BulletSim
This is equivalent to the av_av_collisions_off option in ODE.
|
|
|
