OpenSimulator - User contributions [en]

Configuration

2009-12-28T03:44:17Z

Erixoltan:

{{Template:Quicklinks}}
 
==OpenSim simulator configuration file==
The region simulator configuration is managed using a file called [[OpenSim.ini]]. This file is used regardless of whether the sim is running in standalone or grid mode. This file includes some additional configuration information from the config-include/ directory. Detailed information on the options available for setttings in this file can be found [[OpenSim.ini|here]].
Please note, that the name OpenSim.ini can be changed via command line arguments (see above). Also, note that the default download does not include an OpenSim.ini file, but rather provides an example file. To get started editing your ini file, please cd into opensim/bin/ and copy OpenSim.ini.example to OpenSim.ini.

It is also possible to distribute the inifile settings over two files. This is useful if you want to run several OpenSim processes where most of your settings are identical but some settings differ.
The master file is read first, then the inifile is read. Settings given in the inifile overrule settings given in the master file.
The master file has the same format and the same keywords as the inifile, so the same documentation applies.

==Database==
Opensim's supports the following database-engines:
* SQLite (default - a lightweight database that comes bundled with OpenSim and can be used without requiring any extra configuration. It is mostly intended to get you up and running quickly, not for production use. A few features here (such as attachment persistence) have not yet been fully implemented.)
* MySQL (fully supported). This is the recommended database for any use beyond experimentation or small standalone applications. See [[Mysql-config]] for configuration information. The OpenSim.ini.example file and other .example files will also have example MySQL configuration strings. 
* MSSQL (partially supported - some recent OpenSim features may not yet be implemented)

More information on database support can be found on the [[OpenSim Database support]] page.

==Standalone vs. Grid==
We recommend that you first get OpenSim running in standalone mode before you attempt to connect it to a grid or run your own grid. An OpenSim configuration consists of regions (run by region simulators) and 5 core backend services (which manage users, the grid, assets, inventories, and grid-wide messaging, collectively known as UGAIM).

A system running in '''standalone mode''' (that is, one with OpenSim.ini where gridmode = false) runs everything (all UGAIM services and one or more regions) in a single executable (OpenSim.exe).

In '''grid mode''', the five services ([[User Server|User]], [[Grid Server|Grid]], [[Asset Server|Asset]], [[Inventory Server|Inventory]], [[Messaging Server|Messaging]], or UGAIM) are not part of the region server. Instead, they can be run separately either on the same machine or spread out across multiple computers. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the core servers for asset, inventory and other data management.

Naturally, this means that running in grid mode is more complicated than running in standalone mode. It requires an understanding of UUID, X,Y location, server handshake passwords, estates and estate owners, and a couple of other settings. These require more care and patience to set up.

If you want to run a grid of your own (either private or public) you would start the core services up before connecting a region simulator. If you want to connect your region server to a grid that someone else is running, you need only start the region server in grid mode (with the necessary security keys and location information mentioned in the last paragraph).

= Running OpenSim in Standalone mode =

Running OpenSim in standalone mode is relatively straitforward because OpenSim.ini.example is already set up to achieve this. All you need to do initially is copy OpenSim.ini.example to OpenSim.ini before starting OpenSim and following the rest of the command prompts. Here's the full procedure assuming that you have a binary distribution of OpenSim (if you have a source distribution then you will need to [[Build_Instructions|build]] it first).

<ol>
<li>Go the bin/ directory in the OpenSim distribution</li>
<li>Copy OpenSim.ini.example to OpenSim.ini</li>
<li>Start OpenSim</li>
Windows
OpenSim.exe
or OpenSim.32BitLaunch.exe if using the ODE physics plugin under 64 bit Windows
Linux
mono OpenSim.exe

<li>
When you first start OpenSim in standalone mode, it will ask you several questions at the console. These will set up a single region for you. The configuration will be placed at bin/Regions/Regions.ini which you can then go and edit later on.

Many of the questions have defaults. Here are some explanations of the questions asked.

