Connecting

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
(Removed dead link)
m (Reverted edits by Debra (talk) to last revision by MakoBot)
 
(20 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
{{Template:Quicklinks}}
+
{{Quicklinks}}
 
<br />
 
<br />
==Compatible Viewers==
 
Before you can connect to OpenSim, you'll need to have downloaded one of the following clients that can connect to OpenSim.
 
  
* [http://get.secondlife.com Linden Client] (Release version 2 is '''not''' fully supported by OpenSim.)
+
== Obtaining OpenSimulator Available Viewers ==
* [http://mjm-labs.com/viewer/ Hippo Viewer] - a fork of version 1.23 of the Linden Client with OpenSim specific enhancements
+
'''OpenSimulator does not come with a viewer in its distribution.''' You'll need to download an OpenSimulator compatible client before connecting to OpenSimulator grids.
* [[RealXtend]] - a fork of the 1.23 Linden Client that has specialized features (not fully supported.)
+
{{:Compatible Viewers}}
* [http://www.phoenixviewer.com/ Phoenix Viewer] Based on the now discontinued Emerald Viewer (which was based on the 1.23 LL viewer), one of the most popular viewers. Combines many improvements and  features from different viewers.
+
* [http://imprudenceviewer.org/ Imprudence] Innovative viewer, and highly popular amongst users on [[Grid_List/OSGrid|OSGrid]].
+
  
 +
Some other viewers that can connect to Second Life can also connect to OpenSimulator. You can find them in the [http://wiki.secondlife.com/wiki/Downloads#Third_Party_Directory_Viewers Third Party Directory] at the Second Life wiki.
  
===Other compatible viewers===
 
The viewers below are open source, and not based on the Snowglobe, nor on the Snowstorm viewers.
 
  
* [http://forge.opensimulator.org/gf/project/idealistviewer/ Idealist viewer], Not actively developed.
+
'''Note that you will have to register a new account for each grid that you want to be on'''. This means that your Second Life login does not work on any other grid, and that your login for other grids will not work on Second Life, etc.
* [http://lookingglassviewer.org/wiki/Main_Page/ Looking Glass viewer], Status active.
+
* [http://3di-rei.org/ 3Di viewer], Status unknown.
+
  
==Connecting with the Linden Viewer==
+
Many viewers with grid selectors will show a link to that grid's signup page when selecting a grid. You can create your account by clicking that link, and following the instructions on the signup page.
  
<span style="color:#ff0000;">'''***NOTE***''': These instructions apply to the Linden Labs viewer ONLY. Most other viewers have a more elegant method to choose a grid. See the documentation for those viewers for more information.</span>
+
== Connecting to the Grid with A Grid Selector (Recommended) ==
  
Every OpenSim grid or instance will specify a '''loginuri''', which is a uri of the form '''http://someserver:9000''' (standalone mode) or '''http://someserver:8002''' (grid mode).  For instance, for osgrid, this is http://login.osgrid.org.  The following sections assume that you have that uri.  We'll use http://login.osgrid.org as our example url.
+
Most viewers have a grid selector which in many cases is already visible, and located at the bottom of the login screen. If it is not visible, try pressing Ctrl-Shift-G to (un)hide the grid selector.
  
A list of major public grids can be found at [[Grid_List]].  OSGrid is just one of many available.
+
=== If the grid is present in the list ===
 +
If you see the grid you want to connect to in the grid selector, then simply choose it from the drop down menu, enter the username and password that you chose when you created your account on that grid, and click the "Log in" button.
  
=== Linux ===
+
=== If the grid is missing from the list ===
* change directory to you viewer (SecondLife_XYZ)
+
If your preferred grid is not present in the drop down menu, then you will have to add it manually. You will have to do this only once.  
* run <code>./secondlife -loginuri http://login.osgrid.org</code>
+
First, find the grid manager. Usually, this can be found in the preferences of your viewer, in a tab called "Grids". In general, the only fields that you will have to fill in are:
  
=== Windows ===
+
* '''Grid Name''' (or alike) - A name you can easily identify the grid by. OpenSimulator grids don't use this information, so you can name it anything you like.
* make a copy of the SecondLife icon on your desktop
+
* '''Login URI''' - The most important information. It should be like "<nowiki>http://someserver:9000" or "http://someserver". For instance, for OSGrid, this is "http://login.osgrid.org/".</nowiki>
* rename it to the grid you want to connect to
+
* edit the properties on the icon and set the command line to <code>...\SecondLife.exe" -loginuri http://login.osgrid.org</code>
+
  
=== Mac ===
+
Near these fields, you will also find a button named "Get Grid Info" or similar. If you click it, it may fill out several blank fields with URIs.  
* Make a 'somefilename.sh' file, and put this in it:
+
In some cases, clicking the button will cause an error message to pop up, or in rare cases, freeze the viewer. If clicking the button causes problems of any kind, you can leave the remaining fields empty, or find the missing info and add it manually. Leaving the fields empty will normally not cause problems, and you will still be able to log in to that grid, although on some grids, some features may be unavailable until the missing info is added.
* /Applications/Second\ Life.app/Contents/MacOS/Second\ Life -loginuri http://login.osgrid.org
+
* set it to executable
+
* run it
+
+
If you have multiple viewers and multiple grids to connect to, you can try the following AppleScript (one could do something similar with a shell script).  Feel free to copy and modify for your own use.
+
--
+
--  This script selects a viewer and a grid for virtual worlds.
+
--
+
--
+
-- Variables for the two supported viewers.  More may be added here.
+
--
+
set lindenViewer to "\"/Applications/SecondLife/Second Life.app/Contents/MacOS/Second Life\""
+
+
set emeraldViewer to "\"/Applications/SecondLife/GreenLife Emerald Viewer.app/Contents/MacOS/GreenLife Emerald Viewer\""
+
--
+
-- Variables for options to select the specified grid. Since the viewers
+
-- are based on the 2nd life viewer, the options are the same for each
+
-- viewer. Also, connecting to the Second Life grid is the default option
+
-- if no other options are provided.
+
--
+
-- Currently, four grids are supported.  More may be easily added.
+
--
+
set lindenOptions to ""
+
+
set localStandalone to " -loginuri http://vw.server.lan:9000 -loginpage http://vw.server.lan/opensim/index.html"
+
+
set localGrid to " -loginuri http://vw.server.lan:8000 -loginpage http://vw.server.lan/opensim/index.html"
+
+
set osGridOptions to " -loginuri http://osgrid.org:8002 -loginpage http://osgrid.org/loginscreen.php -helperuri http://osgrid.org/"
+
--
+
-- Display dialog and select the viewer.
+
--
+
set dialogResult to display dialog "Choose viewer:
+
1) 2nd Life viewer
+
2) Emerald viewer:" default answer "1" with title "Select Viewer" with icon 1
+
+
set option to text returned of dialogResult
+
+
if option = "2" then
+
set viewer to emeraldViewer
+
else
+
set viewer to lindenViewer
+
end if
+
--
+
-- Display dialog and select the grid.
+
--
+
set dialogResult to display dialog "Choose server:
+
1) 2nd Life grid
+
2) local standalone
+
3) local grid
+
4) OS Grid" default answer "2" with title "Select Grid" with icon 1
+
+
set grid to text returned of dialogResult
+
+
if grid = "1" then
+
set options to lindenOptions
+
else if grid = "2" then
+
set options to localStandalone
+
else if grid = "3" then
+
set options to localGrid
+
else if grid = "4" then
+
set options to osGridOptions
+
else
+
set options to localStandalone
+
end if
+
--
+
-- Combine the grid and viewer and execute the result.
+
--
+
set command to viewer & options
+
do shell script command
+
  
===Linden Viewer options===
+
Click the "Apply" or "OK" button to store your new grid in the menu, and you will be ready to log in as explainted under [[Connecting#If the grid is present in the list|If_the_grid_is_present_in_the_list]]
The Linden viewer has a number of other options.  Some are useful, some are not.  The viewer has a help option which produces the following results:
+
  --autologin          log in as last saved user
+
  --channel arg        n/a
+
  --console arg        n/a
+
  --cooperative arg    Yield some idle time to local host.
+
  --crashonstartup      Crashes on startup. For QA use.
+
  --debugviews          n/a
+
  --drop arg            n/a
+
  --god                Log in a god if you have god access.
+
  --grid arg            Specify the name of the grid, local, or an IP address
+
                        to connect to.
+
  -h [ --help ]        display this help message
+
  --helperuri arg      helper web CGI prefix to use
+
  --ignorepixeldepth    Ignore pixel depth settings.
+
  --inbw arg            n/a
+
  --logfile arg        n/a
+
  --login args          3 tokens: first, last and password
+
  --loginpage arg      Login authentication page to use.
+
  --loginuri arg        login server and CGI script to use
+
  --multiple            Allow multple viewers.
+
  --no-verify-ssl-cert  n/a
+
  --noaudio            n/a
+
  --noinvlib            Do not request the inventory library.
+
  --nopreload          n/a
+
  --noprobe            n/a
+
  --noquicktime        n/a
+
  --nosound            n/a
+
  --novoice            Disable voice.
+
  --outbw arg          n/a
+
  --port arg            n/a
+
  --purge              Delete files in the cache.
+
  --qa                  Activated debugging menu in Advanced Settings.
+
  --quitafter arg      n/a
+
  --rotate              n/a
+
  --safe                Reset preferences, run in safe mode.
+
  --set args            specify the value of a particular
+
                                      configuration variable that
+
                                      overrides all other settings
+
                             
+
  --setdefault args      specify the value of a particular
+
                                      configuration variable which can be
+
                                      overridden by settings.xml
+
                             
+
  --settings arg        Specify the filename of a configuration file.
+
  --skin arg            ui/branding skin folder to use
+
  --slurl arg          Startup SLurl
+
  --url arg            Startup location
+
  --psn arg            MacOSX process serial number
+
  
===== Note =====
+
For instructions that are specific for your favorite viewer, see your viewer's website.
  
The above described methods work for the SecondLife viewer, other viewers that support the GridInfo protocol won't need this.
+
== Connecting to the Grid with Viewer Parameters ==
  
== Alternative Connection Approaches ==
+
If your viewer doesn't have a grid selector, or if you are having problems adding the grid to your viewer's grid list, then an alternative method is to use viewer parameters.
  
=== Via a Web Browser ===
+
Basically, all you will really need is to pass the ''--loginuri'' command line parameter to the viewer and launch with it, although you will want to use all of the viewer parameters that are suggested for your preferred grid.
  
You can also set up a [[Browser Protocol Handler]] which will make opensim:// links in your browser do the expected thing, and launch the right OpenSim viewer.
+
For example, you use the Second Life Viewer on Windows, and want to connect to OSGrid. A quick-and-easy way would be as follows:
  
** Project site
+
* Press Windows Key + R, this wil open the Run dialog.
** http://forge.opensimulator.org/gf/project/xenki/
+
* In the Run dialog, enter the following:
 +
SecondLife.exe --loginuri <nowiki>http://login.osgrid.org/ --loginpage http://www.osgrid.org/splash/</nowiki>
 +
* Press "Enter", or click "OK" and your viewer should start. After clicking the login button, you will enter OSGrid.
 +
 
 +
 
 +
On OSX, you could also use AppleScript, which enables you to select multiple grids to connect to. See the [[OSX Grid Selector Script]] article for a pre-made script.
 +
 
 +
For more information on viewer parameters that are known to work with the Linden Lab Second Life Viewer and with Snowglobe based viewers, see [http://wiki.secondlife.com/wiki/Viewer_parameters#Using_Viewer_parameters this Second Life wiki page] about using viewer parameters.
 +
 
 +
The Linden Labs viewer has a number of additional options. Most of which are not useful to average users. See the [http://wiki.secondlife.com/wiki/Viewer_parameters#Parameter_reference parameter reference] on the Second Life Wiki for details.
 +
 
 +
== Connecting to your locally hosted server from behind a DSL router using NAT ==
 +
 
 +
'''Loopback'''
 +
Most DSL routers/modems prevent loopback connections as a security feature. This means that a NATed IP address ( such as 192.168.2.40 ) can not connect to your forward facing IP address ( such as 199.149.252.44 ) from behind your DSL router/modem. In a case like this, external IP addresses may connect to your server/region but you can not ( this applies to both standalone and grid modes ).
 +
 
 +
List of routers featuring NAT Loopback : [[NAT Loopback Routers]]
 +
 
 +
'''Router solution'''
 +
If you are using a ZyXEL DSL router/modem from Embarq, please read [[Network Settings#Local connections with ZyXEL DSL modem/router and NAT/Port Forwarding|this guide]]. This will show you how to reconfigure your DSL router/modem to fix this problem. Similar solutions may exist for other DSL router/modems. A Google search for the make and model of your DSL router/modem may provide you with a manual to assist you in this.
 +
 
 +
A word of caution : be VERY careful what you change and take good notes along the way so you can undo any changes you make in error.
 +
 
 +
'''DNS solution(Linux)'''
 +
It's possible to host your own DNS-server, so you can prevent some of the dns-naming problems mentioned before. If <nowiki>http://example.org</nowiki> resolves to the external ip, and that loopback connection is prevented by your router, you could point your resolv.conf to a local nameserver like:
 +
nameserver 192.168.2.2
 +
Now you need bind/named installed in order to handle the dns-requests. You can find a bind example configfile here.
 +
 
 +
== Alternative Connection Approaches ==
 +
 
 +
=== Via a Web Browser ===
  
* '''Xenki''' - Xenki is an XBAP 3D application intended to be a browser add-on for OpenSim.
+
You can also set up a [[Browser Protocol Handler]] which will make opensim:// links in your browser do the expected thing, and launch the right OpenSimulator viewer.
** '''What is Xenki?'''
+
** http://www.adamfrisby.com/blog/2008/08/what-is-xenki/
+
** '''Sources:'''
+
** http://www.adamfrisby.com/blog/2008/08/xenki-010-alpha-sources-posted/
+
  
=== Via Rezme ===
+
[[Category:Help]]
TBD
+

Latest revision as of 12:26, 7 December 2012


[edit] Obtaining OpenSimulator Available Viewers

OpenSimulator does not come with a viewer in its distribution. You'll need to download an OpenSimulator compatible client before connecting to OpenSimulator grids.


If you find a viewer which can connect to OpenSimulator then please add it to the bottom of the appropriate list.

[edit] Compatibility issues

Since OpenSimulator and viewers development is done by diferent teams with diferent timing and even goals, compatibility can not be assured.
To connect to a older version of OpenSimulator, you may need to use a older version of your favority viewer. Consult your grid team, or the viewer team
This may also limit Hypergrid capability.

[edit] Viewers

  • Cool VL Viewer - the oldest of all actively maintained Third Party Viewers (former name: Cool SL Viewer).
  • FireStorm Viewer - v3 based TPV, the successor to Phoenix. The most widely used viewer on Second Life.
  • Kokua - v3 based successor of Imprudence.
  • Radegast Metaverse Client - Radegast-ng is Light client, evolution of Radagast from libopenmetaverae project.
  • Singularity - A Snowglobe-based viewer with many current features backported.
  • Dayturn - A OpenSim compatible viewer derived from Kokua.
  • Scenegate - A viewer with a focus on accessibility, and onboarding. With a simplified UI more suitable to just visit worlds, rather than building (but the full UI is still accessible). Derived from Alchemy Viewer

[edit] Beta Viewers

Singularity Nightly Builds http://www.singularityviewer.org/kb/nightly-builds

Dayturn-windows https://bitbucket.org/dayturn/dayturn-windows/downloads/

[edit] Text-only Viewers

These are lightweight viewers, which either do not offer a graphical component or where the graphical component is not used by deault. The function of these viewers however is to connect to a grid, chat, manage inventory, etc. Useful on systems with low specifications or for bringing an alt online without having your main avatar log out, or to quickly take care of messages, inventory, etc.

  • JOpenMetaverse Purely Java based OpenSim client core library. Windows, MacOS,, Linux and Android Compatible. Please see jopenmetaverse introduction
  • METAbolt - METAbolt is a non-graphical (text based) viewer. It's light weight and cross grid, which means it will work in Second Life™ as well as other grids that are based on OpenSIM. The viewer is Open Source so it's free. Currently METAbolt is only available for Windows platforms.
  • Mobile Grid Client - A Second Life and OpenSim (Open Simulator) messaging client for your Android powered device (mobile phone, cell phone, tablet...).

[edit] Inactive Viewers

  • RealXtend - a fork of the 1.23 Linden Client that has specialized features (not fully supported.)
  • Idealist viewer
  • 3Di viewer
  • Xenki, an XBAP 3D application intended to be a browser add-on for OpenSimulator.
  • Looking Glass viewer, Discontinued. Only OSGrid, ScienceSim and localhost are available from the list.
  • Imprudence Innovative viewer with a high focus on OpenSimulator.

Some other viewers that can connect to Second Life can also connect to OpenSimulator. You can find them in the Third Party Directory at the Second Life wiki.


Note that you will have to register a new account for each grid that you want to be on. This means that your Second Life login does not work on any other grid, and that your login for other grids will not work on Second Life, etc.

Many viewers with grid selectors will show a link to that grid's signup page when selecting a grid. You can create your account by clicking that link, and following the instructions on the signup page.

[edit] Connecting to the Grid with A Grid Selector (Recommended)

Most viewers have a grid selector which in many cases is already visible, and located at the bottom of the login screen. If it is not visible, try pressing Ctrl-Shift-G to (un)hide the grid selector.

[edit] If the grid is present in the list

If you see the grid you want to connect to in the grid selector, then simply choose it from the drop down menu, enter the username and password that you chose when you created your account on that grid, and click the "Log in" button.

[edit] If the grid is missing from the list

If your preferred grid is not present in the drop down menu, then you will have to add it manually. You will have to do this only once. First, find the grid manager. Usually, this can be found in the preferences of your viewer, in a tab called "Grids". In general, the only fields that you will have to fill in are:

  • Grid Name (or alike) - A name you can easily identify the grid by. OpenSimulator grids don't use this information, so you can name it anything you like.
  • Login URI - The most important information. It should be like "http://someserver:9000" or "http://someserver". For instance, for OSGrid, this is "http://login.osgrid.org/".

Near these fields, you will also find a button named "Get Grid Info" or similar. If you click it, it may fill out several blank fields with URIs. In some cases, clicking the button will cause an error message to pop up, or in rare cases, freeze the viewer. If clicking the button causes problems of any kind, you can leave the remaining fields empty, or find the missing info and add it manually. Leaving the fields empty will normally not cause problems, and you will still be able to log in to that grid, although on some grids, some features may be unavailable until the missing info is added.

Click the "Apply" or "OK" button to store your new grid in the menu, and you will be ready to log in as explainted under If_the_grid_is_present_in_the_list

For instructions that are specific for your favorite viewer, see your viewer's website.

[edit] Connecting to the Grid with Viewer Parameters

If your viewer doesn't have a grid selector, or if you are having problems adding the grid to your viewer's grid list, then an alternative method is to use viewer parameters.

Basically, all you will really need is to pass the --loginuri command line parameter to the viewer and launch with it, although you will want to use all of the viewer parameters that are suggested for your preferred grid.

For example, you use the Second Life Viewer on Windows, and want to connect to OSGrid. A quick-and-easy way would be as follows:

  • Press Windows Key + R, this wil open the Run dialog.
  • In the Run dialog, enter the following:
SecondLife.exe --loginuri http://login.osgrid.org/ --loginpage http://www.osgrid.org/splash/
  • Press "Enter", or click "OK" and your viewer should start. After clicking the login button, you will enter OSGrid.


On OSX, you could also use AppleScript, which enables you to select multiple grids to connect to. See the OSX Grid Selector Script article for a pre-made script.

For more information on viewer parameters that are known to work with the Linden Lab Second Life Viewer and with Snowglobe based viewers, see this Second Life wiki page about using viewer parameters.

The Linden Labs viewer has a number of additional options. Most of which are not useful to average users. See the parameter reference on the Second Life Wiki for details.

[edit] Connecting to your locally hosted server from behind a DSL router using NAT

Loopback Most DSL routers/modems prevent loopback connections as a security feature. This means that a NATed IP address ( such as 192.168.2.40 ) can not connect to your forward facing IP address ( such as 199.149.252.44 ) from behind your DSL router/modem. In a case like this, external IP addresses may connect to your server/region but you can not ( this applies to both standalone and grid modes ).

List of routers featuring NAT Loopback : NAT Loopback Routers

Router solution If you are using a ZyXEL DSL router/modem from Embarq, please read this guide. This will show you how to reconfigure your DSL router/modem to fix this problem. Similar solutions may exist for other DSL router/modems. A Google search for the make and model of your DSL router/modem may provide you with a manual to assist you in this.

A word of caution : be VERY careful what you change and take good notes along the way so you can undo any changes you make in error.

DNS solution(Linux) It's possible to host your own DNS-server, so you can prevent some of the dns-naming problems mentioned before. If http://example.org resolves to the external ip, and that loopback connection is prevented by your router, you could point your resolv.conf to a local nameserver like:

nameserver 192.168.2.2

Now you need bind/named installed in order to handle the dns-requests. You can find a bind example configfile here.

[edit] Alternative Connection Approaches

[edit] Via a Web Browser

You can also set up a Browser Protocol Handler which will make opensim:// links in your browser do the expected thing, and launch the right OpenSimulator viewer.

Personal tools
General
About This Wiki