How to create a Destination Guide for your grid

The Openvue grid has its own destination guide, seen here with the Singularity viewer.

The Openvue grid has its own destination guide, seen here with the Singularity viewer.

The latest releases virtual world viewers, such as Firestorm, Singularity, and Kokua can provide access to a “Destination Guide” for your OpenSim grid for both local and hypergrid visitors.

And this guide can feature both local and hypergrid destinations.


Destination guide for the Openvue grid. (Image courtesy Austin Tate.)

But the grid owner first has to enable this feature in their configuration files.

Here’s how.

Grid configuration settings

Here are the configuration instructions if you have a full-scale grid running “Robust” centralized grid services.

In your Robust.ini or Robust.HG.ini file [LoginService] section there is a “DestinationGuide” parameter which can be used to communicate a URL to use for the destination guide to “V3″ style viewers which enable this.

Uncomment the entry and provide a suitable URL to be used.

   ; For V3 destination guide
   DestinationGuide = ""

Make the content be suitable for presenting in the “in-viewer” browser, so avoid complex HTML or any viewer-side scripting. PHP should work as that is generated server-side. The viewers by default show the destination panel as a narrow strip which can be resized horizontally, but has fixed height, so you may want to tailor the display contents to that.

Here is how I set it up for the Openvue grid:

   ; For V3 destination guide
   DestinationGuide = ""

You can have the user click on a link to open a teleport dialogue in the viewer by providing links on destination names or thumbnail images in this destination page. Use the following format — and notice that the spaces are kept as spaces:

   "secondlife:///app/teleport/Region Name/128/128/22"

If you wish to show a hypergrid destination use a form like this…

   "secondlife:///app/teleport/ Plaza"
If you use the Singularity viewer and teleport to the OpenSim Community Conference grid at and pull up the Destination Guide, you'll see some featured destinations for that grid.

If you use the Singularity viewer and teleport to the OpenSim Community Conference grid at and pull up the Destination Guide, you’ll see some featured destinations for that grid.

Diva Wifi configuration settings

The Openvue destinations page at is actually served from the Diva “Wifi” web interface and its ability to provide “additionally served resources” for example as web pages which can pull in some parametric information from the OpenSim grid server. This is done by adding a “ServePath_…” entry in the [WifiService] section of WiFi.ini as follows…

    ;; Additionally served resources
    ;; Syntax: ServePath_Name = "LocalPath, ServedPath"
    ;;         (Name is any arbitrary identifier)
    ;; With the following example, the contents of folder "resources" at the same
    ;; level as the OpenSim base "bin" folder can be accessed via path /resources
    ServePath_Resources = "../resources, /resources"

This article adapted with permission from Austin Tate’s Informatics Blog.

Related Posts

Austin Tate

Austin Tate is Director of the Artificial Intelligence Applications Institute and holds the Personal Chair of Knowledge-Based Systems at the University of Edinburgh. He is also coordinator for the Virtual University of Edinburgh, a virtual educational and research institute bringing together those interested in the use of virtual worlds for teaching, research and outreach.

25 Responses

  1. Thanks for Gavin Hird for drawing my attention to this issue in his Google Plus post:

    •' Geir Nøklebye says:

      You’re welcome! 😉

      Actually Austin described this about a year ago, so I am a bit surprised nobody picked it up. I had no idea about his work – it just struck me as a possibility while testing every menu option in Kokua and having reviewed Robust.HG.ini the same day.

      •' Ai Austin says:

        Credit where credit really is due… in my blog post I was reporting the underlying work done by BlueWall, one of the core OpenSim developers, and people who we should all be very grateful to. I tend to watch for config changes and test them out auite exhaustively. Our Openvue and my own personal AiLand grid and used for all kinds of latest dev vesion testing like this.. some of which works and makes it way into the next version.. and some of which does not.

        As Geir said.. if we spot the diffferences between the TPVs we could report back to them to get them all on the same page. I find the Firestorm and CtrlAltStudio folks are quite understanding of Opensim specific issues and try to be helpful. For me I would assume the destination guide should be the one for the grid you are on at any time. But we still have a range of issues with grid identification in the hop:// protocols and other grid localisation things in TPVs.

  2. One thing to note, however — it looks like some viewers show the guide for the grid you’re on, while other viewers show the guide for the grid you started on — no matter where you hypergrid to.

    For example, I just set up the destination guide for the Hyperica grid, where I have my main avatar.

    With Firestorm and Kokua, whenever I travel anywhere, and I pull up the destination guide, I get the one from Hyperica (which is currently a blank page — sorry guys, working on it!).

    With Singularity, I get the one for the local grid.

    So, I guess the lesson is that if you have a nice destination guide on your home grid that you want to be able to access wherever you go, use Firestorm or Kokua.

    And if you want to be able to see the destination guides for the grids you visit, use Singularity.

    •' Geir Nøklebye says:

      For me it is the other way around. Kokua updates dynamically, Singularity (alpha build) shows the initial one.

      I guess you have to test your viewer. It might be good if people report their findings back to the developers to they all behave in the same, predictable manner.

      Looking forward to seeing the Hyperica formatted version. 🙂

  3.' Ai Austin says:

    I am trying to encourage all grids to set up at least a simple destination guide and the folks for the OpenSim Community Conference did set that up.

    And everyone should adopt hop:// links for OpenSim rather than continuing to misuse secondlife:// but its nit universally adopted in TOVs yet, and doe snit work quite as it should everywhere in the various location specification areas in all TPVs that do support hops:// but we are gradually getting thee.

    •' Geir Nøklebye says:

      For small grids it is probably better to be member of a consolidated destination guide like Hyperica or Opensim Virtual.

    •' Bryan French says:

      As nice as those suggestions are not every grid uses or suggests the use of V3 viewers. If our grid adopted hop:// exclusively then 50% of our residents wouldn’t be able to go anywhere. Our download page says “Exo-Life does not offer support
      for any other viewers than those [listed]” So people are forewarned things may not work if you use so other viewers.

      •' Ai Austin says:

        Point taken Bryan… I was not really suggesting removing anything that already works, and even legacy HG addresses… but the simple URL format and style hop://domain:port/region/x/y/z with region, x, y and z being optional is a great way to go. Viewers can then be registered to be handlers for that protocol as well as the previous secondlife:// protocol.

  4. I have started making a Hyperica destination guide. You can already use it — the parts that aren’t finished are grayed out and will be completed later.

    This is the main page to link to in your Robust files:

    I’ve tried to duplicate the Second Life style as much as possible. Well, as much as my CSS skills would allow!

    Everything — the styles and the formatting – fits within one HTML file (no separate styles file) — so it should be easy for anyone to grab and adapt.

    The only one of the category sections that’s live right now is the “Top grids” one, and it takes you to this page:

    (You don’t have to save this URL, but if you want, feel free to copy the whole thing for your own grid.)

    I’ve tested this on my Hyperica grid with the Firestorm browser and it works, and the teleport links to the other grids work. HOWEVER — it gives me an error message. It still works, but it tells me that it could not add secondlife to the grid list.

    You can ignore it and it sends you on your way, but it looks like I’m going to have to change all the links to ones that don’t give an error message.

  5. For those interested in the Second Life Destination Guide HTML, here is the URL:

  6. i hope people know that the destinations can be pulled from the search database and displayed with bootstrap. easy to do with php and html.

  7.' Paul E. Emery says:

    Seems to be some confused info in the comments as it applies getting a destination guide for stand alone grids e.g. diva distro. since there are no “Robust” ini files you need to go to your “Myworld.ini” file and find the [LoginService] section and put in DestinationGuide = “”