<ul>
<li>'''New region name''' - the name for your region. Don't leave this blank!</li>
<li>'''Region UUID''' - the unique ID of your region. In pretty much all cases you will want to accept the randomly generated default in the square brackets. The only time when you wouldn't is if you were trying to set up a configuration to point to pre-existing region data. But in this case you are probably better off editing the Regions.ini file directly anyway</li>
<li>'''Region Location''' - this is the location of the region on the grid. In standalone mode you can safely leave these as the default (1000,1000). If you were to set up additional regions later on in Regions.ini then they would need different grid co-ordinates (e.g. 1000,1001). OpenSim regions can be placed anywhere on a 65536 by 65536 grid.
<li>'''Internal IP address''' - This should always be 0.0.0.0 (0.0.0.0 means "listen for connections on any interface", basically a wildcard) if you want to access this server from the internet or another server on your internal network, this should be the IP address assigned to the OpenSim Server. You should also set up the server to Use a Static IP address, and not DHCP
<li>'''Internal port''' - This is the IP port for all incoming client connections. The name is a bit misleading since it will be used externally (by a Second Life viewer, for instance) as well as internally. You can make this any port you want, but it is safe to leave at the default 9000. Each region on your server must have a unique port</li>
<li>'''Allow alternate ports''' - This is currently experimental. Please leave it at the default of False.</li>
<li>'''External host name''' - If you leave this at the default 'SYSTEMIP' then this will become the LAN network address of the machine (e.g. 192.168.1.2). This is fine if you are connecting only from within your LAN. If you want to connect to it from a client on the internet, this should be the External IP Address of your router. Fully Qualified Domain Names (FQDNs) should also work.
<li>'''Master Avatar UUID''' - This is a legacy OpenSim feature and can be left at the default of 00000000-0000-0000-0000-000000000000. Later on, you may want to change this to your own avatar's UUID in Regions.ini if you have problems editing terrain.</li>
<li>'''Master Avatar first name''' - This is an alternative way of specifying the master avatar by avatar name rather than UUID. If you press enter here then both this field and the last name field will be left blank. Accepting the blank default is fine - this can always be changed later in Regions.ini</li>
<li>'''Master Avatar last name''' - The last name of the master avatar.
<li>'''Master Avatar sandbox password''' - The password of the master avatar.

