SimulatorFeatures

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
(SimulatorFeaturesModule)
m (English improvement)
Line 1: Line 1:
 
= SimulatorFeaturesModule =
 
= SimulatorFeaturesModule =
This information is based on current development version. This has changed in time, occasionally in incoherent ways
+
This information is based on the current OpenSim development version. This has changed over time, occasionally in incoherent ways.
 
== Overview ==
 
== Overview ==
The SimulatorFeaturesModule provides support to the mechanism client programs (viewers) use to request information about some features or properties of a region, for example BOM support, version of LSL/OSSL syntaxe, etc.<br>
+
The SimulatorFeaturesModule provides support to the mechanism by which client programs (viewers) request information about some features or properties of a region, for example Bakes on mesh (BOM) support, version of LSL/OSSL syntax, etc.<br>
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.
+
Viewer should ask for this information every time they see a new region. Unfortunately some of this may require that the viewer already created an 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
+
This information is sent via HTTP with llsd xml encoding. Some information specific to OpenSimulator is sent in a section (llsd map) OpenSimExtras.
  
 
== Configuration ==
 
== Configuration ==
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 modules, some of which are optional. In fact, the SimulatorFeaturesModule itself is also optional.<br>
in fact, because reasons, this module is also optional.<br>
+
The facilities available via the module are also very dependent on the OpenSimulation version or flavor.
This are also very dependent on the OpenSimulation version or flavor.
+
This is a consequence of legacy decisions, unmanageable modularity and configurability, and blind selfish forking.
Consequence of legacy decisions, unmanageable modularity and configurability, and blind selfish forking.
+
More work is needed to provide consistency, in particular because some of this information is not optional at all if one likes to have viewers that do work.
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 ===
 
=== OpenSim ===
  
OpenSimExtras items in particular are configured in several places through the code, even some modules may override what was defined by others.
+
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 are:
a few examples
+
  
 
<source lang=ini>
 
<source lang=ini>

Revision as of 08:50, 11 November 2020

Contents

SimulatorFeaturesModule

This information is based on the current OpenSim development version. This has changed over time, occasionally in incoherent ways.

Overview

The SimulatorFeaturesModule provides support to the mechanism by which client programs (viewers) request information about some features or properties of a region, for example Bakes on mesh (BOM) support, version of LSL/OSSL syntax, 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 an avatar on that region. This information is sent via HTTP with llsd xml encoding. Some information specific to OpenSimulator is sent in a section (llsd map) OpenSimExtras.

Configuration

Some parameters are constant and defined in code. Others are defined by specific modules, some of which are optional. In fact, the SimulatorFeaturesModule itself is also optional.
The facilities available via the module are also very dependent on the OpenSimulation version or flavor. This is a consequence of legacy decisions, unmanageable modularity and configurability, and blind selfish forking. More work is needed to provide consistency, 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 are:

[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
Personal tools
General
About This Wiki