| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
for both current and future clients
The existing "--default" option only changes the logging level for future clients.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This, by default, enables terrain patches being sent to each avatar
from the avatar away (rather than the old outside-in pattern), only
sending terrain patches within the avatars view distance (making
view loading quicker), and sending multiple terrain patches per
protocol packet (making terrain loading and editing quicker).
|
| |
|
|
|
|
| |
complete with use of the Limit Roll Only Flag.
Signed-off-by: Robert Adams <misterblue@misterblue.com>
|
| | |
|
| |
|
|
| |
This shows static data (e.g. region agent limit) whereas "show scene" shows live data (sim fps, current prims, etc.)
|
| |
|
|
|
|
| |
can stop misleading grid service only console commands from registering.
We need to do this because the simulator initializes and internal copy of the GridService in grid mode for internal purposes
|
| |
|
|
| |
condition check without changing the logic
|
| |
|
|
|
|
|
| |
forward when moving south or west.
Addresses http://opensimulator.org/mantis/view.php?id=5003
Thanks to UbitUmarov for this fix.
|
| |
|
|
| |
child mesh is not available when building a linkset.
|
| |
|
|
| |
thanks Ai Austin for pointing this out.
|
| |
|
|
|
|
|
| |
co-op should be more stable as it doesn't abort threads, which can trigger virtual machine instability
This change will be invisible to users as script DLLs are recompiled automatically where necessary, though the change won't take affect until the next simulator restart.
This change has no effect on existing script state.
If you want to continue using abort, set ScriptStopStrategy = abort in the [XEngine] section of OpenSim.ini
|
| |
|
|
|
|
|
|
| |
As per http://msdn.microsoft.com/en-us/library/system.random%28v=vs.100%29.aspx, the .NET Random class is not thread-safe.
If called by multiple threads at once, methods may return 0.
Except for llRand(), other OpenSimulator code did not lock before calling a shared Random instance.
This commit adds a ThreadSafeRandom class that extends Random but does internal locking so that it is thread-safe.
This change is invisible to existing callers and the explicit locking in the llFrand() implementation is now redundant.
|
| | |
|
| |
|
|
| |
other debug commands live.
|
| |
|
|
| |
that were removed some time ago
|
| |
|
|
|
|
|
| |
existing session use the previous strategy for that script rather than not starting the script at all.
We have to do this since we can't unload existing DLLs if they're all in the same AppDomain.
But we can still update the underlying DLL which will be used in the next simulator session.
|
| |
|
|
|
|
|
| |
CheckOrCreateScriptsDirectory()) when checking that scripts directory exists on compile.
Code was identical apart from error logging, but if there are failures creating these directories then you'll be
seeing lots of errors anyway, and these will be more informative
|
| |
|
|
| |
non-shared and non-shared as shared
|
| |\ |
|
| | | |
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| | |
previous commit 3d70db4a
|
| | |
| |
| |
| |
| |
| |
| | |
uploaded textures.
This implements:
http://opensimulator.org/mantis/view.php?id=7250
|
| | |
| |
| |
| | |
New property created to specify how many days to keep files for. Off by default, also made sure only oar files will be removed.
|
| | |
| |
| |
| |
| |
| |
| | |
regenerate a new child caps seed for a region where we already have one.
I think it's still useful to know this to show up any errors early, but it's reasonable to still carry on rather than throw an exception.
Follow on from Diva's commit 9643792
|
| |/
|
|
| |
for users with different asset servers
|
| |
|
|
| |
that data structure contains important information about the agent that may be needed by modules.
|
| |
|
|
| |
are logged in; the avies would not see the region anymore until they relogged. Same problem as before: inconsistent calculation of scope.
|
| |
|
|
| |
was an inconsistency in the scope between opening and closing child agents in neighboring regions. For opening (in EnableChildAgents), the region's DrawDistance was being used; for closing (in IsOUtsideView) , the viewer's (SP) DrawDistance was being used. This fixes this inconsistency, therefore eliminating bugs observed in TPs between, at least, neighboring varregions.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
chance to fix it
This was working for me locally because it was still picking up all my *.ini config files, which jenkins won't have in its test env
|
| | |
| |
| |
| | |
why it's failing on jenkins but not locally
|
| | |
| |
| |
| |
| |
| | |
shutdown.
Adds regression test for this case.
|
| | | |
|
| | |
| |
| |
| | |
match OpenSimDefaults.ini
|
| | | |
|
| | |
| |
| |
| | |
has. Before this falling from really high caused the avatar to fall faster then the veiwer can handle and cause camera issues.
|
| |/ |
|
| | |
|
| |
|
|
| |
ice-cream Sunday: the packet itself was hardcoding the size of the region...
|
| |
|
|
| |
from locking up when running BulletSim on a separate thread.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the C# column can't be found in the positionMap (but the line can),
use the map immediately after it while correcting for the offset,
unless that results in an LSL position before the previous LSL position
in the positionMap.
The idea behind this heuristic is that in most, if not all cases C#
consumes more characters than LSL (for example LSL_Types.LSLInteger
instead of just 'integer').
Thus if the distance between the columns of two markers differ in
the C# and LSL file, the distance in the C# file will be larger.
Moreover, we can assume that every time this happens we will have
a marker at the beginning of the longer 'keyword', because those
keywords were generated by us in the first place.
For example:
C#: LSL_Types.LSLInteger f2(LSL_Types.LSLString s)
^ ^
1 2
will always have markers at the beginning of the long keywords
'LSL_Types.LSLInteger' and 'LSL_Types.LSLString'.
If an error is generated in between (for example at the beginning
of the function name 'f2') then the correct position is found
by using an offset relative to 2 rather than 1.
Note that a case where this isn't working correctly is
when the user adds extra spaces. For example:
LSL: integer f2( string s)
would still use the start of 'string' as reference and
then go backwards 3 characters only because the corresponding
C# still looks like
C#: LSL_Types.LSLInteger f2(LSL_Types.LSLString s)
^ ^
only 3 chars difference
and the reported error at 'f2' would be here:
LSL: integer f2( string s)
^
This can only be fixed by generating a mapping for 'f2' itself, or
generating a mapping whenever the amount of spaces is changed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a compile error reports a colum/error that is not an exact
match in the positionMap dictionary, the last position in the
map with a line number and position before the reported error
should be returned.
The old code had the following problems:
1) It returns l,c - which are line and column of the C# file, not LSL.
2) It doesn't set l to 'line' when the map has an entry with 'line'.
3) It sorts the map without taking columns into account, which may
result in a random order of the columns. With my mono implementation
the columns were reversed in order.
For example, if the map contains the following lines:
99,5,49,10
100,30,50,10
100,40,1,0
101,5,51,10
and a translation of 100,35 was requested,
then the old code would compare '100' with the keys in
the first column - setting l to that key while it is
smaller. Hence, l is set to 99.
Then it finds the key 100 and doesn't update l.
Because of the reversed sort order, it first compares
the column 35 with 40, finding that it is smaller
and therefore it stops; returning 99,1 instead of finding
the correct 100,30 entry and returning 50,10.
This patch causes 50,10 to be returned.
The remaining problems after this patch are:
1) The sorting might not be necessary at all.
2) The is code duplication (I fixed both instances,
but really there should be no code duplication
imho).
|
| |
|
|
| |
child doesn't have a physical shape. Another attempt at fixing Mantis 7191.
|
| |
|
|
|
|
|
| |
AvatarFlyingGroundMargin and AvatarFlyingGroundUpForce set to 5.0 and
2.0 respectively which seems to give about the same action as in SL.
Also moved force addition to before the velocity to force computation
so the upward velocity is properly applied to the avatar mass.
|
| | |
|