Be aware of [http://osgrid.org/forums/viewtopic.php?f=5&t=400&start=0&st=0&sk=t&sd=a loopback] problems when Running viewer & server(s) on the same machine (LAN) by using the "external" configuration. ('''You might notice endless waiting for region handshake'''.) See also [http://opensimulator.org/wiki/Troubleshooting troubleshoot hints]. If you're having Connectivity problems. [http://opensimulator.org/wiki/Network_Settings Be sure to read the Network Configuration Page]. This is important if you see Region handshake issues</li>

See [[Configuring_Regions]] for information about the Regions.ini file that these questions generate.

</ul>

<li> To create a user type </li>

create user

in the server console. This will ask you a series of questions for creating a user (such as first name, last name and password).

<li> To connect to your new sim with your user, start up a Second Life viewer with the following command line switches: </li>

'''Client on same machine as OpenSim:''' -loginuri http://127.0.0.1:9000/ -loginpage http://127.0.0.1:9000/?method=login

'''Client on same LAN as OpenSim:''' -loginuri http://lan_ip:9000/ -loginpage http://lan_ip:9000/?method=login

Client on different machine or internet:''' -loginuri http://external_ip:9000/ -loginpage http://external_ip:9000/?method=login'''

Then enter the user name and password you set up in the previous step and your new user should hopefully login.

</ol>

= Running OpenSim in Grid mode =

Running OpenSim in grid mode is considerably more complicated. Grid services need to be set up and the region simulator configuration needs to be changed to use these instead of the built-in standalone mode ones.

==Configuring the grid services==
[[Image:Exclamation.png|left]]
NOTE: The grid servers are in the process of being redesigned.
Some services are now run in a common 'ROBUST' (Basic Universal Server Technology) server shell
while others are still run as separate legacy servers.
'''More Details on ROBUST are Here -->'''[[ROBUST|'''ROBUST''']]''' <--  including Conversion From UGAIM To UGRM (0.6.6 -> 0.6.7) and UGRM to URM (0.6.7 -> 0.6.8)'''

As of OpenSim 0.6.8, R.O.B.U.S.T. has connectors for the asset (A), grid (G) and inventory (I) functionality. The legacy servers are still required for user (U) and messaging (M) functionality. The steps below will get you up and running. We'll assume that your current directory is bin/ within the OpenSim distribution.

<ol>
<li>'''Configure the user server'''</li>
<ul>
<li>Start OpenSim.Grid.UserServer.exe</li>
<li>You will be asked a number of configuration questions. If the grid servers are all on one machine, most defaults are safe to use. The configuration is stored in the UserServer_Config.xml file which can be changed afterwards if necessary.</li>
<li>The user server will then load and display it's prompt:</li>
User#
</ul>

<li>'''Configure R.O.B.U.S.T.'''</li>
<ul>
<li>Copy OpenSim.Server.ini.example to OpenSim.Server.ini. Don't forget to change ConnectionString for your database settings. (on version 0.6.6 copy OpenSim.Services.ini.example to OpenSim.Services.ini - then use OpenSim.Services instead OpenSim.Server)
</li>
Linux
bin$ cp OpenSim.Server.ini.example OpenSim.Server.ini
Windows
C:\OpenSim\bin> copy OpenSim.Server.ini.example OpenSim.Server.ini
<li>Start OpenSim.Server.exe</li>
<li>The server will start up it's asset, inventory and grid components and display the R.O.B.U.S.T prompt:</li>
R.O.B.U.S.T.#
<li>For more information on the R.O.B.U.S.T. configuration file and more information if you are migrating from an earlier release of OpenSim, refer to [[R.O.B.U.S.T.]]</li>
</ul>

<li>'''Configure the messaging server'''</li>
<ul>
<li>Start OpenSim.Grid.MessagingServer.exe</li>
<li>Answer the configuration questions. Again, if all servers are run on the same machine, it's safe to press enter for all questions. The configuration is stored in MessagingServer_Config.xml.</li>
<li>The server will start and present you with it's prompt:</li>
Messaging#
</ul>

</ol>

For information on running the legacy servers, particularly if you're using an older version of before 0.6.7 that doesn't contain the ROBUST framework, see [[LegacyServers]]

=== Summary of commands for running grid service executables ===

'''Windows'''
cd bin
OpenSim.Grid.UserServer.exe
OpenSim.Server.exe
OpenSim.Grid.MessagingServer.exe

'''Linux / Mac OS X'''
cd bin
mono OpenSim.Grid.UserServer.exe
mono OpenSim.Server.exe
mono OpenSim.Grid.MessagingServer.exe

==Configuring regions==

When first run, a new OpenSim installation will ask you a series of questions to set up one region. If you want to change these settings or set up multiple regions, please see [[Configuring_Regions]]

==Configuring and Starting the region simulator==
<ol>
<li>Find the [Architecture] section, comment out the line that says</li>
Include-Standalone = "config-include/Standalone.ini"
and uncomment the line saying
Include-Grid = "config-include/Grid.ini

<li>save OpenSim.ini, and go into the config-include directory.</li>
<li>copy the following files</li>
GridCommon.ini.example to GridCommon.ini
CenomeCache.ini.example to CenomeCache.ini
FlotsamCache.ini.example to FlotsamCache.ini

<li>Open all these files (Grid.ini, GridCommon.ini, CenomeCache.ini and FlotsamCache.ini) and edit to suit your needs</li>

<li>You should now be ready to start up your sim. The mode that OpenSim.exe starts in is normally controlled by a setting in your OpenSim.ini. It defaults to standalone mode if that setting is not specified or the file is not found. If you wish, you can force opensim to start in gridmode on the command line as follows:</li>
OpenSim.exe -gridmode=true
or if using the ODE physics plugin under 64 bit Windows
OpenSim.32BitLaunch.exe
or:
mono OpenSim.exe -gridmode=true
if you're using Mono under Linux or Mac OSX.

With any luck, everything will come up without fatal errors.

If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.

<li>Go to the UserServer console, and type 'create user' to create a new avatar. It will prompt you for the name and password, and the X and Y of the sim that should be his home location. Use 1000 and 1000, or wherever you told your sim to live when you brought it up in standalone mode. At the console of any of these servers, you should be able to type 'help' to get a list of commands.</li>

<li>You should now be able to connect to your new grid with your secondlife client. You need to tell your client to point at the UserServer rather than directly at the sim, though:</li>
secondlife -loginuri http://127.0.0.1:8002/
8002 is the default port for the UserServer, and that IP address should be changed to the server you are running the UserServer on, if they are not all on the same box. Happy OpenSimming! 
''Note: if you are using Windows Vista, remember to start servers as Admin. If not it will prompt you an error in console like "Error - Access denied"''
</ol>

==Attaching your sim to someone else's grid==
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, you should edit the <tt>OpenSim.ini</tt> file in the <tt>bin</tt> directory. In that file, there is a <tt>[Network]</tt> section with URLs for the grid, user, and asset servers, as well as send and receive keys (for a basic level of security). The addresses and send/receive keys will vary depending on the grid you are connecting to, and the grid operator should tell you what values to use.

The other file you may have to change is in your <tt>bin/Regions</tt> directory. This is where your individual region config files are. If you only have one region, it will by default be called <tt>Regions.ini</tt> in OpenSim 0.6.7 and later and <tt>regions.xml</tt> in OpenSim 0.6.6 and earlier.

This can be edited with any text editor. The grid owner may tell you what X and Y location you can place your sim at (you can't have multiple sims at the same location on the grid). If so, the fields you will need to change in this file are <tt>sim_location_x</tt> and <tt>sim_location_y</tt>. And the <tt>external_host_name</tt> should be set to the hostname or IP address of your simulation server (i.e., the machine that is running <tt>OpenSim.exe</tt>).
A list of public grids that you can attach your sim to is at [[OpenSim: Grids]]

=Further notes=

==Running OpenSim 0.6.7 and onwards in 64 bit Windows==
[[Image:Exclamation.png|left]]
As of OpenSim 0.6.7, the default physics engine for OpenSim was changed to the ODE engine. This is because ODE is by far the most advanced physics engine plugin currently in OpenSim. Unfortunately, it has the drawback in that it's library is not compilable under 64bit in Windows. Therefore, 64 bit Windows users may need to run

OpenSim.32BitLaunch.exe

instead of

OpenSim.exe

To launch their region simulator.

An alternative is to use the basicphysics engine instead or one of the other alternative physics engines bundled with OpenSim, though all these are far less functional than the ODE plugin.

==Note About Mono==
If you're using mono, you should increase the value of the mono environment variable MONO_THREADS_PER_CPU from its default of 5 to some number that works for your sim. The exact number depends on many factors including: the number of CPUs in your machine, what else you use that machine for, how many regions you have in your sim, how many of them are adjacent, how many scripts you have, and how many avatars you expect to serve at the same time. As a reference, Wright Plaza in OSGrid, which is running as a single region on a sim and routinely hosts meetings with 20 avatars, uses the value 125.

If this number is too low, the operation of your sim will start to break in all sorts of different ways. A common symptom is the freezing of all activity upon login of a new avatar. Other symptoms are a lot more subtle.

For example: $ export MONO_THREADS_PER_CPU=125

== Legacy Configuration Information ==
These are some pages containing some legacy configuration information of unknown accuracy.

[[OpenSim 0.6.6 legacy configuration information]]

== Additional Configuration Tasks (for advanced users) ==

===OpenSim.exe command line options===
OpenSim.exe has command line options which allow you to perform actions such as reading configuratio nfiles from a different directory. See [[OpenSim.exe Command Line Options]] for more details.

===Script engine===
OpenSim supports multiple script engines. See [[ScriptEngines]] for details. If you don't know what this means then the default script engine will be fine.

===Permissions Configuration===
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.

=== Logging ===
By default, OpenSim logs information to a file called OpenSim.log in the bin directory. See [[Logging]] for details on how to further configure this if required.

=== Configuration of region modules ===
* [[IRCBridgeModule]]
* [[Freeswitch_Module]]
* [[Offline Messaging]]

=== Configuration of Metaverse Exchange Protocol (MXP) ===
* [[Metaverse Exchange Protocol]]

=== Configuration of Web Server and Pages===
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.
* [[External Files]]
* [[Internally Generated]]

OSSL TextureDrawing

2009-12-27T03:20:25Z

Erixoltan: Added a summary at the top, simply stating the general capabilities that are covered in detail in the text below.

__NOTOC__
{{Template:Quicklinks}}
 

==General Capabilities==

The OSSL Texture Drawing functions allow the scripter to dynamically generate a texture on the fly, from within the context of an script. (It can be written in LSL, C# or any other supported scripting language.)

The scripting language supports text and images, as well as three simple drawing primitives: line, rectangle and ellipse. Color and pen attributes are included. Font, size and style are supported for text. An image is specified as an URL.

A drawing script can be directly specified in the texture drawing language, or can be built by using helper functions in the scripting language. Examples of both approaches are shown below.

Several extra parameters are available for the texture rendering operation. These include the height and width of the texture, as well as the background color and alpha value. A statement terminator can also be specified.

'''LSL Helper Functions'''

<source lang="lsl">

string osMovePen(string drawList, int x, int y);
string osDrawLine(string drawList, int startX, int startY, int endX, int endY);
string osDrawLine(string drawList, int endX, int endY);
string osDrawText(string drawList, string text);
string osDrawEllipse(string drawList, int width, int height);
string osDrawRectangle(string drawList, int width, int height);
string osDrawFilledRectangle(string drawList, int width, int height);
string osDrawPolygon(string drawList, LSL_List x, LSL_List y);
string osSetFontSize(string drawList, int fontSize);
string osSetPenSize(string drawList, int penSize);
string osSetPenColour(string drawList, string colour);
string osSetPenCap(string drawList, string direction, string type);
string osDrawImage(string drawList, int width, int height, string imageUrl);
</source>
----

'''C# Code Example'''
<source lang="lsl">
//cs
public void default_event_state_entry()
{
string drawList = "";
drawList = osDrawLine (drawList, 10,20,240,20);
drawList = osMovePen (drawList, 50,100);
drawList = osDrawImage(drawList, 100,100,"http://opensimulator.org/images/d/de/Opensim_Wright_Plaza.jpg" );
drawList = osSetPenSize (drawList, 1);
drawList = osSetPenCap(drawList, "end", "arrow");
drawList = osMovePen (drawList, 50,70);
drawList = osDrawEllipse (drawList, 20,20);
drawList = osMovePen(drawList, 90,70);
drawList = osDrawRectangle (drawList, 20,20 );
drawList = osMovePen (drawList,130,70);
drawList = osDrawFilledRectangle(drawList, 20,20);
drawList = osDrawPolygon(drawList, [50,100,150], [50,100,50]);
drawList = osDrawFilledPolygon(drawList, ["50","100","150"], ["50","100","50"]); // It works with integers, float or string as the x and y points
drawList = osSetFontSize (drawList, 12 );
drawList = osMovePen (drawList,15,32);

string regionName = llGetRegionName();
drawList = osDrawText (drawList, "Hello and welcome to " + regionName );

drawList = osSetFontSize (drawList, 7);
drawList = osSetPenColour (drawList, "blue");
drawList = osMovePen (drawList, 70,220);
drawList = osDrawText (drawList, "The End");
osSetDynamicTextureData("", "vector", drawList, "", 0);
}
</source>

==OS Dynamic Texture Language==

Many of the OSSL drawing functions are convenience functions to help build the command line for the osSetDynamicTextureData data parameter. You may find it easier to build the string yourself using the drawing commands directly. Do this by declaring a string then appending sets of commands and parameters until it is ready. Each command is separated by a semi-colon ";". Additional parameters may be set for the image with the extraParams parameter.

;osSetDynamicTextureData(string dynamicID, string contentType, string data, string extraParams, int timer)

:*dynamicID not used yet – send “”
:*contentType use “vector” for drawing commands or use “image” for loadurl
:*data the graphics commands in the string with the format of: “MoveTo 20, 20; FillRectangle 60, 60;”;
:*extraParams width, height, alpha, bgcolour, altdatadelim
:*timer set an update interval

===Commands (data)===
;MoveTo int x, int y;
:Places the brush at the x/y coordinate

;LineTo int x,int y;
:Draws line from present pen position to the x/y coordinate

;Text string content;
:Text to write to the image

;Image float x, float y, string URL
:The x/y placement coordinates and URL of an image to load

;Rectangle float x, float y;
:Draws a rectangle with the current pen from the current pen location to the x/y coordinates

;FillRectangle float x, float y;
:Draws a filled rectangle with the current brush from the current pen location to the x/y coordinates

;Ellipse float x, float y;
:Draws an ellipse with the current brush from the current brush location to the x/y coordinates

;FontSize int size;
:The size of the font for text

;FontProp char;
:'''[B|I|U|S|R]'''

::*'''B''' Bold
::*'''I''' Italic
::*'''U''' Underline
::*'''S''' Strikeout
::*'''R''' Regular

;FontName string name;
:The name of the font to use

;PenSize float size;
:Size of the drawing pen

;PenColour string color;
:Drawing color of the pen

;PenCap string direction, string type;
:Cap of a line, consists of 3 possible directions ("start","end","both") and 4 possible types ("flat","diamond","arrow","round")

'''Example'''
<source lang="lsl">
string drawData;

drawData += "PenColour Teal; FillRectangle 1024, 512;";
drawData += "PenColour PowderBlue;";
drawData += "MoveTo 40, 30; FontSize 25; Text 2000 UTC:;";
drawData += "MoveTo 250, 30; Text Speed Build Competition;";
drawData += "MoveTo 40, 70; Text 0120 UTC:;";
drawData += "MoveTo 250, 70;Text Working On Sign;";
drawData += "MoveTo 40, 110; Text 0500 UTC:;";
drawData += "MoveTo 250, 110; Text Going To Sleep!;";
drawData += "MoveTo 40, 150; Text 0600 UTC:;";
drawData += "MoveTo 250, 150; FontProp B,I;Text Waking Up!;";
drawData += "FontProp R;";
drawData += "MoveTo 40, 190; Text Have a great day!!;";
drawData += "PenCap end,arrow; LineTo 50,250; MoveTo 50,250;";

osSetDynamicTextureData("","vector", drawData,"width:1024,height:512,alpha:254", 0);

</source>

===Extra Parameters (extraParams)===
;height
:the height for the image in pixels

;width
:the width of the image in pixels

;alpha
:the opacity of the image
::''0-255'' to set the opacity for an image with an alpha channel
::''false'' for an image with no alpha channel

;bgcolour
:the background color of the image

[[http://msdn.microsoft.com/en-us/library/aa358802.aspx .net colors]]

;altdatadelim
:an alternative delimiter for each parameter - useful if you want to display text that contains semicolons, for example C# or LSL code.

Talk:OSSL TextureDrawing

2009-12-27T03:10:12Z

Erixoltan:

Hey this is a GREAT FEATURE.

Looks like there is no support for transparency yet, for individual drawing elements. For example, I can set the alpha of the whole rendering operation but can't change it for just a single ellipse that I'm drawing. (Hope that's coming soon!)
--[[User:Erixoltan|Erixoltan]] 03:05, 27 December 2009 (UTC)

Talk:OSSL TextureDrawing

2009-12-27T03:05:28Z

Erixoltan:

Hey this is a GREAT FEATURE.

Looks like there is no support for transparency yet. Hope that's coming soon!
--[[User:Erixoltan|Erixoltan]] 03:05, 27 December 2009 (UTC)

Talk:OSSL TextureDrawing

2009-12-27T03:05:11Z

Erixoltan: Support and hope for transparency feature.

Hey this is a GREAT FEATURE.

Looks like there is no support for transparency yet. Hope that's coming soon!