http://opensimulator.org/api.php?action=feedcontributions&feedformat=atom&user=FleepOpenSimulator - User contributions [en]2026-04-06T10:32:55ZUser contributionsMediaWiki 1.19.9http://opensimulator.org/wiki/Inventory_ArchivesInventory Archives2013-07-11T12:18:10Z<p>Fleep: /* Usage */ - IARs are saved to the /bin directory by default and an IAR file must be located in /bin to import</p>
<hr />
<div>{{Quicklinks}}<br />
<br /><br />
<br />
= Introduction =<br />
<br />
OpenSimulator Inventory Archives (IARs) are a means by which inventory folders and items can be saved offline to a single file (an IAR). This file can then be loaded into a different OpenSimulator installation.<br />
<br />
Like [[OpenSim Archives]], IARs save all the necessary asset data required to fully restore the items including textures, sounds, scripts and objects contained in the inventory of other objects.<br />
<br />
IARs have been enabled in OpenSimulator since Git revision 5a64ca (OpenSimulator 0.6.7 and later).<br />
<br />
= Usage =<br />
<br />
IARs are saved and loaded from the region console. By default, they are saved to the /bin directory of your installation, and an IAR file must be located in the /bin directory to be imported.<br />
<br />
== save iar ==<br />
<br />
The command to save an IAR on the region console is<br />
<br />
save iar [-h|--home=<url>] [-v|--verbose] [--noassets] <user-name> <path> <password> [<filename>]<br />
<br />
where <br />
<br />
* <user-name> is the name of the user to save inventory from<br />
<br />
* <path> is the path to an inventory item or folder. If the path is for a folder, that folder and all its contents (both descendant folders and items) are saved. If the path is for an item, then only that item is saved. <br />
<br />
Components of the path are separated by a forward slash ("/"). If you need to specify a path with spaces, you can surround the whole thing with double quotation marks (e.g. "Folder A/Folder B"). <br />
<br />
You can specify that the contents of a folder should be saved rather than the folder itself using the * wildcard. For instance, "a/b/*" will save the contents of folder b but not folder b itself.<br />
<br />
If a name or folder contains a forward slash ("/") then it can be escaped with the backslash (i.e. "\/") to stop it being seen as a path separator. Back slashes themselves need to be escaped with another backslash (i.e. "\\").<br />
<br />
One further issue here is that it's not possible to distinguish between identically named folders or items on the path - the workaround is to rename your items/folders if you need to specify them in the path :)<br />
<br />
* <password> is the password of the user.<br />
<br />
* <filename> is an optional filename for the IAR. If none is supplied, then the filename user-inventory.iar is used in the current directory. I recommend that iars have the .iar extension.<br />
<br />
=== Switches ===<br />
<br />
* If the --noassets option is specified, then the archive will be saved without assets. This can be handy if you're backing up the asset database separately and don't want the expense of including all the assets in each archive.<br />
* --home=<url> is the URL of this world's profile service. It is not required that the profile service is operational; the information will be saved, and it will be displayed wherever the archive will be loaded. NOTE: the older --profile option (the previous name of this switch) produced IARs that are not compatible with OpenSimulator 0.7.0.2 and earlier; do not use this option if you want to produce a compatible IAR.<br />
* --verbose prints out versbose saving messages<br />
<br />
=== Examples ===<br />
<br />
Here's an example. Suppose you have an inventory structure like this<br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| <br />
+-- FolderB<br />
| |<br />
| +-- ItemX<br />
|<br />
+-- ItemY<br />
<br />
If you type <br />
<br />
save iar John Doe FolderA PASSWORD my-items.iar<br />
<br />
then FolderA and everything in FolderA (FolderB, ItemX and ItemY) will be saved into an IAR called my-items.iar. On the other hand, if you type<br />
<br />
save iar John Doe FolderA/FolderB/ItemX PASSWORD my-items.iar<br />
<br />
then only ItemX will be saved.<br />
<br />
If there is a space in the path to the item, for example if John Doe's folder was named "Folder A" instead of "FolderA", then quotes around the path are necessary on the command line:<br />
<br />
save iar John Doe "Folder A/FolderB/ItemX" PASSWORD my-items.iar<br />
<br />
==== Saving an entire user's inventory ====<br />
<br />
With save iar you can save your entire inventory as well as the contents of particular folders or individual items.<br />
<br />
For instance, typing<br />
<br />
save iar John Doe /* password<br />
<br />
would save your entire inventory to user-inventory.iar (since no filename was given). This can later be restored using the --merge switch in the load iar command. For more details please see the "Restoring an entire user's inventory" section below.<br />
<br />
'''Please note that for OpenSimulator 0.7.5 and before, the path for save iar must be specified as "/*" and not just "/". Specifying only "/" will still save the entire inventory but there will be a base folder called "My Inventory", which will be created on reload under a user's existing "My Inventory" folder.'''<br />
<br />
'''From OpenSimulator git master dev code commit d54d3180 (Sat Feb 16 00:49:06 2013), "/" will also instead save the user's entire inventory without the "My Inventory" folder. This is because "My Inventory" is not actually a real folder but rather the name of the user's inventory. I believe this is more intuitive and it means that inventories saved using / can be restored using the load iar --merge function as well. This change will be in the next OpenSimulator release (0.7.6). -- [[User:Justincc|Justincc]] 02:26, 16 February 2013 (UTC)'''<br />
<br />
== load iar ==<br />
<br />
An IAR can be reloaded to an OpenSimulator instance with the load iar command<br />
<br />
load iar [-m|--merge] <user-name> <path> <password> [<filename>]<br />
<br />
where<br />
<br />
* <user name> is the name of the user to whom to load the inventory<br />
<br />
* <path> is the path to which the IAR should be loaded. This has to be a folder which already exists in "My Inventory". See the save iar command for more details.<br />
<br />
* <password> is the password of the user.<br />
<br />
* [<filename>] is an optional filename for the IAR. If none is specified, then the filename is assumed to be user-inventory.iar in the current directory.<br />
<br />
=== Switches ===<br />
<br />
* If the --merge option is given, then IAR items are loaded into the existing folder structure where possible, instead of always creating new folders.<br />
<br />
=== Examples ===<br />
<br />
1. Suppose that "David Hume" has recieved the my-items.iar saved above containing FolderA, FolderB, ItemX and ItemY. David Hume already has an inventory structure like this. <br />
<br />
My Inventory<br />
|<br />
+-- Folder1<br />
| <br />
+-- Folder2<br />
| <br />
+-- Folder3<br />
<br />
David wants to load the IAR to Folder3, so on the region console he executes <br />
<br />
load iar David Hume Folder1/Folder3 password my-items.iar<br />
<br />
After a little while he ends up with the folder structure <br />
<br />
My Inventory<br />
|<br />
+-- Folder1<br />
| <br />
+-- Folder2<br />
|<br />
+-- Folder3 <br />
|<br />
+-- FolderA<br />
| <br />
+-- FolderB<br />
| |<br />
| +-- ItemX<br />
|<br />
+-- ItemY<br />
<br />
where ItemX and ItemY are ready for rezzing. <br />
<br />
If there is a space in the path to the item, for example if David's folder was named "Folder 1" instead of "Folder1", then quotes around the path are necessary on the command line:<br />
<br />
load iar David Hume "Folder 1/Folder3" password my-items.iar<br />
<br />
From OpenSimulator 0.7 and onwards, you can also load IARs directly from web addresses. For example <br />
<br />
load iar Betrand Russell Folder2 PASSWORD http://justincc.org/downloads/iars/my-great-items.iar<br />
<br />
will load my-great-items.iar from the web into Folder2 of the user "Bertrand Russell". <br />
<br />
2. Let's suppose that a user called Albert Camus has an existing inventory structure <br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| |<br />
| +-- Item1<br />
|<br />
+-- FolderC<br />
|<br />
+-- Item2<br />
<br />
and we execute <br />
<br />
load iar --merge Albert Camus / PASSWORD my-items.iar<br />
<br />
with the IAR saved above. Instead of creating a duplicate FolderA, this will instead result in the inventory structure <br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| |<br />
| +-- FolderB<br />
| | |<br />
| | +-- ItemX<br />
| |<br />
| +-- Item1<br />
| |<br />
| +-- ItemY<br />
|<br />
+-- FolderC<br />
|<br />
+-- Item2<br />
<br />
==== Restoring an entire user's inventory ====<br />
<br />
The --merge option is useful if you are restoring a saved inventory to a new user account, since the base folders (Gestures, Landmarks, Objects, etc.) will not be duplicated.<br />
<br />
For instance, if you have saved a whole user's inventory as detailed above, you can restore it to a freshly created user's inventory with the command.<br />
<br />
load iar --merge Albert Camus / PASSWORD my-inventory.iar<br />
<br />
= Use cases =<br />
<br />
Possible uses<br />
<br />
1. To distribute content to other OpenSimulator installations without need to transfer entire regions. One drawback with IARs for this use case is that creator names are not preserved unless the user has a profile on the target installation. One workaround is to include a notecard detailing the creator and license conditions of the content.<br />
<br />
2. To backup a user's inventory. IARs are currently not that great for this. One can backup an entire inventory by giving a path of "/" to the save iar command. But a load IAR of the same will mean a duplicate set of root child 'standard' folders (Objects, Textures, Clothing, etc.). The loaded folders will not have any type icons.<br />
<br />
== Current limitations ==<br />
<br />
* IAR loading and saving is currently done on a single thread. This may lock up the console for a while with very large IARs. This should be addressed in the future<br />
<br />
* Creator names are not preserved unless the profile exists on the target system. This problem may be addressed in the future.<br />
<br />
== IAR Format ==<br />
<br />
The OpenSimulator [[Inventory Archives|Inventory Archive (IAR)]] format is designed with three aims in mind:<br />
<br />
# Make it easy for people to read and update individual items, assets, etc. within an archive.<br />
# Make it easy to compose two inventory archives into a single inventory archive.<br />
# Make it easy to compose archives from scratch.<br />
<br />
Therefore, all the different entities (assets, items, etc.) are packaged in individual files (e.g. one for each asset) with human readable filenames and machine readable extensions (e.g. .jp2 for textures, .txt for notecards).<br />
* [[IAR Format 0.1]]<br />
* [[IAR Format 0.2]]<br />
* [[IAR Format 0.3]]<br />
<br />
= Bugs =<br />
<br />
Please search the OpenSimulator Mantis for information on current IAR bugs. <br />
<br />
FEB.23.2010: <br />
<br />
There is a slight "quirk"&nbsp;with MySql in regards to Max_Allowed_Packet size, which the default is 1 Megabyte.&nbsp; This is too small for some of the larger data blobs being stored.&nbsp; It is recomended to increase the default value to 16 Megabytes. <br />
<br />
Locate your MY.ini for MySql (EXAMPLE, in Windows it is located @ "C:\Program Files\MySQL\MySQL Server 5.1")&nbsp; Modify this file to include the following under the mysqld section: <br />
<br />
'''[mysqld]''' <br />
<br />
# The TCP/IP Port the MySQL Server will listen on<br />port=3306<br />max_allowed_packet = 16M<br />
<br />
'''Additional Reference''':&nbsp; [http://dev.mysql.com/doc/refman/5.1/en/packet-too-large.html dev.mysql.com/doc/refman/5.1/en/packet-too-large.html]<br />
<br />
= Current Status =<br />
<br />
Operational. Bug reports appreciated through the usual Mantis channels.<br />
<br />
Though we will strive to maintain compatibilty for old archives with newer OpenSimulator versions, please do not rely on these archives as your only backup for inventory.<br />
<br />
= Downloadable IAR files =<br />
<br />
* http://justincc.org/downloads/iars/my-great-items.iar - justincc's initial example IAR.<br />
* http://www.aviefactory.com/Gene_Jacobs_Clothes.iar - Gene Jacobs Men's Clothing Collection (Original Creator)<br />
* http://www.aviefactory.com/Genes_Female_Stuff.iar - Female Skins and Shapes (Found off the web)<br />
* http://www.gridhop.net/IAR/lightshare.iar - [[User:Thomax|txOh]]'s LightShare controller. Useful only if you have [[LightShare]] enabled in OpenSim.ini.<br />
<br />
Please feel free to place links to other IARs here.<br />
<br />
= External Links =<br />
<br />
[http://justincc.org/blog/category/iars/ http://justincc.org/blog/category/iars/] - articles by justincc on IARs, including tutorials, background information and possible future developments.<br />
<br />
[http://www.metaverseink.com/blog/?p=29 The OpenSimulator Library just got more interesting] - Diva Canto's article on how to extend the OpenSimulator Library using IARs.<br />
<br />
= See Also =<br />
<br />
* [[OpenSim Archives|How to use OpenSimulator Archives (OAR)]]<br />
<br />
[[Category:Users]]<br />
[[Category:Support]]<br />
[[Category:Tech Reference]]<br />
[[Category:Help]]<br />
[[Category:Configuration]]<br />
[[Category:Getting Started]]<br />
[[Category:Development]]</div>Fleephttp://opensimulator.org/wiki/Inventory_ArchivesInventory Archives2012-04-03T03:21:49Z<p>Fleep: /* Examples */</p>
<hr />
<div>{{Quicklinks}}<br />
<br /><br />
<br />
= Introduction =<br />
<br />
OpenSimulator Inventory Archives (IARs) are a means by which inventory folders and items can be saved offline to a single file (an IAR). This file can then be loaded into a different OpenSimulator installation.<br />
<br />
Like [[OpenSim Archives]], IARs save all the necessary asset data required to fully restore the items including textures, sounds, scripts and objects contained in the inventory of other objects.<br />
<br />
IARs have been enabled in OpenSimulator since Git revision 5a64ca (OpenSimulator 0.6.7 and later).<br />
<br />
= Usage =<br />
<br />
IARs are saved and loaded from the region console.<br />
<br />
== save iar ==<br />
<br />
The command to save an IAR on the region console is<br />
<br />
save iar [-h|--home=<url>] [-v|--verbose] [--noassets] <user-name> <path> <password> [<filename>]<br />
<br />
where <br />
<br />
* <user-name> is the name of the user to save inventory from<br />
<br />
* <path> is the path to an inventory item or folder. If the path is for a folder, that folder and all its contents (both descendant folders and items) are saved. If the path is for an item, then only that item is saved. <br />
<br />
Components of the path are separated by a forward slash ("/"). If you need to specify a path with spaces, you can surround the whole thing with double quotation marks (e.g. "Folder A/Folder B"). <br />
<br />
You can specify that the contents of a folder should be saved rather than the folder itself using the * wildcard. For instance, "/*" will save your entire inventory but not the "My Inventory" folder itself. This can be useful if you want to restore a saved inventory to an existing one using the load iar --merge function discussed later on.<br />
<br />
If a name or folder contains a forward slash ("/") then it can be escaped with the backslash (i.e. "\/") to stop it being seen as a path separator. Back slashes themselves need to be escaped with another backslash (i.e. "\\").<br />
<br />
One further issue here is that it's not possible to distinguish between identically named folders or items on the path - the workaround is to rename your items/folders if you need to specify them in the path :)<br />
<br />
* <password> is the password of the user.<br />
<br />
* <filename> is an optional filename for the IAR. If none is supplied, then the filename user-inventory.iar is used in the current directory. I recommend that iars have the .iar extension.<br />
<br />
=== Switches ===<br />
<br />
* If the --noassets option is specified, then the archive will be saved without assets. This can be handy if you're backing up the asset database separately and don't want the expense of including all the assets in each archive.<br />
* --home=<url> is the URL of this world's profile service. It is not required that the profile service is operational; the information will be saved, and it will be displayed wherever the archive will be loaded. NOTE: the older --profile option (the previous name of this switch) produced IARs that are not compatible with OpenSimulator 0.7.0.2 and earlier; do not use this option if you want to produce a compatible IAR.<br />
* --verbose prints out versbose saving messages<br />
<br />
=== Examples ===<br />
<br />
Here's an example. Suppose you have an inventory structure like this<br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| <br />
+-- FolderB<br />
| |<br />
| +-- ItemX<br />
|<br />
+-- ItemY<br />
<br />
If you type <br />
<br />
save iar John Doe FolderA PASSWORD my-items.iar<br />
<br />
then FolderA and everything in FolderA (FolderB, ItemX and ItemY) will be saved into an IAR called my-items.iar. On the other hand, if you type<br />
<br />
save iar John Doe FolderA/FolderB/ItemX PASSWORD my-items.iar<br />
<br />
then only ItemX will be saved.<br />
<br />
If there is a space in the path to the item, for example if John Doe's folder was named "Folder A" instead of "FolderA", then quotes around the path are necessary on the command line:<br />
<br />
save iar John Doe "Folder A/FolderB/ItemX" PASSWORD my-items.iar<br />
<br />
<br />
With save iar you can save your entire inventory as well as the contents of particular folders or individual items.<br />
<br />
For instance, typing<br />
<br />
save iar John Doe / password<br />
<br />
would save your entire inventory to user-inventory.iar (since no filename was given).<br />
<br />
== load iar ==<br />
<br />
An IAR can be reloaded to an OpenSimulator instance with the load iar command<br />
<br />
load iar [-m|--merge] <user-name> <path> <password> [<filename>]<br />
<br />
where<br />
<br />
* <user name> is the name of the user to whom to load the inventory<br />
<br />
* <path> is the path to which the IAR should be loaded. This has to be a folder which already exists in "My Inventory". See the save iar command for more details.<br />
<br />
* <password> is the password of the user.<br />
<br />
* [<filename>] is an optional filename for the IAR. If none is specified, then the filename is assumed to be user-inventory.iar in the current directory.<br />
<br />
=== Switches ===<br />
<br />
* If the --merge option is given, then IAR items are loaded into the existing folder structure where possible, instead of always creating new folders.<br />
<br />
=== Examples ===<br />
<br />
Suppose that "David Hume" has recieved the my-items.iar saved above containing FolderA, FolderB, ItemX and ItemY. David Hume already has an inventory structure like this. <br />
<br />
My Inventory<br />
|<br />
+-- Folder1<br />
| <br />
+-- Folder2<br />
| <br />
+-- Folder3<br />
<br />
David wants to load the IAR to Folder3, so on the region console he executes <br />
<br />
load iar David Hume Folder1/Folder3 password my-items.iar<br />
<br />
After a little while he ends up with the folder structure <br />
<br />
My Inventory<br />
|<br />
+-- Folder1<br />
| <br />
+-- Folder2<br />
|<br />
+-- Folder3 <br />
|<br />
+-- FolderA<br />
| <br />
+-- FolderB<br />
| |<br />
| +-- ItemX<br />
|<br />
+-- ItemY<br />
<br />
where ItemX and ItemY are ready for rezzing. <br />
<br />
If there is a space in the path to the item, for example if David's folder was named "Folder 1" instead of "Folder1", then quotes around the path are necessary on the command line:<br />
<br />
load iar David Hume "Folder 1/Folder3" password my-items.iar<br />
<br />
<br><br />
<br />
From OpenSimulator 0.7 and onwards, you can also load IARs directly from web addresses. For example <br />
<br />
load iar Betrand Russell Folder2 PASSWORD http://justincc.org/downloads/iars/my-great-items.iar<br />
<br />
will load my-great-items.iar from the web into Folder2 of the user "Bertrand Russell". <br />
<br />
==== Examples ====<br />
<br />
Let's suppose that a user called Albert Camus has an existing inventory structure <br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| |<br />
| +-- Item1<br />
|<br />
+-- FolderC<br />
|<br />
+-- Item2<br />
<br />
and we execute <br />
<br />
load iar --merge Albert Camus / PASSWORD my-items.iar<br />
<br />
with the IAR saved above. Instead of creating a duplicate FolderA, this will instead result in the inventory structure <br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| |<br />
| +-- FolderB<br />
| | |<br />
| | +-- ItemX<br />
| |<br />
| +-- Item1<br />
| |<br />
| +-- ItemY<br />
|<br />
+-- FolderC<br />
|<br />
+-- Item2<br />
<br />
The --merge option is useful if you are restoring a saved inventory to a new user account, since the base folders (Gestures, Landmarks, Objects, etc.) will not be duplicated.<br />
<br />
= IAR files =<br />
<br />
* http://justincc.org/downloads/iars/my-great-items.iar - justincc's initial example IAR.<br />
* http://www.aviefactory.com/Gene_Jacobs_Clothes.iar - Gene Jacobs Men's Clothing Collection (Original Creator)<br />
* http://www.aviefactory.com/Genes_Female_Stuff.iar - Female Skins and Shapes (Found off the web)<br />
* http://www.gridhop.net/IAR/lightshare.iar - [[User:Thomax|txOh]]'s LightShare controller. Useful only if you have [[LightShare]] enabled in OpenSim.ini.<br />
<br />
Please feel free to place links to other IARs here.<br />
<br />
= Further Information =<br />
<br />
[http://justincc.org/blog/category/iars/ http://justincc.org/blog/category/iars/] - articles by justincc on IARs, including tutorials, background information and possible future developments.<br />
<br />
[http://www.metaverseink.com/blog/?p=29 The OpenSimulator Library just got more interesting] - Diva Canto's article on how to extend the OpenSimulator Library using IARs.<br />
<br />
= Use cases =<br />
<br />
Possible uses<br />
<br />
1. To distribute content to other OpenSimulator installations without need to transfer entire regions. One drawback with IARs for this use case is that creator names are not preserved unless the user has a profile on the target installation. One workaround is to include a notecard detailing the creator and license conditions of the content.<br />
<br />
2. To backup a user's inventory. IARs are currently not that great for this. One can backup an entire inventory by giving a path of "/" to the save iar command. But a load IAR of the same will mean a duplicate set of root child 'standard' folders (Objects, Textures, Clothing, etc.). The loaded folders will not have any type icons.<br />
<br />
== Current limitations ==<br />
<br />
* IAR loading and saving is currently done on a single thread. This may lock up the console for a while with very large IARs. This should be addressed in the future<br />
<br />
* Creator names are not preserved unless the profile exists on the target system. This problem may be addressed in the future.<br />
<br />
== IAR Format ==<br />
<br />
The OpenSimulator [[Inventory Archives|Inventory Archive (IAR)]] format is designed with three aims in mind:<br />
<br />
# Make it easy for people to read and update individual items, assets, etc. within an archive.<br />
# Make it easy to compose two inventory archives into a single inventory archive.<br />
# Make it easy to compose archives from scratch.<br />
<br />
Therefore, all the different entities (assets, items, etc.) are packaged in individual files (e.g. one for each asset) with human readable filenames and machine readable extensions (e.g. .jp2 for textures, .txt for notecards).<br />
* [[IAR Format 0.1]]<br />
* [[IAR Format 0.2]]<br />
* [[IAR Format 0.3]]<br />
<br />
= FAQ =<br />
<br />
Nothing yet.<br />
<br />
= Bugs =<br />
<br />
Please search the OpenSimulator Mantis for information on current IAR bugs. <br />
<br />
FEB.23.2010: <br />
<br />
There is a slight "quirk"&nbsp;with MySql in regards to Max_Allowed_Packet size, which the default is 1 Megabyte.&nbsp; This is too small for some of the larger data blobs being stored.&nbsp; It is recomended to increase the default value to 16 Megabytes. <br />
<br />
Locate your MY.ini for MySql (EXAMPLE, in Windows it is located @ "C:\Program Files\MySQL\MySQL Server 5.1")&nbsp; Modify this file to include the following under the mysqld section: <br />
<br />
'''[mysqld]''' <br />
<br />
# The TCP/IP Port the MySQL Server will listen on<br />port=3306<br />max_allowed_packet = 16M<br />
<br />
'''Additional Reference''':&nbsp; [http://dev.mysql.com/doc/refman/5.1/en/packet-too-large.html dev.mysql.com/doc/refman/5.1/en/packet-too-large.html]<br />
<br />
= Current Status =<br />
<br />
Operational but experimental. Bug reports are appreciated and there will almost certainly be quite a few right now. Suggestions for improvement are also welcome. The best place for these right now might be [http://justincc.org/blog/2009/09/14/introducing-opensim-inventory-archives-iars/ my blog post on IARs], since I'm bound to see them then.<br />
<br />
Though we will strive to maintain compatibilty for old archives with newer OpenSimulator versions, please do not rely on these archives as your only backup for inventory.<br />
<br />
= See Also =<br />
<br />
* [[OpenSim Archives|How to use OpenSimulator Archives (OAR)]]<br />
<br />
[[Category:Users]]<br />
[[Category:Support]]<br />
[[Category:Tech Reference]]<br />
[[Category:Help]]<br />
[[Category:Configuration]]<br />
[[Category:Getting Started]]<br />
[[Category:Development]]</div>Fleephttp://opensimulator.org/wiki/Inventory_ArchivesInventory Archives2012-04-03T03:21:09Z<p>Fleep: /* Examples */</p>
<hr />
<div>{{Quicklinks}}<br />
<br /><br />
<br />
= Introduction =<br />
<br />
OpenSimulator Inventory Archives (IARs) are a means by which inventory folders and items can be saved offline to a single file (an IAR). This file can then be loaded into a different OpenSimulator installation.<br />
<br />
Like [[OpenSim Archives]], IARs save all the necessary asset data required to fully restore the items including textures, sounds, scripts and objects contained in the inventory of other objects.<br />
<br />
IARs have been enabled in OpenSimulator since Git revision 5a64ca (OpenSimulator 0.6.7 and later).<br />
<br />
= Usage =<br />
<br />
IARs are saved and loaded from the region console.<br />
<br />
== save iar ==<br />
<br />
The command to save an IAR on the region console is<br />
<br />
save iar [-h|--home=<url>] [-v|--verbose] [--noassets] <user-name> <path> <password> [<filename>]<br />
<br />
where <br />
<br />
* <user-name> is the name of the user to save inventory from<br />
<br />
* <path> is the path to an inventory item or folder. If the path is for a folder, that folder and all its contents (both descendant folders and items) are saved. If the path is for an item, then only that item is saved. <br />
<br />
Components of the path are separated by a forward slash ("/"). If you need to specify a path with spaces, you can surround the whole thing with double quotation marks (e.g. "Folder A/Folder B"). <br />
<br />
You can specify that the contents of a folder should be saved rather than the folder itself using the * wildcard. For instance, "/*" will save your entire inventory but not the "My Inventory" folder itself. This can be useful if you want to restore a saved inventory to an existing one using the load iar --merge function discussed later on.<br />
<br />
If a name or folder contains a forward slash ("/") then it can be escaped with the backslash (i.e. "\/") to stop it being seen as a path separator. Back slashes themselves need to be escaped with another backslash (i.e. "\\").<br />
<br />
One further issue here is that it's not possible to distinguish between identically named folders or items on the path - the workaround is to rename your items/folders if you need to specify them in the path :)<br />
<br />
* <password> is the password of the user.<br />
<br />
* <filename> is an optional filename for the IAR. If none is supplied, then the filename user-inventory.iar is used in the current directory. I recommend that iars have the .iar extension.<br />
<br />
=== Switches ===<br />
<br />
* If the --noassets option is specified, then the archive will be saved without assets. This can be handy if you're backing up the asset database separately and don't want the expense of including all the assets in each archive.<br />
* --home=<url> is the URL of this world's profile service. It is not required that the profile service is operational; the information will be saved, and it will be displayed wherever the archive will be loaded. NOTE: the older --profile option (the previous name of this switch) produced IARs that are not compatible with OpenSimulator 0.7.0.2 and earlier; do not use this option if you want to produce a compatible IAR.<br />
* --verbose prints out versbose saving messages<br />
<br />
=== Examples ===<br />
<br />
Here's an example. Suppose you have an inventory structure like this<br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| <br />
+-- FolderB<br />
| |<br />
| +-- ItemX<br />
|<br />
+-- ItemY<br />
<br />
If you type <br />
<br />
save iar John Doe FolderA PASSWORD my-items.iar<br />
<br />
then FolderA and everything in FolderA (FolderB, ItemX and ItemY) will be saved into an IAR called my-items.iar. On the other hand, if you type<br />
<br />
save iar John Doe FolderA/FolderB/ItemX PASSWORD my-items.iar<br />
<br />
then only ItemX will be saved.<br />
<br />
If there is a space in the path to the item, for example if John Doe's folder was named "Folder A" instead of "FolderA", then quotes around the path are necessary on the command line:<br />
<br />
save iar John Doe "Folder A/FolderB/ItemX" PASSWORD my-items.iar<br />
<br />
<br />
With save iar you can save your entire inventory as well as the contents of particular folders or individual items.<br />
<br />
For instance, typing<br />
<br />
save iar John Doe / password<br />
<br />
would save your entire inventory to user-inventory.iar (since no filename was given).<br />
<br />
== load iar ==<br />
<br />
An IAR can be reloaded to an OpenSimulator instance with the load iar command<br />
<br />
load iar [-m|--merge] <user-name> <path> <password> [<filename>]<br />
<br />
where<br />
<br />
* <user name> is the name of the user to whom to load the inventory<br />
<br />
* <path> is the path to which the IAR should be loaded. This has to be a folder which already exists in "My Inventory". See the save iar command for more details.<br />
<br />
* <password> is the password of the user.<br />
<br />
* [<filename>] is an optional filename for the IAR. If none is specified, then the filename is assumed to be user-inventory.iar in the current directory.<br />
<br />
=== Switches ===<br />
<br />
* If the --merge option is given, then IAR items are loaded into the existing folder structure where possible, instead of always creating new folders.<br />
<br />
=== Examples ===<br />
<br />
Suppose that "David Hume" has recieved the my-items.iar saved above containing FolderA, FolderB, ItemX and ItemY. David Hume already has an inventory structure like this. <br />
<br />
My Inventory<br />
|<br />
+-- Folder1<br />
| <br />
+-- Folder2<br />
| <br />
+-- Folder3<br />
<br />
David wants to load the IAR to Folder3, so on the region console he executes <br />
<br />
load iar David Hume Folder1/Folder3 password my-items.iar<br />
<br />
After a little while he ends up with the folder structure <br />
<br />
My Inventory<br />
|<br />
+-- Folder1<br />
| <br />
+-- Folder2<br />
|<br />
+-- Folder3 <br />
|<br />
+-- FolderA<br />
| <br />
+-- FolderB<br />
| |<br />
| +-- ItemX<br />
|<br />
+-- ItemY<br />
<br />
where ItemX and ItemY are ready for rezzing. <br />
<br />
Note that if there is a space in the path to the item, for example if David's folder was named "Folder 1" instead of "Folder1", then quotes around the path are necessary on the command line:<br />
<br />
load iar David Hume "Folder 1/Folder3" password my-items.iar<br />
<br />
<br><br />
<br />
From OpenSimulator 0.7 and onwards, you can also load IARs directly from web addresses. For example <br />
<br />
load iar Betrand Russell Folder2 PASSWORD http://justincc.org/downloads/iars/my-great-items.iar<br />
<br />
will load my-great-items.iar from the web into Folder2 of the user "Bertrand Russell". <br />
<br />
==== Examples ====<br />
<br />
Let's suppose that a user called Albert Camus has an existing inventory structure <br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| |<br />
| +-- Item1<br />
|<br />
+-- FolderC<br />
|<br />
+-- Item2<br />
<br />
and we execute <br />
<br />
load iar --merge Albert Camus / PASSWORD my-items.iar<br />
<br />
with the IAR saved above. Instead of creating a duplicate FolderA, this will instead result in the inventory structure <br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| |<br />
| +-- FolderB<br />
| | |<br />
| | +-- ItemX<br />
| |<br />
| +-- Item1<br />
| |<br />
| +-- ItemY<br />
|<br />
+-- FolderC<br />
|<br />
+-- Item2<br />
<br />
The --merge option is useful if you are restoring a saved inventory to a new user account, since the base folders (Gestures, Landmarks, Objects, etc.) will not be duplicated.<br />
<br />
= IAR files =<br />
<br />
* http://justincc.org/downloads/iars/my-great-items.iar - justincc's initial example IAR.<br />
* http://www.aviefactory.com/Gene_Jacobs_Clothes.iar - Gene Jacobs Men's Clothing Collection (Original Creator)<br />
* http://www.aviefactory.com/Genes_Female_Stuff.iar - Female Skins and Shapes (Found off the web)<br />
* http://www.gridhop.net/IAR/lightshare.iar - [[User:Thomax|txOh]]'s LightShare controller. Useful only if you have [[LightShare]] enabled in OpenSim.ini.<br />
<br />
Please feel free to place links to other IARs here.<br />
<br />
= Further Information =<br />
<br />
[http://justincc.org/blog/category/iars/ http://justincc.org/blog/category/iars/] - articles by justincc on IARs, including tutorials, background information and possible future developments.<br />
<br />
[http://www.metaverseink.com/blog/?p=29 The OpenSimulator Library just got more interesting] - Diva Canto's article on how to extend the OpenSimulator Library using IARs.<br />
<br />
= Use cases =<br />
<br />
Possible uses<br />
<br />
1. To distribute content to other OpenSimulator installations without need to transfer entire regions. One drawback with IARs for this use case is that creator names are not preserved unless the user has a profile on the target installation. One workaround is to include a notecard detailing the creator and license conditions of the content.<br />
<br />
2. To backup a user's inventory. IARs are currently not that great for this. One can backup an entire inventory by giving a path of "/" to the save iar command. But a load IAR of the same will mean a duplicate set of root child 'standard' folders (Objects, Textures, Clothing, etc.). The loaded folders will not have any type icons.<br />
<br />
== Current limitations ==<br />
<br />
* IAR loading and saving is currently done on a single thread. This may lock up the console for a while with very large IARs. This should be addressed in the future<br />
<br />
* Creator names are not preserved unless the profile exists on the target system. This problem may be addressed in the future.<br />
<br />
== IAR Format ==<br />
<br />
The OpenSimulator [[Inventory Archives|Inventory Archive (IAR)]] format is designed with three aims in mind:<br />
<br />
# Make it easy for people to read and update individual items, assets, etc. within an archive.<br />
# Make it easy to compose two inventory archives into a single inventory archive.<br />
# Make it easy to compose archives from scratch.<br />
<br />
Therefore, all the different entities (assets, items, etc.) are packaged in individual files (e.g. one for each asset) with human readable filenames and machine readable extensions (e.g. .jp2 for textures, .txt for notecards).<br />
* [[IAR Format 0.1]]<br />
* [[IAR Format 0.2]]<br />
* [[IAR Format 0.3]]<br />
<br />
= FAQ =<br />
<br />
Nothing yet.<br />
<br />
= Bugs =<br />
<br />
Please search the OpenSimulator Mantis for information on current IAR bugs. <br />
<br />
FEB.23.2010: <br />
<br />
There is a slight "quirk"&nbsp;with MySql in regards to Max_Allowed_Packet size, which the default is 1 Megabyte.&nbsp; This is too small for some of the larger data blobs being stored.&nbsp; It is recomended to increase the default value to 16 Megabytes. <br />
<br />
Locate your MY.ini for MySql (EXAMPLE, in Windows it is located @ "C:\Program Files\MySQL\MySQL Server 5.1")&nbsp; Modify this file to include the following under the mysqld section: <br />
<br />
'''[mysqld]''' <br />
<br />
# The TCP/IP Port the MySQL Server will listen on<br />port=3306<br />max_allowed_packet = 16M<br />
<br />
'''Additional Reference''':&nbsp; [http://dev.mysql.com/doc/refman/5.1/en/packet-too-large.html dev.mysql.com/doc/refman/5.1/en/packet-too-large.html]<br />
<br />
= Current Status =<br />
<br />
Operational but experimental. Bug reports are appreciated and there will almost certainly be quite a few right now. Suggestions for improvement are also welcome. The best place for these right now might be [http://justincc.org/blog/2009/09/14/introducing-opensim-inventory-archives-iars/ my blog post on IARs], since I'm bound to see them then.<br />
<br />
Though we will strive to maintain compatibilty for old archives with newer OpenSimulator versions, please do not rely on these archives as your only backup for inventory.<br />
<br />
= See Also =<br />
<br />
* [[OpenSim Archives|How to use OpenSimulator Archives (OAR)]]<br />
<br />
[[Category:Users]]<br />
[[Category:Support]]<br />
[[Category:Tech Reference]]<br />
[[Category:Help]]<br />
[[Category:Configuration]]<br />
[[Category:Getting Started]]<br />
[[Category:Development]]</div>Fleephttp://opensimulator.org/wiki/User_talk:JustinccUser talk:Justincc2012-04-03T03:16:59Z<p>Fleep: </p>
<hr />
<div>Hi Justin,<br />
Is your email really 'AT googlemail DORT com' .. or should that be ... '''DOT''' com ? :)<br />
<br />
--[[User:Mstram|Mstram]] 14:16, 9 April 2009 (UTC)<br />
<br />
:Hi Mstram. 'Tis a somewhat feeble attempt at a little extra bot confusing obfuscation :) - [[User:Justincc|Justincc]] 14:48, 9 April 2009 (UTC)<br />
<br />
== My Links ==<br />
<br />
[[Foundation]]<br />
<br />
== Status Page ==<br />
<br />
Hi Justin, <br />
<br />
You've deleted the the page [[Status]], however, there are 42 other pages that linked there. Many of those pages had breadcrumbs referring to the status page. So what to do with those? Where should they link to now? <br />
<br />
BTW, it's nice to know that you can delete pages. You may want to have a look at the [[:Category:To Delete|To Delete]] category, there are many pages in there that should be reviewed and deleted. <br />
<br />
--[[User:Fritigern|Fritigern]] 04:27, 22 December 2010 (UTC) <br />
<br />
:Hi Fritigern. From my brief look at it, many of the pages that the status page linked to were very out of date. The ones which aren't or have some semblence of usefulness or already linked elsewhere, I think. My intention was to come back on Friday and chase down the subsequently broken links, but I probably should have the left the page intact until then, at least (I'm too used to quickly editing the wiki because few other people are doing it!).<br />
<br />
:So I've restored the page for my now but my intention is still to come back and delete it on Friday (and chase down the broken links). But if you have any other ideas (e.g. whether it should be retained) then I'd be very pleased to discuss them.<br />
<br />
:Thanks for pointing out the "To Delete" category. I hope to get the time to go through that on Friday too.<br />
<br />
:Thanks for your editing btw - it's really nice to have someone else looking at this stuff too.<br />
<br />
:--[[User:Justincc|Justincc]] 01:10, 23 December 2010 (UTC)<br />
<br />
<br> <br />
<br />
::I think it's a very common mistake for an editor, an even for a Wiki sysop to overlook the "[[Special:WhatLinksHere/Status|What links here]]" link on a page that he/she wishes to delete. That link showed me that many osfunction pages link to [[Status]] <br />
::So what would i do about this? Hmmm... I am not sure. I would probably (because other pages depend on it in one form or another) do a complete rewrite of that page, making the info more current, though since i am basically just a "dumb end user" (tongue-in-cheek very much intended!), i wouldn't know the first thing of what the status really is. <br />
::As for my editing, it really started because i couldn't easily find the info that i needed at that time (i can't remember what it was, just that i couldn't find it&nbsp;;-)) <br />
::One thing that i really would like to see on the wiki, is more information in ''layman's terms''. A lot of the documentation was written by devs, and i know that it can often be hard for devs/coders/techs to translate their jargon to something that non-coders can understand too. <br />
::One example of an article that i find confusing is [[Wifi]], see also the discussion page of that article. Another one would be the one about [[NINJA Physics]]. <br />
::<br />
::...Which brings me to something that i hope you can find the time to look into. The wiki's search function doesn't seem to work properly. As in that i would enter "ninja" (all lower case), click "search", and expect to find the [[NINJA Physics]] article listed as one of the search results. Instead, it comes up with nothing. Even when searching for "NINJA Physics" (using the correct case), the search results remain empty. This happens with all other search terms as well. The "Go" button does work though, as long as the search term is entered with the correct case. <br />
::This search problem really is a problem, since it makes the wiki not searchable, and therefore makes it less useful for end users. OS is a complex piece of software, and it is not always 100% clear why things goes *beep* instead of *ding*, or how to do this or that...&nbsp;:-) <br />
::--[[User:Fritigern|Fritigern]] 02:24, 24 December 2010 (UTC)<br />
<br />
:::I had a look at the "[[Special:WhatLinksHere/Status|What links here]]" for the Status page and I see what you mean. As far as I can tell, pretty much everything linked off this page is out of date or unmaintained. But it's too much of a Sisyphean task for me right now to clean up all the inbound links so I'll have to leave as is. <br />
:::I went through the delete category and deleted all the pages except [[Wikistructure]]. <br />
:::I agree with you about the information, but to be honest there's very few of the developers who write any kind of documentation at all. So even getting the tech heavy stuff is quite a rarity, let alone things more understandable by the layman. <br />
:::The search on the wiki was recently updated by [[Teravus]] - it wasn't working at all before. So it might be worth leaving him a note about the current problems. He is also on IRC on and off. <br />
:::--[[User:Justincc|Justincc]] 00:29, 25 December 2010 (UTC)<br />
<br />
<br> <br />
<br />
::::Awesome! I will leave [[User:Teravus|Teravus]] a message after the holidays, or at least after Christmas&nbsp;:) <br />
::::As for the [[WikiStructure]] article, i see it contains the templates that people can use when editing the wiki. This includes the <nowiki>{{delete}}</nowiki> template, which is only there as an example. I hope to go over more articles in the new year, in order to tackle this, and other similar problems, and other confusing stuffs. <br />
::::Oh, I've started to make some changes to the [[Wifi]] text, hopefully making them easier to read for laymen, (for instance, instead of saying something like "wifi interacts with OpenSimulator's code base", i chose to have it say "wifi uses OpenSim's built-in features". It's not the exact same thing, but it is easier to understand.<br>Alright, i'm gonna make it Christmas at Fritiville, thanks for cleaning up the deletable articles, keeping the wiki clean will make everyone happy :-)<br>--[[User:Fritigern|Fritigern]] 21:48, 25 December 2010 (UTC)<br />
<br />
== Proposal against spam (having new sysop) ==<br />
<br />
I feel that we have many spam pages these days(I can't concentrate on revising and creating articles due to that). I've came up on the quick-and-dirty idea of redirecting the spam page to another page, which introduce OpenSimulator Project, but it is not the complete solution(we can't delete the pages or images, ban user nor block account creations). Actually you are busy with codes, and I don't want you to take the time to kill spams on the wiki instead of adding new features, fixing bugs and applying the patches(by me lol).<br />
<br />
I bet if [[User:Fritigern|Fritigern]] become sysop, this kind of problems will be solved quickly. He always patrols on OpenSimulator wiki, finding spams and taking the action against them quickly. Thanks<br />
<br />
-- [[User:Makopoppo|Makopoppo]] 11:19, 3 June 2011 (UTC)<br />
<br />
:Great idea, Makopoppo. In fact, I made both you and Fritigen sysops. If you don't want the bit then please tell me. [[User:Justincc|Justincc]] 20:09, 3 June 2011 (UTC)<br />
<br />
::Thanks, Justincc! I'll clean up piled spam images gradually. -- [[User:Makopoppo|Makopoppo]] 23:54, 3 June 2011 (UTC)<br />
<br />
:::Brilliant. Many, many thanks for your help - it's really appreciated. [[User:Justincc|Justincc]] 23:55, 3 June 2011 (UTC)<br />
<br />
::::Woot! Thank you so much Justin! I will do my best to be a great sysop!!! --[[User:Fritigern|Fritigern]] 21:24, 4 June 2011 (UTC)<br />
<br />
== Upgrading The Wiki ==<br />
<br />
Hi Justin.<br />
I know this kinda sounds like nagging, but i really think that the wiki could benefit from an update to the most recent release of mediawiki.The wiki is running v 1.13, but the current version is 1.17, with 1.18 just around the corner.<br />
<br />
Pros:<br />
* Better anti-spam tools<br />
* Additional CSS classes, allowing for example the hiding/showing of sections, making for cleaner looking pages.<br />
* Out-of-the-box LSL source highlighting<br />
* Fixed various vulnerabilities<br />
* Auto-completion in search box<br />
* Better WYSIWYG editor, it no longer replaces wiki markup with HTML code.<br />
* Since version 1.16, it is possible to update MediaWiki by running a web installer, making upgrading less of a hassle.<br />
<br />
Cons:<br />
* Since there's been a large gap between versions, immediate rollout would be a bad idea. I would stringly suggest a parallel database+folder containing a snapshot of the wiki, and all of its files/articles. Then testing the new version, making modifications to the wiki's skin to accomodate for the new version, as well as finding bottlenecks with changed configuation parameters, and whatever may come to light, If resources permit, i would even suggest running the two versions in parallel on the same server, making the transition from 1.13 to 1.17 less painful.<br />
* There have been changes to the database format. So database will need to be updated, which may require the wiki to be offline for that period. Versions of PHP and MySQL are still within system requirements.<br />
<br />
<br />
General:<br />
The current version of the Opensim wiki has support for SVG graphics. However, the version of ImageMagick which is currently installed on the server does not. For example, the file [[:Image:Template-info.svg]] is a valid SVG file, but does not display because ImageMagick is unfalimiar with the format and displays an error message instead.<br />
<br />
<br />
See also the release notes for [http://www.mediawiki.org/wiki/Release_notes/1.14 1.14], [http://www.mediawiki.org/wiki/Release_notes/1.15 1.15], [http://www.mediawiki.org/wiki/Release_notes/1.16 1.16] and [http://www.mediawiki.org/wiki/Release_notes/1.17 1.17] for more info on the changes and improvements between versions, as well as [http://www.mediawiki.org/wiki/Manual:Upgrading the upgrading manual].<br />
<br />
<br />
Would you please consider this? And if you lack the time, perhaps someone else will be able to do this. First person to come to mind would be Makopoppo, if she has time.<br />
<br />
--[[User:Fritigern|Fritigern]] 12:01, 3 August 2011 (UTC)<br />
<br />
: Not only do I lack the time, but any time I spend on this is almost certain time that I don't spend on fixing OpenSim, which is by far my most valuable contribution. The problem is that changing things on the server is sensitive as well. Let's keep thinking about this over the coming weeks.<br />
<br />
:: Sorry if I was a little short yesterday - I get like that when I'm tired :). If upgrading would help fight spam then do please tell me it's really important.<br />
<br />
::: Hi Fritigern. coyled upgraded mediawiki to 1.17 last night -- [[User:Justincc|Justincc]] 09:06, 20 October 2011 (PDT)<br />
<br />
:::: That's absolutely awsome. I hope this will give us some respite from the waves of spam that we've been getting. But even if it picks up again, we will have the framewirk that allows us to install the extensions that we may need to prevent the spam more effectively.<br />
:::: --[[User:Fritigern|Fritigern]] 00:31, 21 October 2011 (PDT)<br />
<br />
== Proposal for introducing some extensions ==<br />
<br />
Hi, Justin. Thank you for upgrading wiki software:) It enabled us to introduce a lot of useful extensions rather safely. Just for reference, [http://wiki.secondlife.com/wiki/Special:Version SecondLife wiki enables some other extensions] though I doubt if we need all of them. Still, I want to use following extensions soon.<br />
<br />
* [http://www.mediawiki.org/wiki/Extension:VariablesExtension Variables] - enables the syntaxes like {{#var:somevariable|somevalue}}<br />
* [http://www.mediawiki.org/wiki/Extension:DeletePagePermanently Delete Page Permanently] - removes malicious titles of spam pages from recent pages list. Only if you take regular backup of wiki<br />
<br />
Could you enable them, at least Variables extension, whenever you have time? Thanks.<br />
<br />
-- [[User:Makopoppo|Makopoppo]] 17:51, 8 January 2012 (PST)<br />
<br />
:Hi Makopoppo. Our sysadmin (Dave Coyle [coyled]) has some misgivings about enabling the delete page permanently extension, but there's no problem installing the variables one. Hope this is okay. Hoping to do this tomorrow, please poke me if I forget!<br />
<br />
:And thanks for all the work you do on the wiki!<br />
<br />
:Also, it might also be worth asking on the opensim-dev list in future, since I regard this as a dev issue. I should have put my discussion with Dave on there as well but forgot this time. However, as a great wiki worker, if you want to just message me directly then please do! -- [[User:Justincc|Justincc]] 16:12, 12 January 2012 (PST)<br />
<br />
:: Sorry, Makopoppo. Something completely unexpected popped up today and I didn't get time to do the install. I will try to do this as soon as I get an opportunity -- [[User:Justincc|Justincc]] 17:39, 13 January 2012 (PST)<br />
<br />
::: {{#vardefine:hello|Now installed. Sorry for the delay!}}<br />
::: {{#var:hello}} -- [[User:Justincc|Justincc]] 17:26, 27 January 2012 (PST)<br />
<br />
:::: Thank you, Justin! It works perfectly. I sorted some interspersed templates for release informations (version, date, urls, ...) into one template [[:Template:ReleaseInfo]]. You will probably no longer have to fix around many templates in every releasing:) -- [[User:Makopoppo|Makopoppo]] 00:11, 28 January 2012 (PST)<br />
<br />
== IAR Page ==<br />
<br />
Hi Justin, thanks for&nbsp;[http://opensimulator.org/wiki/User_talk:Fleep%7Cfor your note about quotes around the path]&nbsp;when loading an IAR file. I didn't realize quotes were only necessary if there is a space in the path - I guess my paths have always contained spaces, so it appeared to me that quotes were required. I've [http://opensimulator.org/wiki/Inventory_Archives#Examples_2 edited the IAR page again to clarify], let me know if that doesn't look better. Thanks again! &nbsp;:) [[User:Fleep|Fleep]] 20:14, 2 April 2012 (PDT)</div>Fleephttp://opensimulator.org/wiki/User_talk:JustinccUser talk:Justincc2012-04-03T03:16:11Z<p>Fleep: </p>
<hr />
<div>Hi Justin,<br />
Is your email really 'AT googlemail DORT com' .. or should that be ... '''DOT''' com ? :)<br />
<br />
--[[User:Mstram|Mstram]] 14:16, 9 April 2009 (UTC)<br />
<br />
:Hi Mstram. 'Tis a somewhat feeble attempt at a little extra bot confusing obfuscation :) - [[User:Justincc|Justincc]] 14:48, 9 April 2009 (UTC)<br />
<br />
== My Links ==<br />
<br />
[[Foundation]]<br />
<br />
== Status Page ==<br />
<br />
Hi Justin, <br />
<br />
You've deleted the the page [[Status]], however, there are 42 other pages that linked there. Many of those pages had breadcrumbs referring to the status page. So what to do with those? Where should they link to now? <br />
<br />
BTW, it's nice to know that you can delete pages. You may want to have a look at the [[:Category:To Delete|To Delete]] category, there are many pages in there that should be reviewed and deleted. <br />
<br />
--[[User:Fritigern|Fritigern]] 04:27, 22 December 2010 (UTC) <br />
<br />
:Hi Fritigern. From my brief look at it, many of the pages that the status page linked to were very out of date. The ones which aren't or have some semblence of usefulness or already linked elsewhere, I think. My intention was to come back on Friday and chase down the subsequently broken links, but I probably should have the left the page intact until then, at least (I'm too used to quickly editing the wiki because few other people are doing it!).<br />
<br />
:So I've restored the page for my now but my intention is still to come back and delete it on Friday (and chase down the broken links). But if you have any other ideas (e.g. whether it should be retained) then I'd be very pleased to discuss them.<br />
<br />
:Thanks for pointing out the "To Delete" category. I hope to get the time to go through that on Friday too.<br />
<br />
:Thanks for your editing btw - it's really nice to have someone else looking at this stuff too.<br />
<br />
:--[[User:Justincc|Justincc]] 01:10, 23 December 2010 (UTC)<br />
<br />
<br> <br />
<br />
::I think it's a very common mistake for an editor, an even for a Wiki sysop to overlook the "[[Special:WhatLinksHere/Status|What links here]]" link on a page that he/she wishes to delete. That link showed me that many osfunction pages link to [[Status]] <br />
::So what would i do about this? Hmmm... I am not sure. I would probably (because other pages depend on it in one form or another) do a complete rewrite of that page, making the info more current, though since i am basically just a "dumb end user" (tongue-in-cheek very much intended!), i wouldn't know the first thing of what the status really is. <br />
::As for my editing, it really started because i couldn't easily find the info that i needed at that time (i can't remember what it was, just that i couldn't find it&nbsp;;-)) <br />
::One thing that i really would like to see on the wiki, is more information in ''layman's terms''. A lot of the documentation was written by devs, and i know that it can often be hard for devs/coders/techs to translate their jargon to something that non-coders can understand too. <br />
::One example of an article that i find confusing is [[Wifi]], see also the discussion page of that article. Another one would be the one about [[NINJA Physics]]. <br />
::<br />
::...Which brings me to something that i hope you can find the time to look into. The wiki's search function doesn't seem to work properly. As in that i would enter "ninja" (all lower case), click "search", and expect to find the [[NINJA Physics]] article listed as one of the search results. Instead, it comes up with nothing. Even when searching for "NINJA Physics" (using the correct case), the search results remain empty. This happens with all other search terms as well. The "Go" button does work though, as long as the search term is entered with the correct case. <br />
::This search problem really is a problem, since it makes the wiki not searchable, and therefore makes it less useful for end users. OS is a complex piece of software, and it is not always 100% clear why things goes *beep* instead of *ding*, or how to do this or that...&nbsp;:-) <br />
::--[[User:Fritigern|Fritigern]] 02:24, 24 December 2010 (UTC)<br />
<br />
:::I had a look at the "[[Special:WhatLinksHere/Status|What links here]]" for the Status page and I see what you mean. As far as I can tell, pretty much everything linked off this page is out of date or unmaintained. But it's too much of a Sisyphean task for me right now to clean up all the inbound links so I'll have to leave as is. <br />
:::I went through the delete category and deleted all the pages except [[Wikistructure]]. <br />
:::I agree with you about the information, but to be honest there's very few of the developers who write any kind of documentation at all. So even getting the tech heavy stuff is quite a rarity, let alone things more understandable by the layman. <br />
:::The search on the wiki was recently updated by [[Teravus]] - it wasn't working at all before. So it might be worth leaving him a note about the current problems. He is also on IRC on and off. <br />
:::--[[User:Justincc|Justincc]] 00:29, 25 December 2010 (UTC)<br />
<br />
<br> <br />
<br />
::::Awesome! I will leave [[User:Teravus|Teravus]] a message after the holidays, or at least after Christmas&nbsp;:) <br />
::::As for the [[WikiStructure]] article, i see it contains the templates that people can use when editing the wiki. This includes the <nowiki>{{delete}}</nowiki> template, which is only there as an example. I hope to go over more articles in the new year, in order to tackle this, and other similar problems, and other confusing stuffs. <br />
::::Oh, I've started to make some changes to the [[Wifi]] text, hopefully making them easier to read for laymen, (for instance, instead of saying something like "wifi interacts with OpenSimulator's code base", i chose to have it say "wifi uses OpenSim's built-in features". It's not the exact same thing, but it is easier to understand.<br>Alright, i'm gonna make it Christmas at Fritiville, thanks for cleaning up the deletable articles, keeping the wiki clean will make everyone happy :-)<br>--[[User:Fritigern|Fritigern]] 21:48, 25 December 2010 (UTC)<br />
<br />
== Proposal against spam (having new sysop) ==<br />
<br />
I feel that we have many spam pages these days(I can't concentrate on revising and creating articles due to that). I've came up on the quick-and-dirty idea of redirecting the spam page to another page, which introduce OpenSimulator Project, but it is not the complete solution(we can't delete the pages or images, ban user nor block account creations). Actually you are busy with codes, and I don't want you to take the time to kill spams on the wiki instead of adding new features, fixing bugs and applying the patches(by me lol).<br />
<br />
I bet if [[User:Fritigern|Fritigern]] become sysop, this kind of problems will be solved quickly. He always patrols on OpenSimulator wiki, finding spams and taking the action against them quickly. Thanks<br />
<br />
-- [[User:Makopoppo|Makopoppo]] 11:19, 3 June 2011 (UTC)<br />
<br />
:Great idea, Makopoppo. In fact, I made both you and Fritigen sysops. If you don't want the bit then please tell me. [[User:Justincc|Justincc]] 20:09, 3 June 2011 (UTC)<br />
<br />
::Thanks, Justincc! I'll clean up piled spam images gradually. -- [[User:Makopoppo|Makopoppo]] 23:54, 3 June 2011 (UTC)<br />
<br />
:::Brilliant. Many, many thanks for your help - it's really appreciated. [[User:Justincc|Justincc]] 23:55, 3 June 2011 (UTC)<br />
<br />
::::Woot! Thank you so much Justin! I will do my best to be a great sysop!!! --[[User:Fritigern|Fritigern]] 21:24, 4 June 2011 (UTC)<br />
<br />
== Upgrading The Wiki ==<br />
<br />
Hi Justin.<br />
I know this kinda sounds like nagging, but i really think that the wiki could benefit from an update to the most recent release of mediawiki.The wiki is running v 1.13, but the current version is 1.17, with 1.18 just around the corner.<br />
<br />
Pros:<br />
* Better anti-spam tools<br />
* Additional CSS classes, allowing for example the hiding/showing of sections, making for cleaner looking pages.<br />
* Out-of-the-box LSL source highlighting<br />
* Fixed various vulnerabilities<br />
* Auto-completion in search box<br />
* Better WYSIWYG editor, it no longer replaces wiki markup with HTML code.<br />
* Since version 1.16, it is possible to update MediaWiki by running a web installer, making upgrading less of a hassle.<br />
<br />
Cons:<br />
* Since there's been a large gap between versions, immediate rollout would be a bad idea. I would stringly suggest a parallel database+folder containing a snapshot of the wiki, and all of its files/articles. Then testing the new version, making modifications to the wiki's skin to accomodate for the new version, as well as finding bottlenecks with changed configuation parameters, and whatever may come to light, If resources permit, i would even suggest running the two versions in parallel on the same server, making the transition from 1.13 to 1.17 less painful.<br />
* There have been changes to the database format. So database will need to be updated, which may require the wiki to be offline for that period. Versions of PHP and MySQL are still within system requirements.<br />
<br />
<br />
General:<br />
The current version of the Opensim wiki has support for SVG graphics. However, the version of ImageMagick which is currently installed on the server does not. For example, the file [[:Image:Template-info.svg]] is a valid SVG file, but does not display because ImageMagick is unfalimiar with the format and displays an error message instead.<br />
<br />
<br />
See also the release notes for [http://www.mediawiki.org/wiki/Release_notes/1.14 1.14], [http://www.mediawiki.org/wiki/Release_notes/1.15 1.15], [http://www.mediawiki.org/wiki/Release_notes/1.16 1.16] and [http://www.mediawiki.org/wiki/Release_notes/1.17 1.17] for more info on the changes and improvements between versions, as well as [http://www.mediawiki.org/wiki/Manual:Upgrading the upgrading manual].<br />
<br />
<br />
Would you please consider this? And if you lack the time, perhaps someone else will be able to do this. First person to come to mind would be Makopoppo, if she has time.<br />
<br />
--[[User:Fritigern|Fritigern]] 12:01, 3 August 2011 (UTC)<br />
<br />
: Not only do I lack the time, but any time I spend on this is almost certain time that I don't spend on fixing OpenSim, which is by far my most valuable contribution. The problem is that changing things on the server is sensitive as well. Let's keep thinking about this over the coming weeks.<br />
<br />
:: Sorry if I was a little short yesterday - I get like that when I'm tired :). If upgrading would help fight spam then do please tell me it's really important.<br />
<br />
::: Hi Fritigern. coyled upgraded mediawiki to 1.17 last night -- [[User:Justincc|Justincc]] 09:06, 20 October 2011 (PDT)<br />
<br />
:::: That's absolutely awsome. I hope this will give us some respite from the waves of spam that we've been getting. But even if it picks up again, we will have the framewirk that allows us to install the extensions that we may need to prevent the spam more effectively.<br />
:::: --[[User:Fritigern|Fritigern]] 00:31, 21 October 2011 (PDT)<br />
<br />
== Proposal for introducing some extensions ==<br />
<br />
Hi, Justin. Thank you for upgrading wiki software:) It enabled us to introduce a lot of useful extensions rather safely. Just for reference, [http://wiki.secondlife.com/wiki/Special:Version SecondLife wiki enables some other extensions] though I doubt if we need all of them. Still, I want to use following extensions soon.<br />
<br />
* [http://www.mediawiki.org/wiki/Extension:VariablesExtension Variables] - enables the syntaxes like {{#var:somevariable|somevalue}}<br />
* [http://www.mediawiki.org/wiki/Extension:DeletePagePermanently Delete Page Permanently] - removes malicious titles of spam pages from recent pages list. Only if you take regular backup of wiki<br />
<br />
Could you enable them, at least Variables extension, whenever you have time? Thanks.<br />
<br />
-- [[User:Makopoppo|Makopoppo]] 17:51, 8 January 2012 (PST)<br />
<br />
:Hi Makopoppo. Our sysadmin (Dave Coyle [coyled]) has some misgivings about enabling the delete page permanently extension, but there's no problem installing the variables one. Hope this is okay. Hoping to do this tomorrow, please poke me if I forget!<br />
<br />
:And thanks for all the work you do on the wiki!<br />
<br />
:Also, it might also be worth asking on the opensim-dev list in future, since I regard this as a dev issue. I should have put my discussion with Dave on there as well but forgot this time. However, as a great wiki worker, if you want to just message me directly then please do! -- [[User:Justincc|Justincc]] 16:12, 12 January 2012 (PST)<br />
<br />
:: Sorry, Makopoppo. Something completely unexpected popped up today and I didn't get time to do the install. I will try to do this as soon as I get an opportunity -- [[User:Justincc|Justincc]] 17:39, 13 January 2012 (PST)<br />
<br />
::: {{#vardefine:hello|Now installed. Sorry for the delay!}}<br />
::: {{#var:hello}} -- [[User:Justincc|Justincc]] 17:26, 27 January 2012 (PST)<br />
<br />
:::: Thank you, Justin! It works perfectly. I sorted some interspersed templates for release informations (version, date, urls, ...) into one template [[:Template:ReleaseInfo]]. You will probably no longer have to fix around many templates in every releasing:) -- [[User:Makopoppo|Makopoppo]] 00:11, 28 January 2012 (PST)<br />
<br />
== IAR Page ==<br />
<br />
Hi Justin, thanks for&nbsp;[http://opensimulator.org/wiki/User_talk:Fleep%7Cfor your note about quotes around the path]&nbsp;when loading an IAR file. I didn't realize quotes were only necessary if there is a space in the path - I guess my paths have always contained spaces, so it appeared to me that quotes were required. I've [http://opensimulator.org/wiki/Inventory_Archives#Examples edited the IAR page again to clarify], let me know if that doesn't look better. Thanks again! &nbsp;:) [[User:Fleep|Fleep]] 20:14, 2 April 2012 (PDT)</div>Fleephttp://opensimulator.org/wiki/User_talk:JustinccUser talk:Justincc2012-04-03T03:15:26Z<p>Fleep: </p>
<hr />
<div>Hi Justin,<br />
Is your email really 'AT googlemail DORT com' .. or should that be ... '''DOT''' com ? :)<br />
<br />
--[[User:Mstram|Mstram]] 14:16, 9 April 2009 (UTC)<br />
<br />
:Hi Mstram. 'Tis a somewhat feeble attempt at a little extra bot confusing obfuscation :) - [[User:Justincc|Justincc]] 14:48, 9 April 2009 (UTC)<br />
<br />
== My Links ==<br />
<br />
[[Foundation]]<br />
<br />
== Status Page ==<br />
<br />
Hi Justin, <br />
<br />
You've deleted the the page [[Status]], however, there are 42 other pages that linked there. Many of those pages had breadcrumbs referring to the status page. So what to do with those? Where should they link to now? <br />
<br />
BTW, it's nice to know that you can delete pages. You may want to have a look at the [[:Category:To Delete|To Delete]] category, there are many pages in there that should be reviewed and deleted. <br />
<br />
--[[User:Fritigern|Fritigern]] 04:27, 22 December 2010 (UTC) <br />
<br />
:Hi Fritigern. From my brief look at it, many of the pages that the status page linked to were very out of date. The ones which aren't or have some semblence of usefulness or already linked elsewhere, I think. My intention was to come back on Friday and chase down the subsequently broken links, but I probably should have the left the page intact until then, at least (I'm too used to quickly editing the wiki because few other people are doing it!).<br />
<br />
:So I've restored the page for my now but my intention is still to come back and delete it on Friday (and chase down the broken links). But if you have any other ideas (e.g. whether it should be retained) then I'd be very pleased to discuss them.<br />
<br />
:Thanks for pointing out the "To Delete" category. I hope to get the time to go through that on Friday too.<br />
<br />
:Thanks for your editing btw - it's really nice to have someone else looking at this stuff too.<br />
<br />
:--[[User:Justincc|Justincc]] 01:10, 23 December 2010 (UTC)<br />
<br />
<br> <br />
<br />
::I think it's a very common mistake for an editor, an even for a Wiki sysop to overlook the "[[Special:WhatLinksHere/Status|What links here]]" link on a page that he/she wishes to delete. That link showed me that many osfunction pages link to [[Status]] <br />
::So what would i do about this? Hmmm... I am not sure. I would probably (because other pages depend on it in one form or another) do a complete rewrite of that page, making the info more current, though since i am basically just a "dumb end user" (tongue-in-cheek very much intended!), i wouldn't know the first thing of what the status really is. <br />
::As for my editing, it really started because i couldn't easily find the info that i needed at that time (i can't remember what it was, just that i couldn't find it&nbsp;;-)) <br />
::One thing that i really would like to see on the wiki, is more information in ''layman's terms''. A lot of the documentation was written by devs, and i know that it can often be hard for devs/coders/techs to translate their jargon to something that non-coders can understand too. <br />
::One example of an article that i find confusing is [[Wifi]], see also the discussion page of that article. Another one would be the one about [[NINJA Physics]]. <br />
::<br />
::...Which brings me to something that i hope you can find the time to look into. The wiki's search function doesn't seem to work properly. As in that i would enter "ninja" (all lower case), click "search", and expect to find the [[NINJA Physics]] article listed as one of the search results. Instead, it comes up with nothing. Even when searching for "NINJA Physics" (using the correct case), the search results remain empty. This happens with all other search terms as well. The "Go" button does work though, as long as the search term is entered with the correct case. <br />
::This search problem really is a problem, since it makes the wiki not searchable, and therefore makes it less useful for end users. OS is a complex piece of software, and it is not always 100% clear why things goes *beep* instead of *ding*, or how to do this or that...&nbsp;:-) <br />
::--[[User:Fritigern|Fritigern]] 02:24, 24 December 2010 (UTC)<br />
<br />
:::I had a look at the "[[Special:WhatLinksHere/Status|What links here]]" for the Status page and I see what you mean. As far as I can tell, pretty much everything linked off this page is out of date or unmaintained. But it's too much of a Sisyphean task for me right now to clean up all the inbound links so I'll have to leave as is. <br />
:::I went through the delete category and deleted all the pages except [[Wikistructure]]. <br />
:::I agree with you about the information, but to be honest there's very few of the developers who write any kind of documentation at all. So even getting the tech heavy stuff is quite a rarity, let alone things more understandable by the layman. <br />
:::The search on the wiki was recently updated by [[Teravus]] - it wasn't working at all before. So it might be worth leaving him a note about the current problems. He is also on IRC on and off. <br />
:::--[[User:Justincc|Justincc]] 00:29, 25 December 2010 (UTC)<br />
<br />
<br> <br />
<br />
::::Awesome! I will leave [[User:Teravus|Teravus]] a message after the holidays, or at least after Christmas&nbsp;:) <br />
::::As for the [[WikiStructure]] article, i see it contains the templates that people can use when editing the wiki. This includes the <nowiki>{{delete}}</nowiki> template, which is only there as an example. I hope to go over more articles in the new year, in order to tackle this, and other similar problems, and other confusing stuffs. <br />
::::Oh, I've started to make some changes to the [[Wifi]] text, hopefully making them easier to read for laymen, (for instance, instead of saying something like "wifi interacts with OpenSimulator's code base", i chose to have it say "wifi uses OpenSim's built-in features". It's not the exact same thing, but it is easier to understand.<br>Alright, i'm gonna make it Christmas at Fritiville, thanks for cleaning up the deletable articles, keeping the wiki clean will make everyone happy :-)<br>--[[User:Fritigern|Fritigern]] 21:48, 25 December 2010 (UTC)<br />
<br />
== Proposal against spam (having new sysop) ==<br />
<br />
I feel that we have many spam pages these days(I can't concentrate on revising and creating articles due to that). I've came up on the quick-and-dirty idea of redirecting the spam page to another page, which introduce OpenSimulator Project, but it is not the complete solution(we can't delete the pages or images, ban user nor block account creations). Actually you are busy with codes, and I don't want you to take the time to kill spams on the wiki instead of adding new features, fixing bugs and applying the patches(by me lol).<br />
<br />
I bet if [[User:Fritigern|Fritigern]] become sysop, this kind of problems will be solved quickly. He always patrols on OpenSimulator wiki, finding spams and taking the action against them quickly. Thanks<br />
<br />
-- [[User:Makopoppo|Makopoppo]] 11:19, 3 June 2011 (UTC)<br />
<br />
:Great idea, Makopoppo. In fact, I made both you and Fritigen sysops. If you don't want the bit then please tell me. [[User:Justincc|Justincc]] 20:09, 3 June 2011 (UTC)<br />
<br />
::Thanks, Justincc! I'll clean up piled spam images gradually. -- [[User:Makopoppo|Makopoppo]] 23:54, 3 June 2011 (UTC)<br />
<br />
:::Brilliant. Many, many thanks for your help - it's really appreciated. [[User:Justincc|Justincc]] 23:55, 3 June 2011 (UTC)<br />
<br />
::::Woot! Thank you so much Justin! I will do my best to be a great sysop!!! --[[User:Fritigern|Fritigern]] 21:24, 4 June 2011 (UTC)<br />
<br />
== Upgrading The Wiki ==<br />
<br />
Hi Justin.<br />
I know this kinda sounds like nagging, but i really think that the wiki could benefit from an update to the most recent release of mediawiki.The wiki is running v 1.13, but the current version is 1.17, with 1.18 just around the corner.<br />
<br />
Pros:<br />
* Better anti-spam tools<br />
* Additional CSS classes, allowing for example the hiding/showing of sections, making for cleaner looking pages.<br />
* Out-of-the-box LSL source highlighting<br />
* Fixed various vulnerabilities<br />
* Auto-completion in search box<br />
* Better WYSIWYG editor, it no longer replaces wiki markup with HTML code.<br />
* Since version 1.16, it is possible to update MediaWiki by running a web installer, making upgrading less of a hassle.<br />
<br />
Cons:<br />
* Since there's been a large gap between versions, immediate rollout would be a bad idea. I would stringly suggest a parallel database+folder containing a snapshot of the wiki, and all of its files/articles. Then testing the new version, making modifications to the wiki's skin to accomodate for the new version, as well as finding bottlenecks with changed configuation parameters, and whatever may come to light, If resources permit, i would even suggest running the two versions in parallel on the same server, making the transition from 1.13 to 1.17 less painful.<br />
* There have been changes to the database format. So database will need to be updated, which may require the wiki to be offline for that period. Versions of PHP and MySQL are still within system requirements.<br />
<br />
<br />
General:<br />
The current version of the Opensim wiki has support for SVG graphics. However, the version of ImageMagick which is currently installed on the server does not. For example, the file [[:Image:Template-info.svg]] is a valid SVG file, but does not display because ImageMagick is unfalimiar with the format and displays an error message instead.<br />
<br />
<br />
See also the release notes for [http://www.mediawiki.org/wiki/Release_notes/1.14 1.14], [http://www.mediawiki.org/wiki/Release_notes/1.15 1.15], [http://www.mediawiki.org/wiki/Release_notes/1.16 1.16] and [http://www.mediawiki.org/wiki/Release_notes/1.17 1.17] for more info on the changes and improvements between versions, as well as [http://www.mediawiki.org/wiki/Manual:Upgrading the upgrading manual].<br />
<br />
<br />
Would you please consider this? And if you lack the time, perhaps someone else will be able to do this. First person to come to mind would be Makopoppo, if she has time.<br />
<br />
--[[User:Fritigern|Fritigern]] 12:01, 3 August 2011 (UTC)<br />
<br />
: Not only do I lack the time, but any time I spend on this is almost certain time that I don't spend on fixing OpenSim, which is by far my most valuable contribution. The problem is that changing things on the server is sensitive as well. Let's keep thinking about this over the coming weeks.<br />
<br />
:: Sorry if I was a little short yesterday - I get like that when I'm tired :). If upgrading would help fight spam then do please tell me it's really important.<br />
<br />
::: Hi Fritigern. coyled upgraded mediawiki to 1.17 last night -- [[User:Justincc|Justincc]] 09:06, 20 October 2011 (PDT)<br />
<br />
:::: That's absolutely awsome. I hope this will give us some respite from the waves of spam that we've been getting. But even if it picks up again, we will have the framewirk that allows us to install the extensions that we may need to prevent the spam more effectively.<br />
:::: --[[User:Fritigern|Fritigern]] 00:31, 21 October 2011 (PDT)<br />
<br />
== Proposal for introducing some extensions ==<br />
<br />
Hi, Justin. Thank you for upgrading wiki software:) It enabled us to introduce a lot of useful extensions rather safely. Just for reference, [http://wiki.secondlife.com/wiki/Special:Version SecondLife wiki enables some other extensions] though I doubt if we need all of them. Still, I want to use following extensions soon.<br />
<br />
* [http://www.mediawiki.org/wiki/Extension:VariablesExtension Variables] - enables the syntaxes like {{#var:somevariable|somevalue}}<br />
* [http://www.mediawiki.org/wiki/Extension:DeletePagePermanently Delete Page Permanently] - removes malicious titles of spam pages from recent pages list. Only if you take regular backup of wiki<br />
<br />
Could you enable them, at least Variables extension, whenever you have time? Thanks.<br />
<br />
-- [[User:Makopoppo|Makopoppo]] 17:51, 8 January 2012 (PST)<br />
<br />
:Hi Makopoppo. Our sysadmin (Dave Coyle [coyled]) has some misgivings about enabling the delete page permanently extension, but there's no problem installing the variables one. Hope this is okay. Hoping to do this tomorrow, please poke me if I forget!<br />
<br />
:And thanks for all the work you do on the wiki!<br />
<br />
:Also, it might also be worth asking on the opensim-dev list in future, since I regard this as a dev issue. I should have put my discussion with Dave on there as well but forgot this time. However, as a great wiki worker, if you want to just message me directly then please do! -- [[User:Justincc|Justincc]] 16:12, 12 January 2012 (PST)<br />
<br />
:: Sorry, Makopoppo. Something completely unexpected popped up today and I didn't get time to do the install. I will try to do this as soon as I get an opportunity -- [[User:Justincc|Justincc]] 17:39, 13 January 2012 (PST)<br />
<br />
::: {{#vardefine:hello|Now installed. Sorry for the delay!}}<br />
::: {{#var:hello}} -- [[User:Justincc|Justincc]] 17:26, 27 January 2012 (PST)<br />
<br />
:::: Thank you, Justin! It works perfectly. I sorted some interspersed templates for release informations (version, date, urls, ...) into one template [[:Template:ReleaseInfo]]. You will probably no longer have to fix around many templates in every releasing:) -- [[User:Makopoppo|Makopoppo]] 00:11, 28 January 2012 (PST)<br />
<br />
== IAR Page ==<br />
<br />
Hi Justin, thanks for&nbsp;[http://opensimulator.org/wiki/User_talk:Fleep%7Cfor your note about quotes around the path]&nbsp;when loading an IAR file. I didn't realize quotes were only necessary if there is a space in the path - I guess my paths have always contained spaces, so it appeared to me that quotes were required. I've edited the IAR page again to clarify, let me know if that doesn't look better. Thanks again! &nbsp;:) [[User:Fleep|Fleep]] 20:14, 2 April 2012 (PDT)</div>Fleephttp://opensimulator.org/wiki/User_talk:JustinccUser talk:Justincc2012-04-03T03:15:14Z<p>Fleep: </p>
<hr />
<div>Hi Justin,<br />
Is your email really 'AT googlemail DORT com' .. or should that be ... '''DOT''' com ? :)<br />
<br />
--[[User:Mstram|Mstram]] 14:16, 9 April 2009 (UTC)<br />
<br />
:Hi Mstram. 'Tis a somewhat feeble attempt at a little extra bot confusing obfuscation :) - [[User:Justincc|Justincc]] 14:48, 9 April 2009 (UTC)<br />
<br />
== My Links ==<br />
<br />
[[Foundation]]<br />
<br />
== Status Page ==<br />
<br />
Hi Justin, <br />
<br />
You've deleted the the page [[Status]], however, there are 42 other pages that linked there. Many of those pages had breadcrumbs referring to the status page. So what to do with those? Where should they link to now? <br />
<br />
BTW, it's nice to know that you can delete pages. You may want to have a look at the [[:Category:To Delete|To Delete]] category, there are many pages in there that should be reviewed and deleted. <br />
<br />
--[[User:Fritigern|Fritigern]] 04:27, 22 December 2010 (UTC) <br />
<br />
:Hi Fritigern. From my brief look at it, many of the pages that the status page linked to were very out of date. The ones which aren't or have some semblence of usefulness or already linked elsewhere, I think. My intention was to come back on Friday and chase down the subsequently broken links, but I probably should have the left the page intact until then, at least (I'm too used to quickly editing the wiki because few other people are doing it!).<br />
<br />
:So I've restored the page for my now but my intention is still to come back and delete it on Friday (and chase down the broken links). But if you have any other ideas (e.g. whether it should be retained) then I'd be very pleased to discuss them.<br />
<br />
:Thanks for pointing out the "To Delete" category. I hope to get the time to go through that on Friday too.<br />
<br />
:Thanks for your editing btw - it's really nice to have someone else looking at this stuff too.<br />
<br />
:--[[User:Justincc|Justincc]] 01:10, 23 December 2010 (UTC)<br />
<br />
<br> <br />
<br />
::I think it's a very common mistake for an editor, an even for a Wiki sysop to overlook the "[[Special:WhatLinksHere/Status|What links here]]" link on a page that he/she wishes to delete. That link showed me that many osfunction pages link to [[Status]] <br />
::So what would i do about this? Hmmm... I am not sure. I would probably (because other pages depend on it in one form or another) do a complete rewrite of that page, making the info more current, though since i am basically just a "dumb end user" (tongue-in-cheek very much intended!), i wouldn't know the first thing of what the status really is. <br />
::As for my editing, it really started because i couldn't easily find the info that i needed at that time (i can't remember what it was, just that i couldn't find it&nbsp;;-)) <br />
::One thing that i really would like to see on the wiki, is more information in ''layman's terms''. A lot of the documentation was written by devs, and i know that it can often be hard for devs/coders/techs to translate their jargon to something that non-coders can understand too. <br />
::One example of an article that i find confusing is [[Wifi]], see also the discussion page of that article. Another one would be the one about [[NINJA Physics]]. <br />
::<br />
::...Which brings me to something that i hope you can find the time to look into. The wiki's search function doesn't seem to work properly. As in that i would enter "ninja" (all lower case), click "search", and expect to find the [[NINJA Physics]] article listed as one of the search results. Instead, it comes up with nothing. Even when searching for "NINJA Physics" (using the correct case), the search results remain empty. This happens with all other search terms as well. The "Go" button does work though, as long as the search term is entered with the correct case. <br />
::This search problem really is a problem, since it makes the wiki not searchable, and therefore makes it less useful for end users. OS is a complex piece of software, and it is not always 100% clear why things goes *beep* instead of *ding*, or how to do this or that...&nbsp;:-) <br />
::--[[User:Fritigern|Fritigern]] 02:24, 24 December 2010 (UTC)<br />
<br />
:::I had a look at the "[[Special:WhatLinksHere/Status|What links here]]" for the Status page and I see what you mean. As far as I can tell, pretty much everything linked off this page is out of date or unmaintained. But it's too much of a Sisyphean task for me right now to clean up all the inbound links so I'll have to leave as is. <br />
:::I went through the delete category and deleted all the pages except [[Wikistructure]]. <br />
:::I agree with you about the information, but to be honest there's very few of the developers who write any kind of documentation at all. So even getting the tech heavy stuff is quite a rarity, let alone things more understandable by the layman. <br />
:::The search on the wiki was recently updated by [[Teravus]] - it wasn't working at all before. So it might be worth leaving him a note about the current problems. He is also on IRC on and off. <br />
:::--[[User:Justincc|Justincc]] 00:29, 25 December 2010 (UTC)<br />
<br />
<br> <br />
<br />
::::Awesome! I will leave [[User:Teravus|Teravus]] a message after the holidays, or at least after Christmas&nbsp;:) <br />
::::As for the [[WikiStructure]] article, i see it contains the templates that people can use when editing the wiki. This includes the <nowiki>{{delete}}</nowiki> template, which is only there as an example. I hope to go over more articles in the new year, in order to tackle this, and other similar problems, and other confusing stuffs. <br />
::::Oh, I've started to make some changes to the [[Wifi]] text, hopefully making them easier to read for laymen, (for instance, instead of saying something like "wifi interacts with OpenSimulator's code base", i chose to have it say "wifi uses OpenSim's built-in features". It's not the exact same thing, but it is easier to understand.<br>Alright, i'm gonna make it Christmas at Fritiville, thanks for cleaning up the deletable articles, keeping the wiki clean will make everyone happy :-)<br>--[[User:Fritigern|Fritigern]] 21:48, 25 December 2010 (UTC)<br />
<br />
== Proposal against spam (having new sysop) ==<br />
<br />
I feel that we have many spam pages these days(I can't concentrate on revising and creating articles due to that). I've came up on the quick-and-dirty idea of redirecting the spam page to another page, which introduce OpenSimulator Project, but it is not the complete solution(we can't delete the pages or images, ban user nor block account creations). Actually you are busy with codes, and I don't want you to take the time to kill spams on the wiki instead of adding new features, fixing bugs and applying the patches(by me lol).<br />
<br />
I bet if [[User:Fritigern|Fritigern]] become sysop, this kind of problems will be solved quickly. He always patrols on OpenSimulator wiki, finding spams and taking the action against them quickly. Thanks<br />
<br />
-- [[User:Makopoppo|Makopoppo]] 11:19, 3 June 2011 (UTC)<br />
<br />
:Great idea, Makopoppo. In fact, I made both you and Fritigen sysops. If you don't want the bit then please tell me. [[User:Justincc|Justincc]] 20:09, 3 June 2011 (UTC)<br />
<br />
::Thanks, Justincc! I'll clean up piled spam images gradually. -- [[User:Makopoppo|Makopoppo]] 23:54, 3 June 2011 (UTC)<br />
<br />
:::Brilliant. Many, many thanks for your help - it's really appreciated. [[User:Justincc|Justincc]] 23:55, 3 June 2011 (UTC)<br />
<br />
::::Woot! Thank you so much Justin! I will do my best to be a great sysop!!! --[[User:Fritigern|Fritigern]] 21:24, 4 June 2011 (UTC)<br />
<br />
== Upgrading The Wiki ==<br />
<br />
Hi Justin.<br />
I know this kinda sounds like nagging, but i really think that the wiki could benefit from an update to the most recent release of mediawiki.The wiki is running v 1.13, but the current version is 1.17, with 1.18 just around the corner.<br />
<br />
Pros:<br />
* Better anti-spam tools<br />
* Additional CSS classes, allowing for example the hiding/showing of sections, making for cleaner looking pages.<br />
* Out-of-the-box LSL source highlighting<br />
* Fixed various vulnerabilities<br />
* Auto-completion in search box<br />
* Better WYSIWYG editor, it no longer replaces wiki markup with HTML code.<br />
* Since version 1.16, it is possible to update MediaWiki by running a web installer, making upgrading less of a hassle.<br />
<br />
Cons:<br />
* Since there's been a large gap between versions, immediate rollout would be a bad idea. I would stringly suggest a parallel database+folder containing a snapshot of the wiki, and all of its files/articles. Then testing the new version, making modifications to the wiki's skin to accomodate for the new version, as well as finding bottlenecks with changed configuation parameters, and whatever may come to light, If resources permit, i would even suggest running the two versions in parallel on the same server, making the transition from 1.13 to 1.17 less painful.<br />
* There have been changes to the database format. So database will need to be updated, which may require the wiki to be offline for that period. Versions of PHP and MySQL are still within system requirements.<br />
<br />
<br />
General:<br />
The current version of the Opensim wiki has support for SVG graphics. However, the version of ImageMagick which is currently installed on the server does not. For example, the file [[:Image:Template-info.svg]] is a valid SVG file, but does not display because ImageMagick is unfalimiar with the format and displays an error message instead.<br />
<br />
<br />
See also the release notes for [http://www.mediawiki.org/wiki/Release_notes/1.14 1.14], [http://www.mediawiki.org/wiki/Release_notes/1.15 1.15], [http://www.mediawiki.org/wiki/Release_notes/1.16 1.16] and [http://www.mediawiki.org/wiki/Release_notes/1.17 1.17] for more info on the changes and improvements between versions, as well as [http://www.mediawiki.org/wiki/Manual:Upgrading the upgrading manual].<br />
<br />
<br />
Would you please consider this? And if you lack the time, perhaps someone else will be able to do this. First person to come to mind would be Makopoppo, if she has time.<br />
<br />
--[[User:Fritigern|Fritigern]] 12:01, 3 August 2011 (UTC)<br />
<br />
: Not only do I lack the time, but any time I spend on this is almost certain time that I don't spend on fixing OpenSim, which is by far my most valuable contribution. The problem is that changing things on the server is sensitive as well. Let's keep thinking about this over the coming weeks.<br />
<br />
:: Sorry if I was a little short yesterday - I get like that when I'm tired :). If upgrading would help fight spam then do please tell me it's really important.<br />
<br />
::: Hi Fritigern. coyled upgraded mediawiki to 1.17 last night -- [[User:Justincc|Justincc]] 09:06, 20 October 2011 (PDT)<br />
<br />
:::: That's absolutely awsome. I hope this will give us some respite from the waves of spam that we've been getting. But even if it picks up again, we will have the framewirk that allows us to install the extensions that we may need to prevent the spam more effectively.<br />
:::: --[[User:Fritigern|Fritigern]] 00:31, 21 October 2011 (PDT)<br />
<br />
== Proposal for introducing some extensions ==<br />
<br />
Hi, Justin. Thank you for upgrading wiki software:) It enabled us to introduce a lot of useful extensions rather safely. Just for reference, [http://wiki.secondlife.com/wiki/Special:Version SecondLife wiki enables some other extensions] though I doubt if we need all of them. Still, I want to use following extensions soon.<br />
<br />
* [http://www.mediawiki.org/wiki/Extension:VariablesExtension Variables] - enables the syntaxes like {{#var:somevariable|somevalue}}<br />
* [http://www.mediawiki.org/wiki/Extension:DeletePagePermanently Delete Page Permanently] - removes malicious titles of spam pages from recent pages list. Only if you take regular backup of wiki<br />
<br />
Could you enable them, at least Variables extension, whenever you have time? Thanks.<br />
<br />
-- [[User:Makopoppo|Makopoppo]] 17:51, 8 January 2012 (PST)<br />
<br />
:Hi Makopoppo. Our sysadmin (Dave Coyle [coyled]) has some misgivings about enabling the delete page permanently extension, but there's no problem installing the variables one. Hope this is okay. Hoping to do this tomorrow, please poke me if I forget!<br />
<br />
:And thanks for all the work you do on the wiki!<br />
<br />
:Also, it might also be worth asking on the opensim-dev list in future, since I regard this as a dev issue. I should have put my discussion with Dave on there as well but forgot this time. However, as a great wiki worker, if you want to just message me directly then please do! -- [[User:Justincc|Justincc]] 16:12, 12 January 2012 (PST)<br />
<br />
:: Sorry, Makopoppo. Something completely unexpected popped up today and I didn't get time to do the install. I will try to do this as soon as I get an opportunity -- [[User:Justincc|Justincc]] 17:39, 13 January 2012 (PST)<br />
<br />
::: {{#vardefine:hello|Now installed. Sorry for the delay!}}<br />
::: {{#var:hello}} -- [[User:Justincc|Justincc]] 17:26, 27 January 2012 (PST)<br />
<br />
:::: Thank you, Justin! It works perfectly. I sorted some interspersed templates for release informations (version, date, urls, ...) into one template [[:Template:ReleaseInfo]]. You will probably no longer have to fix around many templates in every releasing:) -- [[User:Makopoppo|Makopoppo]] 00:11, 28 January 2012 (PST)<br />
<br />
== IAR Page ==<br />
<br />
Hi Justin, thanks [http://opensimulator.org/wiki/User_talk:Fleep%7Cfor your note about quotes around the path]&nbsp;when loading an IAR file. I didn't realize quotes were only necessary if there is a space in the path - I guess my paths have always contained spaces, so it appeared to me that quotes were required. I've edited the IAR page again to clarify, let me know if that doesn't look better. Thanks again! &nbsp;:) [[User:Fleep|Fleep]] 20:14, 2 April 2012 (PDT)</div>Fleephttp://opensimulator.org/wiki/User_talk:JustinccUser talk:Justincc2012-04-03T03:14:53Z<p>Fleep: </p>
<hr />
<div>Hi Justin,<br />
Is your email really 'AT googlemail DORT com' .. or should that be ... '''DOT''' com ? :)<br />
<br />
--[[User:Mstram|Mstram]] 14:16, 9 April 2009 (UTC)<br />
<br />
:Hi Mstram. 'Tis a somewhat feeble attempt at a little extra bot confusing obfuscation :) - [[User:Justincc|Justincc]] 14:48, 9 April 2009 (UTC)<br />
<br />
== My Links ==<br />
<br />
[[Foundation]]<br />
<br />
== Status Page ==<br />
<br />
Hi Justin, <br />
<br />
You've deleted the the page [[Status]], however, there are 42 other pages that linked there. Many of those pages had breadcrumbs referring to the status page. So what to do with those? Where should they link to now? <br />
<br />
BTW, it's nice to know that you can delete pages. You may want to have a look at the [[:Category:To Delete|To Delete]] category, there are many pages in there that should be reviewed and deleted. <br />
<br />
--[[User:Fritigern|Fritigern]] 04:27, 22 December 2010 (UTC) <br />
<br />
:Hi Fritigern. From my brief look at it, many of the pages that the status page linked to were very out of date. The ones which aren't or have some semblence of usefulness or already linked elsewhere, I think. My intention was to come back on Friday and chase down the subsequently broken links, but I probably should have the left the page intact until then, at least (I'm too used to quickly editing the wiki because few other people are doing it!).<br />
<br />
:So I've restored the page for my now but my intention is still to come back and delete it on Friday (and chase down the broken links). But if you have any other ideas (e.g. whether it should be retained) then I'd be very pleased to discuss them.<br />
<br />
:Thanks for pointing out the "To Delete" category. I hope to get the time to go through that on Friday too.<br />
<br />
:Thanks for your editing btw - it's really nice to have someone else looking at this stuff too.<br />
<br />
:--[[User:Justincc|Justincc]] 01:10, 23 December 2010 (UTC)<br />
<br />
<br> <br />
<br />
::I think it's a very common mistake for an editor, an even for a Wiki sysop to overlook the "[[Special:WhatLinksHere/Status|What links here]]" link on a page that he/she wishes to delete. That link showed me that many osfunction pages link to [[Status]] <br />
::So what would i do about this? Hmmm... I am not sure. I would probably (because other pages depend on it in one form or another) do a complete rewrite of that page, making the info more current, though since i am basically just a "dumb end user" (tongue-in-cheek very much intended!), i wouldn't know the first thing of what the status really is. <br />
::As for my editing, it really started because i couldn't easily find the info that i needed at that time (i can't remember what it was, just that i couldn't find it&nbsp;;-)) <br />
::One thing that i really would like to see on the wiki, is more information in ''layman's terms''. A lot of the documentation was written by devs, and i know that it can often be hard for devs/coders/techs to translate their jargon to something that non-coders can understand too. <br />
::One example of an article that i find confusing is [[Wifi]], see also the discussion page of that article. Another one would be the one about [[NINJA Physics]]. <br />
::<br />
::...Which brings me to something that i hope you can find the time to look into. The wiki's search function doesn't seem to work properly. As in that i would enter "ninja" (all lower case), click "search", and expect to find the [[NINJA Physics]] article listed as one of the search results. Instead, it comes up with nothing. Even when searching for "NINJA Physics" (using the correct case), the search results remain empty. This happens with all other search terms as well. The "Go" button does work though, as long as the search term is entered with the correct case. <br />
::This search problem really is a problem, since it makes the wiki not searchable, and therefore makes it less useful for end users. OS is a complex piece of software, and it is not always 100% clear why things goes *beep* instead of *ding*, or how to do this or that...&nbsp;:-) <br />
::--[[User:Fritigern|Fritigern]] 02:24, 24 December 2010 (UTC)<br />
<br />
:::I had a look at the "[[Special:WhatLinksHere/Status|What links here]]" for the Status page and I see what you mean. As far as I can tell, pretty much everything linked off this page is out of date or unmaintained. But it's too much of a Sisyphean task for me right now to clean up all the inbound links so I'll have to leave as is. <br />
:::I went through the delete category and deleted all the pages except [[Wikistructure]]. <br />
:::I agree with you about the information, but to be honest there's very few of the developers who write any kind of documentation at all. So even getting the tech heavy stuff is quite a rarity, let alone things more understandable by the layman. <br />
:::The search on the wiki was recently updated by [[Teravus]] - it wasn't working at all before. So it might be worth leaving him a note about the current problems. He is also on IRC on and off. <br />
:::--[[User:Justincc|Justincc]] 00:29, 25 December 2010 (UTC)<br />
<br />
<br> <br />
<br />
::::Awesome! I will leave [[User:Teravus|Teravus]] a message after the holidays, or at least after Christmas&nbsp;:) <br />
::::As for the [[WikiStructure]] article, i see it contains the templates that people can use when editing the wiki. This includes the <nowiki>{{delete}}</nowiki> template, which is only there as an example. I hope to go over more articles in the new year, in order to tackle this, and other similar problems, and other confusing stuffs. <br />
::::Oh, I've started to make some changes to the [[Wifi]] text, hopefully making them easier to read for laymen, (for instance, instead of saying something like "wifi interacts with OpenSimulator's code base", i chose to have it say "wifi uses OpenSim's built-in features". It's not the exact same thing, but it is easier to understand.<br>Alright, i'm gonna make it Christmas at Fritiville, thanks for cleaning up the deletable articles, keeping the wiki clean will make everyone happy :-)<br>--[[User:Fritigern|Fritigern]] 21:48, 25 December 2010 (UTC)<br />
<br />
== Proposal against spam (having new sysop) ==<br />
<br />
I feel that we have many spam pages these days(I can't concentrate on revising and creating articles due to that). I've came up on the quick-and-dirty idea of redirecting the spam page to another page, which introduce OpenSimulator Project, but it is not the complete solution(we can't delete the pages or images, ban user nor block account creations). Actually you are busy with codes, and I don't want you to take the time to kill spams on the wiki instead of adding new features, fixing bugs and applying the patches(by me lol).<br />
<br />
I bet if [[User:Fritigern|Fritigern]] become sysop, this kind of problems will be solved quickly. He always patrols on OpenSimulator wiki, finding spams and taking the action against them quickly. Thanks<br />
<br />
-- [[User:Makopoppo|Makopoppo]] 11:19, 3 June 2011 (UTC)<br />
<br />
:Great idea, Makopoppo. In fact, I made both you and Fritigen sysops. If you don't want the bit then please tell me. [[User:Justincc|Justincc]] 20:09, 3 June 2011 (UTC)<br />
<br />
::Thanks, Justincc! I'll clean up piled spam images gradually. -- [[User:Makopoppo|Makopoppo]] 23:54, 3 June 2011 (UTC)<br />
<br />
:::Brilliant. Many, many thanks for your help - it's really appreciated. [[User:Justincc|Justincc]] 23:55, 3 June 2011 (UTC)<br />
<br />
::::Woot! Thank you so much Justin! I will do my best to be a great sysop!!! --[[User:Fritigern|Fritigern]] 21:24, 4 June 2011 (UTC)<br />
<br />
== Upgrading The Wiki ==<br />
<br />
Hi Justin.<br />
I know this kinda sounds like nagging, but i really think that the wiki could benefit from an update to the most recent release of mediawiki.The wiki is running v 1.13, but the current version is 1.17, with 1.18 just around the corner.<br />
<br />
Pros:<br />
* Better anti-spam tools<br />
* Additional CSS classes, allowing for example the hiding/showing of sections, making for cleaner looking pages.<br />
* Out-of-the-box LSL source highlighting<br />
* Fixed various vulnerabilities<br />
* Auto-completion in search box<br />
* Better WYSIWYG editor, it no longer replaces wiki markup with HTML code.<br />
* Since version 1.16, it is possible to update MediaWiki by running a web installer, making upgrading less of a hassle.<br />
<br />
Cons:<br />
* Since there's been a large gap between versions, immediate rollout would be a bad idea. I would stringly suggest a parallel database+folder containing a snapshot of the wiki, and all of its files/articles. Then testing the new version, making modifications to the wiki's skin to accomodate for the new version, as well as finding bottlenecks with changed configuation parameters, and whatever may come to light, If resources permit, i would even suggest running the two versions in parallel on the same server, making the transition from 1.13 to 1.17 less painful.<br />
* There have been changes to the database format. So database will need to be updated, which may require the wiki to be offline for that period. Versions of PHP and MySQL are still within system requirements.<br />
<br />
<br />
General:<br />
The current version of the Opensim wiki has support for SVG graphics. However, the version of ImageMagick which is currently installed on the server does not. For example, the file [[:Image:Template-info.svg]] is a valid SVG file, but does not display because ImageMagick is unfalimiar with the format and displays an error message instead.<br />
<br />
<br />
See also the release notes for [http://www.mediawiki.org/wiki/Release_notes/1.14 1.14], [http://www.mediawiki.org/wiki/Release_notes/1.15 1.15], [http://www.mediawiki.org/wiki/Release_notes/1.16 1.16] and [http://www.mediawiki.org/wiki/Release_notes/1.17 1.17] for more info on the changes and improvements between versions, as well as [http://www.mediawiki.org/wiki/Manual:Upgrading the upgrading manual].<br />
<br />
<br />
Would you please consider this? And if you lack the time, perhaps someone else will be able to do this. First person to come to mind would be Makopoppo, if she has time.<br />
<br />
--[[User:Fritigern|Fritigern]] 12:01, 3 August 2011 (UTC)<br />
<br />
: Not only do I lack the time, but any time I spend on this is almost certain time that I don't spend on fixing OpenSim, which is by far my most valuable contribution. The problem is that changing things on the server is sensitive as well. Let's keep thinking about this over the coming weeks.<br />
<br />
:: Sorry if I was a little short yesterday - I get like that when I'm tired :). If upgrading would help fight spam then do please tell me it's really important.<br />
<br />
::: Hi Fritigern. coyled upgraded mediawiki to 1.17 last night -- [[User:Justincc|Justincc]] 09:06, 20 October 2011 (PDT)<br />
<br />
:::: That's absolutely awsome. I hope this will give us some respite from the waves of spam that we've been getting. But even if it picks up again, we will have the framewirk that allows us to install the extensions that we may need to prevent the spam more effectively.<br />
:::: --[[User:Fritigern|Fritigern]] 00:31, 21 October 2011 (PDT)<br />
<br />
== Proposal for introducing some extensions ==<br />
<br />
Hi, Justin. Thank you for upgrading wiki software:) It enabled us to introduce a lot of useful extensions rather safely. Just for reference, [http://wiki.secondlife.com/wiki/Special:Version SecondLife wiki enables some other extensions] though I doubt if we need all of them. Still, I want to use following extensions soon.<br />
<br />
* [http://www.mediawiki.org/wiki/Extension:VariablesExtension Variables] - enables the syntaxes like {{#var:somevariable|somevalue}}<br />
* [http://www.mediawiki.org/wiki/Extension:DeletePagePermanently Delete Page Permanently] - removes malicious titles of spam pages from recent pages list. Only if you take regular backup of wiki<br />
<br />
Could you enable them, at least Variables extension, whenever you have time? Thanks.<br />
<br />
-- [[User:Makopoppo|Makopoppo]] 17:51, 8 January 2012 (PST)<br />
<br />
:Hi Makopoppo. Our sysadmin (Dave Coyle [coyled]) has some misgivings about enabling the delete page permanently extension, but there's no problem installing the variables one. Hope this is okay. Hoping to do this tomorrow, please poke me if I forget!<br />
<br />
:And thanks for all the work you do on the wiki!<br />
<br />
:Also, it might also be worth asking on the opensim-dev list in future, since I regard this as a dev issue. I should have put my discussion with Dave on there as well but forgot this time. However, as a great wiki worker, if you want to just message me directly then please do! -- [[User:Justincc|Justincc]] 16:12, 12 January 2012 (PST)<br />
<br />
:: Sorry, Makopoppo. Something completely unexpected popped up today and I didn't get time to do the install. I will try to do this as soon as I get an opportunity -- [[User:Justincc|Justincc]] 17:39, 13 January 2012 (PST)<br />
<br />
::: {{#vardefine:hello|Now installed. Sorry for the delay!}}<br />
::: {{#var:hello}} -- [[User:Justincc|Justincc]] 17:26, 27 January 2012 (PST)<br />
<br />
:::: Thank you, Justin! It works perfectly. I sorted some interspersed templates for release informations (version, date, urls, ...) into one template [[:Template:ReleaseInfo]]. You will probably no longer have to fix around many templates in every releasing:) -- [[User:Makopoppo|Makopoppo]] 00:11, 28 January 2012 (PST)<br />
<br />
== IAR Page ==<br />
Hi Justin, thanks [[http://opensimulator.org/wiki/User_talk:Fleep|for your note about quotes around the path]] when loading an IAR file. I didn't realize quotes were only necessary if there is a space in the path - I guess my paths have always contained spaces, so it appeared to me that quotes were required. I've edited the IAR page again to clarify, let me know if that doesn't look better. Thanks again! :) [[User:Fleep|Fleep]] 20:14, 2 April 2012 (PDT)</div>Fleephttp://opensimulator.org/wiki/Inventory_ArchivesInventory Archives2012-04-03T03:13:47Z<p>Fleep: /* Examples */ - Clarifying that quotes are only necessary if there are spaces in the path</p>
<hr />
<div>{{Quicklinks}}<br />
<br /><br />
<br />
= Introduction =<br />
<br />
OpenSimulator Inventory Archives (IARs) are a means by which inventory folders and items can be saved offline to a single file (an IAR). This file can then be loaded into a different OpenSimulator installation.<br />
<br />
Like [[OpenSim Archives]], IARs save all the necessary asset data required to fully restore the items including textures, sounds, scripts and objects contained in the inventory of other objects.<br />
<br />
IARs have been enabled in OpenSimulator since Git revision 5a64ca (OpenSimulator 0.6.7 and later).<br />
<br />
= Usage =<br />
<br />
IARs are saved and loaded from the region console.<br />
<br />
== save iar ==<br />
<br />
The command to save an IAR on the region console is<br />
<br />
save iar [-h|--home=<url>] [-v|--verbose] [--noassets] <user-name> <path> <password> [<filename>]<br />
<br />
where <br />
<br />
* <user-name> is the name of the user to save inventory from<br />
<br />
* <path> is the path to an inventory item or folder. If the path is for a folder, that folder and all its contents (both descendant folders and items) are saved. If the path is for an item, then only that item is saved. <br />
<br />
Components of the path are separated by a forward slash ("/"). If you need to specify a path with spaces, you can surround the whole thing with double quotation marks (e.g. "Folder A/Folder B"). <br />
<br />
You can specify that the contents of a folder should be saved rather than the folder itself using the * wildcard. For instance, "/*" will save your entire inventory but not the "My Inventory" folder itself. This can be useful if you want to restore a saved inventory to an existing one using the load iar --merge function discussed later on.<br />
<br />
If a name or folder contains a forward slash ("/") then it can be escaped with the backslash (i.e. "\/") to stop it being seen as a path separator. Back slashes themselves need to be escaped with another backslash (i.e. "\\").<br />
<br />
One further issue here is that it's not possible to distinguish between identically named folders or items on the path - the workaround is to rename your items/folders if you need to specify them in the path :)<br />
<br />
* <password> is the password of the user.<br />
<br />
* <filename> is an optional filename for the IAR. If none is supplied, then the filename user-inventory.iar is used in the current directory. I recommend that iars have the .iar extension.<br />
<br />
=== Switches ===<br />
<br />
* If the --noassets option is specified, then the archive will be saved without assets. This can be handy if you're backing up the asset database separately and don't want the expense of including all the assets in each archive.<br />
* --home=<url> is the URL of this world's profile service. It is not required that the profile service is operational; the information will be saved, and it will be displayed wherever the archive will be loaded. NOTE: the older --profile option (the previous name of this switch) produced IARs that are not compatible with OpenSimulator 0.7.0.2 and earlier; do not use this option if you want to produce a compatible IAR.<br />
* --verbose prints out versbose saving messages<br />
<br />
=== Examples ===<br />
<br />
Here's an example. Suppose you have an inventory structure like this<br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| <br />
+-- FolderB<br />
| |<br />
| +-- ItemX<br />
|<br />
+-- ItemY<br />
<br />
If you type <br />
<br />
save iar John Doe FolderA PASSWORD my-items.iar<br />
<br />
then FolderA and everything in FolderA (FolderB, ItemX and ItemY) will be saved into an IAR called my-items.iar. On the other hand, if you type<br />
<br />
save iar John Doe FolderA/FolderB/ItemX PASSWORD my-items.iar<br />
<br />
then only ItemX will be saved.<br />
<br />
With save iar you can save your entire inventory as well as the contents of particular folders or individual items.<br />
<br />
For instance, typing<br />
<br />
save iar John Doe / password<br />
<br />
would save your entire inventory to user-inventory.iar (since no filename was given).<br />
<br />
== load iar ==<br />
<br />
An IAR can be reloaded to an OpenSimulator instance with the load iar command<br />
<br />
load iar [-m|--merge] <user-name> <path> <password> [<filename>]<br />
<br />
where<br />
<br />
* <user name> is the name of the user to whom to load the inventory<br />
<br />
* <path> is the path to which the IAR should be loaded. This has to be a folder which already exists in "My Inventory". See the save iar command for more details.<br />
<br />
* <password> is the password of the user.<br />
<br />
* [<filename>] is an optional filename for the IAR. If none is specified, then the filename is assumed to be user-inventory.iar in the current directory.<br />
<br />
=== Switches ===<br />
<br />
* If the --merge option is given, then IAR items are loaded into the existing folder structure where possible, instead of always creating new folders.<br />
<br />
=== Examples ===<br />
<br />
Suppose that "David Hume" has recieved the my-items.iar saved above containing FolderA, FolderB, ItemX and ItemY. David Hume already has an inventory structure like this. <br />
<br />
My Inventory<br />
|<br />
+-- Folder1<br />
| <br />
+-- Folder2<br />
| <br />
+-- Folder3<br />
<br />
David wants to load the IAR to Folder3, so on the region console he executes <br />
<br />
load iar David Hume Folder1/Folder3 password my-items.iar<br />
<br />
After a little while he ends up with the folder structure <br />
<br />
My Inventory<br />
|<br />
+-- Folder1<br />
| <br />
+-- Folder2<br />
|<br />
+-- Folder3 <br />
|<br />
+-- FolderA<br />
| <br />
+-- FolderB<br />
| |<br />
| +-- ItemX<br />
|<br />
+-- ItemY<br />
<br />
where ItemX and ItemY are ready for rezzing. <br />
<br />
Note that if there is a space in the path to the item, for example if David's folder was named "Folder 1" instead of "Folder1", then quotes around the path are necessary on the command line:<br />
<br />
load iar David Hume "Folder 1/Folder3" password my-items.iar<br />
<br />
<br><br />
<br />
From OpenSimulator 0.7 and onwards, you can also load IARs directly from web addresses. For example <br />
<br />
load iar Betrand Russell Folder2 PASSWORD http://justincc.org/downloads/iars/my-great-items.iar<br />
<br />
will load my-great-items.iar from the web into Folder2 of the user "Bertrand Russell". <br />
<br />
==== Examples ====<br />
<br />
Let's suppose that a user called Albert Camus has an existing inventory structure <br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| |<br />
| +-- Item1<br />
|<br />
+-- FolderC<br />
|<br />
+-- Item2<br />
<br />
and we execute <br />
<br />
load iar --merge Albert Camus / PASSWORD my-items.iar<br />
<br />
with the IAR saved above. Instead of creating a duplicate FolderA, this will instead result in the inventory structure <br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| |<br />
| +-- FolderB<br />
| | |<br />
| | +-- ItemX<br />
| |<br />
| +-- Item1<br />
| |<br />
| +-- ItemY<br />
|<br />
+-- FolderC<br />
|<br />
+-- Item2<br />
<br />
The --merge option is useful if you are restoring a saved inventory to a new user account, since the base folders (Gestures, Landmarks, Objects, etc.) will not be duplicated.<br />
<br />
= IAR files =<br />
<br />
* http://justincc.org/downloads/iars/my-great-items.iar - justincc's initial example IAR.<br />
* http://www.aviefactory.com/Gene_Jacobs_Clothes.iar - Gene Jacobs Men's Clothing Collection (Original Creator)<br />
* http://www.aviefactory.com/Genes_Female_Stuff.iar - Female Skins and Shapes (Found off the web)<br />
* http://www.gridhop.net/IAR/lightshare.iar - [[User:Thomax|txOh]]'s LightShare controller. Useful only if you have [[LightShare]] enabled in OpenSim.ini.<br />
<br />
Please feel free to place links to other IARs here.<br />
<br />
= Further Information =<br />
<br />
[http://justincc.org/blog/category/iars/ http://justincc.org/blog/category/iars/] - articles by justincc on IARs, including tutorials, background information and possible future developments.<br />
<br />
[http://www.metaverseink.com/blog/?p=29 The OpenSimulator Library just got more interesting] - Diva Canto's article on how to extend the OpenSimulator Library using IARs.<br />
<br />
= Use cases =<br />
<br />
Possible uses<br />
<br />
1. To distribute content to other OpenSimulator installations without need to transfer entire regions. One drawback with IARs for this use case is that creator names are not preserved unless the user has a profile on the target installation. One workaround is to include a notecard detailing the creator and license conditions of the content.<br />
<br />
2. To backup a user's inventory. IARs are currently not that great for this. One can backup an entire inventory by giving a path of "/" to the save iar command. But a load IAR of the same will mean a duplicate set of root child 'standard' folders (Objects, Textures, Clothing, etc.). The loaded folders will not have any type icons.<br />
<br />
== Current limitations ==<br />
<br />
* IAR loading and saving is currently done on a single thread. This may lock up the console for a while with very large IARs. This should be addressed in the future<br />
<br />
* Creator names are not preserved unless the profile exists on the target system. This problem may be addressed in the future.<br />
<br />
== IAR Format ==<br />
<br />
The OpenSimulator [[Inventory Archives|Inventory Archive (IAR)]] format is designed with three aims in mind:<br />
<br />
# Make it easy for people to read and update individual items, assets, etc. within an archive.<br />
# Make it easy to compose two inventory archives into a single inventory archive.<br />
# Make it easy to compose archives from scratch.<br />
<br />
Therefore, all the different entities (assets, items, etc.) are packaged in individual files (e.g. one for each asset) with human readable filenames and machine readable extensions (e.g. .jp2 for textures, .txt for notecards).<br />
* [[IAR Format 0.1]]<br />
* [[IAR Format 0.2]]<br />
* [[IAR Format 0.3]]<br />
<br />
= FAQ =<br />
<br />
Nothing yet.<br />
<br />
= Bugs =<br />
<br />
Please search the OpenSimulator Mantis for information on current IAR bugs. <br />
<br />
FEB.23.2010: <br />
<br />
There is a slight "quirk"&nbsp;with MySql in regards to Max_Allowed_Packet size, which the default is 1 Megabyte.&nbsp; This is too small for some of the larger data blobs being stored.&nbsp; It is recomended to increase the default value to 16 Megabytes. <br />
<br />
Locate your MY.ini for MySql (EXAMPLE, in Windows it is located @ "C:\Program Files\MySQL\MySQL Server 5.1")&nbsp; Modify this file to include the following under the mysqld section: <br />
<br />
'''[mysqld]''' <br />
<br />
# The TCP/IP Port the MySQL Server will listen on<br />port=3306<br />max_allowed_packet = 16M<br />
<br />
'''Additional Reference''':&nbsp; [http://dev.mysql.com/doc/refman/5.1/en/packet-too-large.html dev.mysql.com/doc/refman/5.1/en/packet-too-large.html]<br />
<br />
= Current Status =<br />
<br />
Operational but experimental. Bug reports are appreciated and there will almost certainly be quite a few right now. Suggestions for improvement are also welcome. The best place for these right now might be [http://justincc.org/blog/2009/09/14/introducing-opensim-inventory-archives-iars/ my blog post on IARs], since I'm bound to see them then.<br />
<br />
Though we will strive to maintain compatibilty for old archives with newer OpenSimulator versions, please do not rely on these archives as your only backup for inventory.<br />
<br />
= See Also =<br />
<br />
* [[OpenSim Archives|How to use OpenSimulator Archives (OAR)]]<br />
<br />
[[Category:Users]]<br />
[[Category:Support]]<br />
[[Category:Tech Reference]]<br />
[[Category:Help]]<br />
[[Category:Configuration]]<br />
[[Category:Getting Started]]<br />
[[Category:Development]]</div>Fleephttp://opensimulator.org/wiki/Inventory_ArchivesInventory Archives2012-03-31T23:11:42Z<p>Fleep: /* Examples */ - IAR loads require quotes around path, added quotes to example</p>
<hr />
<div>{{Quicklinks}}<br />
<br /><br />
<br />
= Introduction =<br />
<br />
OpenSimulator Inventory Archives (IARs) are a means by which inventory folders and items can be saved offline to a single file (an IAR). This file can then be loaded into a different OpenSimulator installation.<br />
<br />
Like [[OpenSim Archives]], IARs save all the necessary asset data required to fully restore the items including textures, sounds, scripts and objects contained in the inventory of other objects.<br />
<br />
IARs have been enabled in OpenSimulator since Git revision 5a64ca (OpenSimulator 0.6.7 and later).<br />
<br />
= Usage =<br />
<br />
IARs are saved and loaded from the region console.<br />
<br />
== save iar ==<br />
<br />
The command to save an IAR on the region console is<br />
<br />
save iar [-h|--home=<url>] [-v|--verbose] [--noassets] <user-name> <path> <password> [<filename>]<br />
<br />
where <br />
<br />
* <user-name> is the name of the user to save inventory from<br />
<br />
* <path> is the path to an inventory item or folder. If the path is for a folder, that folder and all its contents (both descendant folders and items) are saved. If the path is for an item, then only that item is saved. <br />
<br />
Components of the path are separated by a forward slash ("/"). If you need to specify a path with spaces, you can surround the whole thing with double quotation marks (e.g. "Folder A/Folder B"). <br />
<br />
You can specify that the contents of a folder should be saved rather than the folder itself using the * wildcard. For instance, "/*" will save your entire inventory but not the "My Inventory" folder itself. This can be useful if you want to restore a saved inventory to an existing one using the load iar --merge function discussed later on.<br />
<br />
If a name or folder contains a forward slash ("/") then it can be escaped with the backslash (i.e. "\/") to stop it being seen as a path separator. Back slashes themselves need to be escaped with another backslash (i.e. "\\").<br />
<br />
One further issue here is that it's not possible to distinguish between identically named folders or items on the path - the workaround is to rename your items/folders if you need to specify them in the path :)<br />
<br />
* <password> is the password of the user.<br />
<br />
* <filename> is an optional filename for the IAR. If none is supplied, then the filename user-inventory.iar is used in the current directory. I recommend that iars have the .iar extension.<br />
<br />
=== Switches ===<br />
<br />
* If the --noassets option is specified, then the archive will be saved without assets. This can be handy if you're backing up the asset database separately and don't want the expense of including all the assets in each archive.<br />
* --home=<url> is the URL of this world's profile service. It is not required that the profile service is operational; the information will be saved, and it will be displayed wherever the archive will be loaded. NOTE: the older --profile option (the previous name of this switch) produced IARs that are not compatible with OpenSimulator 0.7.0.2 and earlier; do not use this option if you want to produce a compatible IAR.<br />
* --verbose prints out versbose saving messages<br />
<br />
=== Examples ===<br />
<br />
Here's an example. Suppose you have an inventory structure like this<br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| <br />
+-- FolderB<br />
| |<br />
| +-- ItemX<br />
|<br />
+-- ItemY<br />
<br />
If you type <br />
<br />
save iar John Doe FolderA PASSWORD my-items.iar<br />
<br />
then FolderA and everything in FolderA (FolderB, ItemX and ItemY) will be saved into an IAR called my-items.iar. On the other hand, if you type<br />
<br />
save iar John Doe FolderA/FolderB/ItemX PASSWORD my-items.iar<br />
<br />
then only ItemX will be saved.<br />
<br />
With save iar you can save your entire inventory as well as the contents of particular folders or individual items.<br />
<br />
For instance, typing<br />
<br />
save iar John Doe / password<br />
<br />
would save your entire inventory to user-inventory.iar (since no filename was given).<br />
<br />
== load iar ==<br />
<br />
An IAR can be reloaded to an OpenSimulator instance with the load iar command<br />
<br />
load iar [-m|--merge] <user-name> <path> <password> [<filename>]<br />
<br />
where<br />
<br />
* <user name> is the name of the user to whom to load the inventory<br />
<br />
* <path> is the path to which the IAR should be loaded. This has to be a folder which already exists in "My Inventory". See the save iar command for more details.<br />
<br />
* <password> is the password of the user.<br />
<br />
* [<filename>] is an optional filename for the IAR. If none is specified, then the filename is assumed to be user-inventory.iar in the current directory.<br />
<br />
=== Switches ===<br />
<br />
* If the --merge option is given, then IAR items are loaded into the existing folder structure where possible, instead of always creating new folders.<br />
<br />
=== Examples ===<br />
<br />
Suppose that "David Hume" has recieved the my-items.iar saved above containing FolderA, FolderB, ItemX and ItemY. David Hume already has an inventory structure like this.<br />
<br />
My Inventory<br />
|<br />
+-- Folder1<br />
| <br />
+-- Folder2<br />
| <br />
+-- Folder3<br />
<br />
David wants to load the IAR to Folder3, so on the region console he executes<br />
<br />
load iar David Hume "Folder1/Folder3" password my-items.iar<br />
<br />
After a little while he ends up with the folder structure<br />
<br />
My Inventory<br />
|<br />
+-- Folder1<br />
| <br />
+-- Folder2<br />
|<br />
+-- Folder3 <br />
|<br />
+-- FolderA<br />
| <br />
+-- FolderB<br />
| |<br />
| +-- ItemX<br />
|<br />
+-- ItemY<br />
<br />
where ItemX and ItemY are ready for rezzing.<br />
<br />
From OpenSimulator 0.7 and onwards, you can also load IARs directly from web addresses. For example<br />
<br />
load iar Betrand Russell Folder2 PASSWORD http://justincc.org/downloads/iars/my-great-items.iar<br />
<br />
will load my-great-items.iar from the web into Folder2 of the user "Bertrand Russell".<br />
<br />
==== Examples ====<br />
<br />
Let's suppose that a user called Albert Camus has an existing inventory structure<br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| |<br />
| +-- Item1<br />
|<br />
+-- FolderC<br />
|<br />
+-- Item2<br />
<br />
and we execute<br />
<br />
load iar --merge Albert Camus / PASSWORD my-items.iar<br />
<br />
with the IAR saved above. Instead of creating a duplicate FolderA, this will instead result in the inventory structure<br />
<br />
My Inventory<br />
|<br />
+-- FolderA<br />
| |<br />
| +-- FolderB<br />
| | |<br />
| | +-- ItemX<br />
| |<br />
| +-- Item1<br />
| |<br />
| +-- ItemY<br />
|<br />
+-- FolderC<br />
|<br />
+-- Item2<br />
<br />
The --merge option is useful if you are restoring a saved inventory to a new user account, since the base folders (Gestures, Landmarks, Objects, etc.) will not be duplicated.<br />
<br />
= IAR files =<br />
<br />
* http://justincc.org/downloads/iars/my-great-items.iar - justincc's initial example IAR.<br />
* http://www.aviefactory.com/Gene_Jacobs_Clothes.iar - Gene Jacobs Men's Clothing Collection (Original Creator)<br />
* http://www.aviefactory.com/Genes_Female_Stuff.iar - Female Skins and Shapes (Found off the web)<br />
* http://www.gridhop.net/IAR/lightshare.iar - [[User:Thomax|txOh]]'s LightShare controller. Useful only if you have [[LightShare]] enabled in OpenSim.ini.<br />
<br />
Please feel free to place links to other IARs here.<br />
<br />
= Further Information =<br />
<br />
[http://justincc.org/blog/category/iars/ http://justincc.org/blog/category/iars/] - articles by justincc on IARs, including tutorials, background information and possible future developments.<br />
<br />
[http://www.metaverseink.com/blog/?p=29 The OpenSimulator Library just got more interesting] - Diva Canto's article on how to extend the OpenSimulator Library using IARs.<br />
<br />
= Use cases =<br />
<br />
Possible uses<br />
<br />
1. To distribute content to other OpenSimulator installations without need to transfer entire regions. One drawback with IARs for this use case is that creator names are not preserved unless the user has a profile on the target installation. One workaround is to include a notecard detailing the creator and license conditions of the content.<br />
<br />
2. To backup a user's inventory. IARs are currently not that great for this. One can backup an entire inventory by giving a path of "/" to the save iar command. But a load IAR of the same will mean a duplicate set of root child 'standard' folders (Objects, Textures, Clothing, etc.). The loaded folders will not have any type icons.<br />
<br />
== Current limitations ==<br />
<br />
* IAR loading and saving is currently done on a single thread. This may lock up the console for a while with very large IARs. This should be addressed in the future<br />
<br />
* Creator names are not preserved unless the profile exists on the target system. This problem may be addressed in the future.<br />
<br />
== IAR Format ==<br />
<br />
The OpenSimulator [[Inventory Archives|Inventory Archive (IAR)]] format is designed with three aims in mind:<br />
<br />
# Make it easy for people to read and update individual items, assets, etc. within an archive.<br />
# Make it easy to compose two inventory archives into a single inventory archive.<br />
# Make it easy to compose archives from scratch.<br />
<br />
Therefore, all the different entities (assets, items, etc.) are packaged in individual files (e.g. one for each asset) with human readable filenames and machine readable extensions (e.g. .jp2 for textures, .txt for notecards).<br />
* [[IAR Format 0.1]]<br />
* [[IAR Format 0.2]]<br />
* [[IAR Format 0.3]]<br />
<br />
= FAQ =<br />
<br />
Nothing yet.<br />
<br />
= Bugs =<br />
<br />
Please search the OpenSimulator Mantis for information on current IAR bugs. <br />
<br />
FEB.23.2010: <br />
<br />
There is a slight "quirk"&nbsp;with MySql in regards to Max_Allowed_Packet size, which the default is 1 Megabyte.&nbsp; This is too small for some of the larger data blobs being stored.&nbsp; It is recomended to increase the default value to 16 Megabytes. <br />
<br />
Locate your MY.ini for MySql (EXAMPLE, in Windows it is located @ "C:\Program Files\MySQL\MySQL Server 5.1")&nbsp; Modify this file to include the following under the mysqld section: <br />
<br />
'''[mysqld]''' <br />
<br />
# The TCP/IP Port the MySQL Server will listen on<br />port=3306<br />max_allowed_packet = 16M<br />
<br />
'''Additional Reference''':&nbsp; [http://dev.mysql.com/doc/refman/5.1/en/packet-too-large.html dev.mysql.com/doc/refman/5.1/en/packet-too-large.html]<br />
<br />
= Current Status =<br />
<br />
Operational but experimental. Bug reports are appreciated and there will almost certainly be quite a few right now. Suggestions for improvement are also welcome. The best place for these right now might be [http://justincc.org/blog/2009/09/14/introducing-opensim-inventory-archives-iars/ my blog post on IARs], since I'm bound to see them then.<br />
<br />
Though we will strive to maintain compatibilty for old archives with newer OpenSimulator versions, please do not rely on these archives as your only backup for inventory.<br />
<br />
= See Also =<br />
<br />
* [[OpenSim Archives|How to use OpenSimulator Archives (OAR)]]<br />
<br />
[[Category:Users]]<br />
[[Category:Support]]<br />
[[Category:Tech Reference]]<br />
[[Category:Help]]<br />
[[Category:Configuration]]<br />
[[Category:Getting Started]]<br />
[[Category:Development]]</div>Fleephttp://opensimulator.org/wiki/0.7.3_Release0.7.3 Release2012-03-22T15:47:29Z<p>Fleep: /* General Simulator */</p>
<hr />
<div>{{MainPageQuicklinks}}<br />
=Release Notes=<br />
== General ==<br />
Welcome to OpenSimulator 0.7.3, an open-source multi-user 3D virtual environment server platform. <br />
<br />
As ever, OpenSimulator is a highly complex piece of alpha software. It's very likely but not guaranteed to work and various usage scenarios (standalone, grid, hypergrid, etc.) in combination with different dependencies (e.g. different versions of mono on Linux/Mac) can produce unexpected or unstable behaviour. If it breaks you get to keep both pieces.<br />
<br />
If you are upgrading from a version prior to 0.7.x, make sure to read the [[0.7 Release]] notes. There have been extensive changes in OpenSimulator from 0.6.x to 0.7.<br />
<br />
When you are upgrading, we strongly recommend that you start off with the default configuration files and port over any changes you made to your older version of OpenSimulator.<br />
<br />
As this is a wiki page, please feel free to update it with more information about migration or other issues as and when these come to light.<br />
<br />
You can download this release of OpenSimulator from http://opensimulator.org/wiki/Download<br />
<br />
== Known issues ==<br />
<br />
* Sometimes creating body parts or clothing fails with no error message. This is not consistent - work around is simply to try again.<br />
* In a stock Linden Lab viewer 2/3, various tabs and buttons will point back to the Linden Lab website. In particular, the profile data will try to fetch from the Linden Lab website. It's not known currently how/whether this can be changed in the stock viewer.<br />
* No form of prim equivalence is implemented for meshes.<br />
* Loading scripts from the simulator library does not work properly.<br />
* Multiple attachments on a single attachment point not supported. However, in viewers which do support multiple attachments, the enforcing of a single attachment on the simulator end should be much smoother.<br />
* The MSSQL database plugin does not yet support telehubs.<br />
* The osNpcLoadAppearance() function fails to create the required attachments.<br />
<br />
== Requirements ==<br />
<br />
OpenSimulator requires:<br />
<br />
* .NET Framework 3.5 when running under Windows.<br />
* At least Mono 2.4.3 when running under Mono (Linux or Mac). Mono 2.6.x and Mono 2.10.x onwards work well. Mono 2.8.x versions are reported as less stable in some situations.<br />
<br />
== Backwards Compatibility Notices ==<br />
<br />
* Object sit targets have been adjusted to much better match those found on the Linden grid. This is for long term compatibility purposes. Unfortunately, it means that existing objects will need to have their sit targets manually adjusted. The adjustment is <-0.1, 0, 0.118>.<br />
* Due to a libomv bug fix, teleports in this release are incompatible with OpenSimulator 0.7.0.2 and earlier. This affects primarily Hypergrid teleports, since simulators within the same grid tend to be all in the same version. Teleports to OpenSimulator 0.7.1 and later should work.<br />
<br />
== Changes ==<br />
<br />
=== General Simulator ===<br />
* OpenSimulator can now be run as a 64-bit Windows process by starting it with OpenSim.exe rather than OpenSim.32BitLaunch.exe. This allows OpenSimulator to address more than 2GB of memory of memory on Windows. Other OpenSimulator-supported operating systems (Linux, Mac OSX) could already do this. If you encounter issues, OpenSim.32BitLaunch.exe is still available to run OpenSimulator in 32-bit mode.<br />
* Locales forced to en_US, which fixes an issue with servers where a locale used a coma as a decimal separator rather than a decimal point.<br />
* Performance improvements to scene loop processing.<br />
* Adaptive throttling turned on by default. This makes the viewer to simulator connection more reliable, resulting in fewer dropped packets. One symptom of dropped packets for instance, is some terrain failing to appear on login.<br />
* Unnecessary exceptions no longer thrown by the embedded HttpServer.dll.<br />
* During simulator startup, default setting now disables logins to the simulator until scripts finish compiling to reduce performance issues.<br />
<br />
=== Configurations ===<br />
<br />
* HG: in the simulator configuration, under [GridService], new variable HypergridLinker = true<br />
* The Hypergrid profile URL for a user is now called the home URL. This requires simulator configuration changes. See http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#Configuration_for_OpenSimulator_0.7.3 for more details.<br />
<br />
=== Services ===<br />
* "show digest" asset service console comamnd renamed to "show asset" and extended to show more information.<br />
* Profiles service connector improved to make configuration less error-prone and to allow Hypergrid support.<br />
* OpenID authentication identity queries fixed.<br />
<br />
=== Hypergrid ===<br />
<br />
* Exception no longer thrown an instant message is sent to a hypergrid-enabled simulator running more than one region.<br />
* Exception no longer thrown if hypergrid friend identifier shorter than expected.<br />
* Exception no longer thrown if a hypergrid-enabled simulator receives a bad home URL for a visitor.<br />
* Attachments states are no longer saved when a user leaves a foreign simulator. This may resolve a long-standing issue where attachments are corrupted for travellers.<br />
<br />
=== Objects ===<br />
* Linksets now retaining their proper numbering when one set is linked with another.<br />
* Child prims are no longer rotated if only the root prim of a linkset is rotated.<br />
* Speed of deleting multiple objects improved.<br />
* Scripts deleted from a prim now go into the user's trash rather than disappearing.<br />
* Taking a copy of an object that you don't own no longer places it in the original owner's inventory if the copy is taken before the region is restarted.<br />
* Shape parameter changes on child prims in a linkset now properly persist.<br />
* Omega (as set in llTargetOmega(), for example) now properly persisted in child prims.<br />
* A region-crossing object no longer occasionally gets placed at the opposite side of the origin sim for a moment.<br />
<br />
=== Mesh ===<br />
* Physics collision meshes for mesh now stored by default when these are uploaded by the viewer.<br />
* Uploaded mesh items no longer get reset to the wrong current owner permissions if their name or other property is changed.<br />
<br />
=== Avatars ===<br />
* Avatar movement improved where there are neighbouring regions, especially where those neighbouring regions are offline.<br />
* Various appearance bugs fixed which should result in fewer cloud and grey avatars.<br />
* Default chat distance changed to 20 meters from 30.<br />
* Animations improved.<br />
* Sit target positioning improved. Unfortunately, this will mean that old objects need their sit target to be manually changed.<br />
* If the avatar is told to sit on a prim, it will now warp there if within 10 meters rather than attempting to walk before sitting (which usually failed). If the avatar is further than 10 meters then nothing happens.<br />
* Ground sitting fixed.<br />
* Region crossings improved.<br />
* A falling avatar that is made to start flying again (e.g. by tapping the home key) can now move freely instead of being rooted to the spot.<br />
* Teleport routing fixed so that avatars teleporting to a parcel are now placed in the parcel settings' position and look direction.<br />
<br />
=== Physics ===<br />
* Open Dynamics Engine (ODE) and scene loop allowed frame times now match. This prevents an error developing between the physics simulation and the viewer movement prediction algorithm, resulting in smoother movement and fewer position update messages.<br />
* ODE no longer occasionally fails with a native stacktrace when a simulator is running more than one region.<br />
* A falling avatar is now restricted to a speed of 54 m/s (the same as a skydiver on Earth). This stops the avatar being randomly teleported when it exceeds a certain speed.<br />
* Small performance improvements made to ODE module.<br />
<br />
=== Parcels/Region/Estates ===<br />
* Estate covenant change times now persisted.<br />
* Notecards in covenants no longer appear corrupted if the viewer cache is cleared.<br />
* Telehub support implemented.<br />
* Problem fixed where avatars hitting banlines would sometimes be frozen on the banline until they teleported away. However, there are still many other issues with parcel bans that won't be fixed in this release.<br />
* Parcel sales persistence supported added to the SQLite database module.<br />
<br />
=== Map ===<br />
* Parcel overlays added to map tiles.<br />
<br />
=== Users ===<br />
* In the 'create user' command on the console, a UUID for the user can now be given.<br />
<br />
=== Friends ===<br />
* Removing friends fixed when using the SQLite database plugin.<br />
<br />
=== Archiving ===<br />
* OAR and IAR loading now check if an asset already exists instead of letting the asset service perform the check. This should reduce archive loading times.<br />
* IAR loading no longer fails on a bad asset.<br />
* Experimental --publish option added to OpenSimulator Archives (OARs). This resets owner information when a region is exported so that if it's reloaded to the same grid the original author doesn't appear as the owner of objects rather than the uploader. Creator information is left intact.<br />
<br />
=== NPC ===<br />
* osNpcSit() and osNpcStand() implemented.<br />
* osIsNpc() implemented. This indicates whether a particular key belongs is that of an NPC.<br />
* NPCs can now sit on prims that don't have a sit target.<br />
* Bug fixed where NPCs created in a region with groups-enabled could cause significant temporary lag.<br />
* By default, created NPCs are now 'owned' by the owner of the creating script. Owned NPCs can only be deleted by other scripts with the same owner. See http://opensimulator.org/wiki/OSSLNPC for more details.<br />
<br />
=== Inventory ===<br />
* Bug fixed where giving an inventory folder to an avatar on the same region would cause an error if the folder was accepted.<br />
* Attaching objects to a notecard fixed.<br />
* Dragging inventory items from child prims into user inventory fixed.<br />
<br />
=== Groups ===<br />
* Bug fixed where an object could not be set to a group that the user had just created.<br />
* Bug fixed where an object could not have its group set back to none after being set.<br />
<br />
=== Administration ===<br />
* RemoteAdmin access can now be restricted to an explicit set of IP addresses.<br />
* Exceptions when executing console commands in ROBUST no longer terminate the executable.<br />
* You can now set a custom console prompt.<br />
* "threads abort" console command added which allows a monitored long-lived thread to be manually aborted.<br />
* "threads show" console command improved.<br />
* admin_teleport_agent call added that allows an authorized caller to teleport a user in the simulator to another location.<br />
* JSON handler added for grid info.<br />
* "delete object" console command now only deletes nominated objects in the currently selected region.<br />
* "show object name" and "show object uuid" commands added to view object information from the console.<br />
* show part uuid" and "show part name" commands added to view part information from the console for non-root prims.<br />
* NonphysicalPrimMax configuration setting fixed.<br />
<br />
=== Monitoring ===<br />
* Simulator statistics accuracy improved, though still some way from always accurate.<br />
* More region statistics added to the monitoring module.<br />
<br />
=== Scripting ===<br />
* XEngine shutdown time vastly improved when many scripts are being run.<br />
* Bug fixed where more than 2000 scripts on a region could trigger a stack overflow.<br />
* "scripts show", "scripts suspend", "scripts resume", "scripts start" and "scripts stop" region console command added. These allow scripts to be manipulated from the console.<br />
* "xengine status" command implemented to show various xengine attributes (e.g. work items waiting, compile queue, etc.).<br />
* Permission control for OSSL script functions enhanced so that permission can be given only to the group of the parcel occupied by the script and/or the parcel owner and/or the estate manager and/or the region owner.<br />
* NoAccess 'threat' level added to OSSL permissions filtering so that the default can be for no OSSL functions to be available apart from those individual chosen.<br />
* If a script that is no copy is dragged into the user inventory it is now stopped in the scene.<br />
* OpenSimulator no longer spits out spurious errors and multiple "script saved" viewre messages if the properties of a script in a prim's inventory are changed (e.g. the name).<br />
* llAvatarOnLinkSetTarget() implemented.<br />
* llGetLinkKey and llGetLinkName() improved to return avatar details if sat upon by an avatar and the avatar link number given.<br />
* llGetTexture() now returns the inventory name of a requested texture if it exists in the prim's inventory. It also returns NULL_KEY if an invalid face is given rather than an empty string.<br />
* llGetAnimation() now returns the turning left and turning right state if appropriate.<br />
* llHTTPRequest() improved to properly return the HTTP body as the body from an unsuccessful request, rather than populating this with the status description.<br />
* llRot2Euler() improved to not show inaccurate results a the +/- pi/2 singularity.<br />
* llAngleBetween() fixed to allow denormal rotations.<br />
* Support for rotating physical objects added to llLookAt() and llRotLookAt().<br />
* llEdgeOfWorld() fixed.<br />
* llSetText() fixed to allow only a maximum of 254 characters.<br />
* llGetLinkNumberOfSides() made available to scripts.<br />
* llGetParcelMusicURL() implemented.<br />
* llManageEstateAcccess() implemented.<br />
* llLinkSitTarget() implemented.<br />
* llGetLinkMedia(), llSetLinKMedia() and llClearLinkMedia() implemented.<br />
* LINK_ROOT flag fixed for llGetLinkName().<br />
* PRIM_LINK_TARGET, PRIM_OMEGA and PRIM_POS_LOCAL implemented for llSetPrimitiveParams(), llSetLinkPrimitiveParams() and llSetLinkPrimitiveParamsFast().<br />
* PRIM_POSITION usage fixed.<br />
* Removal of a single LSL sensor no longer removes all other sensors for other scripts in that prim.<br />
* A mesh object now has 8 faces.<br />
* PRIM_SCULPT_FLAG_MIRROR and PRIM_SCULPT_FLAG_INVERT implemented in llSetPrimitiveParams() and other similar functions.<br />
* CHANGED_TEXTURE and CHANGED_COLOR events fixed.<br />
* RCERR_UNKNOWN and RCERR_SIM_PERF LSL constants added though these are not currently used by OpenSimulator.<br />
* osParseJSON() problems fixed.<br />
* osSetRegionWaterHeight() will no longer accept a negative value.<br />
* osTeleportAgent() no longer has a hard-coded check to disallow teleports if the script is not on a parcel with the same owner. This can now be specified in OSSL permissions configyuration.<br />
* osGetGrid*() OSSL functions fixed to return information from the central grid service [GridInfo] section rather than that of the simulator when in grid mode.<br />
* osGetGridCustom() function added to allow arbitrary GridInfo properties to be retrieved.<br />
* osGetGridHomeURI() function added to allow retrieval of the current grid's Hypergrid address.<br />
<br />
=== Testing ===<br />
* pCampBot tool resurrected and improved to allow multiple libomv clients to be logged in with certain behaviours for stress testing purposes.<br />
<br />
== Acknowledgements ==<br />
<br />
Many, many thanks to all the developers, testers and community members who contributed to this release. Your hard work makes this all possible :)<br />
<br />
[[Category:Release Notes]]</div>Fleephttp://opensimulator.org/wiki/0.7.3_Release0.7.3 Release2012-03-22T15:36:08Z<p>Fleep: /* General Simulator */</p>
<hr />
<div>{{MainPageQuicklinks}}<br />
=Release Notes=<br />
== General ==<br />
Welcome to OpenSimulator 0.7.3, an open-source multi-user 3D virtual environment server platform. <br />
<br />
As ever, OpenSimulator is a highly complex piece of alpha software. It's very likely but not guaranteed to work and various usage scenarios (standalone, grid, hypergrid, etc.) in combination with different dependencies (e.g. different versions of mono on Linux/Mac) can produce unexpected or unstable behaviour. If it breaks you get to keep both pieces.<br />
<br />
If you are upgrading from a version prior to 0.7.x, make sure to read the [[0.7 Release]] notes. There have been extensive changes in OpenSimulator from 0.6.x to 0.7.<br />
<br />
When you are upgrading, we strongly recommend that you start off with the default configuration files and port over any changes you made to your older version of OpenSimulator.<br />
<br />
As this is a wiki page, please feel free to update it with more information about migration or other issues as and when these come to light.<br />
<br />
You can download this release of OpenSimulator from http://opensimulator.org/wiki/Download<br />
<br />
== Known issues ==<br />
<br />
* Sometimes creating body parts or clothing fails with no error message. This is not consistent - work around is simply to try again.<br />
* In a stock Linden Lab viewer 2/3, various tabs and buttons will point back to the Linden Lab website. In particular, the profile data will try to fetch from the Linden Lab website. It's not known currently how/whether this can be changed in the stock viewer.<br />
* No form of prim equivalence is implemented for meshes.<br />
* Loading scripts from the simulator library does not work properly.<br />
* Multiple attachments on a single attachment point not supported. However, in viewers which do support multiple attachments, the enforcing of a single attachment on the simulator end should be much smoother.<br />
* The MSSQL database plugin does not yet support telehubs.<br />
* The osNpcLoadAppearance() function fails to create the required attachments.<br />
<br />
== Requirements ==<br />
<br />
OpenSimulator requires:<br />
<br />
* .NET Framework 3.5 when running under Windows.<br />
* At least Mono 2.4.3 when running under Mono (Linux or Mac). Mono 2.6.x and Mono 2.10.x onwards work well. Mono 2.8.x versions are reported as less stable in some situations.<br />
<br />
== Backwards Compatibility Notices ==<br />
<br />
* Object sit targets have been adjusted to much better match those found on the Linden grid. This is for long term compatibility purposes. Unfortunately, it means that existing objects will need to have their sit targets manually adjusted. The adjustment is <-0.1, 0, 0.118>.<br />
* Due to a libomv bug fix, teleports in this release are incompatible with OpenSimulator 0.7.0.2 and earlier. This affects primarily Hypergrid teleports, since simulators within the same grid tend to be all in the same version. Teleports to OpenSimulator 0.7.1 and later should work.<br />
<br />
== Changes ==<br />
<br />
=== General Simulator ===<br />
* OpenSimulator can now be run as a 64-bit Windows process by starting it with OpenSim.exe rather than OpenSim.32BitLaunch.exe. This allows OpenSimulator to address more than 2GB of memory of memory on Windows. Other OpenSimulator-supported operating systems (Linux, Mac OSX) could already do this. If you encounter issues, OpenSim.32BitLaunch.exe is still available to run OpenSimulator in 32-bit mode.<br />
* Locales forced to en_US, which fixes an issue with servers where a locale used a coma as a decimal separator rather than a decimal point.<br />
* Performance improvements to scene loop processing.<br />
* Adaptive throttling turned on by default. This makes the viewer to simulator connection more reliable, resulting in fewer dropped packets. One symptom of dropped packets for instance, is some terrain failing to appear on login.<br />
* Unnecessary exceptions no longer thrown by the embedded HttpServer.dll.<br />
* During simulator startup, logins to simulator disabled by default until scripts finish loading.<br />
<br />
=== Configurations ===<br />
<br />
* HG: in the simulator configuration, under [GridService], new variable HypergridLinker = true<br />
* The Hypergrid profile URL for a user is now called the home URL. This requires simulator configuration changes. See http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#Configuration_for_OpenSimulator_0.7.3 for more details.<br />
<br />
=== Services ===<br />
* "show digest" asset service console comamnd renamed to "show asset" and extended to show more information.<br />
* Profiles service connector improved to make configuration less error-prone and to allow Hypergrid support.<br />
* OpenID authentication identity queries fixed.<br />
<br />
=== Hypergrid ===<br />
<br />
* Exception no longer thrown an instant message is sent to a hypergrid-enabled simulator running more than one region.<br />
* Exception no longer thrown if hypergrid friend identifier shorter than expected.<br />
* Exception no longer thrown if a hypergrid-enabled simulator receives a bad home URL for a visitor.<br />
* Attachments states are no longer saved when a user leaves a foreign simulator. This may resolve a long-standing issue where attachments are corrupted for travellers.<br />
<br />
=== Objects ===<br />
* Linksets now retaining their proper numbering when one set is linked with another.<br />
* Child prims are no longer rotated if only the root prim of a linkset is rotated.<br />
* Speed of deleting multiple objects improved.<br />
* Scripts deleted from a prim now go into the user's trash rather than disappearing.<br />
* Taking a copy of an object that you don't own no longer places it in the original owner's inventory if the copy is taken before the region is restarted.<br />
* Shape parameter changes on child prims in a linkset now properly persist.<br />
* Omega (as set in llTargetOmega(), for example) now properly persisted in child prims.<br />
* A region-crossing object no longer occasionally gets placed at the opposite side of the origin sim for a moment.<br />
<br />
=== Mesh ===<br />
* Physics collision meshes for mesh now stored by default when these are uploaded by the viewer.<br />
* Uploaded mesh items no longer get reset to the wrong current owner permissions if their name or other property is changed.<br />
<br />
=== Avatars ===<br />
* Avatar movement improved where there are neighbouring regions, especially where those neighbouring regions are offline.<br />
* Various appearance bugs fixed which should result in fewer cloud and grey avatars.<br />
* Default chat distance changed to 20 meters from 30.<br />
* Animations improved.<br />
* Sit target positioning improved. Unfortunately, this will mean that old objects need their sit target to be manually changed.<br />
* If the avatar is told to sit on a prim, it will now warp there if within 10 meters rather than attempting to walk before sitting (which usually failed). If the avatar is further than 10 meters then nothing happens.<br />
* Ground sitting fixed.<br />
* Region crossings improved.<br />
* A falling avatar that is made to start flying again (e.g. by tapping the home key) can now move freely instead of being rooted to the spot.<br />
* Teleport routing fixed so that avatars teleporting to a parcel are now placed in the parcel settings' position and look direction.<br />
<br />
=== Physics ===<br />
* Open Dynamics Engine (ODE) and scene loop allowed frame times now match. This prevents an error developing between the physics simulation and the viewer movement prediction algorithm, resulting in smoother movement and fewer position update messages.<br />
* ODE no longer occasionally fails with a native stacktrace when a simulator is running more than one region.<br />
* A falling avatar is now restricted to a speed of 54 m/s (the same as a skydiver on Earth). This stops the avatar being randomly teleported when it exceeds a certain speed.<br />
* Small performance improvements made to ODE module.<br />
<br />
=== Parcels/Region/Estates ===<br />
* Estate covenant change times now persisted.<br />
* Notecards in covenants no longer appear corrupted if the viewer cache is cleared.<br />
* Telehub support implemented.<br />
* Problem fixed where avatars hitting banlines would sometimes be frozen on the banline until they teleported away. However, there are still many other issues with parcel bans that won't be fixed in this release.<br />
* Parcel sales persistence supported added to the SQLite database module.<br />
<br />
=== Map ===<br />
* Parcel overlays added to map tiles.<br />
<br />
=== Users ===<br />
* In the 'create user' command on the console, a UUID for the user can now be given.<br />
<br />
=== Friends ===<br />
* Removing friends fixed when using the SQLite database plugin.<br />
<br />
=== Archiving ===<br />
* OAR and IAR loading now check if an asset already exists instead of letting the asset service perform the check. This should reduce archive loading times.<br />
* IAR loading no longer fails on a bad asset.<br />
* Experimental --publish option added to OpenSimulator Archives (OARs). This resets owner information when a region is exported so that if it's reloaded to the same grid the original author doesn't appear as the owner of objects rather than the uploader. Creator information is left intact.<br />
<br />
=== NPC ===<br />
* osNpcSit() and osNpcStand() implemented.<br />
* osIsNpc() implemented. This indicates whether a particular key belongs is that of an NPC.<br />
* NPCs can now sit on prims that don't have a sit target.<br />
* Bug fixed where NPCs created in a region with groups-enabled could cause significant temporary lag.<br />
* By default, created NPCs are now 'owned' by the owner of the creating script. Owned NPCs can only be deleted by other scripts with the same owner. See http://opensimulator.org/wiki/OSSLNPC for more details.<br />
<br />
=== Inventory ===<br />
* Bug fixed where giving an inventory folder to an avatar on the same region would cause an error if the folder was accepted.<br />
* Attaching objects to a notecard fixed.<br />
* Dragging inventory items from child prims into user inventory fixed.<br />
<br />
=== Groups ===<br />
* Bug fixed where an object could not be set to a group that the user had just created.<br />
* Bug fixed where an object could not have its group set back to none after being set.<br />
<br />
=== Administration ===<br />
* RemoteAdmin access can now be restricted to an explicit set of IP addresses.<br />
* Exceptions when executing console commands in ROBUST no longer terminate the executable.<br />
* You can now set a custom console prompt.<br />
* "threads abort" console command added which allows a monitored long-lived thread to be manually aborted.<br />
* "threads show" console command improved.<br />
* admin_teleport_agent call added that allows an authorized caller to teleport a user in the simulator to another location.<br />
* JSON handler added for grid info.<br />
* "delete object" console command now only deletes nominated objects in the currently selected region.<br />
* "show object name" and "show object uuid" commands added to view object information from the console.<br />
* show part uuid" and "show part name" commands added to view part information from the console for non-root prims.<br />
* NonphysicalPrimMax configuration setting fixed.<br />
<br />
=== Monitoring ===<br />
* Simulator statistics accuracy improved, though still some way from always accurate.<br />
* More region statistics added to the monitoring module.<br />
<br />
=== Scripting ===<br />
* XEngine shutdown time vastly improved when many scripts are being run.<br />
* Bug fixed where more than 2000 scripts on a region could trigger a stack overflow.<br />
* "scripts show", "scripts suspend", "scripts resume", "scripts start" and "scripts stop" region console command added. These allow scripts to be manipulated from the console.<br />
* "xengine status" command implemented to show various xengine attributes (e.g. work items waiting, compile queue, etc.).<br />
* Permission control for OSSL script functions enhanced so that permission can be given only to the group of the parcel occupied by the script and/or the parcel owner and/or the estate manager and/or the region owner.<br />
* NoAccess 'threat' level added to OSSL permissions filtering so that the default can be for no OSSL functions to be available apart from those individual chosen.<br />
* If a script that is no copy is dragged into the user inventory it is now stopped in the scene.<br />
* OpenSimulator no longer spits out spurious errors and multiple "script saved" viewre messages if the properties of a script in a prim's inventory are changed (e.g. the name).<br />
* llAvatarOnLinkSetTarget() implemented.<br />
* llGetLinkKey and llGetLinkName() improved to return avatar details if sat upon by an avatar and the avatar link number given.<br />
* llGetTexture() now returns the inventory name of a requested texture if it exists in the prim's inventory. It also returns NULL_KEY if an invalid face is given rather than an empty string.<br />
* llGetAnimation() now returns the turning left and turning right state if appropriate.<br />
* llHTTPRequest() improved to properly return the HTTP body as the body from an unsuccessful request, rather than populating this with the status description.<br />
* llRot2Euler() improved to not show inaccurate results a the +/- pi/2 singularity.<br />
* llAngleBetween() fixed to allow denormal rotations.<br />
* Support for rotating physical objects added to llLookAt() and llRotLookAt().<br />
* llEdgeOfWorld() fixed.<br />
* llSetText() fixed to allow only a maximum of 254 characters.<br />
* llGetLinkNumberOfSides() made available to scripts.<br />
* llGetParcelMusicURL() implemented.<br />
* llManageEstateAcccess() implemented.<br />
* llLinkSitTarget() implemented.<br />
* llGetLinkMedia(), llSetLinKMedia() and llClearLinkMedia() implemented.<br />
* LINK_ROOT flag fixed for llGetLinkName().<br />
* PRIM_LINK_TARGET, PRIM_OMEGA and PRIM_POS_LOCAL implemented for llSetPrimitiveParams(), llSetLinkPrimitiveParams() and llSetLinkPrimitiveParamsFast().<br />
* PRIM_POSITION usage fixed.<br />
* Removal of a single LSL sensor no longer removes all other sensors for other scripts in that prim.<br />
* A mesh object now has 8 faces.<br />
* PRIM_SCULPT_FLAG_MIRROR and PRIM_SCULPT_FLAG_INVERT implemented in llSetPrimitiveParams() and other similar functions.<br />
* CHANGED_TEXTURE and CHANGED_COLOR events fixed.<br />
* RCERR_UNKNOWN and RCERR_SIM_PERF LSL constants added though these are not currently used by OpenSimulator.<br />
* osParseJSON() problems fixed.<br />
* osSetRegionWaterHeight() will no longer accept a negative value.<br />
* osTeleportAgent() no longer has a hard-coded check to disallow teleports if the script is not on a parcel with the same owner. This can now be specified in OSSL permissions configyuration.<br />
* osGetGrid*() OSSL functions fixed to return information from the central grid service [GridInfo] section rather than that of the simulator when in grid mode.<br />
* osGetGridCustom() function added to allow arbitrary GridInfo properties to be retrieved.<br />
* osGetGridHomeURI() function added to allow retrieval of the current grid's Hypergrid address.<br />
<br />
=== Testing ===<br />
* pCampBot tool resurrected and improved to allow multiple libomv clients to be logged in with certain behaviours for stress testing purposes.<br />
<br />
== Acknowledgements ==<br />
<br />
Many, many thanks to all the developers, testers and community members who contributed to this release. Your hard work makes this all possible :)<br />
<br />
[[Category:Release Notes]]</div>Fleephttp://opensimulator.org/wiki/Grid_List/FleepGridGrid List/FleepGrid2012-03-03T07:04:52Z<p>Fleep: </p>
<hr />
<div>__NOTOC__ {{Quicklinks}} <br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
| Name: <br />
| FleepGrid<br />
|-<br />
| Website: <br />
| http://fleepgrid.com/ <br />
|-<br />
| Login URI: <br />
| http://fleepgrid.com:8002<br />
|-<br />
| Approx # Regions <br />
| 11<br />
|-<br />
| Approx # Users <br />
| 150<br />
|-<br />
| Logins/day <br />
| 5<br />
|-<br />
| HyperGrid Enabled <br />
| Yes<br />
|-<br />
| Center Coordinates <br />
| 9013,9013<br />
|-<br />
| Landing Region (9013, 9013)<br />
| FleepGrid Plaza<br />
|-<br />
|}<br />
<br />
FleepGrid is a small, personal research grid owned and operated by Fleep Tuque. Visitors are welcome either via the HyperGrid or by creating an account.</div>Fleephttp://opensimulator.org/wiki/Grid_List/FleepGridGrid List/FleepGrid2012-03-03T07:04:11Z<p>Fleep: </p>
<hr />
<div>__NOTOC__ {{Quicklinks}} <br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
| Name: <br />
| FleepGrid<br />
|-<br />
| Website: <br />
| http://fleepgrid.com/ <br />
|-<br />
| Login URI: <br />
| http://fleepgrid.com:8002<br />
|-<br />
| Wiki/Forum: <br />
| [[OSGridRegionRegistration|Wiki Page about OSGrid]]<br>[http://forums.osgrid.org/ OSGrid forum]<br />
|-<br />
| Approx # Regions <br />
| 11<br />
|-<br />
| Approx # Users <br />
| 150<br />
|-<br />
| Logins/day <br />
| 5<br />
|-<br />
| HyperGrid Enabled <br />
| Yes<br />
|-<br />
| Center Coordinates <br />
| 9013,9013<br />
|-<br />
| Landing Region (9013, 9013)<br />
| FleepGrid Plaza<br />
|-<br />
|}<br />
<br />
FleepGrid is a small, personal research grid owned and operated by Fleep Tuque. Visitors are welcome either via the HyperGrid or by creating an account.</div>Fleephttp://opensimulator.org/wiki/Grid_List/FleepGridGrid List/FleepGrid2012-03-03T07:03:50Z<p>Fleep: Created page with "__NOTOC__ {{Quicklinks}} <br> {| cellspacing="0" cellpadding="5" border="1" |- | Name: | FleepGrid |- | Website: | http://fleepgrid.com/ |- | Login URI: | http://fleepgrid...."</p>
<hr />
<div>__NOTOC__ {{Quicklinks}} <br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
| Name: <br />
| FleepGrid<br />
|-<br />
| Website: <br />
| http://fleepgrid.com/ <br />
|-<br />
| Login URI: <br />
| http://fleepgrid.com:8002<br />
|-<br />
| Wiki/Forum: <br />
| [[OSGridRegionRegistration|Wiki Page about OSGrid]]<br>[http://forums.osgrid.org/ OSGrid forum]<br />
|-<br />
| Approx # Regions <br />
| 11<br />
|-<br />
| Approx # Users <br />
| 150<br />
|-<br />
| Logins/day <br />
| 5<br />
| HyperGrid Enabled <br />
| Yes<br />
|-<br />
| Center Coordinates <br />
| 9013,9013<br />
|-<br />
| Landing Region (9013, 9013)<br />
| FleepGrid Plaza<br />
|-<br />
|}<br />
<br />
FleepGrid is a small, personal research grid owned and operated by Fleep Tuque. Visitors are welcome either via the HyperGrid or by creating an account.</div>Fleephttp://opensimulator.org/wiki/Grid_ListGrid List2012-03-03T06:58:14Z<p>Fleep: /* Public grids */</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br />
==What is the Grid List?==<br />
<br />
There are hundreds (thousands?) of OpenSimulator-based virtual worlds out there. Many of them are free to use and welcome new users. This grid list is a community-generated list of such worlds. If you would like to experience an OpenSimulator-based virtual world before installing your own, try one of these. <br />
<br />
'''IMPORTANT NOTE:''' The OpenSimulator project is not responsible for, nor in any way associated with, any grid listed on this page, nor for any grid's content or activities. Visit at your own risk. Also, there are no guarantees that these worlds are up and running.<br />
<br />
== Public grids ==<br />
<br />
'''Grid List Policy:''' Please list your grid only if uses OpenSimulator as a component. Do not include advertising language. The entries in the main list should just contain the grid name and the plain numbers as defined by the column headers. '''Please use [[Grid List/Template|this template]] for the subpages to keep the information in a comparable manner.''' Grids are listed in the order of appearance, so please add your entry to the bottom of the list. Anyone found inserting a grid up higher in the list will have their entry moved or removed. <br />
<br />
You may want provide a link on your world's website back to the project by using the [[OpenSim Graphics|Powered by OpenSimulator logo]]. Credit is appreciated but not required. <br />
<br />
If you own a grid and are interested in joining a grid association see this page: [[Grid Associations]] <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center" class="sortable" style="width: 724px; height: 2270px;"<br />
|-<br />
! Grid Name <br />
! # Regions <br />
! Approx # Users <br />
! Unique last 30days<br />
|-<br />
| [[Grid List/OSGrid|OSGrid]] <br />
| 7178 <br />
| 64,296 <br />
| 3280<br />
|-<br />
| [[Grid List/Francogrid|Francogrid]] <br />
| 484 <br />
| 3851 <br />
| 180<br />
|-<br />
| [[Grid List/The New World Grid|The New World Grid]] <br />
| 330 <br />
| 5200 <br />
| 590<br />
|-<br />
| [[Grid List/3rd Rock Grid|3rd Rock Grid (Community Based with Geode Currency )]] <br />
| 171 <br />
| 3343 <br />
| 443<br />
|-<br />
| [[Grid List/Metropolis|Metropolis Metaversum (NO money)]] <br />
| 352 <br />
| 1585 <br />
| 239<br />
|-<br />
| [[Grid List/German Grid|German Grid(with OM¢)]] <br />
| 107 <br />
| 2353 <br />
| 385<br />
|-<br />
| [[Grid List/Open-Neuland|OpenSimulator-Club Open Neuland (with OM¢)]] <br />
| 216 <br />
| 384 <br />
| 60<br />
|-<br />
| [[Grid List/Wilder-Westen|OpenSimulator-Club Wilder Westen (with OM¢)]] <br />
| 41 <br />
| 122 <br />
| 36<br />
|-<br />
| [[Grid List/ReactionGrid|ReactionGrid]] <br />
| 76 <br />
| 9756 <br />
| 406<br />
|-<br />
| [[Grid List/Myopengrid.com|Myopengrid (with M$ dollars)]] <br />
| &nbsp; <br />
| &nbsp; <br />
| &nbsp;<br />
|-<br />
| [[Grid List/Your Alternative Life|Your Alternative Life (with OM¢)]] <br />
| 47 <br />
| 2089 <br />
| 1458<br />
|-<br />
| [[Grid List/Openvue|Openvue (on Virtual AIAI Grid)]] <br />
| 12 <br />
| 20 <br />
| 10<br />
|-<br />
| [[Grid List/ScienceSim|ScienceSim]] <br />
| 25 <br />
| 30 <br />
| 15<br />
|-<br />
| [[Grid List/Unica|unica]] <br />
| 16 <br />
| 60 <br />
| 10<br />
|-<br />
| [[Grid List/LISAT|Lost-In-Space-And-Time( Free, H.G. 7.2 and wifi login)]] <br />
| &nbsp; <br />
| &nbsp; <br />
| &nbsp;<br />
|-<br />
| [[Grid List/Avination|Avination (w/economy and combat system]] <br />
| 1138 <br />
| 25860 <br />
| 8727<br />
|-<br />
| [[Grid List/SimValley NL|SimValley NL]] <br />
| 79 <br />
| 146 <br />
| 23<br />
|-<br />
| [[Grid List/VirtualFrance3D|VirtualFrance3D =&gt;WEB: http://virtualfrance3d.fr]] <br />
| 16 <br />
| 143 <br />
| 31<br />
|-<br />
| [[Grid List/Twisted Sky|Twisted Sky (with OM¢)]] <br />
| 60 <br />
| 290 <br />
| 68<br />
|-<br />
| [[Grid List/TertiaryGrid|Tertiary grid]] <br />
| 25 <br />
| 48 <br />
| 34<br />
|-<br />
| [[Grid List/Logicamp|Logicamp® - The Outdoor Metaverse (with OM¢)]] <br />
| 120 <br />
| 234 <br />
| 91<br />
|-<br />
| [[Grid List/virtyou|virtyou]] <br />
| 110 <br />
| 1676 <br />
| 70<br />
|-<br />
| [[Grid List/Jamland|Jamland]] <br />
| 10 <br />
| 31 <br />
| 14<br />
|-<br />
| [[Grid List/Tlön|Tlön]] <br />
| 11 <br />
| 65 <br />
| 10<br />
|-<br />
| [[Grid List/PMGrid|PMGrid]] <br />
| 40 <br />
| 80 <br />
| 10<br />
|-<br />
| [[Grid List/Cybergrid|Cybergrid]] <br />
| 1 <br />
| 44 <br />
| &nbsp;<br />
|-<br />
| [[Grid List/jokaydiagrid|jokaydiaGRID]] <br />
| 20 <br />
| 253 <br />
| 75<br />
|-<br />
| [[Grid List/Rezzable Visions|Rezzable Visions]] <br />
| &nbsp; <br />
| &nbsp; <br />
| &nbsp;<br />
|-<br />
| [[Grid List/Craft|Craft]] <br />
| 180 <br />
| 900 <br />
| 290<br />
|-<br />
| [[Grid List/Virtual RP|Virtual RP - Roleplay - VRP Combat Meter - Free World]] <br />
| 17 <br />
| 714 <br />
| 55<br />
|-<br />
| [[Grid List/GerGrid|GerGrid (with OS$)]] <br />
| 50 <br />
| 84 <br />
| 15<br />
|-<br />
| [[Grid List/AlphaTowne|Alpha Towne w/G$ Hypergrid 1.5]] <br />
| 308 <br />
| 1172 <br />
| 909<br />
|-<br />
| [[Grid List/Annuna Grid|Annuna Grid]] <br />
| 60 <br />
| 60 <br />
| &nbsp;<br />
|-<br />
| [[Grid List/VeeSome|VeeSome]] <br />
| 48 <br />
| 106 <br />
| 53<br />
|-<br />
| [[Grid List/VirtuaLife|Virtualife with RP and economy inworld]] <br />
| 132 <br />
| 1000 <br />
| 500<br />
|-<br />
| [[Grid List/REDISIS|Redisis share knowledge]] <br />
| 130 <br />
| 60 <br />
| 20<br />
|-<br />
| [[Grid List/PearGrid|PearGrid]] <br />
| 18 <br />
| 34 <br />
| 8<br />
|-<br />
| [[Grid List/Island Oasis|Island Oasis (w/ OM¢)RP, Vehicles, Combat]] <br />
| 69<br />
| 1506<br />
| 327<br />
|-<br />
| [[Grid List/SpotON3D|SpotON3D]] <br />
| 195 <br />
| 4389 <br />
| 869<br />
|-<br />
| [[Grid List/HAVEN: Your World|HAVEN: Your World]] <br />
| 13 <br />
| 11 <br />
| 7<br />
|-<br />
| [[Grid List/Flatlandia.cc|Flatlandia.cc]] <br />
| 33 <br />
| 177 <br />
| 110<br />
|-<br />
| [[Grid List/AnSky|AnSky]] <br />
| 11 <br />
| 39 <br />
| &nbsp;<br />
|-<br />
| [[Grid List/Lisat|ArtGridOnLine]] <br />
| 12 <br />
| 48 <br />
| 15<br />
|-<br />
| [[Grid List/EU-Grid|EU-Grid]] <br />
| 10 <br />
| 350 <br />
| &nbsp;<br />
|-<br />
| [[Grid List/GiantGrid|GiantGrid]] <br />
| 169 <br />
| 261 <br />
| 157<br />
|-<br />
| [[Grid List/pseudospace|pseudospace]] <br />
| 12 <br />
| 46 <br />
| &nbsp;<br />
|-<br />
| [[Grid List/Metapocalypse|Metapocalypse Grid]] <br />
| &nbsp; <br />
| &nbsp; <br />
| &nbsp;<br />
|-<br />
| [[Grid List/UFSGrid|UFSGrid]] <br />
| 0 <br />
| 0 <br />
| 0<br />
|-<br />
| [[Grid List/Virtual Worlds Grid|Virtual Worlds Grid]] <br />
| 527 <br />
| 30 <br />
| 4<br />
|-<br />
| [[Grid List/The SecondLearning Grid|The SecondLearning Grid (with OM¢)]] <br />
| 4 <br />
| 55 <br />
| 46<br />
|-<br />
| [[Grid List/slitalia|slitalia]] <br />
| 8 <br />
| 36 <br />
| 46<br />
|-<br />
| [[Grid List/Sofitek|Sofitek]] <br />
| 6 <br />
| 10 <br />
| 10<br />
|-<br />
| [[Grid List/AstralGrid|AstralGrid]] <br />
| 70 <br />
| 40 <br />
| 30<br />
|-<br />
| [[Grid List/MOSES|MOSES : Military Open Simulator Enterprise Strategy]] <br />
| 117 <br />
| 227 <br />
| 102<br />
|-<br />
| [[Grid List/Dorenas World|Dorenas World]] <br />
| 102 <br />
| 182 <br />
| 34<br />
|-<br />
| [[Grid List/Enakai|Enakai]] <br />
| 16 <br />
| 14 <br />
| 34<br />
|-<br />
| [[Grid List/Speculoos|Speculoos.net: belgian cookie flavored grid]] <br />
| 44 <br />
| 14 <br />
| 30<br />
|-<br />
| [[Grid List/EverWorlds.com|EverWorlds: Bringing People Together (Old name: Destiny Zero) ]] <br />
| 17 <br />
| 2 <br />
| 3<br />
|-<br />
| [[Grid List/IcaruSRealmS|=IcaruS= RealmS ]] <br />
| 26 <br />
| &nbsp; <br />
| 14<br />
|-<br />
| [[Grid List/ccdbbs.com|Lost Paradise]] <br />
| 234<br />
| 91<br />
| 72<br />
|-<br />
| [[Grid List/Valhalla Virtual|Valhalla Virtual]] <br />
| 9 <br />
| 25 <br />
| 4<br />
|-<br />
| [[SkyLine Grid]]<br />
| 10<br />
| 6<br />
| 6<br />
|-<br />
| [[OSGrid EU]]<br />
| 100<br />
| 1<br />
| 1<br />
|-<br />
| [[NewtonGrid]]<br />
| 9<br />
| 2<br />
| 1<br />
|-<br />
| [[Grid List/Cyber Wrld|Cyber Wrld]]<br />
| 5<br />
| 8<br />
| 8<br />
|-<br />
| [[FleepGrid]]<br />
| 11<br />
| 150<br />
| 20<br />
|}<br />
<br />
<br> <br />
<br />
This is a list of Grids that been inactive for a few days and or have claimed to be inactive by the owner. <!-- MAJ le 30/12/2011 --> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center" class="sortable" style="width: 724px; height: 2270px;"<br />
|-<br />
! Grid Name <br />
! # Regions <br />
! Approx # Users <br />
! Unique last 30days<br />
|-<br />
| [[Grid List/Uvatar|Uvatar.com]] <br />
| &nbsp;??? <br />
| &nbsp;??? <br />
| 0 <!-- Logins are disabled. Last update to the website was in 2012, many unfixed errors to the site. --><br />
|-<br />
| [[Grid List/Cyberlandia|Cyberlandia]] <br />
| 185 <br />
| 1600 <br />
| 269<br />
|-<br />
| [[Grid List/Avatar Hangout|Avatar Hangout (with OMC)]] <br />
| 73 <br />
| 8,626 <br />
| 58<br />
|-<br />
| [[Grid List/DGP Grid|DGP Grid]] <br />
| &nbsp; <br />
| &nbsp; <br />
| &nbsp;<br />
|-<br />
| [[Grid List/Meta7|Meta7]] <br />
| 293 <br />
| 4997 <br />
| 1321<br />
|-<br />
| [[Grid List/tescos.org.uk|tescos.org.uk (curency ƒ)]] <br />
| 30 <br />
| 20 <br />
| 20<br />
|-<br />
| [[Grid List/Role Play Worlds|Role Play Worlds - Your Fantasy, your world]] <br />
| 129 <br />
| 2276 <br />
| 298<br />
|-<br />
| [[Grid List/Avatrian|Avatrian]] <br />
| 11 <br />
| 25 <br />
| 150<br />
|-<br />
| [[Grid List/OSBEST|OSBEST]] <br />
| 12 <br />
| 8 <br />
| 8<br />
|-<br />
| [[Grid List/Sim-World|Sim-World With SW$ and Economy]] <br />
| 83 <br />
| 1952 <br />
| 311<br />
|-<br />
| [[Grid List/Austria|Austria]] <br />
| 9 <br />
| 6 <br />
| 9<br />
|-<br />
| [[Grid List/Psychedelia|Psychedelia]] <br />
| 5 <br />
| 7 <br />
| 11<br />
|-<br />
| [[Grid List/MCM Realm|MCM Realm]] <br />
| 22 <br />
| 73 <br />
| 23<br />
|-<br />
| [[Grid List/Oasis Grid|Oasis Grid]] <br />
| 89 <br />
| 3068 <br />
| 228<br />
|-<br />
| [[Grid List/AtMeeting|AtMeeting Grid]] <br />
| 20 <br />
| 30 <br />
| 25<br />
|-<br />
| [[Grid List/OpenUtopia|OpenUtopia Grid]] <br />
| 1 <br />
| 3 <br />
| 3<br />
|-<br />
| [[Grid List/Virtualgames3d|Virtualgames3d]] <br />
| 140 <br />
| 1350 <br />
| 500<br />
|-<br />
| [[Grid List/Grid4Us|Grid4Us]] <br />
| 22 <br />
| 130 <br />
| 50<br />
|-<br />
| [[Grid List/K-grid|K-grid]] <br />
| &nbsp; <br />
| &nbsp; <br />
| &nbsp;<br />
|-<br />
| [[Grid List/Le Monde de Darwin|Le Monde de Darwin]] <br />
| 73 <br />
| 83 <br />
| 36<br />
|-<br />
| [[Grid List/NeXtLife|NeXtLife Grid]] <br />
| 15 <br />
| 7 <br />
| 7<br />
|-<br />
| [[Grid List/Sensation Games|Sensation Games]] <br />
| 1 <br />
| 2 <br />
| 1<br />
|-<br />
| [[Grid List/SLI-Grid|SLI-Grid]] <br />
| 5 <br />
| &nbsp; <br />
| &nbsp;<br />
|-<br />
| [[Grid List/DSGrid|www.dsgrid.eu]] <br />
| 15 <br />
| 162 <br />
| 22<br />
|-<br />
| TGGrid <br />
| 11 <br />
| 9 <br />
| 13<br />
|-<br />
| [[Grid List/digsynth.com|World of the Free]] <br />
| 0 <br />
| 0 <br />
| 0<br />
|}<br />
<br />
== Other OpenSim-based Environments ==<br />
<br />
[[Grid List/Heritage Key|Heritage Key]] - OpenSim-based original 3D environment.<br />
<br />
<br />
== Office Hour ==<br />
<br />
Each week on Tuesday, OSGrid hosts an official Office Hour where the OpenSim developers meet and discuss the weeks software development activities. This is a good place to get to know what is going on with OpenSim.<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center"<br />
!Grid<br />
!Region<br />
!Time<br />
|-<br />
|OSGrid<br />
|Wright Plaza<br />
|Tuesday 11:00AM Pacific Time (USA)<br />
|-<br />
|EU-Grid<br />
|EU-Grid Central Hub<br />
|Sat 15:00 to 19:00 MET<br />
|-<br />
|AUGrid / Asia Pacific Office Hours<br />
|Norgan Plaza<br />
|Friday's 11am2pm AEST (GMT/UTC + 10)<br />
|-<br />
|Cyberlandia Grid Italiana<br />
|Cyberlandia, Central Hub<br />
|Mercoledi and Venerdi<BR>22:00 to 23:00 (GMT/UTC + 1)<br />
|-<br />
|WorldSim Terra<br />
|Lusitania Center<br />
|Saturdays 19:00 to 20:00 (GMT/UTC)<br />
|-<br />
|Avatar Hangout - Residents<br />
|Meeting Hall in Avatar Hangout region<br />
|Sundays 1pm to 3pm (InGame Time)<br />
|-<br />
|Avatar Hangout - Estate Owners<br />
|via Estate Owners group in Skype<br />
|Saturday 2pm to 4pm (InGame Time)<br />
|-<br />
|LISAT<br />
|&nbsp;<br />
|Saturday midnight "UTC"<br>Wednesday 1400(2pm)UTC<br>"Universal.Time.Coordinated"<br />
|-<br />
|[http://virtyou.com/ virtyou MainGrid]<br />
|Waterland01 <br />
|Tuesday 11:00 - 12:00 [http://en.wikipedia.org/wiki/Central_European_Time CET] (UTC+1),<br>Thursday 20:00 - 21:00 [http://en.wikipedia.org/wiki/Central_European_Time CET] (UTC+1)<br />
|-<br />
|[http://www.logicamp.com/ logicamp MainGrid]<br />
|Logicamp<br />
|Friday 11:00 - 12:00 GMT+1<br />
|-<br />
|[http://www.opensimulator-club.de/ Open Neuland / OpenSimulator-Club]<br />
|Neuland <br />
|Tuesday 19:30 - 21:00 [http://en.wikipedia.org/wiki/Central_European_Time CET] (UTC+1)<br />
|-<br />
|[http://www.griditaliaservice.com// GridItalia Metaverso Italiano]<br />
|GridItalia Orientation<br />
|Dal Lunedi' al Venerdi' 22:00 to 00:00 (GMT/UTC + 1)<br />
|-<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
== Grid Test Hours ==<br />
<br />
Several grids provide valuable testing information for the project, each run a special 'test' hour to test capabilities of the platform. These are run at the same time every week. It may also be a good chance to meet people who can answer questions you may have.<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center"<br />
!Grid<br />
!Region<br />
!Time<br />
|-<br />
|Apex Grid<br />
|Spaceport 2<br />
|Sat 1800 UTC<br />
|-<br />
|FrancoGrid<br />
|Orion<br />
|Everydays 2100GMT+1<br />
|-<br />
|New World Grid<br />
|Welcome<br />
|Every Tuesday at 2030 UTC<br />
|-<br />
|AUGrid<br />
|Norgan Plaza<br />
|Generally Tuesdays 11am~1pm and/or 2~5pm AEST (GMT/UTC+10)<br />[http://augrid.org/forum/index.php?topic=9.0]<br />
|-<br />
|WorldSim Terra<br />
|Lusitania Center<br />
|Generally Sundays 19:00 to 22.00(GMT/UTC)<br />[http://www.worldsimterra.com/index.php?option=com_agora&task=viewtopic&id=223 Next Test Hours]<br />
|-<br />
|VirtualFrance<br />
|versailles <br />
|Generally Mondays and Thursdays 2100GMT+1<br />[http://www.virtualfrance.0rg.fr]<br />
|-<br />
|Logicamp<br />
|Logicamp <br />
|Generally Mondays 0900 GMT+1<br />[http://www.logicamp.com]<br />
|-<br />
|AstralGrid<br />
|AstralGrid<br />
|Generally Mondays 21:00 GMT+1<br />[http://www.virtual.world.ch.vu]<br />
|}<br />
<br />
== Standalone sims ==<br />
<br />
Standalone sims have "generic" logins being from "Testa User" .. "Testz User", with password "test". <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center"<br />
|-<br />
! Name <br />
! Login URI <br />
! Maintainer/Site<br />
|-<br />
| Ruth (Zion) <br />
| opensim://ruth.petitbe.be:9000/ <br />
| Dalien Talbot (dalien on IRC, or via blog - http://daltonic.blogspot.com/)<br />
|-<br />
| CyberSpacia <br />
| opensim://cyberspacia.net:9000/ <br />
| Spun Pty Ltd (mailto:the.grid@cyberspacia.net)<br />
|-<br />
| janoz <br />
| opensim://77.250.27.219:9000/ <br />
| (mailto:info@janoz.nl)<br />
|-<br />
| Opengrid <br />
| opensim://opengrid.fr:9000/ <br />
| Test grid for http://www.opensimulator.fr - 24/7 available<br />
|-<br />
| Phrearch <br />
| opensim://os-networks.net:9000/ <br />
| Phrearch: http://os-networks.net<br />
|-<br />
| Timecatcher Haven Lands( Not online 24/7) <br />
| opensim://timecatcher.ath.cx:9000/ <br />
| Timecatcher: (mailto:anon26841397@hotmail.co.uk)<br />
|-<br />
| Europeansim (NOW 24/7 ish:-) <br />
| opensim://82.30.71.119:8002/ <br />
| Edenrealm Sim(mailto:zoon@edenrealm.co.uk) BritGrid OpenSim 0.6.9 (Dev) - 26 regions - Hypergrid? - Avatar creation at: http://www.europeansim.thruhere.net Blog http://www.edenrealm.co.uk/<br />
|-<br />
| OpenSIM.de (24/7) <br />
| opensim://opensim.m34.mx-host.de:9090 <br />
| German Standalone-Sim with german (deutsch) speaking Live-Support and OpenSIM-Wiki at http://www.opensim.de<br />
|-<br />
| Viradu Science Fiction World<br />
| opensim://viradu.com:9000<br />
| [[Image:Vban.jpg|180px|thumb|left|Viradu.com Science Fiction Virtual World]]A Science Fiction Themed Virtual World since 1/7/2009, by Michael Blade, Sci-fi Blogger - 12 regions NOTE: Please read Blog for connect instructions ---&gt; http://viradu.com for more info. This world is now open for settlement to those who enjoy science fiction, rules apply. Also see hypergrid 1.5 list. Test User test<br />
|-<br />
| Lokir <br />
| opensim://lokir.org:9000 <br />
| A multicultural, multilanguage Bristol based art space and sandbox in the UK. Experimental servers testing new versions towards having hypergrid and megaregion functionality, but stable sim server version is currently 5.4, so quite old. See http://lokir.org/opensim for more info, or use the name and password "Test User test" to log in as a guest.<br />
|-<br />
| SPARTA! (open 24/7) <br />
| opensim://204.12.98.91:9000 <br />
| New (as of 2/20/2010) U.S. based sim. Right now this is more for my amusement than anything. Looking for testers or just bored people who have extra time on their hands. Should it become popular I'll consider expanding services. No registration required. Use any name you like. Questions? mailto:davidakaplan@gmail.com. THIS... IS... SPARTA!!!<br />
|-<br />
| [http://www.yoursimspot.com YourSimSpot.Com]<br><br />
| YourSimSpot.com:9000<br />
| YourSimSpot is a hosting solution for 3D virtual worlds for business, education, collaboration, and individuals based on the OpenSimulator platform. We specialize in providing the technology needed for these environments. <br />
|-<br />
| Desert of Artlioch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br />
| [http://universi.servegame.org:9000 http://universi.servegame.org:9000]&nbsp; <br />
| A Science Fiction Desert world with hypergrid.&nbsp;Currently has no currency and only 2 regions.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
|-<br />
|Realms of Discordia<br />
| [http://www.griffonsnest.com:9000 http://www.griffonsnest.com:9000]&nbsp;<br />
|My small testing sim, open 24 hours, feel free to come by, visit, build, whatever. 9 Regions with 3 current residents. <br />
|}<br />
<br />
= See Also =<br />
<br />
* [[Grid_Associations|Grid Associations]]<br />
* [[Public_Hypergrid_Nodes|HyperGrid Nodes]]<br />
<br />
[[Category:Grids]]</div>Fleephttp://opensimulator.org/wiki/Offline_MessagingOffline Messaging2011-11-09T17:28:32Z<p>Fleep: /* Through OpenSim.Wiredux as a module */</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br /><br />
<br />
Offline messaging makes it possible to send IM's to people that are not online and saves the messages directly to a database.<br />
<br />
=== Through OpenSim.Wiredux as a module ===<br />
<br />
In the latest version of OpenSim.Wiredux the offline module is already ready to be used<br />
* Grab the latest version of the Wiredux<br />
* Install the wi_offline_msg.sql file on your database<br />
You need to enable the Offline Messaging Module in your Opensim.ini file.<br />
<br />
=== Changes in the OpenSim.ini file ===<br />
<br />
<source lang=text><br />
[Messaging]<br />
; Control which region module is used for instant messaging.<br />
; Default is InstantMessageModule (this is the name of the core IM module as well as the setting)<br />
InstantMessageModule = InstantMessageModule<br />
; MessageTransferModule = MessageTransferModule<br />
OfflineMessageModule = OfflineMessageModule<br />
OfflineMessageURL = http://yourserver/offline.php<br />
MuteListModule = MuteListModule<br />
MuteListURL = http://yourserver/mute.php<br />
</source><br />
<br />
When you did it right, reboot your region and try to send a message to an offline person. Check the database to see that it has written a record.<br />
<br />
Next time that person logs in, he will get the message and the database will be updated<br />
<br />
P.D: The MuteListModule and URL must be uncommented in order for the offline module to work, even if there is no mute.php file in the web folder.</div>Fleephttp://opensimulator.org/wiki/Offline_MessagingOffline Messaging2011-11-09T17:28:02Z<p>Fleep: Reverting page to previous version.</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br /><br />
<br />
Offline messaging makes it possible to send IM's to people that are not online and saves the messages directly to a database.<br />
<br />
=== Through OpenSim.Wiredux as a module ===<br />
<br />
Offline messaging makes it possible to send IM's to people that are not online and saves the messages directly to a database.<br />
Through OpenSim.Wiredux as a module<br />
In the latest version of OpenSim.Wiredux the offline module is already ready to be used<br />
* Grab the latest version of the Wiredux<br />
* Install the wi_offline_msg.sql file on your database<br />
You need to enable the Offline Messaging Module in your Opensim.ini file.<br />
<br />
=== Changes in the OpenSim.ini file ===<br />
<br />
<source lang=text><br />
[Messaging]<br />
; Control which region module is used for instant messaging.<br />
; Default is InstantMessageModule (this is the name of the core IM module as well as the setting)<br />
InstantMessageModule = InstantMessageModule<br />
; MessageTransferModule = MessageTransferModule<br />
OfflineMessageModule = OfflineMessageModule<br />
OfflineMessageURL = http://yourserver/offline.php<br />
MuteListModule = MuteListModule<br />
MuteListURL = http://yourserver/mute.php<br />
</source><br />
<br />
When you did it right, reboot your region and try to send a message to an offline person. Check the database to see that it has written a record.<br />
<br />
Next time that person logs in, he will get the message and the database will be updated<br />
<br />
P.D: The MuteListModule and URL must be uncommented in order for the offline module to work, even if there is no mute.php file in the web folder.</div>Fleephttp://opensimulator.org/wiki/Offline_MessagingOffline Messaging2011-11-09T16:51:35Z<p>Fleep: /* Through OpenSim.Wiredux as a module */</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br /><br />
<br />
Offline messaging makes it possible to send IM's to people that are not online and saves the messages directly to a database.<br />
<br />
=== Through OpenSim.Wiredux as a module ===<br />
<br />
In the latest version of OpenSim.Wiredux the offline module is already ready to be used<br />
<br />
* Grab the latest version of the Wiredux from [http://forge.opensimulator.org/svn/opensimwi http://forge.opensimulator.org/svn/opensimwi]<br />
<br />
Note: For Windows users or those who have not used Subversion before, the [http://www.codinghorror.com/blog/2008/04/setting-up-subversion-on-windows.html instructions to set up the TortoiseSVN client on Windows] may be helpful (scroll down for the client part of the instructions). After you've installed TortoiseSVN, then create a directory in the location of your choosing and then right click - choose "SVN Checkout..." - and enter the URL provided above to download the entire package. When the screen appears to enter the username and password, username: anonymous password: [blank].<br />
<br />
* Create the necessary tables using the wi_offline_msg.sql file in the package <br />
<br />
* You need to enable the Offline Messaging Module in your Opensim.ini file.<br />
<br />
=== Changes in the OpenSim.ini file ===<br />
<br />
<source lang=text><br />
[Messaging]<br />
; Control which region module is used for instant messaging.<br />
; Default is InstantMessageModule (this is the name of the core IM module as well as the setting)<br />
InstantMessageModule = InstantMessageModule<br />
; MessageTransferModule = MessageTransferModule<br />
OfflineMessageModule = OfflineMessageModule<br />
OfflineMessageURL = http://yourserver/offline.php<br />
MuteListModule = MuteListModule<br />
MuteListURL = http://yourserver/mute.php<br />
</source><br />
<br />
When you did it right, reboot your region and try to send a message to an offline person. Check the database to see that it has written a record.<br />
<br />
Next time that person logs in, he will get the message and the database will be updated<br />
<br />
P.D: The MuteListModule and URL must be uncommented in order for the offline module to work, even if there is no mute.php file in the web folder.</div>Fleephttp://opensimulator.org/wiki/Offline_MessagingOffline Messaging2011-11-09T16:27:04Z<p>Fleep: /* Through OpenSim.Wiredux as a module */</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br /><br />
<br />
Offline messaging makes it possible to send IM's to people that are not online and saves the messages directly to a database.<br />
<br />
=== Through OpenSim.Wiredux as a module ===<br />
<br />
In the latest version of OpenSim.Wiredux the offline module is already ready to be used<br />
<br />
* Grab the latest version of the Wiredux from [http://forge.opensimulator.org/svn/opensimwi http://forge.opensimulator.org/svn/opensimwi]<br />
<br />
Note: For Windows users or those who have not used Subversion before, the [http://www.codinghorror.com/blog/2008/04/setting-up-subversion-on-windows.html instructions to set up the TortoiseSVN client on Windows] may be helpful (scroll down for the client part of the instructions). After you've installed TortoiseSVN, then create a directory in the location of your choosing and then right click - choose "SVN Checkout..." - and enter the URL provided above to download the entire package. When the screen appears to enter the username and password, username: anonymous password: [blank].<br />
<br />
* Create a directory in your webserver root folder called "offlineIM" and copy the contents of the package "webroot" directory to your "offlineIM" directory. Note: IIS users, your webserver root folder is C:\inetpub\wwwroot.<br />
<br />
* Create the necessary tables using the wi_offline_msg.sql file in the package on your opensim database<br />
<br />
In the package, you'll find \branches\jamenai\trunk\install\sql_update\wi_offline_msgs.sql. Run it.<br />
<pre><br />
mysql> source /(your_path_to_the_package)/branches/jamenai/trunk/install/sql_update/wi_offline_msgs.sql<br />
</pre><br />
It will create two tables for ofline IMs. <br />
<br />
* You need to enable the Offline Messaging Module in your Opensim.ini file.<br />
<br />
=== Changes in the OpenSim.ini file ===<br />
<br />
<source lang=text><br />
[Messaging]<br />
; Control which region module is used for instant messaging.<br />
; Default is InstantMessageModule (this is the name of the core IM module as well as the setting)<br />
InstantMessageModule = InstantMessageModule<br />
; MessageTransferModule = MessageTransferModule<br />
OfflineMessageModule = OfflineMessageModule<br />
OfflineMessageURL = http://yourserver/offline.php<br />
MuteListModule = MuteListModule<br />
MuteListURL = http://yourserver/mute.php<br />
</source><br />
<br />
When you did it right, reboot your region and try to send a message to an offline person. Check the database to see that it has written a record.<br />
<br />
Next time that person logs in, he will get the message and the database will be updated<br />
<br />
P.D: The MuteListModule and URL must be uncommented in order for the offline module to work, even if there is no mute.php file in the web folder.</div>Fleephttp://opensimulator.org/wiki/Offline_MessagingOffline Messaging2011-11-09T16:18:49Z<p>Fleep: /* Through OpenSim.Wiredux as a module */</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br /><br />
<br />
Offline messaging makes it possible to send IM's to people that are not online and saves the messages directly to a database.<br />
<br />
=== Through OpenSim.Wiredux as a module ===<br />
<br />
In the latest version of OpenSim.Wiredux the offline module is already ready to be used<br />
<br />
* Grab the latest version of the Wiredux from [http://forge.opensimulator.org/svn/opensimwi http://forge.opensimulator.org/svn/opensimwi]<br />
<br />
Note: For Windows users or those who have not used Subversion before, the [http://www.codinghorror.com/blog/2008/04/setting-up-subversion-on-windows.html instructions to set up the TortoiseSVN client on Windows] may be helpful (scroll down for the client part of the instructions). After you've installed TortoiseSVN, then create a directory in the location of your choosing and then right click - choose "SVN Checkout..." - and enter the URL provided above to download the entire package. When the screen appears to enter the username and password, username: anonymous password: [blank].<br />
<br />
* Create a directory in your webserver root folder called "offlineIM" and copy the contents of the package "webroot" directory to your "offlineIM" directory. Note: IIS users, your webserver root folder is C:\inetpub\wwwroot.<br />
<br />
* Create the necessary tables using the wi_offline_msg.sql file in the package on your opensim database<br />
<br />
In the package, you'll find \branches\jamenai\trunk\install\sql_update\wi_offline_msgs.sql. Run it.<br />
<pre><br />
mysql> source /(your_path_to_the_package)/branches/jamenai/trunk/install/sql_update/wi_offline_msgs.sql<br />
</pre><br />
It will create the tables for ofline IMs. Note that the recent version(5.X) of mysql server may fail to create them. If so, change<br />
* ''timestamp(14)'' to ''timestamp''<br />
* ''TYPE=MyISAM'' to ''ENGINE=MyISAM''<br />
and try again.<br />
<br />
You need to enable the Offline Messaging Module in your Opensim.ini file.<br />
<br />
=== Changes in the OpenSim.ini file ===<br />
<br />
<source lang=text><br />
[Messaging]<br />
; Control which region module is used for instant messaging.<br />
; Default is InstantMessageModule (this is the name of the core IM module as well as the setting)<br />
InstantMessageModule = InstantMessageModule<br />
; MessageTransferModule = MessageTransferModule<br />
OfflineMessageModule = OfflineMessageModule<br />
OfflineMessageURL = http://yourserver/offline.php<br />
MuteListModule = MuteListModule<br />
MuteListURL = http://yourserver/mute.php<br />
</source><br />
<br />
When you did it right, reboot your region and try to send a message to an offline person. Check the database to see that it has written a record.<br />
<br />
Next time that person logs in, he will get the message and the database will be updated<br />
<br />
P.D: The MuteListModule and URL must be uncommented in order for the offline module to work, even if there is no mute.php file in the web folder.</div>Fleephttp://opensimulator.org/wiki/Offline_MessagingOffline Messaging2011-11-09T16:08:44Z<p>Fleep: /* Through OpenSim.Wiredux as a module */</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br /><br />
<br />
Offline messaging makes it possible to send IM's to people that are not online and saves the messages directly to a database.<br />
<br />
=== Through OpenSim.Wiredux as a module ===<br />
<br />
In the latest version of OpenSim.Wiredux the offline module is already ready to be used<br />
<br />
* Grab the latest version of the Wiredux from [http://forge.opensimulator.org/svn/opensimwi http://forge.opensimulator.org/svn/opensimwi]<br />
<br />
Note: For Windows users or those who have not used Subversion before, the [http://www.codinghorror.com/blog/2008/04/setting-up-subversion-on-windows.html instructions to set up the TortoiseSVN client on Windows] may be helpful (scroll down for the client part of the instructions). After you've installed TortoiseSVN, then create a directory in the location of your choosing and then right click - choose "SVN Checkout..." - and enter the URL provided above to download the entire package. When the screen appears to enter the username and password, username: anonymous password: [blank].<br />
<br />
* Install the wi_offline_msg.sql file on your database<br />
<br />
You need to enable the Offline Messaging Module in your Opensim.ini file.<br />
<br />
=== Changes in the OpenSim.ini file ===<br />
<br />
<source lang=text><br />
[Messaging]<br />
; Control which region module is used for instant messaging.<br />
; Default is InstantMessageModule (this is the name of the core IM module as well as the setting)<br />
InstantMessageModule = InstantMessageModule<br />
; MessageTransferModule = MessageTransferModule<br />
OfflineMessageModule = OfflineMessageModule<br />
OfflineMessageURL = http://yourserver/offline.php<br />
MuteListModule = MuteListModule<br />
MuteListURL = http://yourserver/mute.php<br />
</source><br />
<br />
When you did it right, reboot your region and try to send a message to an offline person. Check the database to see that it has written a record.<br />
<br />
Next time that person logs in, he will get the message and the database will be updated<br />
<br />
P.D: The MuteListModule and URL must be uncommented in order for the offline module to work, even if there is no mute.php file in the web folder.</div>Fleephttp://opensimulator.org/wiki/Offline_MessagingOffline Messaging2011-11-09T15:45:35Z<p>Fleep: /* Through OpenSim.Wiredux as a module */ - added instructions for Windows users new to SVN...</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br /><br />
<br />
Offline messaging makes it possible to send IM's to people that are not online and saves the messages directly to a database.<br />
<br />
=== Through OpenSim.Wiredux as a module ===<br />
<br />
In the latest version of OpenSim.Wiredux the offline module is already ready to be used<br />
<br />
* Grab the latest version of the Wiredux from [http://forge.opensimulator.org/gf/project/opensimwi/scmsvn/ http://forge.opensimulator.org/gf/project/opensimwi/scmsvn/]<br />
<br />
Note: For Windows users or those who have not used Subversion before, the [http://www.codinghorror.com/blog/2008/04/setting-up-subversion-on-windows.html instructions to set up the TortoiseSVN client on Windows] may be helpful (scroll down for the client part of the instructions). After you've installed TortoiseSVN, then create a directory in the location of your choosing and then right click - choose "SVN Checkout..." - and enter the URL provided above to download the entire package.<br />
<br />
* Install the wi_offline_msg.sql file on your database<br />
<br />
You need to enable the Offline Messaging Module in your Opensim.ini file.<br />
<br />
=== Changes in the OpenSim.ini file ===<br />
<br />
<source lang=text><br />
[Messaging]<br />
; Control which region module is used for instant messaging.<br />
; Default is InstantMessageModule (this is the name of the core IM module as well as the setting)<br />
InstantMessageModule = InstantMessageModule<br />
; MessageTransferModule = MessageTransferModule<br />
OfflineMessageModule = OfflineMessageModule<br />
OfflineMessageURL = http://yourserver/offline.php<br />
MuteListModule = MuteListModule<br />
MuteListURL = http://yourserver/mute.php<br />
</source><br />
<br />
When you did it right, reboot your region and try to send a message to an offline person. Check the database to see that it has written a record.<br />
<br />
Next time that person logs in, he will get the message and the database will be updated<br />
<br />
P.D: The MuteListModule and URL must be uncommented in order for the offline module to work, even if there is no mute.php file in the web folder.</div>Fleephttp://opensimulator.org/wiki/OpenSimSearchOpenSimSearch2011-11-09T15:44:47Z<p>Fleep: /* How to setup OSS */ - Added instructions for Windows users new to SVN</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br /><br />
<br />
OpenSimSearch makes it possible to have working Search included in OpenSim. At this moment only the Popular Places, Places, Landsales are fully activate, Events works in basic mode, still working on Classifieds and in the future the "New" search that works with HTML pages.<br />
<br />
==How to setup OSS==<br />
<br />
* Make sure you have a Apache/PHP/MySQL configuration ready else Search won't work!!<br />
<br />
You can grab the latest version of OpenSimSearch through SVN, use the command below and use 'anonymous' as the username and a blank password to checkout the code.<br />
<br />
<code><br />
svn checkout http://forge.opensimulator.org/svn/ossearch<br />
</code><br />
<br />
Note: For Windows users or those who have not used Subversion before, the [http://www.codinghorror.com/blog/2008/04/setting-up-subversion-on-windows.html instructions to set up the TortoiseSVN client on Windows] may be helpful (scroll down for the client part of the instructions). After you've installed TortoiseSVN, then create a directory in the location of your choosing and then right click - choose "SVN Checkout..." - and enter the URL provided above to download the entire package.<br />
<br />
====Using the Binary====<br />
<br />
<h5> The following parts are for the Grid owner only</h5><br />
<br />
* In the trunk/bin folder you can find the latest binary release which you can include into your OpenSim.Just grab the 2 binary files and place them in the <b>bin</b> folder of OpenSim.<br />
<br />
* Copy all files in the trunk/webroot to your webserver <br />
<br />
* Create a new database called <b>ossearch</b><br />
<br />
* Import the SQL file ossearch.sql into your database <br />
<br />
<code><br />
mysql --user --password ossearch < ossearch.sql<br />
</code><br />
<br />
* Make sure you change the databaseinfo.php file to reflect your settings.<br />
<br />
<source lang=php><br />
<?php<br />
$DB_HOST = "<servername>";<br />
$DB_USER = "<username>";<br />
$DB_PASSWORD = "<password>";<br />
$DB_NAME = "<database>";<br />
?><br />
</source><br />
<br />
<h5> The following parts are for the Region owners </h5><br />
<br />
* In the trunk/bin folder you can find the latest binary release which you can include into your OpenSim.Just grab the 2 binary files and place them in the <b>bin</b> folder of OpenSim.<br />
<br />
* Search needs the DataSnapShot module to be activated, here's how to get it activated:<br />
<br />
<source lang=text><br />
[DataSnapshot]<br />
; The following set of configs pertains to search.<br />
; Set index_sims to true to enable search engines to index your searchable data<br />
; If false, no data will be exposed, DataSnapshot module will be off, and you can ignore the rest of <br />
; these search-related configs<br />
index_sims = true<br />
; The variable data_exposure controls what the regions expose:<br />
; minimum: exposes only things explicitly marked for search<br />
; all: exposes everything<br />
data_exposure = minimum<br />
; If search is on, change this to your grid name; will be ignored for standalones<br />
gridname = "<yourgridname>"<br />
; Period between data snapshots, in seconds. 20 minutes, for starters, so that you see the initial changes fast.<br />
; Later, you may want to increase this to 3600 (1 hour) or more<br />
default_snapshot_period = 1200<br />
; This will be created in bin, if it doesn't exist already. It will hold the data snapshots.<br />
snapshot_cache_directory = "DataSnapshot"<br />
; This semicolon-separated string serves to notify specific data services about the existence <br />
; of this sim. Uncomment if you want to index your data with this and/or other search providers.<br />
data_services="http://<yourserver>/search/register.php"<br />
</source><br />
<br />
* Add the following 2 lines to your OpenSim.ini file to get Search activated<br />
<br />
<code><br />
[Search]<br><br />
SearchURL = http://gridserver/search/query.php<br />
</code><br />
<br />
<h5>[Grid owners]</h5><br />
<br />
* Startup your region server and check your MySQL database table <b>hostregister</b> if the regionserver registered itself. If it registers, that means the DataSnapShot Module is working and you can use Search.<br />
<br />
In the trunk/webroot folder there's a file called parser.php. This file is the parser of the info from the DataSnapShot Module. This file needs to be run with cron or some other way. If this file isn't run, the search tables won't be filled and you won't see anything.<br />
<br />
To set up a cron job, take a look at this page:<br />
<br />
* http://www.linuxhelp.net/guides/cron/<br />
<br />
<h5>[Region owners]</h5><br />
<br />
* Startup your region server and have the Grid owner check if your region shows up in the MySQL database table <b>hostregister</b>. When it does, your region now has Search enabled from the Grid<br />
<br />
====Notes for the Grid Owners====<br />
<br />
* If you're a Grid owner, make sure that regionserver can access your Search URL else the Search on those regions will fail.<br />
<br />
* Whenever a sim fails, sometimes the user that has set the cron job up will fire off emails to the root user. These emails can be annoying but only give warnings about it working.</div>Fleephttp://opensimulator.org/wiki/OpenSimProfileOpenSimProfile2011-11-09T15:42:29Z<p>Fleep: /* How to setup OSP */</p>
<hr />
<div>==How to setup OSP==<br />
<br />
* Make sure you have a Apache/PHP/MySQL configuration ready else Profiles won't work!!<br />
* You also need to make sure you have php-xmlrpc or you will need to compile it in with php.<br />
<br />
You can grab the latest version of OpenSimProfile through SVN, use the command below to checkout the code.<br />
<br />
<code><br />
svn checkout http://forge.opensimulator.org/svn/osprofile<br />
</code><br />
<br />
Note: For Windows users or those who have not used Subversion before, the [http://www.codinghorror.com/blog/2008/04/setting-up-subversion-on-windows.html instructions to set up the TortoiseSVN client on Windows] may be helpful (scroll down for the client part of the instructions). After you've installed TortoiseSVN, then create a directory in the location of your choosing and then right click - choose "SVN Checkout..." - and enter the URL provided above to download the entire package.<br />
<br />
==Upload site to webroot==<br />
<br />
Next thing you need to do is upload your profile.php and databaseinfo.php located /trunk/webroot/ to your public http folder so Regions can connect to it.<br />
<br />
<br />
<br />
==Create a database==<br />
<br />
First you will need to create a database. Once you have finished that you can execute the following SQL file osprofiles.sql located in /trunk/webroot/sql/ from the SVN.<br />
<br />
Then you need to setup your database connection file located /trunk/webroot/databaseinfo.php OR your webroot where you had uploaded databaseinfo.php<br />
<br />
<br />
<br />
<source lang=php><br />
<?php<br />
$DB_HOST = "<servername>";<br />
$DB_USER = "<username>";<br />
$DB_PASSWORD = "<password>";<br />
$DB_NAME = "<database>";<br />
?><br />
</source><br />
<br />
<br />
<br />
==Setup Module==<br />
<br />
Now that we have everything else setup you just have to install the Module and reset your Regions Server.<br />
<br />
First Copy trunk/bin/OpenSimProfile.Modules.dll and put it into your OpenSim/bin folder.<br />
<br />
Now you go ahead and edit your OpenSim.ini on any servers that host Regions.<br />
<br />
Inside OpenSim.ini add the following:<br />
<br />
<source lang=php><br />
[Profile]<br />
; Change it to your own HTTP server to have the Profile server work<br />
ProfileURL = http://gridserver/profile.php<br />
</source><br />
<br />
==Finished==<br />
<br />
Just reboot your Regions server and you should now be able to edit and save your profiles!</div>Fleephttp://opensimulator.org/wiki/OpenSimProfileOpenSimProfile2011-11-09T15:41:10Z<p>Fleep: /* How to setup OSP */ - Added instructions for using SVN for Windows users.</p>
<hr />
<div>==How to setup OSP==<br />
<br />
* Make sure you have a Apache/PHP/MySQL configuration ready else Profiles won't work!!<br />
* You also need to make sure you have php-xmlrpc or you will need to compile it in with php.<br />
<br />
You can grab the latest version of OpenSimProfile through SVN, use the command below to checkout the code.<br />
<br />
<code><br />
svn checkout http://forge.opensimulator.org/svn/osprofile<br />
</code><br />
<br />
Note: For Windows users or those who have not used Subversion before, the instructions to set up the TortoiseSVN client on this page may be helpful (scroll down for the client part of the instructions). After you've installed TortoiseSVN, then create a directory in the location of your choosing and then right click - choose "SVN Checkout..." - and enter the URL provided above to download the entire package.<br />
<br />
==Upload site to webroot==<br />
<br />
Next thing you need to do is upload your profile.php and databaseinfo.php located /trunk/webroot/ to your public http folder so Regions can connect to it.<br />
<br />
<br />
<br />
==Create a database==<br />
<br />
First you will need to create a database. Once you have finished that you can execute the following SQL file osprofiles.sql located in /trunk/webroot/sql/ from the SVN.<br />
<br />
Then you need to setup your database connection file located /trunk/webroot/databaseinfo.php OR your webroot where you had uploaded databaseinfo.php<br />
<br />
<br />
<br />
<source lang=php><br />
<?php<br />
$DB_HOST = "<servername>";<br />
$DB_USER = "<username>";<br />
$DB_PASSWORD = "<password>";<br />
$DB_NAME = "<database>";<br />
?><br />
</source><br />
<br />
<br />
<br />
==Setup Module==<br />
<br />
Now that we have everything else setup you just have to install the Module and reset your Regions Server.<br />
<br />
First Copy trunk/bin/OpenSimProfile.Modules.dll and put it into your OpenSim/bin folder.<br />
<br />
Now you go ahead and edit your OpenSim.ini on any servers that host Regions.<br />
<br />
Inside OpenSim.ini add the following:<br />
<br />
<source lang=php><br />
[Profile]<br />
; Change it to your own HTTP server to have the Profile server work<br />
ProfileURL = http://gridserver/profile.php<br />
</source><br />
<br />
==Finished==<br />
<br />
Just reboot your Regions server and you should now be able to edit and save your profiles!</div>Fleephttp://opensimulator.org/wiki/Offline_MessagingOffline Messaging2011-11-09T15:28:22Z<p>Fleep: /* Through OpenSim.Wiredux as a module */</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br /><br />
<br />
Offline messaging makes it possible to send IM's to people that are not online and saves the messages directly to a database.<br />
<br />
=== Through OpenSim.Wiredux as a module ===<br />
<br />
In the latest version of OpenSim.Wiredux the offline module is already ready to be used<br />
<br />
* Grab the latest version of the Wiredux from [http://forge.opensimulator.org/gf/project/opensimwi/scmsvn/ http://forge.opensimulator.org/gf/project/opensimwi/scmsvn/]<br />
<br />
* Install the wi_offline_msg.sql file on your database<br />
<br />
You need to enable the Offline Messaging Module in your Opensim.ini file.<br />
<br />
=== Changes in the OpenSim.ini file ===<br />
<br />
<source lang=text><br />
[Messaging]<br />
; Control which region module is used for instant messaging.<br />
; Default is InstantMessageModule (this is the name of the core IM module as well as the setting)<br />
InstantMessageModule = InstantMessageModule<br />
; MessageTransferModule = MessageTransferModule<br />
OfflineMessageModule = OfflineMessageModule<br />
OfflineMessageURL = http://yourserver/offline.php<br />
MuteListModule = MuteListModule<br />
MuteListURL = http://yourserver/mute.php<br />
</source><br />
<br />
When you did it right, reboot your region and try to send a message to an offline person. Check the database to see that it has written a record.<br />
<br />
Next time that person logs in, he will get the message and the database will be updated<br />
<br />
P.D: The MuteListModule and URL must be uncommented in order for the offline module to work, even if there is no mute.php file in the web folder.</div>Fleephttp://opensimulator.org/wiki/Offline_MessagingOffline Messaging2011-11-09T15:27:58Z<p>Fleep: /* Through OpenSim.Wiredux as a module */ - adding URL to the location of the Wiredux module</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br /><br />
<br />
Offline messaging makes it possible to send IM's to people that are not online and saves the messages directly to a database.<br />
<br />
=== Through OpenSim.Wiredux as a module ===<br />
<br />
In the latest version of OpenSim.Wiredux the offline module is already ready to be used<br />
<br />
* Grab the latest version of the Wiredux from [http://forge.opensimulator.org/gf/project/opensimwi/scmsvn/]<br />
<br />
* Install the wi_offline_msg.sql file on your database<br />
<br />
You need to enable the Offline Messaging Module in your Opensim.ini file.<br />
<br />
=== Changes in the OpenSim.ini file ===<br />
<br />
<source lang=text><br />
[Messaging]<br />
; Control which region module is used for instant messaging.<br />
; Default is InstantMessageModule (this is the name of the core IM module as well as the setting)<br />
InstantMessageModule = InstantMessageModule<br />
; MessageTransferModule = MessageTransferModule<br />
OfflineMessageModule = OfflineMessageModule<br />
OfflineMessageURL = http://yourserver/offline.php<br />
MuteListModule = MuteListModule<br />
MuteListURL = http://yourserver/mute.php<br />
</source><br />
<br />
When you did it right, reboot your region and try to send a message to an offline person. Check the database to see that it has written a record.<br />
<br />
Next time that person logs in, he will get the message and the database will be updated<br />
<br />
P.D: The MuteListModule and URL must be uncommented in order for the offline module to work, even if there is no mute.php file in the web folder.</div>Fleephttp://opensimulator.org/wiki/Enabling_GroupsEnabling Groups2011-11-05T00:09:56Z<p>Fleep: /* Deploying XmlRpcGroups */ - where to copy XmlRpcGroupsServer folder for IIS</p>
<hr />
<div>{{Quicklinks}}<br />
= Groups Overview =<br />
<br />
== What is "Groups" in OpenSimulator? ==<br />
<br />
''Groups'' is one of the optional functionality of OpenSimulator, which enables the users to create grid-wide(or hypergrid-wide) community in your regions. For the general knowledge about the concept of Group or how to create your in-world group, see [http://wiki.secondlife.com/wiki/Group "Group" article in SecondLife Wiki].<br />
<br />
== Components for the Groups ==<br />
<br />
The Groups functionality consists of the three components: '''Group Service''', '''Group Services Connector''' and '''Group Module'''. Group Server handles data for in-world groups(i.e. group infos, ranks or notices). In most cases, it connects to their database to persist them. On the other hand, the OpenSimulator handle in-world groups with Group Module, which implements IGroupsModule. It in turn calls Group Service Connector, which implements IGroupsServicesConnector, to retreive data from Group Service issuing xmlrpc calls.<br />
<br />
[[Image:GroupsComponents.png]]<br />
<br />
Thus, you will need to set up these three compornents to enable the Groups in your OpenSimulator. The following sections describe how to do that. Currently there are two known Group Services:<br />
* [http://code.google.com/p/flotsam/ Flotsam Project] : [[#XmlRpcGroups]]<br />
* [http://code.google.com/p/openmetaverse/wiki/SimianGrid SimianGrid Project] : [[#SimianGrid ]]<br />
You can even create your own Groups functionality by yourself, implementing IGroupsModule or/and IGroupServicesConnector.<br />
<br />
== Requirements ==<br />
<br />
If you want to run Group Services on your own, you need to know how to deploy your web applications on so-called web server, such as Apache or IIS.<br />
<br />
<br />
= XmlRpcGroups =<br />
<br />
== Database Settings ==<br />
<br />
First, create your database. If you don't even know how to install or login to MySQL, see [[Database Settings#MySQL Walkthrough]].<br />
Note: If your MySQL database uses the utf8 character set, you may receive errors when creating the tables needed for groups in the table creation step below. A MySQL database using the latin1 character set should not have that issue. <br />
<pre><br />
mysql> create database opensim_group;<br />
mysql> use opensim_group;<br />
mysql> create user 'opensim_group'@'localhost' identified by 'opensim_group_password';<br />
mysql> grant all on opensim_group.* to 'opensim_group'@'localhost';<br />
</pre><br />
<br />
== Getting XmlRpcGroups ==<br />
<br />
Download and extract the package from the following link.<br />
<br />
http://code.google.com/p/flotsam/wiki/XmlRpcGroups<br />
<br />
== Creating Tables ==<br />
<br />
Create tables inside your newly created database. In the package, you'll find 'groups.sql'. Run it.<br />
<pre><br />
mysql> source /(your_path_to_the_package)/groups.sql<br />
</pre><br />
It will create the tables for groups. If it succeed, the database has seven tables now. Note that the recent version(5.X) of mysql server may fail to create them. If so, change<br />
* ''timestamp(14)'' to ''timestamp''<br />
* ''TYPE=MyISAM'' to ''ENGINE=MyISAM''<br />
and try again.<br />
<br />
== Deploying XmlRpcGroups ==<br />
<br />
Deploy XmlRpcGroups php application to your web server.<br />
<br />
For IIS: Copy the XmlRpcGroupsServer folder to c:\inetpub\wwwroot<br />
<br />
== Configuring XmlRpcGroups ==<br />
<br />
Copy 'config.php.exmple' to 'config.php'. This file will be the configuration file for gorup service. At least, you need to fill in following properties like that:<br />
<pre><br />
$dbName = "opensim_group";<br />
$dbHost = "localhost";<br />
$dbPort = 3306;<br />
$dbUser = "opensim_group";<br />
$dbPassword ="opensim_group_password";<br />
</pre><br />
Optionally, you can set these parameters to ensure the security of xmlrpc service:<br />
<pre><br />
$groupWriteKey = 'group_write_key';<br />
$groupReadKey = 'group_read_key';<br />
</pre><br />
Note that if you want to enable UTF-8 characters in group descriptions, ranks or notices, you need to write this line in somewhere(between "<?php" and "?>") in config.php file to prevent them from getting garbled:<br />
<pre><br />
$xmlrpc_internalencoding = 'UTF-8'<br />
</pre><br />
<br />
== Configuring Your OpenSimulator ==<br />
<br />
Open OpenSim.ini file. In the [Groups] section, you'll find some properties. Change them so that it will look like that:<br />
<pre><br />
[Groups]<br />
;# {Enabled} {} {Enable groups?} {true false} false<br />
;; Enables the groups module<br />
Enabled = true<br />
<br />
;# {Module} {Enabled:true} {Groups module to use? (Use GroupsModule to use Flotsam/Simian)} {} Default<br />
;; This is the current groups stub in Region.CoreModules.Avatar.Groups.<br />
;; All the other settings below only really apply to the Flotsam/SimianGrid<br />
;; GroupsModule.<br />
;; This module can use a PHP XmlRpc server from the Flotsam project at<br />
;; http://code.google.com/p/flotsam/<br />
;; or from the SimianGrid project at http://code.google.com/p/openmetaverse<br />
Module = GroupsModule<br />
<br />
;# {MessagingEnabled} {Module:GroupsModule} {Is groups messaging enabled?} {true false} true<br />
;MessagingEnabled = true<br />
<br />
;# {MessagingModule} {MessagingEnabled:true} {Module to use for groups messaging} {GroupsMessagingModule} GroupsMessagingModule<br />
MessagingModule = GroupsMessagingModule<br />
<br />
;# {ServicesConnectorModule} {Module:GroupsModule} {Service connector to use for groups} {XmlRpcGroupsServicesConnector SimianGroupsServicesConnector} XmlRpcGroupsServicesConnector<br />
;; Service connectors to the Groups Service as used in the GroupsModule. Select one depending on<br />
;; whether you're using a Flotsam XmlRpc backend or a SimianGrid backend<br />
ServicesConnectorModule = XmlRpcGroupsServicesConnector<br />
<br />
;# {GroupsServerURI} {Module:GroupsModule} {Groups Server URI} {}<br />
;; URI for the groups services<br />
;; e.g. http://yourxmlrpcserver.com/xmlrpc.php for Flotsam XmlRpc<br />
;; or http://mygridserver.com:82/Grid/ for SimianGrid<br />
GroupsServerURI = "http://localhost/(context_path_to_deployed_xmlrpc_service)/xmlrpc.php"<br />
<br />
;# {NoticesEnabled} {Module:GroupsModule} {Enable group notices?} {true false} true<br />
;; Enable Group Notices<br />
; NoticesEnabled = true<br />
<br />
;; This makes the Groups modules very chatty on the console.<br />
;DebugEnabled = false<br />
<br />
;; XmlRpc Security settings. These must match those set on your backend<br />
;; groups service if the service is using these keys<br />
XmlRpcServiceReadKey = group_read_key<br />
XmlRpcServiceWriteKey = group_write_key<br />
</pre><br />
<br />
As of OpenSimulator 0.7.1.X, you need to uncomment MessagingModule or ServicesConnectorModule line even if you are using GroupsMessagingModule or XmlRpcGroupsServicesConnector([http://opensimulator.org/mantis/view.php?id=5543 #5543]).<br />
<br />
<br />
= SimianGrid =<br />
<br />
http://code.google.com/p/openmetaverse/wiki/Installation<br />
<br />
<!-- TODO --><br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/Enabling_GroupsEnabling Groups2011-11-04T23:35:54Z<p>Fleep: /* Database Settings */ - Note about errors during table creation if MySQL database uses the utf8 charset.</p>
<hr />
<div>{{Quicklinks}}<br />
= Groups Overview =<br />
<br />
== What is "Groups" in OpenSimulator? ==<br />
<br />
''Groups'' is one of the optional functionality of OpenSimulator, which enables the users to create grid-wide(or hypergrid-wide) community in your regions. For the general knowledge about the concept of Group or how to create your in-world group, see [http://wiki.secondlife.com/wiki/Group "Group" article in SecondLife Wiki].<br />
<br />
== Components for the Groups ==<br />
<br />
The Groups functionality consists of the three components: '''Group Service''', '''Group Services Connector''' and '''Group Module'''. Group Server handles data for in-world groups(i.e. group infos, ranks or notices). In most cases, it connects to their database to persist them. On the other hand, the OpenSimulator handle in-world groups with Group Module, which implements IGroupsModule. It in turn calls Group Service Connector, which implements IGroupsServicesConnector, to retreive data from Group Service issuing xmlrpc calls.<br />
<br />
[[Image:GroupsComponents.png]]<br />
<br />
Thus, you will need to set up these three compornents to enable the Groups in your OpenSimulator. The following sections describe how to do that. Currently there are two known Group Services:<br />
* [http://code.google.com/p/flotsam/ Flotsam Project] : [[#XmlRpcGroups]]<br />
* [http://code.google.com/p/openmetaverse/wiki/SimianGrid SimianGrid Project] : [[#SimianGrid ]]<br />
You can even create your own Groups functionality by yourself, implementing IGroupsModule or/and IGroupServicesConnector.<br />
<br />
== Requirements ==<br />
<br />
If you want to run Group Services on your own, you need to know how to deploy your web applications on so-called web server, such as Apache or IIS.<br />
<br />
<br />
= XmlRpcGroups =<br />
<br />
== Database Settings ==<br />
<br />
First, create your database. If you don't even know how to install or login to MySQL, see [[Database Settings#MySQL Walkthrough]].<br />
Note: If your MySQL database uses the utf8 character set, you may receive errors when creating the tables needed for groups in the table creation step below. A MySQL database using the latin1 character set should not have that issue. <br />
<pre><br />
mysql> create database opensim_group;<br />
mysql> use opensim_group;<br />
mysql> create user 'opensim_group'@'localhost' identified by 'opensim_group_password';<br />
mysql> grant all on opensim_group.* to 'opensim_group'@'localhost';<br />
</pre><br />
<br />
== Getting XmlRpcGroups ==<br />
<br />
Download and extract the package from the following link.<br />
<br />
http://code.google.com/p/flotsam/wiki/XmlRpcGroups<br />
<br />
== Creating Tables ==<br />
<br />
Create tables inside your newly created database. In the package, you'll find 'groups.sql'. Run it.<br />
<pre><br />
mysql> source /(your_path_to_the_package)/groups.sql<br />
</pre><br />
It will create the tables for groups. If it succeed, the database has seven tables now. Note that the recent version(5.X) of mysql server may fail to create them. If so, change<br />
* ''timestamp(14)'' to ''timestamp''<br />
* ''TYPE=MyISAM'' to ''ENGINE=MyISAM''<br />
and try again.<br />
<br />
== Deploying XmlRpcGroups ==<br />
<br />
Deploy XmlRpcGroups php application to your web server. <br />
<br />
== Configuring XmlRpcGroups ==<br />
<br />
Copy 'config.php.exmple' to 'config.php'. This file will be the configuration file for gorup service. At least, you need to fill in following properties like that:<br />
<pre><br />
$dbName = "opensim_group";<br />
$dbHost = "localhost";<br />
$dbPort = 3306;<br />
$dbUser = "opensim_group";<br />
$dbPassword ="opensim_group_password";<br />
</pre><br />
Optionally, you can set these parameters to ensure the security of xmlrpc service:<br />
<pre><br />
$groupWriteKey = 'group_write_key';<br />
$groupReadKey = 'group_read_key';<br />
</pre><br />
Note that if you want to enable UTF-8 characters in group descriptions, ranks or notices, you need to write this line in somewhere(between "<?php" and "?>") in config.php file to prevent them from getting garbled:<br />
<pre><br />
$xmlrpc_internalencoding = 'UTF-8'<br />
</pre><br />
<br />
== Configuring Your OpenSimulator ==<br />
<br />
Open OpenSim.ini file. In the [Groups] section, you'll find some properties. Change them so that it will look like that:<br />
<pre><br />
[Groups]<br />
;# {Enabled} {} {Enable groups?} {true false} false<br />
;; Enables the groups module<br />
Enabled = true<br />
<br />
;# {Module} {Enabled:true} {Groups module to use? (Use GroupsModule to use Flotsam/Simian)} {} Default<br />
;; This is the current groups stub in Region.CoreModules.Avatar.Groups.<br />
;; All the other settings below only really apply to the Flotsam/SimianGrid<br />
;; GroupsModule.<br />
;; This module can use a PHP XmlRpc server from the Flotsam project at<br />
;; http://code.google.com/p/flotsam/<br />
;; or from the SimianGrid project at http://code.google.com/p/openmetaverse<br />
Module = GroupsModule<br />
<br />
;# {MessagingEnabled} {Module:GroupsModule} {Is groups messaging enabled?} {true false} true<br />
;MessagingEnabled = true<br />
<br />
;# {MessagingModule} {MessagingEnabled:true} {Module to use for groups messaging} {GroupsMessagingModule} GroupsMessagingModule<br />
MessagingModule = GroupsMessagingModule<br />
<br />
;# {ServicesConnectorModule} {Module:GroupsModule} {Service connector to use for groups} {XmlRpcGroupsServicesConnector SimianGroupsServicesConnector} XmlRpcGroupsServicesConnector<br />
;; Service connectors to the Groups Service as used in the GroupsModule. Select one depending on<br />
;; whether you're using a Flotsam XmlRpc backend or a SimianGrid backend<br />
ServicesConnectorModule = XmlRpcGroupsServicesConnector<br />
<br />
;# {GroupsServerURI} {Module:GroupsModule} {Groups Server URI} {}<br />
;; URI for the groups services<br />
;; e.g. http://yourxmlrpcserver.com/xmlrpc.php for Flotsam XmlRpc<br />
;; or http://mygridserver.com:82/Grid/ for SimianGrid<br />
GroupsServerURI = "http://localhost/(context_path_to_deployed_xmlrpc_service)/xmlrpc.php"<br />
<br />
;# {NoticesEnabled} {Module:GroupsModule} {Enable group notices?} {true false} true<br />
;; Enable Group Notices<br />
; NoticesEnabled = true<br />
<br />
;; This makes the Groups modules very chatty on the console.<br />
;DebugEnabled = false<br />
<br />
;; XmlRpc Security settings. These must match those set on your backend<br />
;; groups service if the service is using these keys<br />
XmlRpcServiceReadKey = group_read_key<br />
XmlRpcServiceWriteKey = group_write_key<br />
</pre><br />
<br />
As of OpenSimulator 0.7.1.X, you need to uncomment MessagingModule or ServicesConnectorModule line even if you are using GroupsMessagingModule or XmlRpcGroupsServicesConnector([http://opensimulator.org/mantis/view.php?id=5543 #5543]).<br />
<br />
<br />
= SimianGrid =<br />
<br />
http://code.google.com/p/openmetaverse/wiki/Installation<br />
<br />
<!-- TODO --><br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/Installing_and_Running_HypergridInstalling and Running Hypergrid2011-10-24T13:27:30Z<p>Fleep: /* Linking regions (Optional) */</p>
<hr />
<div>{{Quicklinks}}<br />
<br />
== Installing & Running OpenSim in Hypergrid Mode ==<br />
The setup for hypergrid differs depending on whether you run OpenSim as a standalone or as a grid. There also came considerable changes with version 0.7. If you are using an older version 0.6.x of OpenSimulator, then refer to [[#Configuration for OpenSimulator 0.6.x]] further down this page.<br />
<br />
== Configuration ==<br />
In order for OpenSimulator to be accessible in the hypergrid, you must use an externally visible IP address or domain name. You also may need to set up port forwarding for all ports (TCP and UDP) that OpenSimulator and the regions use. Typically, these are port 8002 for an installation running in grid mode and port 9000 for standalones. Regions typically use ports starting at 9000. For more information, see [[Network Settings]].<br />
<br />
=== Standalone ===<br />
The configuration for hypergrid is activated in section [Architecture] in file OpenSim.ini. Ensure that the line for Include-HGStandalone is the only one that is uncommented in this section:<br />
<source lang="ini">[Architecture]<br />
;Include-Standalone = "config-include/Standalone.ini"<br />
Include-HGStandalone = "config-include/StandaloneHypergrid.ini"<br />
;Include-Grid = "config-include/Grid.ini"<br />
;Include-HGGrid = "config-include/GridHypergrid.ini"<br />
;Include-SimianGrid = "config-include/SimianGrid.ini"</source><br />
<br />
In StandaloneCommon.ini the network addresses in sections [LoginService] and [GatekeeperService] must be changed to your external network address:<br />
<source lang="ini">[LoginService]<br />
; ... (other settings in this section) ...<br />
HomeURI = "http://example.com:9000"<br />
GatekeeperURI = "http://example.com:9000"<br />
InventoryServerURI = "http://example.com:9000"<br />
AssetServerURI = "http://example.com:9000"<br />
<br />
[GatekeeperService]<br />
; ... (other settings in this section) ...<br />
ExternalName = "http://example.com:9000"</source><br />
<br />
If you want to use a different port with these addresses, then you must adjust the HTTP listener port in section [Network] in OpenSim.ini, too:<br />
<source lang="ini">[Network]<br />
; ... (other settings in this section) ...<br />
http_listener_port = 9000<br />
</source><br />
<br />
As a last step, the regions must be configured according to the previous changes. See [[#Region Setup for both Grid and Standalone]].<br />
<br />
=== Grid ===<br />
To enable hypergrid for a grid, both the Robust server and the region servers (simulators) must be configured approprietly.<br />
<br />
==== Robust Server ====<br />
The Robust server is started with configuration file Robust.HG.ini instead of Robust.ini. If this file does not yet exist in your installation, create it by making a copy of Robust.HG.ini.example. Make the changes appropriate for your environment (e.g. adjust the database connection string). For hypergrid, the following settings are relevant:<br />
<br />
<source lang="ini">[LoginService]<br />
; ... (other settings in this section) ...<br />
HomeURI = "http://example.com:8002"<br />
GatekeeperURI = "http://example.com:8002"<br />
InventoryServerURI = "http://example.com:8002"<br />
AssetServerURI = "http://example.com:8002"<br />
<br />
[GatekeeperService]<br />
; ... (other settings in this section) ...<br />
ExternalName = "http://example.com:8002"<br />
</source><br />
<br />
If you want to change the port(s) used with these addresses, you will also need to adjust the ports in parameter ''''ServiceConnectors'''' in section [Startup] and probably the port configured in section [Network] as well.<br />
<br />
After these adjustments, the Robust server can be started. On Windows/.NET:<br />
Robust -inifile=Robust.HG.ini<br />
Or, with Mono (e.g. on Linux or OSX):<br />
mono Robust.exe -inifile=Robust.HG.ini<br />
<br />
==== Simulator ====<br />
The region servers (simulators) that connect to the Robust server read their configuration from file OpenSim.ini. To activate hypergrid for them, the line for Include-HGGrid in section [Architecture] must be uncommented:<br />
<source lang="ini">[Architecture]<br />
;Include-Standalone = "config-include/Standalone.ini"<br />
;Include-HGStandalone = "config-include/StandaloneHypergrid.ini"<br />
;Include-Grid = "config-include/Grid.ini"<br />
Include-HGGrid = "config-include/GridHypergrid.ini"<br />
;Include-SimianGrid = "config-include/SimianGrid.ini"<br />
</source><br />
<br />
=== Region Setup for both Grid and Standalone ===<br />
Finally, all your regions must use the same external address that is set for GatekeeperService, for example:<br />
<source lang="ini">[Region One]<br />
; ... (other settings in this section) ...<br />
ExternalHostName = "example.com"<br />
</source><br />
<br />
For the ports which are used by your regions, TCP and UDP requests must be forwarded through any firewall that is securing your network.<br />
<br />
== Configuration for OpenSimulator 0.6.x ==<br />
{{obsolete}}<br />
=== Installing ===<br />
<br />
Checkout OpenSim, prebuild and build as normal or Download and install Binary Packages from the [[Main Page|MAIN&nbsp;Page ]]<br>If you're running your opensim in '''Grid Mode''' mode with&nbsp;servers on other machines, you&nbsp;only need to modify your OpenSim.ini to enable HyperGrid. <br />
<br />
If you're running in standalone and you want it to be network-able, or if you have your grid on loopback (127.0.0.1) change all the [Network] server addresses to. See below. <br />
<br />
=== EXAMPLE Network Sections ===<br />
<br />
==== Default Example, Network Settings for a Stand Alone: ====<br />
<br />
<source lang="ini">[Network]<br />
http_listener_port = 9000<br />
<br />
grid_server_url = "http://example.com:9000"<br />
<br />
grid_send_key = null<br />
grid_recv_key = null<br />
<br />
user_server_url = "http://example.com:9000"<br />
<br />
user_send_key = null<br />
user_recv_key = null<br />
<br />
asset_server_url = "http://example.com:9000"<br />
<br />
inventory_server_url = "http://example.com:9000"<br />
messaging_server_url = "http://example.com:9000"</source> <br />
<br />
==== Default Example, Network Settings for a Grided Server: ====<br />
<br />
<source lang="ini">[Network]<br />
http_listener_port = 9000<br />
<br />
grid_server_url = "http://example.com:8001"<br />
grid_send_key = null<br />
grid_recv_key = null<br />
<br />
user_server_url = "http://example.com:8002"<br />
user_send_key = null<br />
user_recv_key = null<br />
<br />
asset_server_url = "http://example.com:8003"<br />
inventory_server_url = "http://example.com:8003"<br />
messaging_server_url = "http://example.com:8006"</source> <br />
<br />
==== Network Settings&nbsp;for OSGrid Attched Servers: ====<br />
<br />
<source lang="ini">[Network]<br />
http_listener_port = 9000<br />
grid_server_url = "http://osgrid.org:8001" ;default 8003<br />
grid_send_key = "1234"<br />
grid_recv_key = "1234"<br />
<br />
user_server_url = "http://osgrid.org:8002" <br />
user_send_key = "1234"<br />
user_recv_key = "1234"<br />
<br />
asset_server_url = "http://assets.osgrid.org:8003" <br />
inventory_server_url = "http://osgrid.org:8004" ;default 8003<br />
messaging_server_url = "http://osgrid.org:8006"</source> <br />
<br />
==== Modifications needed to be applied to OpenSim.ini to enable Hypergrid ====<br />
<br />
- Change the following line at the top of the OpenSim.ini <br />
<pre>hypergrid = false to true</pre><br />
- NEXT, Add or Modify the ### WORLD MAP Section as shown <br />
<br />
<source lang="ini">; ##<br />
; ## WORLD MAP<br />
; ##<br />
<br />
WorldMapModule = "WorldMap"<br />
MapImageModule = "MapImageModule"<br />
WorldMapModule = "HGWorldMapModule" ;NOT INCLUDED IN DEFAULT OpenSim.ini.EXAMPLE</source> <br />
<br />
''Information: HGWorldMapModule will, after teleporting to another grid, clean up tiles in your map left over from the grid on which you were previously.'' <br />
<br />
- NEXT, Modify the [Archictecture] Section at the bottom <br />
<br />
Uncomment the appropriate Include-HG* = line by removing the semi colon and making sure that is the only ONE uncommented. (example shows for a Stand Alone HG enabled installation) <br />
<br />
<source lang="ini">[Architecture]<br />
;Include-Standalone = "config-include/Standalone.ini" ; DEFAULT UNCOMMENTED<br />
Include-HGStandalone = "config-include/StandaloneHypergrid.ini"<br />
;Include-Grid = "config-include/Grid.ini"<br />
;Include-HGGrid = "config-include/GridHypergrid.ini"</source>&nbsp; <br />
<br />
Your OpenSimulator instance should now be ready for inbound &amp; outbound Hypergrid use<br />
<br />
== The 4096 Regions Limit ==<br />
Due to a viewer issue, teleports to destinations that are more than 4096 regions away in any direction will not work as expected. Most viewers will do the teleport but the destination region will not be rendered and thus remain invisible to you. What this means in practice is that if you wish to teleport from a region located at cell coordinates (1000, 1000) you cannot go beyond (5095, 5095). To reach destinations that are placed at farer locations, you should either place your own region closer to the destination, or use some intermediate region that is reachable from both your region and the destination region.<br />
<br />
Refer to [[Public Hypergrid Nodes]] to see some known grids and standalones and where they are located. <br />
<br />
== Important Notes ==<br />
Make sure you have a 'home' set. If your home region doesn't exist, the hyperlink TPs may not work. To set your home, go to one of your local regions and "Set Home" from the viewer. <br />
<br />
To Enable scripted Teleporting between regions, standalone, HyperGrid etc, you can use osTeleportAgent function, Example here: [[OsTeleportAgent|OsTeleportAgent]]<br />
<br />
== Linking regions (Optional) ==<br />
<br />
Linking hypergrid regions permits users on your system to easily hypergrid teleport to other grids via the viewer map. For example, if you run Grid A and your friend runs Grid B and both grids are Hypergrid enabled, you can "link" to a region on Grid B from your ROBUST console to create a persistent hypergrid link to your friend's Grid B that appears on the viewer map. <br />
<br />
After creating the link using one of the methods below, your users on Grid A will see a map tile showing the connection to GridB on the viewer map, and can teleport to Grid B by double clicking the map tile to teleport.<br />
<br />
You can view all hypergrid linked regions by typing the "show hyperlinks" command on the ROBUST console, and remove linked regions using the unlink-region command described below.<br />
<br />
=== Method 1 ===<br />
<br />
On the console, type for example:<br />
<pre>link-region &lt;Xloc&gt; &lt;Yloc&gt; http://osl2.nac.uci.edu:9006/</pre><br />
Use Xloc and Yloc that make sense to your world, i.e. close to your regions, but not adjacent. Replace <nowiki>http://osl2.nac.uci.edu:9006/</nowiki> with the URL (i.e. protocol, domain name/ip address, and http_listener_port) of the simulator where the region is running you want to link to.<br />
You can link to a specific region within an instance, by using the name of the region at the end, for example: <br />
<pre>link-region &lt;Xloc&gt; &lt;Yloc&gt; http://osl2.nac.uci.edu:9006/ UCI Welcome</pre><br />
The above syntax is the preferred one for this console command starting with revision r/14611 (commit 72748746; this will be in release 0.7.1). The following syntax was used before and is still supported but deprecated in current (development) versions of OpenSimulator:<br />
<pre>link-region &lt;Xloc&gt; &lt;Yloc&gt; osl2.nac.uci.edu:9006</pre> or <pre>link-region 997 997 osl2.nac.uci.edu:9006:UCI Welcome</pre><br />
Please note that this older syntax uses just the hostname without a protocol specification like <nowiki>http://</nowiki> and a colon instead of a space to append a region name.<br />
<br />
=== Method 2 ===<br />
<br />
There is also some initial support for reading the links from a xml file. <br />
<br />
Use the console command: link-region &lt;URI&gt; [&lt;excludeList&gt;] <br />
<br />
The uri can be either the path of a local xml file or a xml document on a http server. <br />
<br />
The format of the xml file is: <br />
<br />
<source lang="xml"><Nini><br />
<Section Name="Region1"> <br />
<Key Name="xloc" Value="1002"/><br />
<Key Name="yloc" Value="1006" /><br />
<Key Name="externalPort" Value="9006" /><br />
<Key Name="externalHostName" Value="osl2.nac.uci.edu" /><br />
<Key Name="localName" Value="OSGrid-Gateway" /><br />
<Key Name="real-xloc" Value="10222"/> //optional field that gives the region's real location on its home grid<br />
<Key Name="real-yloc" Value="10265" /> //optional field that gives the region's real location on its home grid<br />
</Section><br />
<Section Name="Region2"> <br />
...<br />
</Section><br />
...<br />
</Nini></source> <br />
<br />
[Note] The section names can be anything you want, but they all should be different and have no spaces in the name. <br />
<br />
==== ExcludeList: ====<br />
<br />
The exclude list is a single string paramater with the format: excludeList:&lt;SectionName&gt;[;&lt;SectionName&gt;] <br />
<br />
This means that while reading from the xml file any sections that are listed in the excludeList will be ignored and no HyperGrid link created for them. <br />
<br />
This could allow, link lists to be created on a webserver that everyone could add their own regions to, and then they just make sure they add their own section name(s) to the exclude list on their own region(s). <br />
<br />
So for example, someone might create a editable online list for the up coming OpenSimulator's 2nd birthday. Which might look something like: <br />
<br />
<source lang="xml"><Nini><br />
<Section Name="OSGrid-Party"> <br />
<Key Name="xloc" Value="1002"/><br />
<Key Name="yloc" Value="1006" /><br />
<Key Name="externalPort" Value="9006" /><br />
<Key Name="externalHostName" Value="osl2.nac.uci.edu" /><br />
<Key Name="localName" Value="OSGrid-Gateway" /><br />
</Section><br />
<Section Name="UCIGrid-Party"> <br />
...<br />
</Section><br />
</Nini></source> I could then add my own region to the list with the section name "MW-Party". Then when I startup that region that I want to be part of this hypergrid, I use the command: <br />
<pre>"link-region &lt;URI of xml file&gt; excludeList:MW-Party"</pre><br />
This is so that my region doesn't try to create a hyper link to itself. <br />
<br />
=== Method 3 (dynamic) ===<br />
<br />
Starting in r8193, if you're in an HG-enabled region, you'll be able to dynamically link sims, and TP there, in any one of these ways (and probably more). All you need to know is the target address, e.g. from the list below. <br />
<br />
1) Type for example secondlife://ucigrid04.nacs.uci.edu:9007/ in the chat box, pull up the chat history and click on that link <br />
<br />
2) Pull up the map and search for things like ucigrid04.nacs.uci.edu:9007 <br />
<br />
3) Using the embedded browser visit pages that have links like '''secondlife://ucigrid04.nacs.uci.edu:9007'''/ (there's one up at http://www.ics.uci.edu/~lopes/hypergrid/test.html) <br />
<br />
Again, you can link to a specific region within an instance by adding the name of that region at the end, like this: '''secondlife://ucigrid04.nacs.uci.edu:9007:Gateway 7000/''' <br />
<br />
=== Checking the 4096 Regions Limit ===<br />
Due to the [[#The 4096 Regions Limit|4096 Regions Limit]], there is a check in OpenSimulator since version 0.7.0.1 which verifies that the intended link will be within reach of any of your regions. If none of the regions in your grid or standalone is located within a distance radius of 4096 regions from the region to be linked, then the link will be rejected. You can disable this check in StandaloneCommon.ini (for standalones) or Robust.HG.ini (for grids) with<br />
<source lang="ini">[GridService]<br />
Check4096 = false</source><br />
<br />
=== Persistent Linked Regions ===<br />
With grid mode, methods 1 and 2 will work on both the Robust console and the region console. On the region console, linked regions will not be stored in the database and will vanish when the region is shut down. Regions that are linked on the Robust console will be persistent over restarts until they are explicitly removed with unlink-region.<br />
<br />
== Listing linked regions ==<br />
<br />
To see a list of all linked regions, use the following command on the console (available since 0.7.1 r/13457, also in 0.7-post-fixes):<br />
<pre>show hyperlinks</pre><br />
<br />
== Unlinking regions ==<br />
<br />
On the console, use the command: <br />
<pre>unlink-region &lt;local region name&gt;</pre><br />
<br />
As local region name you should use what command <tt>show hyperlinks</tt> shows for the region that you want to unlink, for example<br />
<br />
<pre>unlink-region http://osl2.nac.uci.edu:9006/</pre><br />
<br />
With OpenSimulator revisions before r/14611 (i.e. before release 0.7.1), the syntax is a little different, for example<br />
<pre>unlink-region osl2.nac.uci.edu:9006</pre><br />
<br />
Please note that region names can only have a maximum length of 32 characters when using MySQL as a database. If a linked region has a longer name, it will be truncated. The unlink-region command will only find a region, if the name is also truncated to a maximum length of 32 characters. This limit has been extended to 128 characters for the full local region name in OpenSimulator 0.7.1 (since r/14611).<br />
<br />
== Additional References ==<br />
<br />
Implemented osFunctions: [[OSSL Implemented|OSSL Implemented]] <br />
<br />
Enabling osFunctions: [[OSSL Enabling Functions|OSSL Enabling Functions]] <br />
<br />
HyperGrid Security: [[Hypergrid Security|Hypergrid Security]] <br />
<br />
Banning Foreign Users in Hypergrid: [[Banning Foreign Users in Hypergrid|Banning Foreign Users in Hypergrid]] <br />
<br />
Public HyperGrid Nodes Listing: [[Public Hypergrid Nodes|Public Hypergrid Nodes]] <br />
<br />
Hypergrid Inventory Access: [[Hypergrid Inventory Access|Hypergrid Inventory Access (proposal)]] <br />
<br />
CATEGORY: [[:Category:Hypergrid|Hypergrid]]<br><br />
<br />
<br />
[[Category:Hypergrid]]</div>Fleephttp://opensimulator.org/wiki/Installing_and_Running_HypergridInstalling and Running Hypergrid2011-10-24T13:25:39Z<p>Fleep: /* Linking regions (Optional) */</p>
<hr />
<div>{{Quicklinks}}<br />
<br />
== Installing & Running OpenSim in Hypergrid Mode ==<br />
The setup for hypergrid differs depending on whether you run OpenSim as a standalone or as a grid. There also came considerable changes with version 0.7. If you are using an older version 0.6.x of OpenSimulator, then refer to [[#Configuration for OpenSimulator 0.6.x]] further down this page.<br />
<br />
== Configuration ==<br />
In order for OpenSimulator to be accessible in the hypergrid, you must use an externally visible IP address or domain name. You also may need to set up port forwarding for all ports (TCP and UDP) that OpenSimulator and the regions use. Typically, these are port 8002 for an installation running in grid mode and port 9000 for standalones. Regions typically use ports starting at 9000. For more information, see [[Network Settings]].<br />
<br />
=== Standalone ===<br />
The configuration for hypergrid is activated in section [Architecture] in file OpenSim.ini. Ensure that the line for Include-HGStandalone is the only one that is uncommented in this section:<br />
<source lang="ini">[Architecture]<br />
;Include-Standalone = "config-include/Standalone.ini"<br />
Include-HGStandalone = "config-include/StandaloneHypergrid.ini"<br />
;Include-Grid = "config-include/Grid.ini"<br />
;Include-HGGrid = "config-include/GridHypergrid.ini"<br />
;Include-SimianGrid = "config-include/SimianGrid.ini"</source><br />
<br />
In StandaloneCommon.ini the network addresses in sections [LoginService] and [GatekeeperService] must be changed to your external network address:<br />
<source lang="ini">[LoginService]<br />
; ... (other settings in this section) ...<br />
HomeURI = "http://example.com:9000"<br />
GatekeeperURI = "http://example.com:9000"<br />
InventoryServerURI = "http://example.com:9000"<br />
AssetServerURI = "http://example.com:9000"<br />
<br />
[GatekeeperService]<br />
; ... (other settings in this section) ...<br />
ExternalName = "http://example.com:9000"</source><br />
<br />
If you want to use a different port with these addresses, then you must adjust the HTTP listener port in section [Network] in OpenSim.ini, too:<br />
<source lang="ini">[Network]<br />
; ... (other settings in this section) ...<br />
http_listener_port = 9000<br />
</source><br />
<br />
As a last step, the regions must be configured according to the previous changes. See [[#Region Setup for both Grid and Standalone]].<br />
<br />
=== Grid ===<br />
To enable hypergrid for a grid, both the Robust server and the region servers (simulators) must be configured approprietly.<br />
<br />
==== Robust Server ====<br />
The Robust server is started with configuration file Robust.HG.ini instead of Robust.ini. If this file does not yet exist in your installation, create it by making a copy of Robust.HG.ini.example. Make the changes appropriate for your environment (e.g. adjust the database connection string). For hypergrid, the following settings are relevant:<br />
<br />
<source lang="ini">[LoginService]<br />
; ... (other settings in this section) ...<br />
HomeURI = "http://example.com:8002"<br />
GatekeeperURI = "http://example.com:8002"<br />
InventoryServerURI = "http://example.com:8002"<br />
AssetServerURI = "http://example.com:8002"<br />
<br />
[GatekeeperService]<br />
; ... (other settings in this section) ...<br />
ExternalName = "http://example.com:8002"<br />
</source><br />
<br />
If you want to change the port(s) used with these addresses, you will also need to adjust the ports in parameter ''''ServiceConnectors'''' in section [Startup] and probably the port configured in section [Network] as well.<br />
<br />
After these adjustments, the Robust server can be started. On Windows/.NET:<br />
Robust -inifile=Robust.HG.ini<br />
Or, with Mono (e.g. on Linux or OSX):<br />
mono Robust.exe -inifile=Robust.HG.ini<br />
<br />
==== Simulator ====<br />
The region servers (simulators) that connect to the Robust server read their configuration from file OpenSim.ini. To activate hypergrid for them, the line for Include-HGGrid in section [Architecture] must be uncommented:<br />
<source lang="ini">[Architecture]<br />
;Include-Standalone = "config-include/Standalone.ini"<br />
;Include-HGStandalone = "config-include/StandaloneHypergrid.ini"<br />
;Include-Grid = "config-include/Grid.ini"<br />
Include-HGGrid = "config-include/GridHypergrid.ini"<br />
;Include-SimianGrid = "config-include/SimianGrid.ini"<br />
</source><br />
<br />
=== Region Setup for both Grid and Standalone ===<br />
Finally, all your regions must use the same external address that is set for GatekeeperService, for example:<br />
<source lang="ini">[Region One]<br />
; ... (other settings in this section) ...<br />
ExternalHostName = "example.com"<br />
</source><br />
<br />
For the ports which are used by your regions, TCP and UDP requests must be forwarded through any firewall that is securing your network.<br />
<br />
== Configuration for OpenSimulator 0.6.x ==<br />
{{obsolete}}<br />
=== Installing ===<br />
<br />
Checkout OpenSim, prebuild and build as normal or Download and install Binary Packages from the [[Main Page|MAIN&nbsp;Page ]]<br>If you're running your opensim in '''Grid Mode''' mode with&nbsp;servers on other machines, you&nbsp;only need to modify your OpenSim.ini to enable HyperGrid. <br />
<br />
If you're running in standalone and you want it to be network-able, or if you have your grid on loopback (127.0.0.1) change all the [Network] server addresses to. See below. <br />
<br />
=== EXAMPLE Network Sections ===<br />
<br />
==== Default Example, Network Settings for a Stand Alone: ====<br />
<br />
<source lang="ini">[Network]<br />
http_listener_port = 9000<br />
<br />
grid_server_url = "http://example.com:9000"<br />
<br />
grid_send_key = null<br />
grid_recv_key = null<br />
<br />
user_server_url = "http://example.com:9000"<br />
<br />
user_send_key = null<br />
user_recv_key = null<br />
<br />
asset_server_url = "http://example.com:9000"<br />
<br />
inventory_server_url = "http://example.com:9000"<br />
messaging_server_url = "http://example.com:9000"</source> <br />
<br />
==== Default Example, Network Settings for a Grided Server: ====<br />
<br />
<source lang="ini">[Network]<br />
http_listener_port = 9000<br />
<br />
grid_server_url = "http://example.com:8001"<br />
grid_send_key = null<br />
grid_recv_key = null<br />
<br />
user_server_url = "http://example.com:8002"<br />
user_send_key = null<br />
user_recv_key = null<br />
<br />
asset_server_url = "http://example.com:8003"<br />
inventory_server_url = "http://example.com:8003"<br />
messaging_server_url = "http://example.com:8006"</source> <br />
<br />
==== Network Settings&nbsp;for OSGrid Attched Servers: ====<br />
<br />
<source lang="ini">[Network]<br />
http_listener_port = 9000<br />
grid_server_url = "http://osgrid.org:8001" ;default 8003<br />
grid_send_key = "1234"<br />
grid_recv_key = "1234"<br />
<br />
user_server_url = "http://osgrid.org:8002" <br />
user_send_key = "1234"<br />
user_recv_key = "1234"<br />
<br />
asset_server_url = "http://assets.osgrid.org:8003" <br />
inventory_server_url = "http://osgrid.org:8004" ;default 8003<br />
messaging_server_url = "http://osgrid.org:8006"</source> <br />
<br />
==== Modifications needed to be applied to OpenSim.ini to enable Hypergrid ====<br />
<br />
- Change the following line at the top of the OpenSim.ini <br />
<pre>hypergrid = false to true</pre><br />
- NEXT, Add or Modify the ### WORLD MAP Section as shown <br />
<br />
<source lang="ini">; ##<br />
; ## WORLD MAP<br />
; ##<br />
<br />
WorldMapModule = "WorldMap"<br />
MapImageModule = "MapImageModule"<br />
WorldMapModule = "HGWorldMapModule" ;NOT INCLUDED IN DEFAULT OpenSim.ini.EXAMPLE</source> <br />
<br />
''Information: HGWorldMapModule will, after teleporting to another grid, clean up tiles in your map left over from the grid on which you were previously.'' <br />
<br />
- NEXT, Modify the [Archictecture] Section at the bottom <br />
<br />
Uncomment the appropriate Include-HG* = line by removing the semi colon and making sure that is the only ONE uncommented. (example shows for a Stand Alone HG enabled installation) <br />
<br />
<source lang="ini">[Architecture]<br />
;Include-Standalone = "config-include/Standalone.ini" ; DEFAULT UNCOMMENTED<br />
Include-HGStandalone = "config-include/StandaloneHypergrid.ini"<br />
;Include-Grid = "config-include/Grid.ini"<br />
;Include-HGGrid = "config-include/GridHypergrid.ini"</source>&nbsp; <br />
<br />
Your OpenSimulator instance should now be ready for inbound &amp; outbound Hypergrid use<br />
<br />
== The 4096 Regions Limit ==<br />
Due to a viewer issue, teleports to destinations that are more than 4096 regions away in any direction will not work as expected. Most viewers will do the teleport but the destination region will not be rendered and thus remain invisible to you. What this means in practice is that if you wish to teleport from a region located at cell coordinates (1000, 1000) you cannot go beyond (5095, 5095). To reach destinations that are placed at farer locations, you should either place your own region closer to the destination, or use some intermediate region that is reachable from both your region and the destination region.<br />
<br />
Refer to [[Public Hypergrid Nodes]] to see some known grids and standalones and where they are located. <br />
<br />
== Important Notes ==<br />
Make sure you have a 'home' set. If your home region doesn't exist, the hyperlink TPs may not work. To set your home, go to one of your local regions and "Set Home" from the viewer. <br />
<br />
To Enable scripted Teleporting between regions, standalone, HyperGrid etc, you can use osTeleportAgent function, Example here: [[OsTeleportAgent|OsTeleportAgent]]<br />
<br />
== Linking regions (Optional) ==<br />
<br />
Linking hypergrid regions permits users on your system to easily hypergrid teleport to other grids via the viewer map. For example, if you run Grid A and your friend runs Grid B and both grids are Hypergrid enabled, you can "link" to a region on Grid B from your ROBUST console to create a persistent hypergrid link to your friend's Grid B that appears on the viewer map. <br />
<br />
After creating the link using one of the methods below, your users on Grid A will see a map tile showing the connection to GridB on the viewer map, and can teleport to GridB by double clicking the map tile to teleport.<br />
<br />
=== Method 1 ===<br />
<br />
On the console, type for example:<br />
<pre>link-region &lt;Xloc&gt; &lt;Yloc&gt; http://osl2.nac.uci.edu:9006/</pre><br />
Use Xloc and Yloc that make sense to your world, i.e. close to your regions, but not adjacent. Replace <nowiki>http://osl2.nac.uci.edu:9006/</nowiki> with the URL (i.e. protocol, domain name/ip address, and http_listener_port) of the simulator where the region is running you want to link to.<br />
You can link to a specific region within an instance, by using the name of the region at the end, for example: <br />
<pre>link-region &lt;Xloc&gt; &lt;Yloc&gt; http://osl2.nac.uci.edu:9006/ UCI Welcome</pre><br />
The above syntax is the preferred one for this console command starting with revision r/14611 (commit 72748746; this will be in release 0.7.1). The following syntax was used before and is still supported but deprecated in current (development) versions of OpenSimulator:<br />
<pre>link-region &lt;Xloc&gt; &lt;Yloc&gt; osl2.nac.uci.edu:9006</pre> or <pre>link-region 997 997 osl2.nac.uci.edu:9006:UCI Welcome</pre><br />
Please note that this older syntax uses just the hostname without a protocol specification like <nowiki>http://</nowiki> and a colon instead of a space to append a region name.<br />
<br />
=== Method 2 ===<br />
<br />
There is also some initial support for reading the links from a xml file. <br />
<br />
Use the console command: link-region &lt;URI&gt; [&lt;excludeList&gt;] <br />
<br />
The uri can be either the path of a local xml file or a xml document on a http server. <br />
<br />
The format of the xml file is: <br />
<br />
<source lang="xml"><Nini><br />
<Section Name="Region1"> <br />
<Key Name="xloc" Value="1002"/><br />
<Key Name="yloc" Value="1006" /><br />
<Key Name="externalPort" Value="9006" /><br />
<Key Name="externalHostName" Value="osl2.nac.uci.edu" /><br />
<Key Name="localName" Value="OSGrid-Gateway" /><br />
<Key Name="real-xloc" Value="10222"/> //optional field that gives the region's real location on its home grid<br />
<Key Name="real-yloc" Value="10265" /> //optional field that gives the region's real location on its home grid<br />
</Section><br />
<Section Name="Region2"> <br />
...<br />
</Section><br />
...<br />
</Nini></source> <br />
<br />
[Note] The section names can be anything you want, but they all should be different and have no spaces in the name. <br />
<br />
==== ExcludeList: ====<br />
<br />
The exclude list is a single string paramater with the format: excludeList:&lt;SectionName&gt;[;&lt;SectionName&gt;] <br />
<br />
This means that while reading from the xml file any sections that are listed in the excludeList will be ignored and no HyperGrid link created for them. <br />
<br />
This could allow, link lists to be created on a webserver that everyone could add their own regions to, and then they just make sure they add their own section name(s) to the exclude list on their own region(s). <br />
<br />
So for example, someone might create a editable online list for the up coming OpenSimulator's 2nd birthday. Which might look something like: <br />
<br />
<source lang="xml"><Nini><br />
<Section Name="OSGrid-Party"> <br />
<Key Name="xloc" Value="1002"/><br />
<Key Name="yloc" Value="1006" /><br />
<Key Name="externalPort" Value="9006" /><br />
<Key Name="externalHostName" Value="osl2.nac.uci.edu" /><br />
<Key Name="localName" Value="OSGrid-Gateway" /><br />
</Section><br />
<Section Name="UCIGrid-Party"> <br />
...<br />
</Section><br />
</Nini></source> I could then add my own region to the list with the section name "MW-Party". Then when I startup that region that I want to be part of this hypergrid, I use the command: <br />
<pre>"link-region &lt;URI of xml file&gt; excludeList:MW-Party"</pre><br />
This is so that my region doesn't try to create a hyper link to itself. <br />
<br />
=== Method 3 (dynamic) ===<br />
<br />
Starting in r8193, if you're in an HG-enabled region, you'll be able to dynamically link sims, and TP there, in any one of these ways (and probably more). All you need to know is the target address, e.g. from the list below. <br />
<br />
1) Type for example secondlife://ucigrid04.nacs.uci.edu:9007/ in the chat box, pull up the chat history and click on that link <br />
<br />
2) Pull up the map and search for things like ucigrid04.nacs.uci.edu:9007 <br />
<br />
3) Using the embedded browser visit pages that have links like '''secondlife://ucigrid04.nacs.uci.edu:9007'''/ (there's one up at http://www.ics.uci.edu/~lopes/hypergrid/test.html) <br />
<br />
Again, you can link to a specific region within an instance by adding the name of that region at the end, like this: '''secondlife://ucigrid04.nacs.uci.edu:9007:Gateway 7000/''' <br />
<br />
=== Checking the 4096 Regions Limit ===<br />
Due to the [[#The 4096 Regions Limit|4096 Regions Limit]], there is a check in OpenSimulator since version 0.7.0.1 which verifies that the intended link will be within reach of any of your regions. If none of the regions in your grid or standalone is located within a distance radius of 4096 regions from the region to be linked, then the link will be rejected. You can disable this check in StandaloneCommon.ini (for standalones) or Robust.HG.ini (for grids) with<br />
<source lang="ini">[GridService]<br />
Check4096 = false</source><br />
<br />
=== Persistent Linked Regions ===<br />
With grid mode, methods 1 and 2 will work on both the Robust console and the region console. On the region console, linked regions will not be stored in the database and will vanish when the region is shut down. Regions that are linked on the Robust console will be persistent over restarts until they are explicitly removed with unlink-region.<br />
<br />
== Listing linked regions ==<br />
<br />
To see a list of all linked regions, use the following command on the console (available since 0.7.1 r/13457, also in 0.7-post-fixes):<br />
<pre>show hyperlinks</pre><br />
<br />
== Unlinking regions ==<br />
<br />
On the console, use the command: <br />
<pre>unlink-region &lt;local region name&gt;</pre><br />
<br />
As local region name you should use what command <tt>show hyperlinks</tt> shows for the region that you want to unlink, for example<br />
<br />
<pre>unlink-region http://osl2.nac.uci.edu:9006/</pre><br />
<br />
With OpenSimulator revisions before r/14611 (i.e. before release 0.7.1), the syntax is a little different, for example<br />
<pre>unlink-region osl2.nac.uci.edu:9006</pre><br />
<br />
Please note that region names can only have a maximum length of 32 characters when using MySQL as a database. If a linked region has a longer name, it will be truncated. The unlink-region command will only find a region, if the name is also truncated to a maximum length of 32 characters. This limit has been extended to 128 characters for the full local region name in OpenSimulator 0.7.1 (since r/14611).<br />
<br />
== Additional References ==<br />
<br />
Implemented osFunctions: [[OSSL Implemented|OSSL Implemented]] <br />
<br />
Enabling osFunctions: [[OSSL Enabling Functions|OSSL Enabling Functions]] <br />
<br />
HyperGrid Security: [[Hypergrid Security|Hypergrid Security]] <br />
<br />
Banning Foreign Users in Hypergrid: [[Banning Foreign Users in Hypergrid|Banning Foreign Users in Hypergrid]] <br />
<br />
Public HyperGrid Nodes Listing: [[Public Hypergrid Nodes|Public Hypergrid Nodes]] <br />
<br />
Hypergrid Inventory Access: [[Hypergrid Inventory Access|Hypergrid Inventory Access (proposal)]] <br />
<br />
CATEGORY: [[:Category:Hypergrid|Hypergrid]]<br><br />
<br />
<br />
[[Category:Hypergrid]]</div>Fleephttp://opensimulator.org/wiki/Installing_and_Running_HypergridInstalling and Running Hypergrid2011-10-24T13:24:56Z<p>Fleep: /* Linking regions (Optional) */ - added description of what linking a region actually does..</p>
<hr />
<div>{{Quicklinks}}<br />
<br />
== Installing & Running OpenSim in Hypergrid Mode ==<br />
The setup for hypergrid differs depending on whether you run OpenSim as a standalone or as a grid. There also came considerable changes with version 0.7. If you are using an older version 0.6.x of OpenSimulator, then refer to [[#Configuration for OpenSimulator 0.6.x]] further down this page.<br />
<br />
== Configuration ==<br />
In order for OpenSimulator to be accessible in the hypergrid, you must use an externally visible IP address or domain name. You also may need to set up port forwarding for all ports (TCP and UDP) that OpenSimulator and the regions use. Typically, these are port 8002 for an installation running in grid mode and port 9000 for standalones. Regions typically use ports starting at 9000. For more information, see [[Network Settings]].<br />
<br />
=== Standalone ===<br />
The configuration for hypergrid is activated in section [Architecture] in file OpenSim.ini. Ensure that the line for Include-HGStandalone is the only one that is uncommented in this section:<br />
<source lang="ini">[Architecture]<br />
;Include-Standalone = "config-include/Standalone.ini"<br />
Include-HGStandalone = "config-include/StandaloneHypergrid.ini"<br />
;Include-Grid = "config-include/Grid.ini"<br />
;Include-HGGrid = "config-include/GridHypergrid.ini"<br />
;Include-SimianGrid = "config-include/SimianGrid.ini"</source><br />
<br />
In StandaloneCommon.ini the network addresses in sections [LoginService] and [GatekeeperService] must be changed to your external network address:<br />
<source lang="ini">[LoginService]<br />
; ... (other settings in this section) ...<br />
HomeURI = "http://example.com:9000"<br />
GatekeeperURI = "http://example.com:9000"<br />
InventoryServerURI = "http://example.com:9000"<br />
AssetServerURI = "http://example.com:9000"<br />
<br />
[GatekeeperService]<br />
; ... (other settings in this section) ...<br />
ExternalName = "http://example.com:9000"</source><br />
<br />
If you want to use a different port with these addresses, then you must adjust the HTTP listener port in section [Network] in OpenSim.ini, too:<br />
<source lang="ini">[Network]<br />
; ... (other settings in this section) ...<br />
http_listener_port = 9000<br />
</source><br />
<br />
As a last step, the regions must be configured according to the previous changes. See [[#Region Setup for both Grid and Standalone]].<br />
<br />
=== Grid ===<br />
To enable hypergrid for a grid, both the Robust server and the region servers (simulators) must be configured approprietly.<br />
<br />
==== Robust Server ====<br />
The Robust server is started with configuration file Robust.HG.ini instead of Robust.ini. If this file does not yet exist in your installation, create it by making a copy of Robust.HG.ini.example. Make the changes appropriate for your environment (e.g. adjust the database connection string). For hypergrid, the following settings are relevant:<br />
<br />
<source lang="ini">[LoginService]<br />
; ... (other settings in this section) ...<br />
HomeURI = "http://example.com:8002"<br />
GatekeeperURI = "http://example.com:8002"<br />
InventoryServerURI = "http://example.com:8002"<br />
AssetServerURI = "http://example.com:8002"<br />
<br />
[GatekeeperService]<br />
; ... (other settings in this section) ...<br />
ExternalName = "http://example.com:8002"<br />
</source><br />
<br />
If you want to change the port(s) used with these addresses, you will also need to adjust the ports in parameter ''''ServiceConnectors'''' in section [Startup] and probably the port configured in section [Network] as well.<br />
<br />
After these adjustments, the Robust server can be started. On Windows/.NET:<br />
Robust -inifile=Robust.HG.ini<br />
Or, with Mono (e.g. on Linux or OSX):<br />
mono Robust.exe -inifile=Robust.HG.ini<br />
<br />
==== Simulator ====<br />
The region servers (simulators) that connect to the Robust server read their configuration from file OpenSim.ini. To activate hypergrid for them, the line for Include-HGGrid in section [Architecture] must be uncommented:<br />
<source lang="ini">[Architecture]<br />
;Include-Standalone = "config-include/Standalone.ini"<br />
;Include-HGStandalone = "config-include/StandaloneHypergrid.ini"<br />
;Include-Grid = "config-include/Grid.ini"<br />
Include-HGGrid = "config-include/GridHypergrid.ini"<br />
;Include-SimianGrid = "config-include/SimianGrid.ini"<br />
</source><br />
<br />
=== Region Setup for both Grid and Standalone ===<br />
Finally, all your regions must use the same external address that is set for GatekeeperService, for example:<br />
<source lang="ini">[Region One]<br />
; ... (other settings in this section) ...<br />
ExternalHostName = "example.com"<br />
</source><br />
<br />
For the ports which are used by your regions, TCP and UDP requests must be forwarded through any firewall that is securing your network.<br />
<br />
== Configuration for OpenSimulator 0.6.x ==<br />
{{obsolete}}<br />
=== Installing ===<br />
<br />
Checkout OpenSim, prebuild and build as normal or Download and install Binary Packages from the [[Main Page|MAIN&nbsp;Page ]]<br>If you're running your opensim in '''Grid Mode''' mode with&nbsp;servers on other machines, you&nbsp;only need to modify your OpenSim.ini to enable HyperGrid. <br />
<br />
If you're running in standalone and you want it to be network-able, or if you have your grid on loopback (127.0.0.1) change all the [Network] server addresses to. See below. <br />
<br />
=== EXAMPLE Network Sections ===<br />
<br />
==== Default Example, Network Settings for a Stand Alone: ====<br />
<br />
<source lang="ini">[Network]<br />
http_listener_port = 9000<br />
<br />
grid_server_url = "http://example.com:9000"<br />
<br />
grid_send_key = null<br />
grid_recv_key = null<br />
<br />
user_server_url = "http://example.com:9000"<br />
<br />
user_send_key = null<br />
user_recv_key = null<br />
<br />
asset_server_url = "http://example.com:9000"<br />
<br />
inventory_server_url = "http://example.com:9000"<br />
messaging_server_url = "http://example.com:9000"</source> <br />
<br />
==== Default Example, Network Settings for a Grided Server: ====<br />
<br />
<source lang="ini">[Network]<br />
http_listener_port = 9000<br />
<br />
grid_server_url = "http://example.com:8001"<br />
grid_send_key = null<br />
grid_recv_key = null<br />
<br />
user_server_url = "http://example.com:8002"<br />
user_send_key = null<br />
user_recv_key = null<br />
<br />
asset_server_url = "http://example.com:8003"<br />
inventory_server_url = "http://example.com:8003"<br />
messaging_server_url = "http://example.com:8006"</source> <br />
<br />
==== Network Settings&nbsp;for OSGrid Attched Servers: ====<br />
<br />
<source lang="ini">[Network]<br />
http_listener_port = 9000<br />
grid_server_url = "http://osgrid.org:8001" ;default 8003<br />
grid_send_key = "1234"<br />
grid_recv_key = "1234"<br />
<br />
user_server_url = "http://osgrid.org:8002" <br />
user_send_key = "1234"<br />
user_recv_key = "1234"<br />
<br />
asset_server_url = "http://assets.osgrid.org:8003" <br />
inventory_server_url = "http://osgrid.org:8004" ;default 8003<br />
messaging_server_url = "http://osgrid.org:8006"</source> <br />
<br />
==== Modifications needed to be applied to OpenSim.ini to enable Hypergrid ====<br />
<br />
- Change the following line at the top of the OpenSim.ini <br />
<pre>hypergrid = false to true</pre><br />
- NEXT, Add or Modify the ### WORLD MAP Section as shown <br />
<br />
<source lang="ini">; ##<br />
; ## WORLD MAP<br />
; ##<br />
<br />
WorldMapModule = "WorldMap"<br />
MapImageModule = "MapImageModule"<br />
WorldMapModule = "HGWorldMapModule" ;NOT INCLUDED IN DEFAULT OpenSim.ini.EXAMPLE</source> <br />
<br />
''Information: HGWorldMapModule will, after teleporting to another grid, clean up tiles in your map left over from the grid on which you were previously.'' <br />
<br />
- NEXT, Modify the [Archictecture] Section at the bottom <br />
<br />
Uncomment the appropriate Include-HG* = line by removing the semi colon and making sure that is the only ONE uncommented. (example shows for a Stand Alone HG enabled installation) <br />
<br />
<source lang="ini">[Architecture]<br />
;Include-Standalone = "config-include/Standalone.ini" ; DEFAULT UNCOMMENTED<br />
Include-HGStandalone = "config-include/StandaloneHypergrid.ini"<br />
;Include-Grid = "config-include/Grid.ini"<br />
;Include-HGGrid = "config-include/GridHypergrid.ini"</source>&nbsp; <br />
<br />
Your OpenSimulator instance should now be ready for inbound &amp; outbound Hypergrid use<br />
<br />
== The 4096 Regions Limit ==<br />
Due to a viewer issue, teleports to destinations that are more than 4096 regions away in any direction will not work as expected. Most viewers will do the teleport but the destination region will not be rendered and thus remain invisible to you. What this means in practice is that if you wish to teleport from a region located at cell coordinates (1000, 1000) you cannot go beyond (5095, 5095). To reach destinations that are placed at farer locations, you should either place your own region closer to the destination, or use some intermediate region that is reachable from both your region and the destination region.<br />
<br />
Refer to [[Public Hypergrid Nodes]] to see some known grids and standalones and where they are located. <br />
<br />
== Important Notes ==<br />
Make sure you have a 'home' set. If your home region doesn't exist, the hyperlink TPs may not work. To set your home, go to one of your local regions and "Set Home" from the viewer. <br />
<br />
To Enable scripted Teleporting between regions, standalone, HyperGrid etc, you can use osTeleportAgent function, Example here: [[OsTeleportAgent|OsTeleportAgent]]<br />
<br />
== Linking regions (Optional) ==<br />
<br />
Linking hypergrid regions permits users on your system to easily hypergrid teleport to other grids via the viewer map. For example, if you run GridA and your friend runs GridB and both grids are Hypergrid enabled, you can "link" to a region on Grid B from your ROBUST console to create a persistent hypergrid link to your friend's GridB that appears on the viewer map. <br />
<br />
After creating the link using one of the methods below, your users on GridA will see a map tile showing the connection to GridB on the viewer map, and can teleport to GridB by double clicking the map tile to teleport.<br />
<br />
=== Method 1 ===<br />
<br />
On the console, type for example:<br />
<pre>link-region &lt;Xloc&gt; &lt;Yloc&gt; http://osl2.nac.uci.edu:9006/</pre><br />
Use Xloc and Yloc that make sense to your world, i.e. close to your regions, but not adjacent. Replace <nowiki>http://osl2.nac.uci.edu:9006/</nowiki> with the URL (i.e. protocol, domain name/ip address, and http_listener_port) of the simulator where the region is running you want to link to.<br />
You can link to a specific region within an instance, by using the name of the region at the end, for example: <br />
<pre>link-region &lt;Xloc&gt; &lt;Yloc&gt; http://osl2.nac.uci.edu:9006/ UCI Welcome</pre><br />
The above syntax is the preferred one for this console command starting with revision r/14611 (commit 72748746; this will be in release 0.7.1). The following syntax was used before and is still supported but deprecated in current (development) versions of OpenSimulator:<br />
<pre>link-region &lt;Xloc&gt; &lt;Yloc&gt; osl2.nac.uci.edu:9006</pre> or <pre>link-region 997 997 osl2.nac.uci.edu:9006:UCI Welcome</pre><br />
Please note that this older syntax uses just the hostname without a protocol specification like <nowiki>http://</nowiki> and a colon instead of a space to append a region name.<br />
<br />
=== Method 2 ===<br />
<br />
There is also some initial support for reading the links from a xml file. <br />
<br />
Use the console command: link-region &lt;URI&gt; [&lt;excludeList&gt;] <br />
<br />
The uri can be either the path of a local xml file or a xml document on a http server. <br />
<br />
The format of the xml file is: <br />
<br />
<source lang="xml"><Nini><br />
<Section Name="Region1"> <br />
<Key Name="xloc" Value="1002"/><br />
<Key Name="yloc" Value="1006" /><br />
<Key Name="externalPort" Value="9006" /><br />
<Key Name="externalHostName" Value="osl2.nac.uci.edu" /><br />
<Key Name="localName" Value="OSGrid-Gateway" /><br />
<Key Name="real-xloc" Value="10222"/> //optional field that gives the region's real location on its home grid<br />
<Key Name="real-yloc" Value="10265" /> //optional field that gives the region's real location on its home grid<br />
</Section><br />
<Section Name="Region2"> <br />
...<br />
</Section><br />
...<br />
</Nini></source> <br />
<br />
[Note] The section names can be anything you want, but they all should be different and have no spaces in the name. <br />
<br />
==== ExcludeList: ====<br />
<br />
The exclude list is a single string paramater with the format: excludeList:&lt;SectionName&gt;[;&lt;SectionName&gt;] <br />
<br />
This means that while reading from the xml file any sections that are listed in the excludeList will be ignored and no HyperGrid link created for them. <br />
<br />
This could allow, link lists to be created on a webserver that everyone could add their own regions to, and then they just make sure they add their own section name(s) to the exclude list on their own region(s). <br />
<br />
So for example, someone might create a editable online list for the up coming OpenSimulator's 2nd birthday. Which might look something like: <br />
<br />
<source lang="xml"><Nini><br />
<Section Name="OSGrid-Party"> <br />
<Key Name="xloc" Value="1002"/><br />
<Key Name="yloc" Value="1006" /><br />
<Key Name="externalPort" Value="9006" /><br />
<Key Name="externalHostName" Value="osl2.nac.uci.edu" /><br />
<Key Name="localName" Value="OSGrid-Gateway" /><br />
</Section><br />
<Section Name="UCIGrid-Party"> <br />
...<br />
</Section><br />
</Nini></source> I could then add my own region to the list with the section name "MW-Party". Then when I startup that region that I want to be part of this hypergrid, I use the command: <br />
<pre>"link-region &lt;URI of xml file&gt; excludeList:MW-Party"</pre><br />
This is so that my region doesn't try to create a hyper link to itself. <br />
<br />
=== Method 3 (dynamic) ===<br />
<br />
Starting in r8193, if you're in an HG-enabled region, you'll be able to dynamically link sims, and TP there, in any one of these ways (and probably more). All you need to know is the target address, e.g. from the list below. <br />
<br />
1) Type for example secondlife://ucigrid04.nacs.uci.edu:9007/ in the chat box, pull up the chat history and click on that link <br />
<br />
2) Pull up the map and search for things like ucigrid04.nacs.uci.edu:9007 <br />
<br />
3) Using the embedded browser visit pages that have links like '''secondlife://ucigrid04.nacs.uci.edu:9007'''/ (there's one up at http://www.ics.uci.edu/~lopes/hypergrid/test.html) <br />
<br />
Again, you can link to a specific region within an instance by adding the name of that region at the end, like this: '''secondlife://ucigrid04.nacs.uci.edu:9007:Gateway 7000/''' <br />
<br />
=== Checking the 4096 Regions Limit ===<br />
Due to the [[#The 4096 Regions Limit|4096 Regions Limit]], there is a check in OpenSimulator since version 0.7.0.1 which verifies that the intended link will be within reach of any of your regions. If none of the regions in your grid or standalone is located within a distance radius of 4096 regions from the region to be linked, then the link will be rejected. You can disable this check in StandaloneCommon.ini (for standalones) or Robust.HG.ini (for grids) with<br />
<source lang="ini">[GridService]<br />
Check4096 = false</source><br />
<br />
=== Persistent Linked Regions ===<br />
With grid mode, methods 1 and 2 will work on both the Robust console and the region console. On the region console, linked regions will not be stored in the database and will vanish when the region is shut down. Regions that are linked on the Robust console will be persistent over restarts until they are explicitly removed with unlink-region.<br />
<br />
== Listing linked regions ==<br />
<br />
To see a list of all linked regions, use the following command on the console (available since 0.7.1 r/13457, also in 0.7-post-fixes):<br />
<pre>show hyperlinks</pre><br />
<br />
== Unlinking regions ==<br />
<br />
On the console, use the command: <br />
<pre>unlink-region &lt;local region name&gt;</pre><br />
<br />
As local region name you should use what command <tt>show hyperlinks</tt> shows for the region that you want to unlink, for example<br />
<br />
<pre>unlink-region http://osl2.nac.uci.edu:9006/</pre><br />
<br />
With OpenSimulator revisions before r/14611 (i.e. before release 0.7.1), the syntax is a little different, for example<br />
<pre>unlink-region osl2.nac.uci.edu:9006</pre><br />
<br />
Please note that region names can only have a maximum length of 32 characters when using MySQL as a database. If a linked region has a longer name, it will be truncated. The unlink-region command will only find a region, if the name is also truncated to a maximum length of 32 characters. This limit has been extended to 128 characters for the full local region name in OpenSimulator 0.7.1 (since r/14611).<br />
<br />
== Additional References ==<br />
<br />
Implemented osFunctions: [[OSSL Implemented|OSSL Implemented]] <br />
<br />
Enabling osFunctions: [[OSSL Enabling Functions|OSSL Enabling Functions]] <br />
<br />
HyperGrid Security: [[Hypergrid Security|Hypergrid Security]] <br />
<br />
Banning Foreign Users in Hypergrid: [[Banning Foreign Users in Hypergrid|Banning Foreign Users in Hypergrid]] <br />
<br />
Public HyperGrid Nodes Listing: [[Public Hypergrid Nodes|Public Hypergrid Nodes]] <br />
<br />
Hypergrid Inventory Access: [[Hypergrid Inventory Access|Hypergrid Inventory Access (proposal)]] <br />
<br />
CATEGORY: [[:Category:Hypergrid|Hypergrid]]<br><br />
<br />
<br />
[[Category:Hypergrid]]</div>Fleephttp://opensimulator.org/wiki/Server_CommandsServer Commands2011-10-24T13:20:03Z<p>Fleep: /* Details of Hypergrid Commands */</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br />
= What are server commands? =<br />
<br />
You can type server commands on the region server or ROBUST service console to do various things.<br />
<br />
'''Disclaimer''': some commands may not work as expected, some may not work at all, and there is a chance that you may even lose all your settings/contents. This summary quickly goes out of date - the best place to find commands is by typing "help" on the region console.<br />
<br />
Except where noted, this list should be accurate for OpenSim 0.7.1.<br />
<br />
= Commands =<br />
<br />
== Region Console Commands ==<br />
<br />
=== General ===<br />
<br />
*alert <message> - send an in-world alert to everyone<br />
*alert-user <first> <last> <message> - send an an in-world alert to a specific user<br />
*appearance show - show avatar appearance information. At the moment, this just does a baked texture check for everybody in the region. If the check returns 'corrupt' then the avatar has not uploaded baked textures and other avatars will continue to see them as a gas ball (command is dev branch only).<br />
*backup - trigger a simulator backup (Persist objects to the database now). The simulator does this automatically at regular intervals and on shutdown.<br />
*bypass permissions &lt;true / false&gt; - Bypass in-world permission checks <br />
*change region <region name> - subsequent commands apply only to the specified region. If region name is "root" then all regions are selected<br />
*clear-assets - forcibly clears asset cache, probably leaving sim unstable. Use with caution. <br />
*command-script [name of scriptfile] - Runs a command script containing server commands <br />
*config get [<section>] [<key>] - Get the current configuration, either for a particular key, a particular section or the whole config.<br />
*config save <path> - Save the current configuration to a file.<br />
*config set <section> <key> - Set a particular configuration value. On the whole, this is useless since neither OpenSim nor modules dynamically reload config values.<br />
*config show [<section>] [<key>] - Synonym for 'config get'<br />
*create region [name] [filename] - Create a new region <br />
*debug packet <level> - Turn on packet debugging, where OpenSim prints out summaries of incoming and outgoing packets for viewers, depending on the level set<br />
*debug permissions - Turn on permissions debugging<br />
*debug scene - Turn on scene debugging<br />
*delete-region <name> - Delete a region from disk<br />
*edit scale [primitivename] [xvalue] [yvalue] [zvalue] - changes size of the named prim <br />
*emergency-monitoring - turn emergency debugging monitoring mode on or off.<br />
*export-map [<path>] - Save an image of the world map (default name is exportmap.jpg)<br />
*force permissions - Force permissions on or off.<br />
*force update - triggers a resend of all prims in a region <br />
*help [<command>] - Get general command list or more detailed help on a specific command or set of commands<br />
*kick user <first> <last> [message]: - Kick a user off the simulator<br />
*kill uuid <UUID> - Kill an object by UUID (helpful with red lines in the console)<br />
*link-mapping - Set a local grid co-ordinate to link to a remote hypergrid <br />
*link-region - Link a HyperGrid region. Not sure how this differs from link-mapping<br />
*load iar <first> <last> <inventory path> <password> [<archive path>] - Load user inventory archive. See [[Inventory_Archives]].<br />
*load oar [filename] - load an OpenSimulator archive. This entirely replaces the current region. Default filename is '''region.oar'''. See [[OpenSim Archives]].<br />
*load xml [-newIDs [<x> <y> <z>]] - Load a region's data from XML format (0.7.*: DEPRECATED and may be REMOVED soon. Use "load xml2" instead)<br />
:those xml are the result of the export save or *export save-all<br />
*load xml2 [filename] - optional parameters not supported for XML2 format as at 1-Jul-2008 <br />
*modules list - List modules<br />
*modules load <name> - Load a module<br />
*modules unload <name> - Unload a module<br />
* monitor report - Returns a variety of statistics about the current region and/or simulator<br />
* quit - equivalent to shutdown.<br />
* region restart abort [<message>] - Abort a scheduled region restart, with an optional message<br />
* region restart bluebox <message> <delta seconds>+ - Schedule a region restart. If one delta is given then the region is restarted in delta seconds time. A time to restart is sent to users in the region as a dismissable bluebox notice. If multiple deltas are given then a notice is sent when we reach each delta.<br />
* region restart notice <message> <delta seconds>+ - Schedule a region restart. Same as above except showing a transient notice instead of a dismissable bluebox.<br />
* reload estate - reload estate data<br />
*remove-region - remove a region from the simulator<br />
*restart - Restarts all sims in this instance<br />
*save iar <first> <last> <inventory path> <password> [<archive path>] - Save user inventory archive. See [[Inventory_Archives]]<br />
*save oar [filename] - save the current region to an OpenSimulator archive. Default filename is '''region.oar'''. See [[OpenSim Archives]].<br />
*save prims xml2 [<prim name> <file name>] - Save named prim to XML2<br />
*save xml [filename] - save prims to XML <br />
*save xml2 [filename] - save prims to XML (Format 2 - rearrangement of some nodes, to make loading/saving easier) <br />
* set log level [level] - change the console logging level only. For example, off or debug. See [[Logging]] for more information.<br />
*set region flags <Region name> <flags> - Set database flags for region<br />
*set terrain heights <corner> <min> <max> [<x>] [<y>] - Sets the terrain texture heights on corner #<corner> to <min>/<max>, if <x> or <y> are specified, it will only set it on regions with a matching coordinate. Specify -1 in <x> or <y> to wildcard that coordinate. Corner # SW = 0, NW = 1, SE = 2, NE = 3.<br />
*set terrain texture <number> <uuid> [<x>] [<y>] - Sets the terrain <number> to <uuid>, if <x> or <y> are specified, it will only set it on regions with a matching coordinate. Specify -1 in <x> or <y> to wildcard that coordinate.<br />
* show caps - show all registered capabilities URLs<br />
:NOTE: In OpenSim 0.7.1, "show capabilities" is shown as a result for help command, but actually only "show caps" will be accepted. ([http://opensimulator.org/mantis/view.php?id=5467 #5467])<br />
* show circuits - Show agent circuit data<br />
* show connections - show connections data<br />
* show http-handlers - show all registered http handlers<br />
* show hyperlinks - list hg regions<br />
* show info - show server information (version and startup path)<br />
* show modules - show module data<br />
* show neighbours - Shows the local regions' neighbours<br />
* show pending-objects - show number of objects in the pending queues of all viewers<br />
* show pqueues [full] - show priority queue data for each client. Without the 'full' option, only root agents are shown. With the 'full' option child agents are also shown.<br />
* show queues - Show queue data for agent connections.<br />
* show ratings - Show rating data<br />
* show regions - Show region data (Region Names, XLocation YLocation coordinates, Region Ports, Estate Names)<br />
* show stats - show usefull statistical information for this server. See [[#Frame Statistics Values|Frame Statistics Values]] below for more information.<br />
* show threads - shows the persistent threads registered with the system. Does not include threadpool threads. <br />
* show throttles [full] - Show throttle data for each client connection, and the maximum allowed for each connection by the server. Without the 'full' option, only root agents are shown. With the 'full' option child agents are also shown.<br />
* show uptime - show server startup time and uptime.<br />
* show users [full]- show info about currently connected users to this region. Without the 'full' option, only users actually on the region are shown. With the 'full' option child agents of users in neighbouring regions are also shown.<br />
* show version - show server version.<br />
* shutdown - disconnects all clients and shutdown.<br />
* unlink-region <local name> - unlink a hypergrid region<br />
<br />
=== Appearance Module Commands ===<br />
* appearance show - Show information about avatar appearance. Currently just checks whether the baked texture is "OK" or "corrupt". Still in development. Only exists in development code at the moment.<br />
<br />
=== Land Module Commands ===<br />
<br />
* land show - Shows all parcels on the current region.<br />
<br />
=== Terrain Module Commands ===<br />
<br />
Note that some of these may require a sim restart to show properly.<br />
* terrain load - Loads a terrain from a specified file.<br />
* terrain load-tile - Loads a terrain from a section of a larger file.<br />
* terrain save - Saves the current heightmap to a specified file.<br />
* terrain fill - Fills the current heightmap with a specified value.<br />
* terrain elevate - Raises the current heightmap by the specified amount.<br />
* terrain lower - Lowers the current heightmap by the specified amount.<br />
* terrain multiply - Multiplies the heightmap by the value specified.<br />
* terrain bake - Saves the current terrain into the regions revert map.<br />
* terrain revert - Loads the revert map terrain into the regions heightmap.<br />
* terrain newbrushes - Enables experimental brushes which replace the standard terrain brushes. WARNING: This is a debug setting and may be removed at any time.<br />
* terrain stats - Shows some information about the regions heightmap for debugging purposes.<br />
* terrain effect - Runs a specified plugin effect<br />
<br />
=== Tree Module Commands ===<br />
<br />
'''tree active''' - Change activity state for the trees module<br />
<br />
'''tree freeze''' - Freeze/Unfreeze activity for a defined copse<br />
<br />
'''tree load''' - Load a copse definition from an xml file<br />
<br />
'''tree plant '''- Start the planting on a copse<br />
<br />
'''tree rate''' - Reset the tree update rate (mSec)<br />
<br />
'''tree reload''' - Reload copse definitions from the in-scene trees<br />
<br />
'''tree remove''' - Remove a copse definition and all its in-scene trees<br />
<br />
'''tree statistics''' - Log statistics about the trees <br />
<br />
=== Windlight/[[LightShare]] Module Commands ===<br />
<br />
'''windlight load''' - Load windlight profile from the database and broadcast<br />
<br />
'''windlight enable''' - Enable the windlight plugin<br />
<br />
'''windlight disable''' - Enable the windlight plugin<br />
<br />
==Asset Service Commands==<br />
*delete asset - Delete an asset from the database. Doesn't appear to be implemented.<br />
*dump asset <ID> - Dump an asset to the filesystem. (dev code only)<br />
*show digest <ID> - Show summary information about an asset.<br />
<br />
==User Service Commands==<br />
* create user [first] [last] [passw] [RegionX] [RegionY] - creates a new user and password<br />
:or just: create user - and server prompts for all data<br />
:<br />
:'''Note for use of create user in standalone mode:''' use the user default coordinates<br />
:of 1000,1000 for Start Region X and Y position otherwise server<br />
:gives error of "[LOGIN]: Not found region" <br />
* reset user password - reset a user's password.<br />
* login-level <value> - Set the miminim userlevel allowed to login.<br />
* login-reset - reset the login level to its default value.<br />
* login-text <text to print during the login><br />
* show account <firstname> <lastname> - show account details for the given user name (0.7.2-dev)<br />
* set user level <firstname> <lastname> <level> - Set UserLevel for the user, which determines whether a user has a god account (0.7.2-dev)<br />
<br />
== Details of Terrain Module Commands==<br />
<br />
==== terrain load ====<br />
Loads a terrain from a specified file.<br />
<br />
Parameters<br />
* filename (String)<br />
The file you wish to load from, the file extension determines the loader to be used. Supported extensions include: .r32 (RAW32) .f32 (RAW32) .ter (Terragen) .raw (LL/SL RAW) .jpg (JPEG) .jpeg (JPEG) .bmp (BMP) .png (PNG) .gif (GIF) .tif (TIFF) .tiff (TIFF)<br />
<br />
==== terrain load-tile ====<br />
Loads a terrain from a section of a larger file.<br />
<br />
Parameters<br />
* filename (String)<br />
The file you wish to load from, the file extension determines the loader to be used. Supported extensions include: .r32 (RAW32) .f32 (RAW32) .ter (Terragen) .raw (LL/SL RAW) .jpg (JPEG) .jpeg (JPEG) .bmp (BMP) .png (PNG) .gif (GIF) .tif (TIFF) .tiff (TIFF)<br />
* file width (Integer)<br />
The width of the file in tiles<br />
* file height (Integer)<br />
The height of the file in tiles<br />
* minimum X tile (Integer)<br />
The X region coordinate of the first section on the file<br />
* minimum Y tile (Integer)<br />
The Y region coordinate of the first section on the file<br />
<br />
==== terrain save ====<br />
Saves the current heightmap to a specified file.<br />
<br />
Parameters<br />
* filename (String)<br />
The destination filename for your heightmap, the file extension determines the format to save in. Supported extensions include: .r32 (RAW32) .f32 (RAW32) .ter (Terragen) .raw (LL/SL RAW) .jpg (JPEG) .jpeg (JPEG) .bmp (BMP) .png (PNG) .gif (GIF) .tif (TIFF) .tiff (TIFF)<br />
<br />
==== terrain fill ====<br />
Fills the current heightmap with a specified value.<br />
<br />
Parameters<br />
* value (Double)<br />
The numeric value of the height you wish to set your region to.<br />
<br />
==== terrain elevate ====<br />
Raises the current heightmap by the specified amount.<br />
<br />
Parameters<br />
* amount (Double)<br />
<br />
==== terrain lower ====<br />
Lowers the current heightmap by the specified amount.<br />
<br />
Parameters<br />
* amount (Double)<br />
The amount of height to remove from the terrain in meters.<br />
<br />
==== terrain multiply ====<br />
Multiplies the heightmap by the value specified.<br />
<br />
Parameters<br />
* value (Double)<br />
The value to multiply the heightmap by.<br />
<br />
==== terrain bake ====<br />
Saves the current terrain into the regions revert map.<br />
<br />
==== terrain revert ====<br />
Loads the revert map terrain into the regions heightmap.<br />
<br />
==== terrain newbrushes ====<br />
Enables experimental brushes which replace the standard terrain brushes. WARNING: This is a debug setting and may be removed at any time.<br />
<br />
Parameters<br />
* Enabled? (Boolean)<br />
true / false - Enable new brushes<br />
<br />
==== terrain stats ====<br />
Shows some information about the regions heightmap for debugging purposes.<br />
<br />
==== terrain effect ====<br />
Runs a specified plugin effect<br />
<br />
Parameters<br />
* name (String)<br />
The plugin effect you wish to run, or 'list' to see all plugins<br />
<br />
== Details of Hypergrid Commands==<br />
<br />
For full details and explanations of Hypergrid Commands, see the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#Linking_regions_.28Optional.29 Linking Regions] sections of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page.<br />
<br />
'''show hyperlinks''' <br />
<br />
This command will show a list of all hypergrid linked regions.<br />
<br />
'''link-region <Xloc> <Yloc> <host> <port> <location-name>'''<br />
<br />
* Use Xloc and Yloc that make sense to your world, i.e. close to your regions, but not adjacent.<br />
* replace osl2.nac.uci.edu and 9006 with the domain name / ip address and the port of the region you want to link to<br />
<br />
E.g. link-region 8998 8998 osl2.nac.uci.edu 9006 OSGrid Gateway<br />
<br />
'''unlink-region <local region name>'''<br />
<br />
This command will unlink the specified hypergrid linked region - be sure to use the exact local name as reported by the "show hyperlinks" command.<br />
<br />
'''Important Note'''<br />
<br />
Due to a viewer [https://jira.secondlife.com/browse/SVC-2941 bug], you can only TP between regions that are no more than 4096 cells apart in any dimension. What this means in practice is that if you want to link to OSGrid, you must have your own regions reachable from the (10,000; 10,000) point on the map, which is where OSGrid is centered. Place your regions somewhere in the 8,000s or the 12,000s.<br />
<br />
link-mapping<br />
<br />
[[Category:Support]]<br />
[[Category:Help]]<br />
[[Category:Configuration]]<br />
[[Category:Getting_Started]]<br />
[[Category:Development]]<br />
<br />
==Frame Statistics Values==<br />
<br />
The labels of the Frame Statistics values shown by the console command "show stats" are a bit cryptic. Here is a list of the meanings of these values:<br />
<br />
*Dilatn - time dilation<br />
*SimFPS - sim FPS<br />
*PhyFPS - physics FPS<br />
*AgntUp - # of agent updates<br />
*RootAg - # of root agents<br />
*ChldAg - # of child agents<br />
*Prims - # of total prims<br />
*AtvPrm - # of active prims<br />
*AtvScr - # of active scripts<br />
*ScrLPS - # of script lines per second<br />
*PktsIn - # of in packets per second<br />
*PktOut - # of out packets per second<br />
*PendDl - # of pending downloads<br />
*PendUl - # of pending uploads<br />
*UnackB - # of unacknowledged bytes<br />
*TotlFt - total frame time<br />
*NetFt - net frame time<br />
*PhysFt - physics frame time<br />
*OthrFt - other frame time<br />
*AgntFt - agent frame time<br />
*ImgsFt - image frame time</div>Fleephttp://opensimulator.org/wiki/Server_CommandsServer Commands2011-10-24T13:16:33Z<p>Fleep: /* Details of Hypergrid Commands */ - added link to Installing and Running Hypergrid page which shows more information about hypergrid related console commands</p>
<hr />
<div>__NOTOC__<br />
{{Quicklinks}}<br />
<br />
= What are server commands? =<br />
<br />
You can type server commands on the region server or ROBUST service console to do various things.<br />
<br />
'''Disclaimer''': some commands may not work as expected, some may not work at all, and there is a chance that you may even lose all your settings/contents. This summary quickly goes out of date - the best place to find commands is by typing "help" on the region console.<br />
<br />
Except where noted, this list should be accurate for OpenSim 0.7.1.<br />
<br />
= Commands =<br />
<br />
== Region Console Commands ==<br />
<br />
=== General ===<br />
<br />
*alert <message> - send an in-world alert to everyone<br />
*alert-user <first> <last> <message> - send an an in-world alert to a specific user<br />
*appearance show - show avatar appearance information. At the moment, this just does a baked texture check for everybody in the region. If the check returns 'corrupt' then the avatar has not uploaded baked textures and other avatars will continue to see them as a gas ball (command is dev branch only).<br />
*backup - trigger a simulator backup (Persist objects to the database now). The simulator does this automatically at regular intervals and on shutdown.<br />
*bypass permissions &lt;true / false&gt; - Bypass in-world permission checks <br />
*change region <region name> - subsequent commands apply only to the specified region. If region name is "root" then all regions are selected<br />
*clear-assets - forcibly clears asset cache, probably leaving sim unstable. Use with caution. <br />
*command-script [name of scriptfile] - Runs a command script containing server commands <br />
*config get [<section>] [<key>] - Get the current configuration, either for a particular key, a particular section or the whole config.<br />
*config save <path> - Save the current configuration to a file.<br />
*config set <section> <key> - Set a particular configuration value. On the whole, this is useless since neither OpenSim nor modules dynamically reload config values.<br />
*config show [<section>] [<key>] - Synonym for 'config get'<br />
*create region [name] [filename] - Create a new region <br />
*debug packet <level> - Turn on packet debugging, where OpenSim prints out summaries of incoming and outgoing packets for viewers, depending on the level set<br />
*debug permissions - Turn on permissions debugging<br />
*debug scene - Turn on scene debugging<br />
*delete-region <name> - Delete a region from disk<br />
*edit scale [primitivename] [xvalue] [yvalue] [zvalue] - changes size of the named prim <br />
*emergency-monitoring - turn emergency debugging monitoring mode on or off.<br />
*export-map [<path>] - Save an image of the world map (default name is exportmap.jpg)<br />
*force permissions - Force permissions on or off.<br />
*force update - triggers a resend of all prims in a region <br />
*help [<command>] - Get general command list or more detailed help on a specific command or set of commands<br />
*kick user <first> <last> [message]: - Kick a user off the simulator<br />
*kill uuid <UUID> - Kill an object by UUID (helpful with red lines in the console)<br />
*link-mapping - Set a local grid co-ordinate to link to a remote hypergrid <br />
*link-region - Link a HyperGrid region. Not sure how this differs from link-mapping<br />
*load iar <first> <last> <inventory path> <password> [<archive path>] - Load user inventory archive. See [[Inventory_Archives]].<br />
*load oar [filename] - load an OpenSimulator archive. This entirely replaces the current region. Default filename is '''region.oar'''. See [[OpenSim Archives]].<br />
*load xml [-newIDs [<x> <y> <z>]] - Load a region's data from XML format (0.7.*: DEPRECATED and may be REMOVED soon. Use "load xml2" instead)<br />
:those xml are the result of the export save or *export save-all<br />
*load xml2 [filename] - optional parameters not supported for XML2 format as at 1-Jul-2008 <br />
*modules list - List modules<br />
*modules load <name> - Load a module<br />
*modules unload <name> - Unload a module<br />
* monitor report - Returns a variety of statistics about the current region and/or simulator<br />
* quit - equivalent to shutdown.<br />
* region restart abort [<message>] - Abort a scheduled region restart, with an optional message<br />
* region restart bluebox <message> <delta seconds>+ - Schedule a region restart. If one delta is given then the region is restarted in delta seconds time. A time to restart is sent to users in the region as a dismissable bluebox notice. If multiple deltas are given then a notice is sent when we reach each delta.<br />
* region restart notice <message> <delta seconds>+ - Schedule a region restart. Same as above except showing a transient notice instead of a dismissable bluebox.<br />
* reload estate - reload estate data<br />
*remove-region - remove a region from the simulator<br />
*restart - Restarts all sims in this instance<br />
*save iar <first> <last> <inventory path> <password> [<archive path>] - Save user inventory archive. See [[Inventory_Archives]]<br />
*save oar [filename] - save the current region to an OpenSimulator archive. Default filename is '''region.oar'''. See [[OpenSim Archives]].<br />
*save prims xml2 [<prim name> <file name>] - Save named prim to XML2<br />
*save xml [filename] - save prims to XML <br />
*save xml2 [filename] - save prims to XML (Format 2 - rearrangement of some nodes, to make loading/saving easier) <br />
* set log level [level] - change the console logging level only. For example, off or debug. See [[Logging]] for more information.<br />
*set region flags <Region name> <flags> - Set database flags for region<br />
*set terrain heights <corner> <min> <max> [<x>] [<y>] - Sets the terrain texture heights on corner #<corner> to <min>/<max>, if <x> or <y> are specified, it will only set it on regions with a matching coordinate. Specify -1 in <x> or <y> to wildcard that coordinate. Corner # SW = 0, NW = 1, SE = 2, NE = 3.<br />
*set terrain texture <number> <uuid> [<x>] [<y>] - Sets the terrain <number> to <uuid>, if <x> or <y> are specified, it will only set it on regions with a matching coordinate. Specify -1 in <x> or <y> to wildcard that coordinate.<br />
* show caps - show all registered capabilities URLs<br />
:NOTE: In OpenSim 0.7.1, "show capabilities" is shown as a result for help command, but actually only "show caps" will be accepted. ([http://opensimulator.org/mantis/view.php?id=5467 #5467])<br />
* show circuits - Show agent circuit data<br />
* show connections - show connections data<br />
* show http-handlers - show all registered http handlers<br />
* show hyperlinks - list hg regions<br />
* show info - show server information (version and startup path)<br />
* show modules - show module data<br />
* show neighbours - Shows the local regions' neighbours<br />
* show pending-objects - show number of objects in the pending queues of all viewers<br />
* show pqueues [full] - show priority queue data for each client. Without the 'full' option, only root agents are shown. With the 'full' option child agents are also shown.<br />
* show queues - Show queue data for agent connections.<br />
* show ratings - Show rating data<br />
* show regions - Show region data (Region Names, XLocation YLocation coordinates, Region Ports, Estate Names)<br />
* show stats - show usefull statistical information for this server. See [[#Frame Statistics Values|Frame Statistics Values]] below for more information.<br />
* show threads - shows the persistent threads registered with the system. Does not include threadpool threads. <br />
* show throttles [full] - Show throttle data for each client connection, and the maximum allowed for each connection by the server. Without the 'full' option, only root agents are shown. With the 'full' option child agents are also shown.<br />
* show uptime - show server startup time and uptime.<br />
* show users [full]- show info about currently connected users to this region. Without the 'full' option, only users actually on the region are shown. With the 'full' option child agents of users in neighbouring regions are also shown.<br />
* show version - show server version.<br />
* shutdown - disconnects all clients and shutdown.<br />
* unlink-region <local name> - unlink a hypergrid region<br />
<br />
=== Appearance Module Commands ===<br />
* appearance show - Show information about avatar appearance. Currently just checks whether the baked texture is "OK" or "corrupt". Still in development. Only exists in development code at the moment.<br />
<br />
=== Land Module Commands ===<br />
<br />
* land show - Shows all parcels on the current region.<br />
<br />
=== Terrain Module Commands ===<br />
<br />
Note that some of these may require a sim restart to show properly.<br />
* terrain load - Loads a terrain from a specified file.<br />
* terrain load-tile - Loads a terrain from a section of a larger file.<br />
* terrain save - Saves the current heightmap to a specified file.<br />
* terrain fill - Fills the current heightmap with a specified value.<br />
* terrain elevate - Raises the current heightmap by the specified amount.<br />
* terrain lower - Lowers the current heightmap by the specified amount.<br />
* terrain multiply - Multiplies the heightmap by the value specified.<br />
* terrain bake - Saves the current terrain into the regions revert map.<br />
* terrain revert - Loads the revert map terrain into the regions heightmap.<br />
* terrain newbrushes - Enables experimental brushes which replace the standard terrain brushes. WARNING: This is a debug setting and may be removed at any time.<br />
* terrain stats - Shows some information about the regions heightmap for debugging purposes.<br />
* terrain effect - Runs a specified plugin effect<br />
<br />
=== Tree Module Commands ===<br />
<br />
'''tree active''' - Change activity state for the trees module<br />
<br />
'''tree freeze''' - Freeze/Unfreeze activity for a defined copse<br />
<br />
'''tree load''' - Load a copse definition from an xml file<br />
<br />
'''tree plant '''- Start the planting on a copse<br />
<br />
'''tree rate''' - Reset the tree update rate (mSec)<br />
<br />
'''tree reload''' - Reload copse definitions from the in-scene trees<br />
<br />
'''tree remove''' - Remove a copse definition and all its in-scene trees<br />
<br />
'''tree statistics''' - Log statistics about the trees <br />
<br />
=== Windlight/[[LightShare]] Module Commands ===<br />
<br />
'''windlight load''' - Load windlight profile from the database and broadcast<br />
<br />
'''windlight enable''' - Enable the windlight plugin<br />
<br />
'''windlight disable''' - Enable the windlight plugin<br />
<br />
==Asset Service Commands==<br />
*delete asset - Delete an asset from the database. Doesn't appear to be implemented.<br />
*dump asset <ID> - Dump an asset to the filesystem. (dev code only)<br />
*show digest <ID> - Show summary information about an asset.<br />
<br />
==User Service Commands==<br />
* create user [first] [last] [passw] [RegionX] [RegionY] - creates a new user and password<br />
:or just: create user - and server prompts for all data<br />
:<br />
:'''Note for use of create user in standalone mode:''' use the user default coordinates<br />
:of 1000,1000 for Start Region X and Y position otherwise server<br />
:gives error of "[LOGIN]: Not found region" <br />
* reset user password - reset a user's password.<br />
* login-level <value> - Set the miminim userlevel allowed to login.<br />
* login-reset - reset the login level to its default value.<br />
* login-text <text to print during the login><br />
* show account <firstname> <lastname> - show account details for the given user name (0.7.2-dev)<br />
* set user level <firstname> <lastname> <level> - Set UserLevel for the user, which determines whether a user has a god account (0.7.2-dev)<br />
<br />
== Details of Terrain Module Commands==<br />
<br />
==== terrain load ====<br />
Loads a terrain from a specified file.<br />
<br />
Parameters<br />
* filename (String)<br />
The file you wish to load from, the file extension determines the loader to be used. Supported extensions include: .r32 (RAW32) .f32 (RAW32) .ter (Terragen) .raw (LL/SL RAW) .jpg (JPEG) .jpeg (JPEG) .bmp (BMP) .png (PNG) .gif (GIF) .tif (TIFF) .tiff (TIFF)<br />
<br />
==== terrain load-tile ====<br />
Loads a terrain from a section of a larger file.<br />
<br />
Parameters<br />
* filename (String)<br />
The file you wish to load from, the file extension determines the loader to be used. Supported extensions include: .r32 (RAW32) .f32 (RAW32) .ter (Terragen) .raw (LL/SL RAW) .jpg (JPEG) .jpeg (JPEG) .bmp (BMP) .png (PNG) .gif (GIF) .tif (TIFF) .tiff (TIFF)<br />
* file width (Integer)<br />
The width of the file in tiles<br />
* file height (Integer)<br />
The height of the file in tiles<br />
* minimum X tile (Integer)<br />
The X region coordinate of the first section on the file<br />
* minimum Y tile (Integer)<br />
The Y region coordinate of the first section on the file<br />
<br />
==== terrain save ====<br />
Saves the current heightmap to a specified file.<br />
<br />
Parameters<br />
* filename (String)<br />
The destination filename for your heightmap, the file extension determines the format to save in. Supported extensions include: .r32 (RAW32) .f32 (RAW32) .ter (Terragen) .raw (LL/SL RAW) .jpg (JPEG) .jpeg (JPEG) .bmp (BMP) .png (PNG) .gif (GIF) .tif (TIFF) .tiff (TIFF)<br />
<br />
==== terrain fill ====<br />
Fills the current heightmap with a specified value.<br />
<br />
Parameters<br />
* value (Double)<br />
The numeric value of the height you wish to set your region to.<br />
<br />
==== terrain elevate ====<br />
Raises the current heightmap by the specified amount.<br />
<br />
Parameters<br />
* amount (Double)<br />
<br />
==== terrain lower ====<br />
Lowers the current heightmap by the specified amount.<br />
<br />
Parameters<br />
* amount (Double)<br />
The amount of height to remove from the terrain in meters.<br />
<br />
==== terrain multiply ====<br />
Multiplies the heightmap by the value specified.<br />
<br />
Parameters<br />
* value (Double)<br />
The value to multiply the heightmap by.<br />
<br />
==== terrain bake ====<br />
Saves the current terrain into the regions revert map.<br />
<br />
==== terrain revert ====<br />
Loads the revert map terrain into the regions heightmap.<br />
<br />
==== terrain newbrushes ====<br />
Enables experimental brushes which replace the standard terrain brushes. WARNING: This is a debug setting and may be removed at any time.<br />
<br />
Parameters<br />
* Enabled? (Boolean)<br />
true / false - Enable new brushes<br />
<br />
==== terrain stats ====<br />
Shows some information about the regions heightmap for debugging purposes.<br />
<br />
==== terrain effect ====<br />
Runs a specified plugin effect<br />
<br />
Parameters<br />
* name (String)<br />
The plugin effect you wish to run, or 'list' to see all plugins<br />
<br />
== Details of Hypergrid Commands==<br />
<br />
For full details and explanations of Hypergrid Commands, see the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#Linking_regions_.28Optional.29 Linking Regions] sections of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page.<br />
<br />
link-region <Xloc> <Yloc> <host> <port> <location-name><br />
<br />
* Use Xloc and Yloc that make sense to your world, i.e. close to your regions, but not adjacent.<br />
* replace osl2.nac.uci.edu and 9006 with the domain name / ip address and the port of the region you want to link to<br />
<br />
E.g. link-region 8998 8998 osl2.nac.uci.edu 9006 OSGrid Gateway<br />
<br />
'''Important Note'''<br />
<br />
Due to a viewer [https://jira.secondlife.com/browse/SVC-2941 bug], you can only TP between regions that are no more than 4096 cells apart in any dimension. What this means in practice is that if you want to link to OSGrid, you must have your own regions reachable from the (10,000; 10,000) point on the map, which is where OSGrid is centered. Place your regions somewhere in the 8,000s or the 12,000s.<br />
<br />
link-mapping<br />
<br />
[[Category:Support]]<br />
[[Category:Help]]<br />
[[Category:Configuration]]<br />
[[Category:Getting_Started]]<br />
[[Category:Development]]<br />
<br />
==Frame Statistics Values==<br />
<br />
The labels of the Frame Statistics values shown by the console command "show stats" are a bit cryptic. Here is a list of the meanings of these values:<br />
<br />
*Dilatn - time dilation<br />
*SimFPS - sim FPS<br />
*PhyFPS - physics FPS<br />
*AgntUp - # of agent updates<br />
*RootAg - # of root agents<br />
*ChldAg - # of child agents<br />
*Prims - # of total prims<br />
*AtvPrm - # of active prims<br />
*AtvScr - # of active scripts<br />
*ScrLPS - # of script lines per second<br />
*PktsIn - # of in packets per second<br />
*PktOut - # of out packets per second<br />
*PendDl - # of pending downloads<br />
*PendUl - # of pending uploads<br />
*UnackB - # of unacknowledged bytes<br />
*TotlFt - total frame time<br />
*NetFt - net frame time<br />
*PhysFt - physics frame time<br />
*OthrFt - other frame time<br />
*AgntFt - agent frame time<br />
*ImgsFt - image frame time</div>Fleephttp://opensimulator.org/wiki/Public_Hypergrid_NodesPublic Hypergrid Nodes2011-10-05T12:37:02Z<p>Fleep: /* Hypergrid 1.5 - General Grids/Sims */</p>
<hr />
<div>{{Quicklinks}} <br> <br />
<br />
__TOC__ <br />
<br />
== Hypergrid-enabled sims ==<br />
<br />
The following is a list of hypergrid-ready nodes that you can use for testing your installation and for linking your world. Please add your public node at the bottom of the list if you wish to help build a web of opensims! Anyone found inserting a grid higher in the list may have their entry removed. <br />
<br />
For the time being, and until the security concerns are addressed, we advise you to be careful about who you link to.<br />
<br />
== Hypergrid 1.5 - General Grids/Sims ==<br />
<br />
The following is a list of hypergrid 1.5-ready nodes that you can use for testing your installation and for linking your world. Please add your public node at the bottom of the list if you wish to help build a web of opensims! Anyone found inserting a grid higher in the list may have their entry removed. <br />
<br />
<br> <br />
<br />
{| align="center" border="1" cellspacing="0" cellpadding="5"<br />
|-<br />
! [[Hypergrid|link-region server and port]] <br />
! Organization <br />
! Description <br />
! Grid Location<br />
|-<br />
| ucigrid00.nacs.uci.edu:8002 <br />
| UCI Grid <br />
| [http://ucigrid00.nacs.uci.edu:8002 UCIGrid] V 0.7.1 (post-fixes) <br />
| Centered at 5000,5000<br />
|-<br />
| login.germangrid.de:8002 <br />
| GermanGrid <br />
| [http://www.germangrid.de GermanGrid] V 0.71(dev) <br />
| Centered at 8000,8000<br />
|-<br />
| marlokir.selfip.net:9000 <br />
| Marlokir <br />
| Just a small standalone for testing running on version 0.7.1 (dev). <br />
It will probably be online only temporarily. <br />
<br />
| Centered at 4500,4500<br />
|-<br />
| gridnirvana.net:8002:Rhiga <br />
| Jez's World <br />
| A small private Estate, previously stand alone - but for now part of GridNirvana. <br />
Please feel free to pop over and visit. <br />
<br />
| Centered at 6500,6500<br />
|-<br />
| virtual.aiai.ed.ac.uk:8002:Openvue <br />
| Openvue <br />
| Openvue grid at Virtual University of Edinburgh <br />
| Centered at 1000,1000<br />
|-<br />
| virtual.aiai.ed.ac.uk:8002:Vue-5000 <br />
| Vue-5000 <br />
| Openvue grid at Virtual University of Edinburgh <br />
| Centered at 5000,5000<br />
|-<br />
| virtual.aiai.ed.ac.uk:8002:Vue-9000 <br />
| Vue-9000 <br />
| Openvue grid at Virtual University of Edinburgh <br />
| Centered at 9000,9000<br />
|-<br />
| 145.99.250.20:8002 <br />
| DWGrid <br />
| DWGrid <br />
| Centered at 7000,7000<br />
|-<br />
| metaversesims.net:9000 <br />
| Metaverse Sims <br />
| 6-region standalone hypergrid on V. 0.7.2 (Dev) <br />
| Centred at 9000,9000<br />
|-<br />
| opensim.betatechnologies.info:8002 <br />
| Beta Technologies OpenSim Grid (btgrid) <br />
| Grid for internal development, mostly for academic research and backups from old sims. V. 0.7.0.1 <br />
| Centered at 3650,3650<br />
|-<br />
| hippo.is-a-geek.com:8002 <br />
| The Bloomfield Grid <br />
| This is a personal grid for my friends and familly, However we welcome others with a smile. V. 0.7.0.1 (We are also Hyper Gate enabled) <br />
| Centered at 5000,5000<br />
|-<br />
| tritongrid.com:8002 <br />
| Triton Grid <br />
| This is a 100+ region Public grid. All are welcome (We are also Hyper Gate enabled in several regions throughout the grid) (HG 1.5X Interface 7 Runing the latest .71Dev revs. maintains creator data) <br />
| Centered at 9000,9000<br />
|-<br />
| condensationland.com:9000 <br />
| Condensation Land <br />
| 10 regions <br />
| Centered at 7789, 7789<br />
|-<br />
| chazzmac.webhop.org:9000 <br />
| eden 16 regions <br />
| full 3 story hidden freebie mall, HyperGate, WiFi at http://chazzmac.webhop.org:9000/wifi/ <br />
| Centered at 3917, 4144<br />
|-<br />
| metaversesailing.com:9000 <br />
| Sailing Grid <br />
| A D2 grid on V 0.7.2(release)a .Net hosted 16 region mega with support regions <br />
| Centered at 7000,7000<br />
|-<br />
| ogzoco.no-ip.org:8002 <br />
| Ogzoco Grid &amp; RaionFort <br />
| Mentolyptus Destiny testing &amp; work grid. Hypergrid 1.5, OpenSim 0.7.1 (Currently OsGrid Revision 0.7.1.dev.80f9022 - 10-22-2010). Gateway to multiple grids on map. Photos: http://www.flickr.com/photos/mentolyptus/ - Twitter: https://twitter.com/Ogzoco - EMail: ogzoco@gmail.com <br />
| Centered at 7852, 7852<br />
|-<br />
| grid.ansky.ca:8002 <br />
| AnSky Grid <br />
| 10 regions <br />
| Centered at 7100, 7100<br />
|-<br />
| sim-world.org:8003 <br />
| Sim-World Welcome Center <br />
| 41 regions <br />
| Centered at 10000, 10000<br />
|-<br />
| unethika.kicks-ass.net:8002 <br />
| unethika <br />
| It works (most of the time) and it's fun! Come via hg hop or snag an avatar at [http://unethika.kicks-ass.net/ http://unethika.kicks-ass.net/]&nbsp;! We also run a working(ish) Freeswitch server. &lt;no guarantees, of course&nbsp;:P&gt; <br />
| Centered at 7500, 7500<br />
|-<br />
| odosys.dyndns.org:8002 <br />
| Odonata Systems <br />
| Mimetic Core's developmental grid: works in progress and personal hypergrid sandbox. Accounts disabled but HG visitors welcome. Hosted on laptop + fast ADSL (V 0.7.2 dev, CentOS 6, Mono 2.10.2). Twitter: [http://twitter.com/odosys/ @odosys]. Freenode IRC channel: #odosys.<br />
<br />
Note: If I'm doing heavy building/testing only the lower regions will be running (telehub: Quarantine @ 4995, 5015).<br />
| Centered at 7990, 8012<br />
|-<br />
| fleepgrid.com:8002 <br />
| FleepGrid <br />
| Personal research grid operated by Fleep Tuque, 8-12 sims at any given time. Grid hoppers and testers welcome. Running Opensim 0.7.2 RC2 Release HG 1.5 (i7). Gateway regions available at (1013,1013), (5013,5013), and (13013,13013). See [http://fleepgrid.com http://fleepgrid.com] for more information or follow Fleep at [http://twitter.com/fleep http://twitter.com/fleep].<br />
| Centered at 9013, 9013<br />
|-<br />
| viradu.com:9000 <br />
| Viradu Science Fiction World <br />
| [[Image:Vban.jpg|thumb|left|180px|Viradu.com Science Fiction Virtual World]]12 Science Fiction themed regions run by Michael Blade Sci-fi blogger dedicated to writers and those who love it. Hypergrid Teleporters, Builders welcome, free land grab, rules apply. Tell others about us...Join in the fun! =&gt; [http://viradu.com http://viradu.com]<br>How to build your own virtual world here =&gt; [http://rocketvirtual.com RocketVirtual.com] <br />
| Centered at 5001, 5001<br />
|-<br />
| 62.40.147.45:9090 <br />
| Psychedelia Grid <br />
| The home of psychedelic music. This Grid is for all fans of psychedelic music. Watch the bands playing at the festival and stay over night in your tent. <br />
| centered at 6000, 5990<br />
|-<br />
| '''logicamp.dyndns.org:8002:logicamp''' <br />
| Logicamp <br />
| [http://www.logicamp.com/ Logicamp] is a virtual world specialized in camp-site management and virtual tourism. You can visit it throughout our cable network. <br />
| Centered at 8000, 8000<br />
|-<br />
| logicamp.dyndns.org:8002:SPA1<br> <br />
| [http://www.logicamp.com logicamp]<br> <br />
| Megaregion Entrance (7997,7994)<br>Spa-Francorchamp[[Image:Snapshot 037.png|thumb|none|128px|Spa-Francorchamp]]60 plot Megaregion - [http://logicamp.com logicamp]<br> <br />
| Centered at 7900, 7900<br><br />
|-<br />
| map.terravirtuavw.com:8002:Nexus<br> <br />
| [http://www.terravirtuavw.com Terra Virtua]<br> <br />
| The Terra Virtua intergrid nexus.<br> <br />
| 6000,6000<br><br />
|-<br />
| hg.osgrid.org:80:WestHall<br />
| Possible future home of Champlain College in Burlington, Vermont<br> <br />
| When there, check the map and TP to surrounding regions that are populated with "stuff"br> <br />
| Centered at 6100, 6107<br><br />
|-<br />
| www.pmgrid.org:8002 <br />
| [http://www.pmgrid.org PMGrid] <br />
| Nursery grid to enable people to try their builds at little or no cost. Land available to try your ideas without charge. <br />
| Centered at 7000,7000<br><br />
|-<br />
| 91.121.153.154:8002 <br />
| [http://www.opensimserver.tk Sofitek] <br />
| Sofitek grid, the virtual offices of Sofitek, a web development company. Includes a small selection of free avatars and a hypergate portal to other worlds. Check out the books in the office, and talk to chatbot Lady Sofitek. <br />
| Centered at 10000,10000<br><br />
|-<br />
| [AstralGrid] <br />
| [http://astral.dyndns-server.com Homepage] <br />
| 4 Freebies and 1 sandbox Region <br />
| Centered at 10000,10000<br><br />
|}<br />
<br />
== Hypergrid 1.5 - Education oriented grid/sims ==<br />
<br />
* https://sites.google.com/a/opensim-edu.org/educational-institutions-in-opensim/home - A list of OpenSim educational grids, some Hypergrid enabled. This list has an easy to use form to add new institutions!<br />
<br />
== External directories of Hypergrid-enabled sims ==<br />
<br />
*[http://www.gridhop.net GridHop] <br />
*[http://www.hyperica.com Hyperica]<br />
*[http://www.thehypergates.com/ The HyperGates] -- The first dynamic, auto-updating HyperGrid directory for HyperGrid 1.5 ( OpenSim 0.7.1 and OpenSim 0.7.0.2 ) standalones & grids. Download the HyperGate from the site now and Join the HyperGate Network. The most reliable HyperGrid directory.<br />
*[http://www.hgurl.com hgurl]<br />
<br />
== Old List (HG 1.0) ==<br />
<br />
Keeping this here for historical reasons, but most of these don't work anymore.<br />
<br><br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
|-<br />
! [[Hypergrid|link-region server and port]] <br />
! Organization <br />
! Description <br />
! Grid Location<br />
|-<br />
| '''osl2.nac.uci.edu:9006''' <br />
| University of California, Irvine <br />
| The "UCI Welcome" region connected to OSGrid. It is run by Diva (Crista Lopes) on a machine owned by the University of California, Irvine. You can link to it as a way to link to OSGrid. <br />
| OSGrid is centered at 10,000, 10,000<br />
|-<br />
| '''osl3.nac.uci.edu:9000''' <br />
| University of California, Irvine <br />
| The "UC Irvine" region connected to OSGrid, neighboring Wright Plaza. You can link to it as a way to link to OSGrid. <br />
| OSGrid is centered at 10,000, 10,000<br />
|-<br />
| '''ucigrid02.nacs.uci.edu:9000''' <br />
| University of California, Irvine <br />
| The UCI Grid <br />
| UCIGrid is centered at 8,888, 8,888<br />
|-<br />
| '''ucigrid04.nacs.uci.edu:9003''' <br />
| University of California, Irvine <br />
| The UCI Grid, region "Gateway 3000". Link your lower-1,000's grid to this node in order to bridge to grids in the 10,000's. <br />
| This node is positioned at 3,000, 3,000<br />
|-<br />
| '''ucigrid04.nacs.uci.edu:9007''' <br />
| University of California, Irvine <br />
| The UCI Grid, region "Gateway 7000". Link your 10,000's grid to this node in order to bridge to grids in the lower-1,000's. <br />
| This node is positioned at 7,000, 7,000.<br />
|-<br />
| '''www.meanduland.com:9124''' <br />
| Grid Meanduland <br />
| [http://www.menduland.com], Meanduland - by Ayana and Frank Northmead. Residential grid and playground for couples. Quite, peaceful and fun. Regular live music concerts and coming soon - rpg's, adventure simulations, private beaches, sail boat racing, dune buggy racing, and much much more. All welcome, no membership or landownership requirements, you just need desire to have fun and be a good neighbor. Regions available at cost during Alpha and Beta development of OpenSim. <br />
| Centered at 8000, 8000<br />
|-<br />
| '''hypergrid.cyberlandia.net:9100''' <br />
| Cyberlandia <br />
| The "Cyberlandia Gw" region. http://www.cyberlandia.net Metaverso italiano 3D, more to 250 region and 1000 users. You can link to it as a way to link to Cyberlandia. <br />
| Cyberlandia is centered at&nbsp;???<br />
|-<br />
| '''venezia.cyberlandia.net:9100''' <br />
| Cyberlandia <br />
| The "Osgrid Gw" region connected to Cyberlandia grid http://www.cyberlandia.net. Search on map "Cyberlandia grid" You can link to it as a way to link to OSGrid. <br />
| OSGrid is centered at 10,000, 10,000<br />
|-<br />
| '''regions.ralf-haifisch.biz:9000:Sharkland Tropical 1''' <br />
| Ralf Haifisch on osgrid <br />
| The "Sharkland Tropical" region connected to OSGrid. German welcome aerea, Freebie aerea, region rental, pretty tropical regions <br />
| Centered at 10000,10000 <br />
<br><br />
<br />
|-<br />
| '''joomla-italia.net:9000''' <br />
| Social Network Italia <br />
| The "SNI City" region connected to SNI (Social Network Italia) grid http://www.opensim-italia.net. This grid is connected with Osgrid,Collateral World,Francogrid and Darwin <br />
| Centered at&nbsp;???<br />
|-<br />
| '''collateral.opensim-italia.net:9000''' <br />
| Part of Social Network Italia <br />
| Collateral World <br />
| Centered at&nbsp;???<br />
|-<br />
| '''88.191.79.199:9050''' <br />
| Francogrid <br />
| Francogrid node, connected to "City", behind the welcome land of Francogrid "Orion" <br />
| Centered at 1000 1000<br />
|-<br />
| '''94.23.8.158:9300''' <br />
| Le Monde de Darwin <br />
| The Lost World of Darwin http://www.LeMondedeDarwin.com. [[Image:Hypergrid.jpg|200px]] <br />
| Centered at 1000 1000<br />
|-<br />
| '''sg.k-grid.com:9000''' <br />
| K-Grid <br />
| The Kool grid for the Kool KidZ . Feel free to visit us. The main Gateway is located at 3700,3700 so take that in account before any HyperJump. Adress updated 02/07/09 <br />
| This node is located at 3700,3700<br />
|-<br />
| '''metropolis.hypergrid.org:9000''' <br />
| METROPOLIS-Grid <br />
| The Region "Center-World" connected to the METROPOLIS-Grid http://metropolis.hypergrid.org . German Grid with a lot of free Content and free SIM-hosting. Connected via HG to the most of the Grids listed here <br />
| Centered at 7000,7000<br />
|-<br />
| '''ascent.bluewallgroup.com:9910''' <br />
| BlueWall Information Technologies <br />
| This region is in a good proximity @ (6000,6000) for intermediate jumps to OSGrid from grids in the (2000,2000) range, or any region within 4096 units. [[Image:Hypernaut 001.png|thumb|none|150px|Get your Hypernaut here :)]] <br />
| Centered at 6000,6000<br />
|-<br />
| '''http://myopengrid.com:9005/''' <br />
| '''MyOpenGrid''' <br />
| Myopengrid is connected to osl2.nac.uci.edu "Osgrid Gateway" and 88.191.79.199 9050 "Franco Grid" <br />
| Centered at 7000,7000<br />
|-<br />
| '''cuonsim1.de:9300''' <br />
| Cuon-Grid <br />
| Cuon-Grid is a little grid and has some Main Sims with linux themes, server are in Germany. To login in to the grid use this http://sim-linuxmain.org:8081/CuonGrid/index.html. There are free sims for testing. <br />
| Centered at 10,000, 10,000<br />
|-<br />
| '''metaversesims.net:9000''' <br />
| Metaverse Sims <br />
| 6-region standalone hypergrid on V. 0.7.2 (Dev)<br />
| Centered at 9000, 9000 <br />
<br><br />
<br />
|-<br />
| '''87.230.89.74:9000''' <br />
| SCHWARZE WELT <br />
| inworld location of www.schwarze-welle.de , the maybe biggest dark music streaming readio <br />
| 100000 10000 <br />
<br><br />
<br />
|-<br />
| '''peak.sciencesim.com:9001''' <br />
| ScienceSim <br />
| [http://www.sciencesim.com/ ScienceSim] is a virtual world created for the high performance computing community for scientific visualizations, a number of interesting real world terrains (Mt St Helens and Yellowstone Park) and some astronomical simulations. And some useful, BSD-licensed content. <br />
| Centered at 10000,10000<br />
|-<br />
| '''alpha.bubblecloud.org:9000''' <br />
| Bubble Cloud <br />
| The alpha 00 is the entrance area to bubble cloud grid. Bubble cloud is test grid where anyone can experiment. If you build something please do it in medieval fantasy setting for others to enjoy. <br />
| Centered at 10,000, 10,000<br />
|-<br />
| '''opensim.m34.mx-host.de:9090''' <br />
| OpenSIM.de Sim1 <br />
| [http://www.opensim.de OpenSim.de], 4 Server (Linux/Windows), hypergrided standalones, 16 Regions, German Users (Deutsche Benutzer), Live-Support, IRC-Gateway, Wiki, FAQ, Howto´s, Downloads. Connected to most of the Grids and some hypergrided standalones. <br />
| Centered at 4400,4400<br />
|-<br />
| '''64.150.180.188:9031''' <br />
| Virtual World Trade Center <br />
| [http://PleasurePlanet.net], The VWTC. A repository for freebie items to share with the OS community. Weekly oar files will be made freely available on 4shared.com. <br />
| VWTC is at 3003, 3003<br />
|-<br />
| '''condensationland.com:9000''' <br />
| Zonja Capalini <br />
| Condensation Land, 10 regions <br />
| Centered at 7789, 7789<br />
|-<br />
| '''66.240.232.94:9010''' <br />
| Snoopy Pfeffer <br />
| OSGrid, Samsara, freebie shopping region <br />
| Centered at 10006, 9999<br />
|-<br />
| '''66.240.232.94:9011''' <br />
| Snoopy Pfeffer <br />
| OSGrid, Snoopies, dance club and event region <br />
| Centered at 10005, 9999<br />
|-<br />
| '''twistedsky.net:9000''' <br />
| Twisted Sky <br />
| Welcome region on the Twisted Sky World Grid (at 998, 1000) - http://twistedsky.net <br />
| Centered at 1000, 1000<br />
|-<br />
| '''www.xn--tln-tna.net:8002''' <br />
| Tlön <br />
| Tlön, Uqbar and Orbis Tertius - http://www.tlön.net (http://www.xn--tln-tna.net/) <br />
| Centered at 7650, 7650<br />
|-<br />
| '''www.pmgrid.org:9020''' <br />
| PMGrid <br />
| PMGrid is a set of areas for grid development prior to implementation so there is no specific theme. Visit here and see a varied range of builds and perhaps get some ideas for yourself.[http://pmgrid.julpet.ath.cx http://www.pmgrid.org] <br />
| centered at 7000, 7000<br />
|-<br />
| '''62.40.147.45:9100''' <br />
| Austria Grid <br />
| A virtual copy of the country Austria. This Grid is for all those who want to find their hometown in the virtual landscape of a virtual Austria.This Grid is not only for creating a virtual Austria, it's a meeting point, a place for communication. For permanent link-exchange, write an email. <br />
| centered at 7000, 6990<br />
<br />
|-<br />
| YourSimSpot.com:9000<br><br />
| [http://YourSimSpot.com YourSimSpot]<br><br />
| Main region at YourSimSpot (1000,1000) - [http://YourSimSpot.com YourSimSpot] <br />
| Centered at 1000, 1000<br><br />
|-<br />
| my3dworld.org:9000<br><br />
| My3dWorld<br><br />
| Main region at My3dworld (7900,7900)<br>Home of Johnny 5 bot[[Image:Johnny5.jpg|thumb|none|128px|Meet Johnny 5]]16 plot Megaregion has Hypergate, linked to several other grids on map - [http://my3dworld.org My3dWorld]<br><br />
| Centered at 7900, 7900<br><br />
|-<br />
| sim-world.org:8003<br><br />
| www.sim-world.org<br><br />
| Main region at sim-world island (10000,10000)<br>41 regions has teleport board linked to several other regions on map <br><br />
| Centered at 10000, 10000<br><br />
|-<br />
| universi.servegame.org:9000&nbsp;&nbsp;&nbsp;&nbsp; <br />
| Shatar Lorefield [Universi&nbsp;Legacy]<br />
| <br />
Main region at Oasis (5000, 5000)<br />
<br />
Hypergrid enabled&nbsp;Standalone sim. Need some people to populate this Desert World.<br />
<br />
| Centered at 5000, 5000<br />
|}<br />
<br />
&nbsp;<br />
<br />
<br />
[[Category:Hypergrid]]</div>Fleephttp://opensimulator.org/wiki/Public_Hypergrid_NodesPublic Hypergrid Nodes2011-05-23T12:33:56Z<p>Fleep: /* Hypergrid 1.5 - Enabled Grids/Sims */</p>
<hr />
<div>{{Template:Quicklinks}} <br> <br />
<br />
__TOC__ <br />
<br />
== Hypergrid-enabled sims ==<br />
<br />
The following is a list of hypergrid-ready nodes that you can use for testing your installation and for linking your world. Please add your public node at the bottom of the list if you wish to help build a web of opensims! Anyone found inserting a grid higher in the list may have their entry removed. <br />
<br />
For the time being, and until the security concerns are addressed, we advise you to be careful about who you link to.<br />
<br />
== Hypergrid 1.5 - Enabled Grids/Sims ==<br />
<br />
The following is a list of hypergrid 1.5-ready nodes that you can use for testing your installation and for linking your world. Please add your public node at the bottom of the list if you wish to help build a web of opensims! Anyone found inserting a grid higher in the list may have their entry removed.<br />
<br />
Please note that HG 1.5 is very new and a lot of these Sims/Grids are only there temporarily.<br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center"<br />
|-<br />
! [[Hypergrid|link-region server and port]] <br />
! Organization <br />
! Description <br />
! Grid Location<br />
|-<br />
| ucigrid00.nacs.uci.edu:8002<br />
| UCI Grid <br />
| [http://ucigrid00.nacs.uci.edu:8002 UCIGrid] V 0.7.1 (post-fixes)<br />
| Centered at 5000,5000<br />
|-<br />
| login.germangrid.de:8002<br />
| GermanGrid <br />
| [http://www.germangrid.de GermanGrid] V 0.71(dev)<br />
| Centered at 8000,8000<br />
|-<br />
| marlokir.selfip.net:9000<br />
| Marlokir<br />
| Just a small standalone for testing running on version 0.7.1 (dev).<br />
It will probably be online only temporarily.<br />
| Centered at 4500,4500<br />
|-<br />
| gridnirvana.net:8002:Rhiga<br />
| Jez's World<br />
| A small private Estate, previously stand alone - but for now part of GridNirvana.<br />
Please feel free to pop over and visit.<br />
| Centered at 6500,6500<br />
|-<br />
| virtual.aiai.ed.ac.uk:8002:Openvue <br />
| Openvue<br />
| Openvue grid at Virtual University of Edinburgh<br />
| Centered at 1000,1000<br />
|-<br />
| virtual.aiai.ed.ac.uk:8002:Vue-5000 <br />
| Vue-5000<br />
| Openvue grid at Virtual University of Edinburgh<br />
| Centered at 5000,5000<br />
|-<br />
| virtual.aiai.ed.ac.uk:8002:Vue-9000 <br />
| Vue-9000<br />
| Openvue grid at Virtual University of Edinburgh<br />
| Centered at 9000,9000<br />
|-<br />
| 145.99.250.20:8002<br />
| DWGrid<br />
| DWGrid<br />
| Centered at 7000,7000<br />
|-<br />
| metaversesims.net:9000<br />
| Metaverse Sims<br />
| 6-region standalone hypergrid on V. 0.7.2 (Dev)<br />
| Centred at 9000,9000<br />
|-<br />
| opensim.betatechnologies.info:8002<br />
| Beta Technologies OpenSim Grid (btgrid)<br />
| Grid for internal development, mostly for academic research and backups from old sims. V. 0.7.0.1<br />
| Centered at 3650,3650<br />
|-<br />
| hippo.is-a-geek.com:8002<br />
| The Bloomfield Grid<br />
| This is a personal grid for my friends and familly, However we welcome others with a smile. V. 0.7.0.1 (We are also Hyper Gate enabled)<br />
| Centered at 5000,5000<br />
|-<br />
| tritongrid.com:8002<br />
| Triton Grid<br />
| This is a 100+ region Public grid. All are welcome (We are also Hyper Gate enabled in several regions throughout the grid) (HG 1.5X Interface 7 Runing the latest .71Dev revs. maintains creator data)<br />
| Centered at 9000,9000<br />
|-<br />
| condensationland.com:9000<br />
| Condensation Land<br />
| 10 regions<br />
| Centered at 7789, 7789<br />
|-<br />
| chazzmac.webhop.org:9000<br />
| eden 16 regions<br />
| full 3 story hidden freebie mall, HyperGate, WiFi at http://chazzmac.webhop.org:9000/wifi/<br />
| Centered at 3917, 4144<br />
|-<br />
| metaversesailing.com:9000<br />
| Sailing Grid <br />
| A D2 grid on V 0.7.2(release)a .Net hosted 16 region mega with support regions<br />
| Centered at 7000,7000<br />
|-<br />
| ogzoco.no-ip.org:8002<br />
| Ogzoco Grid & RaionFort<br />
| Mentolyptus Destiny testing & work grid. Hypergrid 1.5, OpenSim 0.7.1 (Currently OsGrid Revision 0.7.1.dev.80f9022 - 10-22-2010). Gateway to multiple grids on map. Photos: http://www.flickr.com/photos/mentolyptus/ - Twitter: https://twitter.com/Ogzoco - EMail: ogzoco@gmail.com<br />
| Centered at 7852, 7852<br />
|-<br />
| grid.ansky.ca:8002<br />
| AnSky Grid<br />
| 10 regions<br />
| Centered at 7100, 7100<br />
|-<br />
| sim-world.org:8003<br />
| Sim-World Welcome Center<br />
| 41 regions<br />
| Centered at 10000, 10000<br />
|-<br />
| unethika.kicks-ass.net:8002<br />
| unethika<br />
| It works (most of the time) and it's fun! Come via hg hop or snag an avatar at [http://unethika.kicks-ass.net/ http://unethika.kicks-ass.net/] ! We also run a working(ish) Freeswitch server. <no guarantees, of course :P><br />
| Centered at 7500, 7500<br />
|-<br />
| odosys.dyndns.org:8002<br />
| Odonata Systems<br />
| Small HG 1.5i7 grid - 'Tenebrae' transmedia fiction project and personal hypergrid sanctuary. Hypernauts welcome: [http://odosys.dyndns.org:8002/wifi accounts]. Hosted on laptop w/residential DSL (OSGrid 0.7.1-dev (b82b0b1) / Ubuntu 10.10 / Mono 2.6.7)<br />
| Centered at 8011, 8013<br />
|-<br />
| fleepgrid.com:8002<br />
| FleepGrid<br />
| Small personal test grid of Fleep Tuque, 6 to 8 sims at any given time. Grid hoppers and testers welcome. Running Opensim 0.7.1 Release HG 1.5 (i7). [http://twitter.com/fleep http://twitter.com/fleep]<br />
| Centered at 9000, 9000<br />
|-<br />
| viradu.com:9000<br />
| Viradu Science Fiction World<br />
| [[Image:Vban.jpg|180px|thumb|left|Viradu.com Science Fiction Virtual World]]12 Science Fiction themed regions run by Michael Blade Sci-fi blogger dedicated to writers and those who love it. Hypergrid Teleporters, Builders welcome, free land grab, rules apply. Tell others about us...Join in the fun! => [http://viradu.com http://viradu.com]<br>How to build your own virtual world here => [http://rocketvirtual.com RocketVirtual.com]<br />
| Centered at 5001, 5001<br />
|-<br />
| 62.40.147.45:9090<br />
| Psychedelia Grid <br />
| The home of psychedelic music. This Grid is for all fans of psychedelic music. Watch the bands playing at the festival and stay over night in your tent. <br />
| centered at 6000, 5990<br />
|-<br />
| '''logicamp.dyndns.org:8002:logicamp''' <br />
| Logicamp <br />
| [http://www.logicamp.com/ Logicamp] is a virtual world specialized in camp-site management and virtual tourism. You can visit it throughout our cable network. <br />
| Centered at 8000, 8000<br />
|-<br />
| logicamp.dyndns.org:8002:SPA1<br><br />
| [http://www.logicamp.com logicamp]<br><br />
| Megaregion Entrance (7997,7994)<br>Spa-Francorchamp[[Image:Snapshot 037.png|thumb|none|128px|Spa-Francorchamp]]60 plot Megaregion - [http://logicamp.com logicamp]<br><br />
| Centered at 7900, 7900<br><br />
|-<br />
| map.terravirtuavw.com:8002:Nexus<br><br />
| [http://www.terravirtuavw.com Terra Virtua]<br><br />
| The Terra Virtua intergrid nexus.<br><br />
| 6000,6000<br><br />
|-<br />
| greyhound.champlain.edu:9070 (216.93.159.182:9070) - Also try 9050<br><br />
| Possible future home of Champlain College in Burlington, Vermont<br><br />
| After almost 3 years of working with OpenSim, this is the first we are opening (with caution) for public view). Visit the nursery on region PerryHall. It may be made available to the public. Bear with me as I get Hypergrid working properly.<br><br />
| Centered at 5000, 5000<br><br />
|}<br />
<br />
== External directories of Hypergrid-enabled sims ==<br />
<br />
*[http://www.gridhop.net GridHop] <br />
*[http://hypernodes.org HyperNodes.org]<br />
*[http://www.hyperica.com Hyperica]<br />
*[http://www.thehypergates.com/ The HyperGates] -- The first dynamic, auto-updating HyperGrid directory for both HyperGrid 1.5 ( OpenSim 0.7.x ) and HyperGrid 1.0 ( OpenSim 0.6.x ) standalones & grids. Download the HyperGate from the site now and Join the HyperGate Network. The most reliable HyperGrid directory.<br />
*[http://www.hgurl.com hgurl]<br />
<br />
<br />
== Old List (HG 1.0) ==<br />
<br />
Keeping this here for historical reasons, but most of these don't work anymore.<br />
<br><br />
<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
|-<br />
! [[Hypergrid|link-region server and port]] <br />
! Organization <br />
! Description <br />
! Grid Location<br />
|-<br />
| '''osl2.nac.uci.edu:9006''' <br />
| University of California, Irvine <br />
| The "UCI Welcome" region connected to OSGrid. It is run by Diva (Crista Lopes) on a machine owned by the University of California, Irvine. You can link to it as a way to link to OSGrid. <br />
| OSGrid is centered at 10,000, 10,000<br />
|-<br />
| '''osl3.nac.uci.edu:9000''' <br />
| University of California, Irvine <br />
| The "UC Irvine" region connected to OSGrid, neighboring Wright Plaza. You can link to it as a way to link to OSGrid. <br />
| OSGrid is centered at 10,000, 10,000<br />
|-<br />
| '''ucigrid02.nacs.uci.edu:9000''' <br />
| University of California, Irvine <br />
| The UCI Grid <br />
| UCIGrid is centered at 8,888, 8,888<br />
|-<br />
| '''ucigrid04.nacs.uci.edu:9003''' <br />
| University of California, Irvine <br />
| The UCI Grid, region "Gateway 3000". Link your lower-1,000's grid to this node in order to bridge to grids in the 10,000's. <br />
| This node is positioned at 3,000, 3,000<br />
|-<br />
| '''ucigrid04.nacs.uci.edu:9007''' <br />
| University of California, Irvine <br />
| The UCI Grid, region "Gateway 7000". Link your 10,000's grid to this node in order to bridge to grids in the lower-1,000's. <br />
| This node is positioned at 7,000, 7,000.<br />
|-<br />
| '''www.meanduland.com:9124''' <br />
| Grid Meanduland <br />
| [http://www.menduland.com], Meanduland - by Ayana and Frank Northmead. Residential grid and playground for couples. Quite, peaceful and fun. Regular live music concerts and coming soon - rpg's, adventure simulations, private beaches, sail boat racing, dune buggy racing, and much much more. All welcome, no membership or landownership requirements, you just need desire to have fun and be a good neighbor. Regions available at cost during Alpha and Beta development of OpenSim. <br />
| Centered at 8000, 8000<br />
|-<br />
| '''hypergrid.cyberlandia.net:9100''' <br />
| Cyberlandia <br />
| The "Cyberlandia Gw" region. http://www.cyberlandia.net Metaverso italiano 3D, more to 250 region and 1000 users. You can link to it as a way to link to Cyberlandia. <br />
| Cyberlandia is centered at&nbsp;???<br />
|-<br />
| '''venezia.cyberlandia.net:9100''' <br />
| Cyberlandia <br />
| The "Osgrid Gw" region connected to Cyberlandia grid http://www.cyberlandia.net. Search on map "Cyberlandia grid" You can link to it as a way to link to OSGrid. <br />
| OSGrid is centered at 10,000, 10,000<br />
|-<br />
| '''regions.ralf-haifisch.biz:9000:Sharkland Tropical 1''' <br />
| Ralf Haifisch on osgrid <br />
| The "Sharkland Tropical" region connected to OSGrid. German welcome aerea, Freebie aerea, region rental, pretty tropical regions <br />
| Centered at 10000,10000 <br />
<br><br />
<br />
|-<br />
| '''joomla-italia.net:9000''' <br />
| Social Network Italia <br />
| The "SNI City" region connected to SNI (Social Network Italia) grid http://www.opensim-italia.net. This grid is connected with Osgrid,Collateral World,Francogrid and Darwin <br />
| Centered at&nbsp;???<br />
|-<br />
| '''collateral.opensim-italia.net:9000''' <br />
| Part of Social Network Italia <br />
| Collateral World <br />
| Centered at&nbsp;???<br />
|-<br />
| '''88.191.79.199:9050''' <br />
| Francogrid <br />
| Francogrid node, connected to "City", behind the welcome land of Francogrid "Orion" <br />
| Centered at 1000 1000<br />
|-<br />
| '''94.23.8.158:9300''' <br />
| Le Monde de Darwin <br />
| The Lost World of Darwin http://www.LeMondedeDarwin.com. [[Image:Hypergrid.jpg|200px]] <br />
| Centered at 1000 1000<br />
|-<br />
| '''sg.k-grid.com:9000''' <br />
| K-Grid <br />
| The Kool grid for the Kool KidZ . Feel free to visit us. The main Gateway is located at 3700,3700 so take that in account before any HyperJump. Adress updated 02/07/09 <br />
| This node is located at 3700,3700<br />
|-<br />
| '''metropolis.hypergrid.org:9000''' <br />
| METROPOLIS-Grid <br />
| The Region "Center-World" connected to the METROPOLIS-Grid http://metropolis.hypergrid.org . German Grid with a lot of free Content and free SIM-hosting. Connected via HG to the most of the Grids listed here <br />
| Centered at 7000,7000<br />
|-<br />
| '''ascent.bluewallgroup.com:9910''' <br />
| BlueWall Information Technologies <br />
| This region is in a good proximity @ (6000,6000) for intermediate jumps to OSGrid from grids in the (2000,2000) range, or any region within 4096 units. [[Image:Hypernaut 001.png|thumb|none|150px|Get your Hypernaut here :)]] <br />
| Centered at 6000,6000<br />
|-<br />
| '''http://myopengrid.com:9005/''' <br />
| '''MyOpenGrid''' <br />
| Myopengrid is connected to osl2.nac.uci.edu "Osgrid Gateway" and 88.191.79.199 9050 "Franco Grid" <br />
| Centered at 7000,7000<br />
|-<br />
| '''cuonsim1.de:9300''' <br />
| Cuon-Grid <br />
| Cuon-Grid is a little grid and has some Main Sims with linux themes, server are in Germany. To login in to the grid use this http://sim-linuxmain.org:8081/CuonGrid/index.html. There are free sims for testing. <br />
| Centered at 10,000, 10,000<br />
|-<br />
| '''metaversesims.net:9000''' <br />
| Metaverse Sims <br />
| 6-region standalone hypergrid on V. 0.7.2 (Dev)<br />
| Centered at 9000, 9000 <br />
<br><br />
<br />
|-<br />
| '''87.230.89.74:9000''' <br />
| SCHWARZE WELT <br />
| inworld location of www.schwarze-welle.de , the maybe biggest dark music streaming readio <br />
| 100000 10000 <br />
<br><br />
<br />
|-<br />
| '''peak.sciencesim.com:9001''' <br />
| ScienceSim <br />
| [http://www.sciencesim.com/ ScienceSim] is a virtual world created for the high performance computing community for scientific visualizations, a number of interesting real world terrains (Mt St Helens and Yellowstone Park) and some astronomical simulations. And some useful, BSD-licensed content. <br />
| Centered at 10000,10000<br />
|-<br />
| '''alpha.bubblecloud.org:9000''' <br />
| Bubble Cloud <br />
| The alpha 00 is the entrance area to bubble cloud grid. Bubble cloud is test grid where anyone can experiment. If you build something please do it in medieval fantasy setting for others to enjoy. <br />
| Centered at 10,000, 10,000<br />
|-<br />
| '''opensim.m34.mx-host.de:9090''' <br />
| OpenSIM.de Sim1 <br />
| [http://www.opensim.de OpenSim.de], 4 Server (Linux/Windows), hypergrided standalones, 16 Regions, German Users (Deutsche Benutzer), Live-Support, IRC-Gateway, Wiki, FAQ, Howto´s, Downloads. Connected to most of the Grids and some hypergrided standalones. <br />
| Centered at 4400,4400<br />
|-<br />
| '''64.150.180.188:9031''' <br />
| Virtual World Trade Center <br />
| [http://PleasurePlanet.net], The VWTC. A repository for freebie items to share with the OS community. Weekly oar files will be made freely available on 4shared.com. <br />
| VWTC is at 3003, 3003<br />
|-<br />
| '''condensationland.com:9000''' <br />
| Zonja Capalini <br />
| Condensation Land, 10 regions <br />
| Centered at 7789, 7789<br />
|-<br />
| '''66.240.232.94:9010''' <br />
| Snoopy Pfeffer <br />
| OSGrid, Samsara, freebie shopping region <br />
| Centered at 10006, 9999<br />
|-<br />
| '''66.240.232.94:9011''' <br />
| Snoopy Pfeffer <br />
| OSGrid, Snoopies, dance club and event region <br />
| Centered at 10005, 9999<br />
|-<br />
| '''twistedsky.net:9000''' <br />
| Twisted Sky <br />
| Welcome region on the Twisted Sky World Grid (at 998, 1000) - http://twistedsky.net <br />
| Centered at 1000, 1000<br />
|-<br />
| '''www.xn--tln-tna.net:8002''' <br />
| Tlön <br />
| Tlön, Uqbar and Orbis Tertius - http://www.tlön.net (http://www.xn--tln-tna.net/) <br />
| Centered at 7650, 7650<br />
|-<br />
| '''www.pmgrid.org:9020''' <br />
| PMGrid <br />
| PMGrid is a set of areas for grid development prior to implementation so there is no specific theme. Visit here and see a varied range of builds and perhaps get some ideas for yourself.[http://pmgrid.julpet.ath.cx http://www.pmgrid.org] <br />
| centered at 7000, 7000<br />
|-<br />
| '''62.40.147.45:9100''' <br />
| Austria Grid <br />
| A virtual copy of the country Austria. This Grid is for all those who want to find their hometown in the virtual landscape of a virtual Austria.This Grid is not only for creating a virtual Austria, it's a meeting point, a place for communication. For permanent link-exchange, write an email. <br />
| centered at 7000, 6990<br />
<br />
|-<br />
| YourSimSpot.com:9000<br><br />
| [http://YourSimSpot.com YourSimSpot]<br><br />
| Main region at YourSimSpot (1000,1000) - [http://YourSimSpot.com YourSimSpot] <br />
| Centered at 1000, 1000<br><br />
|-<br />
| my3dworld.org:9000<br><br />
| My3dWorld<br><br />
| Main region at My3dworld (7900,7900)<br>Home of Johnny 5 bot[[Image:Johnny5.jpg|thumb|none|128px|Meet Johnny 5]]16 plot Megaregion has Hypergate, linked to several other grids on map - [http://my3dworld.org My3dWorld]<br><br />
| Centered at 7900, 7900<br><br />
|-<br />
| sim-world.org:8003<br><br />
| www.sim-world.org<br><br />
| Main region at sim-world island (10000,10000)<br>41 regions has teleport board linked to several other regions on map <br><br />
| Centered at 10000, 10000<br><br />
|-<br />
| universi.servegame.org:9000&nbsp;&nbsp;&nbsp;&nbsp; <br />
| Shatar Lorefield [Universi&nbsp;Legacy]<br />
| <br />
Main region at Oasis (5000, 5000)<br />
<br />
Hypergrid enabled&nbsp;Standalone sim. Need some people to populate this Desert World.<br />
<br />
| Centered at 5000, 5000<br />
|}<br />
<br />
&nbsp;<br />
<br />
<br />
[[Category:Hypergrid]]</div>Fleephttp://opensimulator.org/wiki/0.7.1_Release0.7.1 Release2011-04-23T16:38:19Z<p>Fleep: /* Archives Changes/Additions */</p>
<hr />
<div>'''PLEASE NOTE. THIS PAGE REFERS TO A RELEASE WHICH HAS NOT YET OCCURRED. Thus, these notes are incomplete.'''<br />
<br />
'''The current release candidate is 0.7.1-rc1'''<br />
<br />
[[0.7.1 Planning]]<br />
<br />
=Release Notes=<br />
<br />
As always, OpenSim is alpha software. It's likely but not guaranteed to work and various usage scenarios (standalone, grid, hypergrid, etc.) in combination with different dependencies (e.g. mono) can produce unexpected or unstable behaviour. In other words, if it breaks you get to keep both pieces.<br />
<br />
If you are upgrading from a version prior to 0.7.x, make sure to read the [[0.7 Release]] notes. There have been extensive changes in OpenSimulator from 0.6.x to 0.7. If you are upgrading from 0.7, please read the [[0.7.0.1 Release]] and [[0.7.0.2 Release]] notes.<br />
<br />
This is a major release, the first one supporting Viewer 2's new features -- media on a prim and meshes. However, there are currently issues using viewer 2 and derivatives. The most serious are<br />
<br />
# Default appearance cannot be changed. This is because we do not yet bundle the minimum body part/clothing set (eyes, shape, skin, hair, pants, shirt) to satisfy viewer 2. One workaround is to first create the minimum part/clothing set with viewer 1. Another workaround is to use a web interface that creates a default avatar before login.<br />
# The world map does not show up properly.<br />
# Over time, the current outfit folder may fill with an unmanageable number of inventory links that cannot be deleted.<br />
<br />
We hope to resolve these problems in subsequent releases.<br />
<br />
==Backwards Compatibility Notices==<br />
<br />
* Due to a libomv bug fix, teleports in this release are incompatible with earlier OpenSim releases. This affects primarily Hypergrid teleports, since simulators within the same grid tend to be all in the same version. But if grids have a mix of simulator versions in them, TPs will fail between 0.7.1 and earlier releases.<br />
<br />
==Archives Changes/Additions==<br />
<br />
* Added -v|verbose option to save iar<br />
* Removed the restriction of having to be logged in when loading/saving iars<br />
* Allow OARs and IARs to save and load meshes. IARs can also save coalesced items. If an IAR contains a coalesced item then it might cause errors if reloaded on an older version of OpenSim that does not have support for coalescence.<br />
* Added the option of preserving creator information upon creating archives (OARs and IARs). This is done with a new -p|--profile=<url> option present in save iar/oar. If this option is present, then avatar names are saved in the form <firstname>.<lastname>@<url> (e.g. Neal.Stephenson@metaverse.org). This option should be considered experimental, as are IARs in their entirety. IARs created using the --profile option will not be loadable on OpenSim 0.7.0.2 and earlier. IARs created without this option will be loadable (with the coalescence caveat above).<br />
<br />
==Scripting Changes/Additions==<br />
<br />
* OSSL function names normalization. See [[OSSL Implemented]]<br />
* Added: osUnixTimeToTimestamp, osTeleportOwner, osSetProjectionParam, osSetProjectionParam<br />
* Add PARCEL_DETAILS_ID to LSL<br />
<br />
==Hypergrid Changes/Additions==<br />
<br />
* Normalized Hypergrid addresses to always use standard URLs. So, for example: http://foo.com/hg/service.php is now a valid HG address. This allows for web-compliant implementations of the Hypergrid services.<br />
* link-region command syntax change: link-region x y URL [region name]. Example: link-region 9000 9000 http://hg.osgrid.org:80<br />
* Creator info is now preserved upon HG asset transfers. Complete creator info now shown for the corresponding objects via the viewer as first.last @ domain<br />
* Support for running the HG services behind proxies (XFF header processing)<br />
* Added an option for grid operators to prevent their grid's assets to be transferred to other grids even if the objects are copyable, while allowing foreign visitors to come in. See configuration changes.<br />
* Added checks against hyperlinking to the same grid<br />
<br />
==DB migrations==<br />
<br />
* regions: increased size of region name<br />
* inventoryitems: increased size of creatorID<br />
* prims, primitems: increased size of CreatorID<br />
* Avatars: Value field from VARCHAR(255) to TEXT<br />
* Presence: added LastSeen field<br />
<br />
==General Changes/Additions==<br />
<br />
* Standard SQLite database plugin now works on Mac OSX and 64 bit Linux.<br />
* Now compatible with MySQL 5.5 databases and later.<br />
* Support for coalesced objects in inventory. A coalescence is taken when objects in different linksets are selected and taken simultaneously in the viewer.<br />
* Support for meshes and initial support for mesh physics. <br />
* New console commands: show pending-objects, show circuits, show http-handlers, show caps, land clear, land show, show throttles, region restart [options], etc.<br />
* Object serialization completely rewritten: moved away from automatic .NET serialization. For now the external representation is exactly the same as before, so everything is backwards compatible.<br />
* Updated ODE to post 11.1 (r1755).<br />
* Improved Linden UDP client stack implementation for better Second Life viewer responsiveness.<br />
* Added ability for GetTexture to serve multiple image formats, not just jp2k<br />
* Improved ban checks on TPs and crossings<br />
* Refactored the Freeswitch services so that they conform to the robust style. See [[Freeswitch]]<br />
* Added a bare bones shared and non-shared region modules that serve as examples<br />
* RemoteAdmin service can now bind to a private ip address<br />
* Add support for cross-domain (CORS) AJAX requests to REST console.<br />
* Fixed Flotsam groups<br />
* Removed unimplemented stub Sirikata client stack<br />
* Added viewer's ip address, channel, mac, and id0 to agent circuit data, so that proxies can intervene on logins and HG TPs.<br />
* Changed to using a managed code SQLite library, CSharpSqlite. This makes SQlite work again across the board.<br />
* Refactored simulator data service and estate data service. See configuration changes.<br />
* Added support for loading a terrain tile for multiple regions with image files like tiff and jpeg. Previously this only worked for single regions.<br />
* “config show” command added as a synonym for the “config get” command, in order to bring it into line with other show commands. “config show” will print out the configuration of a region simulator as aggregated from all the loaded configuration files, which can be handy for debugging and fault finding.<br />
* Initial region and estate configuration improved.<br />
<br />
==Configuration Changes from 0.7.x==<br />
<br />
* Simulator main configuration file (OpenSim.ini) has been split between two files: OpenSimDefaults.ini and OpenSim.ini[.example]. The former contains expert/less used configuration variables; the latter contains the configuration variables that most users should know about and change. Do not change variables in OpenSimDefaults.ini; instead, if/when you want to change their values, do it in your own OpenSim.ini by overriding the values.<br />
* New configuration sections: [SimulationDataStore] and [EstateDataStore]. These are system configs in non-writable .ini's. Users can set the connection strings for them in [DatabaseService] section. See .example.<br />
* New configuration variable in the simulator's [HGInventoryAccessModule] section: OutboundPermissions, which controls whether sim operators want to allow visitors to take assets into their grids. If set to False, no assets are sent outbound, even if the objects are copyable.<br />
* New configuration variable in the simulator's [GridService] section: NetworkConnector, so that it can take both robust and simian connectors. Affects grids only, not standalones<br />
* Removed obsolete configuration variables: PrimTerseUpdatesPerPacket, AvatarTerseUpdatesPerPacket, PrimFullUpdatesPerPacket. Added new one: PrimUpdatesPerCallback<br />
* New configuration variables in [Startup] section: DecodedSculptMapPath, UseMeshiesPhysicsMesh<br />
* (HG) New preferred syntax for service URLs in [LoginService] section: SRV_<name>. Old way still works, but it's obsolete. Please see .examples.<br />
* (HG) New config under [GridService] in the simulators side (GridCommon/StandaloneCommon): Gatekeeper. Please see .examples.<br />
<br />
==Bug fixes==<br />
<br />
* Fixed bug where "My estate" name was always used even if the user entered a different name on initial setup<br />
* Added estate name to show regions console command<br />
* Fixed negative dripAmount in TokenBucket which caused random login failures when scene_throttle is set (mantis #5365)<br />
* Improved handling of X-Forwarded-For (XFF) header<br />
* Improved output of show neighbours<br />
* Fixed leak in caps handlers deregistration<br />
* Fixed llSetTexture<br />
* Send object date to viewer in microsecs (mantis #3990)<br />
* Make UUID 3a367d1c-bef1-6d43-7595-e88c1e3aadb3 reference a full alpha texture.<br />
* Change UpdateAgent (for changes in agent position) to be sent once to each simulator rather than once to each region. This should help with some of the delays caused by multiple outstanding requests to a single service point.<br />
* Change SimianGroupsServicesConnectorModule.GetAgentGroupMembership() so that it returns null if the user isn't a member of the group.<br />
* If a non-globbed included file from config cannot be found then warn the user<br />
* Display supported file extensions/formats in "terrain load help" (Mantis #5349)<br />
* Added loading and saving of terrain files using Terragen format (Mantis #1564)<br />
* Check estate bans for walking crossings<br />
* Fixed prim count display in cut regions.<br />
* Implemented SendPLacesReply<br />
* Fix OAR parcel loading so that old parcels are replaced by the new instead of merged.<br />
* Show local IDs in "land show" output.<br />
* Make "show info" and "show version" show the same version text<br />
* Force objectId to UUID.Zero for non-overridden animations in AvatarAnimation packet<br />
* Prevent activation and deactivation of gestures from clobbering the slam bits<br />
* Change gesture activation to not quash any other flags<br />
* Fix slam bits being lost when editing perms in prim inventory<br />
* Fix direct item give permissions<br />
* Deal with possibly un-initialized scripts in object transfers (mantis #5310)<br />
* Fix HG map tiles on map search<br />
* Bring back remote HG regions' map tiles<br />
* Fixed changing clothes moves avatar to various locations in the region (mantis #5198)<br />
* Fix prim inventory lock down<br />
* Fixed bug in Http server (mantis #5128)<br />
* Fix notecards that end with an embedded object causing an exception<br />
* Revamp the viewer -> banlist packet processing so fix a number of bugs. Remove the too coarse CanEditParcel method in favor of a CanEditParcelProperties method that takes a GroupPowers argument to specify what action is to be taken. Also, make the method to set parcel data much more granular. Permissions in a deeded setting should now work.<br />
* Fixed avie stuck in PREJUMP animation<br />
* Trigger event with flag CHANGED_LINK when agent sits on objects that have not a sit target defined (mantis #4692)<br />
* Fixed nudge movements<br />
* Fix the minimap sitting avatar location bug<br />
* Improved appearance representation and handling on TPs and crossings<br />
* Only force prim persistence before delete if the prim is the result of an unpersisted delink. This considerably improves delete performance for objects with large linksets<br />
* Stop LLUDPServer sending updates after object deletes by always queueing deletes<br />
* Amend GetLinkPrimitiveParams with implementations for PRIM_TEXGEN, PRIM_BUMP_SHINY, PRIM_FULLBRIGHT, and PRIM_GLOW<br />
* llUnsit position fix (mantis #4063)<br />
* Trigger changed events CHANGED_TELEPORT, CHANGED_SCALE, CHANGED_SHAPE, CHANGED_REGION_RESTART, CHANGED_REGION <br />
* Fix handling of landmarks for systems with culture settings other than en_US (mantis #5177)<br />
* Allow use of parameters without specifying a file path with command "save oar"<br />
* Fix joining land parcels not being stored correctly in SQLite (mantis #5230)<br />
* Only perform the take object permissions check if an object is being attached directly from the scene, not from existing inventory<br />
* Fix global region coordinates that are delivered by llRequestSimulatorData.<br />
* Fix gesture and viewer preview sounds not playing<br />
* Fix playing sound from HUDs<br />
* Fix attached sounds from HUDs erroneously being delivered to other avatars<br />
* Do not include hyperlinks in a random region search during a login<br />
* Fix: Write asset data into Asset.db when using SQLite<br />
* Add lsClearWindlightScene() to the lightshare module to remove WL settings from a region and allow normal day cycles to be reestablished<br />
* Fixed wrong physical actor size<br />
* osSetDynamicTextureURL crashed region server (mantis #5165)<br />
* Prevent nullrefs in scene object deletion (mantis #5156)<br />
* Added PRIM_NAME, PRIM_DESC and PRIM_ROT_LOCAL<br />
* Fix llParcelMediaCommandList() so that it applies commands only to the parcel that the script is in, not all parcels<br />
* Fixed a delay in llSetLinkPrimitiveParamsFast<br />
* Alphabetize results on region search by prefix matching<br />
* Fix autoreturn to not return zero objects<br />
* Upgraded Mono.Addins.dll to 0.5. This fixes a problem with region modules and mono 2.6.x+<br />
* Fixed CPU pinned high with HGAssetBroker (mantis #5057)<br />
* Improved CalculateMass<br />
* Prevent dropping someone else's attachments<br />
* Several fixes in SimianGrid connectors<br />
* Restrict top colliders / top scripts to estate managers<br />
* Prevent setting arbitrary groups on your objects<br />
* If you can't edit a prim's inventory, you don't need to see the asset ids. Prevents stealing IDs of animations, sounds and textures from prim inventories.<br />
* Restrict inventory items added in a transaction to folder belonging to the connected client.<br />
* Added delay for llSetPrimitiveParams() and llSetLinkPrimitiveParams() functions per the LSL wiki<br />
* Improve the explanative text of migration failures<br />
* Add LandServices to make landmarks work right in grids<br />
* Fixed length calculations for HTTP texture downloads (the end byte is inclusive in Range: headers)<br />
<br />
[[Category:History]]</div>Fleephttp://opensimulator.org/wiki/0.7.1_Planning0.7.1 Planning2011-04-23T16:35:13Z<p>Fleep: /* STATUS */</p>
<hr />
<div>== Summary ==<br />
Release 0.7.1 will be the first one supporting Viewer 2's new features -- media on a prim, meshes, and multiple attachments per attach point. However, Viewer 2 will still not be very usable on this release due to issues with default avatars and the world map.<br />
<br />
== STATUS ==<br />
Read down to Mantis 4962 through the bug list. Of course, there are piles of bugs though no obvious showstoppers (though the physics sculptie meshings comes up a lot - it's something that I've experienced myself but this will be pre-existing) - [[User:Justincc|Justincc]] 23:23, 11 April 2011 (UTC)<br />
<br />
== MUST DO features and refactorings ==<br />
<br />
*<strike>Use ServerURI consistently when naming+accessing simulator services and HG</strike> (done, pending bugs) ([http://opensimulator.org/mantis/view.php?id=5295 Mantis 5259])<br />
<br />
*<strike>Preserve creator information on archives and HG object transfers</strike> (done, pending eventual bugs<br />
<br />
* <strike>New asset set for Viewer 2</strike> (this has been done a long time ago)<br />
<br />
*<strike>Update Mac ODE library to match Windows and Linux versions. This is a suggestion but I think that it's important to do. We just need a core developer with a Mac to build it from opensim-libs -- [[User:Justincc|Justincc]] 21:37, 6 January 2011 (UTC)</strike><br />
<br />
*<strike>Make sure oar and iars are saving control files as the first file in the archive (this is necessary for proper future version behaviour). Do this and then bump the version number (probably 1.1 on both). I really want to get this in for the first release candidate [[User:Justincc|Justincc]] 01:20, 15 April 2011 (UTC). Done</strike><br />
<br />
* <strike>Decide what to do about coalesced items not working in Hypergrid or IARs/OARs. Remove from 0.7.1 or fix?</strike> In discussion with Diva and Bluewall, decision is to put them behind an experimental switch which will be on for master but off for 0.7.1, since there are many unresolved issues (e.g. with iars/oars, hypergrid and rotations) that will take considerable time to fix and won't be stable for an imminent 0.7.1 anyway [[User:Justincc|Justincc]] 01:19, 15 April 2011 (UTC)<br />
<br />
== MUST FIX bugs ==<br />
<br />
* <strike>Invisible avatars ([http://opensimulator.org/mantis/view.php?id=5234 Mantis 5234])</strike> (Invisible avies are a result of bad textures and/or a result of a bug in the UDP texture sending; people should upgrade their viewers to use HTTP textures)<br />
* <strike>Attachments seem to have random issues</strike> (reported by Melanie, unable to repro) <br />
* <strike>Movement jerkiness, possibly packet handling problem ([http://opensimulator.org/mantis/view.php?id=5256 Mantis 5256])</strike> (it's been addressed as best as possible for the time being)<br />
* <strike>osTeleportAgent bugs ([http://opensimulator.org/mantis/view.php?id=5135 Mantis 5135] and [http://opensimulator.org/mantis/view.php?id=5136 Mantis 5136])</strike> (fixed)<br />
* <strike>Resolve the issues with changed events in LSL ([http://opensimulator.org/mantis/view.php?id=5146 Mantis 5146] and its children). At least those change events should be fixed that already worked in OpenSim release 0.6.9, i.e. CHANGED_OWNER, CHANGED_TELEPORT, CHANGED_REGION, and CHANGED_REGION_RESTART. Should now be resolved.</strike><br />
* <strike>HTTP server crash ([http://opensimulator.org/mantis/view.php?id=5128 Mantis 5128])</strike> (fixed)<br />
* <strike>Parcel prim counts - Melanie is working on this. Now done [[User:Justincc|Justincc]] 22:59, 8 April 2011 (UTC)</strike><br />
* <strike>Make estate configuration friendly on a first OpenSim run without configured regions. At the moment, the user has to remember the previous estate name if they want multiple new regions in the same estate. I find this really annoying and regard it as a must fix, but I'm going to look to address it soon [[User:Justincc|Justincc]] 22:51, 15 March 2011 (UTC)</strike><br />
'''FreeSwitch''' - <strike>Confirm suucessful operation of changes to FreeSwitch module handling from previous 0.6.9/0.7.0.x mechanism for 0.7.1 dev master. See [http://opensimulator.org/mantis/view.php?id=5274 Mantis 5274]</strike>. OpenSim .ini file examples should be maded consistent ([http://opensimulator.org/mantis/view.php?id=5338 Mantis 5338]). Reduce default level of Freeswitch diagnostics to Robust.exe console before release. <strike>Fix or alleviate issue with Viewer 2 causing OpenSim.exe server to be bogged down with FreeSwitch sign in calls ([http://opensimulator.org/mantis/view.php?id=5336 Mantis 5336]). [[User:BlueWall|BlueWall]] Updated mantis ([http://opensimulator.org/mantis/view.php?id=5336 Mantis 5336]) with some logging and packet dumps. SL/Vivox routes everything through https, so everything from there was encrypted. Resolved at r/15249.</strike><br />
<br />
== MUST DO documentation ==<br />
<br />
* Explain split into OpenSimDefaults.ini.<br />
* <strike>Fix Groups setup inline documentation in OpenSim.ini.example</strike>. Done in 19f70b9<br />
* <strike>Change HG version number to indicate incompatibility with HG 1.0 on 0.6.9 and HG 1.5 on 0.7.0.x</strike>Diva says this won't add anything to this release, since adaptor changes mean that people couldn't teleport between incompatible hypergrids anyway.<br />
<br />
== Optional ==<br />
<br />
<strike>* Sort out SQLite issues, possibly switch to completely managed code solution.<br />
** <strike>Updated Linux libraries with SQLITE_ENABLE_COLUMN_METADATA support and add Mono.Data.Sqlite.dll.config to map them to mono. Need updated OSx libraries.</strike><br />
** <strike>Just bought a Mac mini 10 minutes ago, so should be able to help with updated libraries in the next couple of weeks :-) [[User:Justincc|Justincc]] 21:23, 29 March 2011 (UTC) - now done [[User:Justincc|Justincc]] 22:52, 8 April 2011 (UTC) </strike><br />
<strike>* Provide a switch to turn mesh support on and off, for those who don't want mesh on their grids. Or alternatively, start using the general [Modules] mechanism to enable/disable individual modules rather than having to have each module perform and control the check itself.</strike><br />
<br />
== Optional Module Checks ==<br />
<br />
<strike>'''Diva Wifi''' - Establish it works with 0.7.1 release (top level URL and facilties needing login not functioning in previously released 0.7.0.2b version, but do work with latest source version at https://github.com/diva/diva-distribution/ ).</strike><br />
<br />
== Deferred to next release bugs ==<br />
<br />
* For viewer 2, there is no default avatar so appearance is always smoke until the user creates the 4 basic body parts (and pants/shirt as well if they don't want to be naked). I was regarding this as a must-fix but now I'm not so sure - [[User:Justincc|Justincc]] 03:46, 2 November 2010 (UTC) Comments: Worth doing to ease of use by new and inexperienced users - [[User:aiaustin|aiaustin]] Also see [http://opensimulator.org/mantis/view.php?id=5260 Mantis 5260] - [[UserDiva|Diva]]<br />
* Warp3D throws an&nbsp;error as at r/14307 (documented in a comment on [http://opensimulator.org/mantis/view.php?id=5130 Mantis 5130]).<br />
* Provide map tile push to a nominated location and core HTTP server functionality to serve maps in Viewer 2 compatible format for use as the map server URI.<br />
<br />
== Plan ==<br />
<br />
*Address MUST DO features and MUST FIX bugs prior to branching 0.7.1. <br />
*Start documenting after branching <br />
*Fix critical bugs that show up after branching<br />
*Try to address Optional items where feasible during RC process<br />
*Test Optional Modules as far as possible during RC process<br />
<br />
<br />
[[Category:History]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T15:05:09Z<p>Fleep: /* Running OpenSim 0.6.7 and onwards in 64 bit Windows */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''Region Location'''<br />
::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, but [http://opensimulator.org/wiki/Hypergrid Hypergrid] enabled regions may need special consideration for region location. See the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#The_4096_Regions_Limit 4096 Regions Limit] section of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page for more information.<br />
* '''Internal IP address'''<br />
::In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''Internal port'''<br />
::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.<br />
* '''Allow alternate ports'''<br />
::This is currently experimental. Please leave it at the default of False.<br />
* '''External host name'''<br />
::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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''Master Avatar UUID'''<br />
::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.<br />
* '''Master Avatar first name'''<br />
::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 file.<br />
* '''Master Avatar last name'''<br />
::The last name of the master avatar.<br />
* '''Master Avatar sandbox password'''<br />
::The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then in the server console type:<br />
<br />
create user<br />
<br />
This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems, [[Network_Settings|be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring the file config-include/StandaloneCommon.ini, a simulator connecting to a grid needs to use and configure the config-include/GridCommon.ini file, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that one of the following lines is uncommented:<br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 its library is not compilable under 64-bit in Windows. <br />
<br />
Therefore, in order to launch the region simulator, 64-bit Windows users may need to run: <br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of:<br />
<br />
OpenSim.exe<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T15:04:44Z<p>Fleep: /* Running OpenSim 0.6.7 and onwards in 64 bit Windows */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''Region Location'''<br />
::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, but [http://opensimulator.org/wiki/Hypergrid Hypergrid] enabled regions may need special consideration for region location. See the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#The_4096_Regions_Limit 4096 Regions Limit] section of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page for more information.<br />
* '''Internal IP address'''<br />
::In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''Internal port'''<br />
::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.<br />
* '''Allow alternate ports'''<br />
::This is currently experimental. Please leave it at the default of False.<br />
* '''External host name'''<br />
::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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''Master Avatar UUID'''<br />
::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.<br />
* '''Master Avatar first name'''<br />
::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 file.<br />
* '''Master Avatar last name'''<br />
::The last name of the master avatar.<br />
* '''Master Avatar sandbox password'''<br />
::The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then in the server console type:<br />
<br />
create user<br />
<br />
This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems, [[Network_Settings|be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring the file config-include/StandaloneCommon.ini, a simulator connecting to a grid needs to use and configure the config-include/GridCommon.ini file, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that one of the following lines is uncommented:<br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 its library is not compilable under 64-bit in Windows. Therefore, in order to launch the region simulator, 64-bit Windows users may need to run: <br />
<br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of:<br />
<br />
OpenSim.exe<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T15:04:13Z<p>Fleep: /* Running OpenSim 0.6.7 and onwards in 64 bit Windows */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''Region Location'''<br />
::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, but [http://opensimulator.org/wiki/Hypergrid Hypergrid] enabled regions may need special consideration for region location. See the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#The_4096_Regions_Limit 4096 Regions Limit] section of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page for more information.<br />
* '''Internal IP address'''<br />
::In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''Internal port'''<br />
::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.<br />
* '''Allow alternate ports'''<br />
::This is currently experimental. Please leave it at the default of False.<br />
* '''External host name'''<br />
::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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''Master Avatar UUID'''<br />
::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.<br />
* '''Master Avatar first name'''<br />
::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 file.<br />
* '''Master Avatar last name'''<br />
::The last name of the master avatar.<br />
* '''Master Avatar sandbox password'''<br />
::The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then in the server console type:<br />
<br />
create user<br />
<br />
This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems, [[Network_Settings|be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring the file config-include/StandaloneCommon.ini, a simulator connecting to a grid needs to use and configure the config-include/GridCommon.ini file, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that one of the following lines is uncommented:<br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 its library is not compilable under 64-bit in Windows. Therefore, in order to launch the region simulator, 64-bit Windows users may need to run: <br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of:<br />
<br />
OpenSim.exe<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T15:01:28Z<p>Fleep: /* Step 2: Configure an OpenSim.exe to use the ROBUST services */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''Region Location'''<br />
::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, but [http://opensimulator.org/wiki/Hypergrid Hypergrid] enabled regions may need special consideration for region location. See the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#The_4096_Regions_Limit 4096 Regions Limit] section of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page for more information.<br />
* '''Internal IP address'''<br />
::In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''Internal port'''<br />
::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.<br />
* '''Allow alternate ports'''<br />
::This is currently experimental. Please leave it at the default of False.<br />
* '''External host name'''<br />
::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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''Master Avatar UUID'''<br />
::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.<br />
* '''Master Avatar first name'''<br />
::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 file.<br />
* '''Master Avatar last name'''<br />
::The last name of the master avatar.<br />
* '''Master Avatar sandbox password'''<br />
::The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then in the server console type:<br />
<br />
create user<br />
<br />
This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems, [[Network_Settings|be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring the file config-include/StandaloneCommon.ini, a simulator connecting to a grid needs to use and configure the config-include/GridCommon.ini file, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that one of the following lines is uncommented:<br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 <br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of <br />
<br />
OpenSim.exe<br />
<br />
To launch their region simulator.<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T15:00:15Z<p>Fleep: /* Step 2: Configure an OpenSim.exe to use the ROBUST services */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''Region Location'''<br />
::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, but [http://opensimulator.org/wiki/Hypergrid Hypergrid] enabled regions may need special consideration for region location. See the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#The_4096_Regions_Limit 4096 Regions Limit] section of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page for more information.<br />
* '''Internal IP address'''<br />
::In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''Internal port'''<br />
::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.<br />
* '''Allow alternate ports'''<br />
::This is currently experimental. Please leave it at the default of False.<br />
* '''External host name'''<br />
::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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''Master Avatar UUID'''<br />
::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.<br />
* '''Master Avatar first name'''<br />
::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 file.<br />
* '''Master Avatar last name'''<br />
::The last name of the master avatar.<br />
* '''Master Avatar sandbox password'''<br />
::The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then in the server console type:<br />
<br />
create user<br />
<br />
This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems, [[Network_Settings|be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring the file config-include/StandaloneCommon.ini, a simulator connecting to a grid needs to use and configure the config-include/GridCommon.ini file, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that the <br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
lines are uncommented. The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 <br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of <br />
<br />
OpenSim.exe<br />
<br />
To launch their region simulator.<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T14:59:18Z<p>Fleep: /* Step 2: Configure an OpenSim.exe to use the ROBUST services */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''Region Location'''<br />
::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, but [http://opensimulator.org/wiki/Hypergrid Hypergrid] enabled regions may need special consideration for region location. See the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#The_4096_Regions_Limit 4096 Regions Limit] section of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page for more information.<br />
* '''Internal IP address'''<br />
::In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''Internal port'''<br />
::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.<br />
* '''Allow alternate ports'''<br />
::This is currently experimental. Please leave it at the default of False.<br />
* '''External host name'''<br />
::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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''Master Avatar UUID'''<br />
::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.<br />
* '''Master Avatar first name'''<br />
::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 file.<br />
* '''Master Avatar last name'''<br />
::The last name of the master avatar.<br />
* '''Master Avatar sandbox password'''<br />
::The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then in the server console type:<br />
<br />
create user<br />
<br />
This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems, [[Network_Settings|be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring config-include/StandaloneCommon.ini, a simulator connecting to a grid needs to use and configure config-include/GridCommon.ini, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that the <br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
lines are uncommented. The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 <br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of <br />
<br />
OpenSim.exe<br />
<br />
To launch their region simulator.<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T14:57:47Z<p>Fleep: /* Connecting to OpenSim */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''Region Location'''<br />
::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, but [http://opensimulator.org/wiki/Hypergrid Hypergrid] enabled regions may need special consideration for region location. See the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#The_4096_Regions_Limit 4096 Regions Limit] section of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page for more information.<br />
* '''Internal IP address'''<br />
::In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''Internal port'''<br />
::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.<br />
* '''Allow alternate ports'''<br />
::This is currently experimental. Please leave it at the default of False.<br />
* '''External host name'''<br />
::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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''Master Avatar UUID'''<br />
::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.<br />
* '''Master Avatar first name'''<br />
::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 file.<br />
* '''Master Avatar last name'''<br />
::The last name of the master avatar.<br />
* '''Master Avatar sandbox password'''<br />
::The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then in the server console type:<br />
<br />
create user<br />
<br />
This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems, [[Network_Settings|be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring config-include/StandaloneCommon.ini, a simulator connecting a grid needs to use and configure config-include/GridCommon.ini, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that the <br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
lines are uncommented. The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 <br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of <br />
<br />
OpenSim.exe<br />
<br />
To launch their region simulator.<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T14:56:41Z<p>Fleep: /* Running OpenSim for the first time */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''Region Location'''<br />
::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, but [http://opensimulator.org/wiki/Hypergrid Hypergrid] enabled regions may need special consideration for region location. See the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#The_4096_Regions_Limit 4096 Regions Limit] section of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page for more information.<br />
* '''Internal IP address'''<br />
::In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''Internal port'''<br />
::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.<br />
* '''Allow alternate ports'''<br />
::This is currently experimental. Please leave it at the default of False.<br />
* '''External host name'''<br />
::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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''Master Avatar UUID'''<br />
::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.<br />
* '''Master Avatar first name'''<br />
::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 file.<br />
* '''Master Avatar last name'''<br />
::The last name of the master avatar.<br />
* '''Master Avatar sandbox password'''<br />
::The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then in the server console type:<br />
<br />
create user<br />
<br />
This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems. [[Network_Settings|Be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring config-include/StandaloneCommon.ini, a simulator connecting a grid needs to use and configure config-include/GridCommon.ini, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that the <br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
lines are uncommented. The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 <br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of <br />
<br />
OpenSim.exe<br />
<br />
To launch their region simulator.<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T14:56:12Z<p>Fleep: /* Running OpenSim for the first time */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''Region Location'''<br />
::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, but [http://opensimulator.org/wiki/Hypergrid Hypergrid]enabled regions may need special consideration for region location. See the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#The_4096_Regions_Limit 4096 Regions Limit] section of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page for more information.<br />
* '''Internal IP address'''<br />
::In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''Internal port'''<br />
::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.<br />
* '''Allow alternate ports'''<br />
::This is currently experimental. Please leave it at the default of False.<br />
* '''External host name'''<br />
::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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''Master Avatar UUID'''<br />
::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.<br />
* '''Master Avatar first name'''<br />
::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 file.<br />
* '''Master Avatar last name'''<br />
::The last name of the master avatar.<br />
* '''Master Avatar sandbox password'''<br />
::The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then in the server console type:<br />
<br />
create user<br />
<br />
This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems. [[Network_Settings|Be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring config-include/StandaloneCommon.ini, a simulator connecting a grid needs to use and configure config-include/GridCommon.ini, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that the <br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
lines are uncommented. The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 <br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of <br />
<br />
OpenSim.exe<br />
<br />
To launch their region simulator.<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T14:55:46Z<p>Fleep: /* Running OpenSim for the first time */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''Region Location'''<br />
::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, but [[http://opensimulator.org/wiki/Hypergrid]]enabled regions may need special consideration for region location. See the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid#The_4096_Regions_Limit 4096 Regions Limit] section of the [http://opensimulator.org/wiki/Installing_and_Running_Hypergrid Installing and Running Hypergrid] page for more information.<br />
* '''Internal IP address'''<br />
::In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''Internal port'''<br />
::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.<br />
* '''Allow alternate ports'''<br />
::This is currently experimental. Please leave it at the default of False.<br />
* '''External host name'''<br />
::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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''Master Avatar UUID'''<br />
::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.<br />
* '''Master Avatar first name'''<br />
::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 file.<br />
* '''Master Avatar last name'''<br />
::The last name of the master avatar.<br />
* '''Master Avatar sandbox password'''<br />
::The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then in the server console type:<br />
<br />
create user<br />
<br />
This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems. [[Network_Settings|Be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring config-include/StandaloneCommon.ini, a simulator connecting a grid needs to use and configure config-include/GridCommon.ini, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that the <br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
lines are uncommented. The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 <br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of <br />
<br />
OpenSim.exe<br />
<br />
To launch their region simulator.<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T14:49:41Z<p>Fleep: /* Running OpenSim for the first time */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''Region Location'''<br />
::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.<br />
* '''Internal IP address'''<br />
::In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''Internal port'''<br />
::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.<br />
* '''Allow alternate ports'''<br />
::This is currently experimental. Please leave it at the default of False.<br />
* '''External host name'''<br />
::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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''Master Avatar UUID'''<br />
::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.<br />
* '''Master Avatar first name'''<br />
::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 file.<br />
* '''Master Avatar last name'''<br />
::The last name of the master avatar.<br />
* '''Master Avatar sandbox password'''<br />
::The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then in the server console type:<br />
<br />
create user<br />
<br />
This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems. [[Network_Settings|Be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring config-include/StandaloneCommon.ini, a simulator connecting a grid needs to use and configure config-include/GridCommon.ini, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that the <br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
lines are uncommented. The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 <br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of <br />
<br />
OpenSim.exe<br />
<br />
To launch their region simulator.<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleephttp://opensimulator.org/wiki/ConfigurationConfiguration2011-04-23T14:46:09Z<p>Fleep: /* Running OpenSim for the first time */</p>
<hr />
<div>{{Template:Quicklinks}}<br />
<br /><br />
==OpenSim simulator configuration file==<br />
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 references some additional configuration information from the config-include/ directory. Information about the various settings is contained in the OpenSim.ini file itself (or OpenSim.ini.example for reference).<br />
<br />
Please note, that the name OpenSim.ini can be changed via [[OpenSim.exe Command Line Options|command line arguments]].<br />
<br />
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 except for a few. 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.<br />
<br />
== Database ==<br />
<br />
Opensim supports the following database-engines. Information about setting these up can be found in the OpenSim.ini.example file and the other various example files in bin/config-include. <br />
<br />
*'''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. It is significantly slower than MySQL. A few features here (such as attachment persistence) have not yet been fully implemented. <br />
<br />
*'''MySQL 5.1''' (fully supported) - This is the recommended database for any use beyond experimentation or small standalone applications. <br />
::*'''OpenSim 0.7.1-rc1''' supports MySQL 5.5 out of the box.<br />
::*'''Windows x64 systems:''' &nbsp;There is currently an unresolved [http://opensimulator.org/mantis/bug_view_advanced_page.php?bug_id=5294 bug_id=5294] found when running OpenSim with MySQL 5.5 on Windows x64 systems.<br />
::*'''Opensim 0.7.0.2:''' &nbsp;Some users have reported problems with MySQL 5.1.55 and up with Opensim 0.7.0.2, see [http://opensim-users.2152040.n2.nabble.com/OpenSim-1-7-0-2-and-MySQL-Versions-td6155064.html this thread] for more information. The issue can be resolved by using an updated version of MySql.Data.dll OR installing an older version of MySQL such as [http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.52 MySQL 5.1.52] with Opensim version 0.7.0.2. &nbsp;<br />
<br />
*'''MSSQL''' (partially supported) - some recent OpenSim features may not yet be implemented. See [[MSSQL-config]] for configuration information.<br />
<br />
==Standalone vs. Grid==<br />
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. OpenSim will start up in standalone mode out-of-the-box on the binary distributions.<br />
<br />
An OpenSim configuration consists of regions (run by region simulators) and backend data services (such as user, assets and inventory management).<br />
<br />
A system running in '''standalone mode''' runs both the region simulator and all the data services in a single process when you run OpenSim.exe. In this mode you can run as many regions as you like but only on a single machine.<br />
<br />
[[image:Opensim-standalone.png|frame|center|OpenSim running in standalone mode. Both simulator and services run in the same process (OpenSim.exe).]]<br />
<br />
In '''grid mode''', the data services are not part of the region server process. Instead, they are run in a separate executable called Robust.exe. A Robust shell can run all the services or they can be split amongst any number of Robust instances. This allows them to be run on entirely separate machines if necessary. In this mode, the OpenSim.exe acts solely as the region server, serving one or more regions that communicate with the separate data services. At this point you can run multiple OpenSim.exe region simulators on different machines.<br />
<br />
[[image:Opensim-grid-simple.png|frame|center|OpenSim running in grid mode. In this case, all the services are being run within a Robust.exe process. Multiple copies of OpenSim.exe (usually running on different machines) all use the same set of common services.]]<br />
<br />
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. We strongly recommend that you don't attempt this unless you are extremely patient and very technically proficient.<br />
<br />
= Running OpenSim in Standalone mode =<br />
Getting a binary distribution of OpenSim running in standalone configuration is relatively straightforward since it's configured this way by default. On the other hand, if you build OpenSim from the source distribution or from the git repository then you will need to:<br />
<br />
# Copy the bin/OpenSim.ini.example file to bin/OpenSim.ini. This configures the 3D simulator itself.<br />
# Copy the bin/config-include/StandaloneCommon.ini.example file to bin/config-include/StandaloneCommon.ini. This configures the in-process data services used by the standalone configuration.<br />
# In the [Architecture] section of OpenSim.ini at the bottom of the file, uncomment the Standalone.ini line. To uncomment a line of code, remove the semi-colon (;) comment symbols preceding the line so that it says:<br />
<br />
Include-Architecture = "config-include/Standalone.ini"<br />
<br />
<br />
Running OpenSim is then a matter of launching OpenSim.exe. Open a command prompt (for Windows users, Start menu > Run > cmd) and navigate to the Opensim /bin directory.<br />
<br />
On a '''Windows 32-bit''' command prompt:<br />
OpenSim.exe<br />
Under '''Windows 64-bit''', ODE cannot yet be compiled for 64 bit mode, so if using the default ODE physics plugin run:<br />
OpenSim.32BitLaunch.exe<br />
On '''Linux''' run:<br />
mono OpenSim.exe<br />
This can be done under both 32 and 64 bit modes with the ODE physics engine.<br />
<br />
== Running OpenSim for the first time ==<br />
<br />
If you're running OpenSim for the first time, it will ask you several questions at the console that will set up a single region for you. The configuration options you enter will be written to the bin/Regions/Regions.ini file, which you can then edit at a later date if you need to make changes.<br />
<br />
Many of the questions have defaults. Here are some explanations of the questions asked:<br />
<br />
* '''New region name'''<br />
::The name for your region. Don't leave this blank!<br />
* '''Region UUID'''<br />
::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<br />
* '''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.<br />
* '''Internal IP address''' - In virtually all cases this can be left as 0.0.0.0 (this is a wildcard that allows OpenSim to listen for UDP connections on any of the server's network interfaces). If you want to restrict UDP connections to only one network interface then you can specify an explicit IP address. This address is only used internally - the '''External host name''' is the one that is actually passed to the viewer (and hence is the important one).<br />
* '''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.<br />
* '''Allow alternate ports''' - This is currently experimental. Please leave it at the default of False.<br />
* '''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) can also be used though they will be converted to a numeric IP address before being sent to the viewer.<br />
<br />
The following details are also asked in OpenSim 0.6.9 and earlier.<br />
<br />
* '''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.<br />
* '''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<br />
* '''Master Avatar last name''' - The last name of the master avatar.<br />
* '''Master Avatar sandbox password''' - The password of the master avatar.<br />
<br />
In OpenSim 0.7 and later, OpenSim will ask you to assign each region to an estate during the setup process. If an estate needs to be created then it will also ask you to assign an estate manager. In standalone mode, an estate manager can also be created during the setup process.<br />
<br />
Don't forget the account details you use to set up the master avatar (in 0.6.9) or the estate manager (in 0.7 and later). Only this user will initially be able to configure the in-world settings for your region. This is also a user account that you can use to perform your initial login test.<br />
<br />
See [[Configuring_Regions]] for more information about the Regions.ini file that these questions generate.<br />
<br />
If you want to create a user other than the estate manager, then type<br />
<br />
create user<br />
<br />
in the server console. This will ask you a series of questions for creating a user (such as first name, last name and password).<br />
<br />
== Connecting to OpenSim ==<br />
<br />
To connect to your new sim with your user, start up a Second Life viewer with the following command line switches:<br />
<br />
'''Client on same machine as OpenSim:'''<br />
-loginuri http://127.0.0.1:9000<br />
<br />
'''Client on same LAN as OpenSim:'''<br />
-loginuri http://lan_ip:9000<br />
<br />
'''Client on different machine or internet:'''<br />
-loginuri http://external_ip:9000<br />
<br />
Then enter the user name and password you set up in the previous step and your new user should login.<br />
<br />
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 &amp; server(s) on the same machine (LAN) by using the "external" configuration. (<u>'''You might notice endless waiting for region handshake'''</u>.) See also [[Troubleshooting|troubleshoot hints]]. If you're having Connectivity problems. [[Network_Settings|Be sure to read the Network Configuration Page]]. This is important if you see Region handshake issues<br />
<br />
= Running OpenSim in Grid mode =<br />
{|<br />
| style="background:LavenderBlush; color:black" |<br />
[[Image:Exclamation.png|left]]<br />
NOTE: 0.7 is the first OpenSim release that fully migrates all services to the ROBUST server shell. OpenSim.Grid.UserServer.exe and MessageServer.exe from OpenSim 0.6.9 are no longer necessary. Please see the [[0.7_Release|0.7 release notes]] for more details. For details on how to set up grid services in OpenSim 0.6.9 and earlier please see [[OpenSim 0.6.9 Grid Mode Configuration]]<br />
|}<br />
<br />
Running OpenSim in grid mode is considerably more complicated than running a standalone instance. Instead of running everything in the same process, backend data services (asset, inventory, etc.) run in one or more separate processes, often on a different machine. This allows multiple OpenSim.exe simulator instances to use the same asset and inventory data.<br />
<br />
== Step 1: Set up a ROBUST services instance ==<br />
<br />
1. In the bin directory, copy Robust.ini.example to Robust.ini. The example file is configured to run all the services in a single ROBUST instance.<br />
<br />
2. Configure the [DatabaseService] section of Robust.ini to use your MySQL database. Only MySQL is supported for running grid services.<br />
<br />
3. Start up Robust.exe. <br />
<br />
mono Robust.exe (Linux, BSD, Mac OS X)<br />
<br />
or<br />
<br />
Robust.exe (Windows)<br />
<br />
If you don't see any errors (in red) on the console then you can move on to the next step.<br />
<br />
4. Every region must belong to an estate, and every estate must have an owner which is a valid user account in OpenSim's user account service. Create a user on the ROBUST command console with the following command.<br />
<br />
create user<br />
<br />
This will ask you for the user's name, password and an optional e-mail. Remember this name since you will need it when you start up the simulator for the first time.<br />
<br />
== Step 2: Configure an OpenSim.exe to use the ROBUST services == <br />
<br />
In grid mode, as in standalone mode, you need to configure OpenSim.ini which controls the 3D simulator itself.<br />
<br />
However, instead of using and configuring config-include/StandaloneCommon.ini, a simulator connecting a grid needs to use and configure config-include/GridCommon.ini, in order to connect to the ROBUST hosted remote data services rather than in-process local ones.<br />
<br />
The steps for both these operations are as follows.<br />
<br />
1. Copy bin/OpenSim.ini.example to OpenSim.ini<br />
<br />
2. Find the [Architecture] section at the very bottom of OpenSim.ini. Make sure that the <br />
<br />
Include-Architecture = "config-include/Grid.ini" (in OpenSim 0.7.1-rc1 and later)<br />
<br />
or<br />
<br />
Include-Grid = "config-include/Grid.ini" (in OpenSim 0.7.0.2 and earlier)<br />
<br />
lines are uncommented. The others should remain commented.<br />
<br />
3. Go to bin/config-include and copy GridCommon.ini.example to GridCommon.ini.<br />
<br />
4. Open GridCommon.ini in a text editor. You will see lots of URL entries, each of which have dummy defaults of http://myassetserver.com:8003, http://myinventoryserver.com:8003, etc. You will need to change each of these to point towards the address of your ROBUST instance. For instance, if you're running ROBUST on a machine with a local IP address of 192.168.1.2, you will need to change AssetServerURI to the setting<br />
<br />
AssetServerURI = "http://192.168.1.2:8003"<br />
<br />
5. Run OpenSim.exe. If you're running OpenSim.exe for the first time you will get the same questions about setting up the region that occur on a first-run in standalone mode. Please see the standalone section for instructions on how to answer these, or read more information about the Regions.ini file on the [http://opensimulator.org/wiki/Configuring_Regions Configuring Regions] page.<br />
<br />
If everything is set up correctly, when starting up OpenSim.exe you shouldn't see any errors. You should also see the ROBUST console display log lines saying that the region has registered with the grid service. For example,<br />
<br />
21:43:45 - [GRID SERVICE]: Region t1 (176cc95e-f693-4b02-8e08-af86e2372faa) registered successfully at 256000-256000<br />
21:43:47 - [GRID SERVICE]: region t1 has 0 neighbours<br />
<br />
6. Login with a client. Your client startup line will look something like<br />
<br />
-loginuri http://192.168.1.2:8002<br />
<br />
The loginuri needs to be the address of the login service. In standalone mode, this was the same address as the region simulator and the port is 9000 by default. However, in grid mode this is the login service hosted on the ROBUST instance. In this case, the address is 192.168.1.2. The port number of 8002 is the traditional one for the grid login service and is the default in Robust.ini.example.<br />
<br />
7. If the login is successful, you will see log lines on the ROBUST console (for the login itself) and then log lines on the region simulator console (as the login process tells the simulator to expect the avatar, tells the viewer the address of the region simulator and then when the viewer starts talking to the simulator directly).<br />
<br />
==Attaching your sim to someone else's grid==<br />
<br />
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, follow the [[Configuration#Step_2:_Configure_an_OpenSim.exe_to_use_the_ROBUST_services]] instructions above.<br />
<br />
The grid will already provide the required services. In step 2 you will need to use the service URLs that they provide to you.<br />
<br />
In your bin/Regions.ini file (or other region config file) you will also need to set your regions to the grid co-ordinates that the grid operator provides to you. See [[Configuring Regions]] for more information.<br />
<br />
=Further notes=<br />
<br />
==Troubleshooting==<br />
<br />
See [[Troubleshooting]] <br />
<br />
==Running OpenSim 0.6.7 and onwards in 64 bit Windows==<br />
[[Image:Exclamation.png|left]]<br />
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 <br />
<br />
OpenSim.32BitLaunch.exe<br />
<br />
instead of <br />
<br />
OpenSim.exe<br />
<br />
To launch their region simulator.<br />
<br />
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.<br />
<br />
==Note About Mono==<br />
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. <br />
<br />
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.<br />
<br />
For example: $ export MONO_THREADS_PER_CPU=125<br />
<br />
==Increasing the stack reserve level when using OpenDynamicsEngine on *nix==<br />
<br />
If you have problems using the OpenDynamicsEngine on *nix, try setting your stack reserve level higher than the default with the following command;<br />
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.<br />
<br />
== Legacy Configuration Information ==<br />
These are some pages containing some legacy configuration information of unknown accuracy.<br />
<br />
[[OpenSim 0.6.6 legacy configuration information]]<br />
<br />
<br />
== Additional Optional Configuration Tasks ==<br />
<br />
===Futher configuring OpenSim===<br />
<br />
If you've looked through OpenSim.ini.example or any other of the config files, you'll see that there's a very large number of configurable parameters. See [[Configuring Simulator Parameters]] for more details.<br />
<br />
===OpenSim.exe command line options===<br />
OpenSim.exe has command line options which allow you to perform actions such as reading configuration files from a different directory. See [[OpenSim.exe Command Line Options]] for more details.<br />
<br />
===Script engine===<br />
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. In fact, recent versions of OpenSim only ship with one script engine, the XEngine.<br />
<br />
===Permissions Configuration===<br />
OpenSim has a quite elaborate set of permissions. See [[OpenSim:Permissions(Server)]] for details. By default, permissions are not active on region simulators.<br />
<br />
=== Logging ===<br />
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.<br />
<br />
=== Configuration of region modules ===<br />
* [[IRCBridgeModule]]<br />
* [[Freeswitch_Module]]<br />
* [[Offline Messaging]]<br />
<br />
=== Configuration of Metaverse Exchange Protocol (MXP) ===<br />
* [[Metaverse Exchange Protocol]]<br />
<br />
=== Configuration of Web Server and Pages===<br />
OpenSim contains a web server that can serve up a variety of pages. Some which come from external files and some are generated internally.<br />
* [[External Files]]<br />
* [[Internally Generated]]<br />
<br />
=== Configuration of Multiple Standalone Regions on the Same Server ===<br />
Change the 'http-listening-port' in opensim.ini to something other than 9000 for the second region, and change the port in regions.ini to something other than 9000 for the second region.<br />
<br />
=References=<br />
<br />
* [http://dist.opensimulator.org/wiki/opensim-standalone.odg OpenOffice draw file for OpenSim standalone diagram]<br />
* [http://dist.opensimulator.org/wiki/opensim-grid-simple.odg OpenOffice draw file for OpenSim grid diagram]<br />
<br />
[[Category:Configuration]]</div>Fleep