SimulatorFeatures
From OpenSimulator
(→Configuration) |
(→Configuration) |
||
Line 9: | Line 9: | ||
Some parameters are constant and defined in code. Others are defined by specific, some optional, modules | Some parameters are constant and defined in code. Others are defined by specific, some optional, modules | ||
in fact, because reasons, this module is also optional.<br> | in fact, because reasons, this module is also optional.<br> | ||
− | This are also very dependent on the OpenSimulation version or flavor | + | This are also very dependent on the OpenSimulation version or flavor. |
− | More work is needed to provide | + | Consequence of legacy decisions, unmanageable modularity and configurability, and blind selfish forking. |
+ | More work is needed to provide consistence, in particular because some of this information is not optional at all if one likes to have viewers that do work. | ||
Revision as of 08:09, 11 November 2020
Contents |
SimulatorFeaturesModule
Overview
The SimulatorFeaturesModule provides the mechanism used to inform the viewer about some features or properties of a region, for example BOM support, version of LSL/OSSL syntaxe, etc.
Viewer should ask for this information every time they see a new region. Unfortunately some of this may require that the viewer already created a avatar on that region.
This information is send via HTTP with llsd xml encoding. some information specific to opensimulator is sent on a section (llsd map) OpenSimExtras
Configuration
Some parameters are constant and defined in code. Others are defined by specific, some optional, modules
in fact, because reasons, this module is also optional.
This are also very dependent on the OpenSimulation version or flavor.
Consequence of legacy decisions, unmanageable modularity and configurability, and blind selfish forking.
More work is needed to provide consistence, in particular because some of this information is not optional at all if one likes to have viewers that do work.
OpenSim
OpenSimExtras items in particular are configured in several places through the code, even some modules may override what was defined by others. a few examples
[SimulatorFeatures] ; Override search service url SearchServerURI = "url to search service" ; Override destination guide url DestinationGuideURI = "url to destination guide" ; Override map service url ;(this may be set in one of several other locations, but we can use this to be consistent) MapTileURL = "url to map service" [Chat] ; Distance in meters that ordinary chat should travel. Default is 20m say_distance = 20 ; Controls whether the chat module is enabled. Default is true. enabled = true; ; Distance in meters that whispers should travel. Default is 10m whisper_distance = 10 ; Distance in meters that shouts should travel. Default is 100m shout_distance = 100