| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
other small tidies of "load oar" console command help.
|
| |
|
|
| |
Signed-off-by: BlueWall <jamesh@bluewallgroup.com>
|
| | |
|
| |
|
|
| |
non-shared and non-shared as shared
|
| | |
|
| |
|
|
|
|
| |
Specifically, StoreEstateSettings was not being used anywhere; instead EstatSetting.Save was being called, but that method is a trigger to the DB-layer code directly, which, besides being wrong, was making it impossible to replace the service with a remote connector.
Also added more packing/unpacking code.
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: Michael Cerquoni <nebadon2025@gmail.com>
|
| |
|
|
|
|
| |
Recent versions of Firestorm and Singularity have started sending the viewer name in the 'Channel' field, leaving only their version number in the 'Viewer' field. So we need to search both of these fields for the viewer name.
This resolves http://opensimulator.org/mantis/view.php?id=6952
|
| |
|
|
| |
regions" console output.
|
| |
|
|
|
| |
the 'load oar' and 'scene' commands. Before they were ignored but the
code now relies on the SOG.IsAttachment function for attachmentness.
|
| | |
|
| |
|
|
|
| |
existing parameters. ('--forceterrain' becomes '--force-terrain').
The old forms have been kept for downward compatiblity.
|
| |
|
|
|
|
|
|
|
|
|
| |
Add --forceterrain and --forceparcel to 'load oar'. In order to not change
the operation of --merge (which does an object merge and suppresses terrain
and parcel information loading), added the --force* parameters to be used
when loading multiple oars to build up a varregion.
Added --rotation and --rotationcenter parameters to 'load oar' which apply a rotation to
the loaded oar objects before displacing. The rotation is in degrees (pos or neg)
and the center defaults to "<128, 128, 0>".
|
| |
|
|
|
| |
--noterrain suppresses the loading of the terrain from the oar.
--noparcels suppresses the loading of parcel information from the oar.
|
| |
|
|
|
|
|
|
|
| |
Adds displacment to all objects and terrain loaded from the oar.
As an example, if you have a 512x512 region and an old 256x256 oar, doing
load oar --displacement "<128,128,0>" oarFile.oar
will load the object (and terrain) into the middle of the 512x512 region.
If displacement is not specified, 'load oar' works like it always has.
If you have a 5
|
| |
|
|
| |
repeated use of these commands will induce floating point accumulation errors. Please back up your region before using.
|
| |
|
|
| |
of rotation and center can be optionally overridden in the command line
|
| |
|
|
| |
but not for foliage, don't know why. Also doesn't work on terrain. Successive use of this command will likely introduce floating point error accumulation. Back up your region before using it :)
|
| |
|
|
|
|
| |
again as "non-shared"
Addresses http://opensimulator.org/mantis/view.php?id=6860
|
| |
|
|
|
|
| |
it clear that all non-clientstack callers should be using this rather than RemoveClient() in order to step through the ScenePresence state machine properly.
Adds IScene.CloseAgent() to replace RemoveClient()
|
| | |
|
| |
|
|
|
| |
Add 'callback' query parameter to managed stats return to return function
form of JSON data.
|
| |
|
|
|
|
|
|
|
|
| |
Disabled by default. Enable by setting
[Startup]ManagedStatsRemoteFetchURI="Something"
and thereafter "http://ServerHTTPPort/Something/" will return all the managed
stats (equivilent to "show stats all" console command).
Accepts queries "cat=", "cont=" and "stat=" to specify statistic category,
container and statistic names. The special name "all" is the default and returns
all values in that group.
|
| |
|
|
|
|
|
| |
back in 2009.
"show modules" is the functional console command that will show currently loaded modules.
Addresses http://opensimulator.org/mantis/view.php?id=6730
|
| | |
|
| |
|
|
| |
to avoid kicking the wrong user or multiple wrong users.
|
| |
|
|
|
|
|
| |
"debug lludp" options
also moves the implementing code into LLUDPServer.cs along with other debug commands from OpenSim.cs
gets all debug lludp commands to only activate for the set scene if not root
|
| |
|
|
|
|
| |
simulator console
This means the "show stats" command is now active on the robust console.
|
| |
|
|
| |
simulator logs, for debug purposes
|
| | |
|
| |
|
|
|
|
| |
and group shared and non-shared modules together
This is to make it easier to tell if a region has a certain module active or not
|
| |
|
|
| |
scene <key> <value>" to "debug scene set <key> <value>" to accomodate future settings
|
| | |
|
| | |
|
| |
|
|
|
|
| |
disable periodic scene backup. For debug purposes.
If false, scene is still saved on shutdown.
|
| |
|
|
|
|
| |
various console commands (e.g. "show users") from working.
This was because the "currently selected" scene reference was being left as the dead scene instead of the restarted Scene object.
|
| |
|
|
| |
This also allows comments in command scripts (lines starting with ;, # or //) to be used across all servers
|
| | |
|
| |
|
|
| |
This helpfully lists version information, startup location and console log level
|
| | |
|
| |
|
|
|
|
| |
This was because we were removing by circuitcode where NPCs have no code.
Now removing by agent ID instead.
This commit also fixes the "show circuits" console command to work properly where the circuit has no associated IP address.
|
| |
|
|
| |
This allows the scene update and maintenance loops to be started and stopped for debug purposes.
|
| |
|
|
| |
Merged ArchiveWriteRequestPreparation.cs and ArchiveWriteRequestExecution.cs. This simplifies the code, and it's faster to write each scene to the archive as it's found rather than all at once at the end.
|
| |
|
|
| |
the simulator executable.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
command
|
| |
|
|
| |
This better reflects the long-term purpose of that project and matches Monitoring modules.
|
