Table of Contents
Hypergrid Teleporting
- OpenSimulator.
-
Viewers supporting hop://, x-grid-info:// and/or
x-grid-location-info:// for OpenSim -
- Clicking the appropriate "hop://", "x-grid-info" or
"x-grid-location-info://" link in a web browser (e.g. in Internet Edge
or Firefox) in Windows should let you choose to open the viewer of
your choice which is registered as supporting the protocol or
scheme. The last to be installed that can handle the protocol is
usually used or you can select the default manually using Windows
Control Panel -> Default Programs (not from Windows 10). The link
includes a grid host name and will usually automatically add the
relevant grid entry and grid information to your viewer's grid manager
if necesary. If you are already logged into OpenSim it should offer
you a teleport to the grid and region you asked for.
- On most viewers, the top address bar when clicked shows the
hypergrid address showing the grid, region and X/Y/Z location you are
at, which can then be shared on web pages, via chat/IM, etc to
advertise locations for events. The Previous, Next and a drop down
list of recent locations might also be shown in some viewers to easy
navigation between recently visited grids and regions.
Typing or pasting a URI into the address bar will take you
straight to the indicated grid/region/X/Y/Z destination.
[If the address bar does not show, right click near the top of the
screen and tick to show it]
- On some viewers, teleporting between locations on that same
OpenSim grid or between different OpenSim grids leaves a
URI in the local (nearby) chat log. If you click that link you
should be able to go back to the last location you hopped from.
- Unfortunately, at present, not all this functionality works in all viewers.
- Unfortunately at present, a different format has to be used in the
Map tool. There, currently, use the format gridname:port:Region
Name (note no http:// and you cannot use %20 for a space in a
region name) or http://griddomain:port/ Region Name with http:// (or
https:// if requied), a space before the region name (not %20) and
then the region name which if it has a space in it cannot be given as %20.
Relevant Mantis/JIRA Issues
Test Hops
You should be able to hop between any of these grid and region
destinations in any order and use the return hop that the viewer
places in local chat at any time. This should include the case for
when you are on your home grid and try to use the chat embedded hop://
link left for a region on that home grid.
- Openvue Hops (no longer active)
- AiLand Hops (no longer active)
- Kitely Hops
- OSGrid Hops
- hop://login.osgrid.org:80/OpenVCE/128/80/22/
- hop://login.osgrid.org:80/Sandbox%20Plaza/128/128/22/
- Note that the :80 port does not match the Firestorm OpenSim
grids entry for OSGrid which does not have port :80 appended. Until
2020, if :80 was in the external HG link then a message "Your start
location did not specify a valid grid." was given. With recent OpenSim
changes to allow multiple alternative domain names for a grid, the
tests below may be tried and may now work...
- hop://login.osgrid.org/OpenVCE/128/80/22/
- hop://hg.osgrid.org/OpenVCE/128/80/22/
- Up to OpenSim 0.9.2.0, the login.osgrid.org:80 loginuri seemed
to be needed rather than the hg.osgrid.org:80 hypergrid URI. If
hg.osgrid.org is used it adds a second entry with same grid name of
OSGrid to the Firestorm OpenSim grid list. Is another OpenSim
Gridinfo entry needed to communicate to the viewer the grid URI to be
used for a hop://
Note that for test purposes, a region with the same name on several grids
is included as a test that no confusion occurs - in this case "OpenVCE"
which is a region on both OSGrid and Openvue.
Testing in Firestorm 6.4.12 OS (62792)
- 15-Nov-2020: Firestorm 6.4.12 OS (62792) and later includes an
important fix to properly put the current grid gatekeeper "GridURL"
into the hop addreses shown in the address bar and for Teleport back
links put into nearby chat. So much more works.
- 15-Nov-2020: See http://blog.inf.ed.ac.uk/atate/2020/11/15/grid-hopping/
Testing in Firestorm 6.4.11 OS (62417)
- 30-Oct-2020: After install Firestorm is shown as a registered
handler for the hop:// protocol in Windows 10. But the latest
Firestorm of any kind (including the SL only version) is
registered. This could be improved by only registering the OpenSim
version for hop://
- 30-Oct-2020: Tests below are done after Firestorm for OpenSim is
the latest installed viewer to avoid the above problem. In this case
the hop:// when clicked does correctly launch the viewer or get
communicated to the running viewer.
- 30-Oct-2020: hop:// addresses show in top address bar for home grid.
- 30-Oct-2020: When on a foreign grid the hop:// shown in the top
address bar wrongly shows the original login (home) grid
loginuri.
- 30-Oct-2020: When teleporting between grids a hop:// link is put
into local chat. This can be used to successfully return to the
location prior to the teleport.
- 30-Oct-2020: However, the hop:// link always shows the original
login (home) grid rather than the grid you are actually on, so fails
to work for teleports to the last location unless that was the home
grid.
- 30-Oct-2020: hop:// link put into local chat now allows teleport
between locations on the same grid.
- 30-Oct-2020: The Map "Copy SLUrl" (which would be better labelled as
"Copy Location") when on a foreign grid shows a hop link which always
includes the original login grid.
- 30-Oct-2020: OSGrid now allows the use of
hop://login.osgrid.org:80 hop://login.osgrid.org or
hop://hg.osgrid.org:80 (probably due to OpenSim allowing alternative
server names), but a second OpenSim grid entry is added in Firestorm,
and BOTH entries show as for login.osgrid.org.
Testing in Firestorm 4.7.3 OS (47323) Releasex64
- 14-Aug-2015: Testing preview 47308 gives results identical to 4.7.1
- 14-Aug-2015: No changes to hop:// handling in 4.7.3
Testing in Firestorm 4.7.1 OS (45302) Previewx64
- 21-Apr-2015: After install Firestorm is shown as a registered
handler for the hop:// protocol.
- 21-Apr-2015: hop:// addresses show in top address bar for home grid.
- 21-Apr-2015: When on a foreign grid the hop:// shown in the top
address bar wrongly shows the original login (home) grid loginuri.
- 21-Apr-2015: When teleporting between grids a hop:// link is put
into local chat. This can be used to successfully return to the
location prior to the teleport.
- 21-Apr-2015: However, the hop:// link always shows the original
login (home) grid rather than the grid you are actually on, so fails
to work for teleports to the last location unless that was the home
grid.
- 21-Apr-2015: The hop:// link put into local chat is also not
usable if you teleport between locations on the same grid. The link
if clicked states "No regions found with that name." and if you click
on the popup place profile teleport button it states "The region you
tried to teleport to does't exist anymore".
- 21-Apr-2015: As in previous testing, for OSGrid you must use
the login uri in a hop://login.osgrid.org:80 link, versus the usual
OSGrid Hypergrid link of hop://hg.osgrid.org:80
Testing in Firestorm 4.6.5 OS (40833)
- 14-May-2014: hop://grid:port/region, hop://grid.port/region/,
hop://grid:port/region/x/y/z or hop://grid:port/region/x/y/z/
all work when given in the address bar.
- 14-May-2014: A hop:// teleport WITHIN one OpenSim grid gives a return
location including the grid URL. This cannot be used to return to the
original location. A message "Grid: No regions found with that name."
is given instead.
- 14-May-2014: The grid part of the hop:// links put into nearby
chat for the location your avatar teleported from always contain the
original login grid, rather than changing to reflect the actual grid
you are on.
- 14-May-2014: hop://grid:port/region or hop://grid:port/region/ on
its own is not recognised as a hop:// link in chat. The X/Y/Z or
X/Y/Z/ has to be given.
Testing in Firestorm 4.6.1 OS (40478)
- 12-Mar-2014: After install of 4.6.1, use of a hop:// external link
shows no program is registered as the hop:// handler. FirestormOS can
though be manually selected as the default program then.
- 12-Mar-2014: hop://grid:port/region, hop://grid.port/region/ or
hop://grid:port/region/x/y/z all seem to work when given in the
address bar.
- 12-Mar-2014: A hop:// teleport WITHIN one OpenSim grid gives a return
location including the grid URL. This cannot be used to return to the
original location. A message "Grid: No regions found with that name."
is given instead.
- 12-Mar-2014: The grid part of the hop:// links put into nearby
chat for the location your avatar teleported from always contain the
original login grid, rather than changing to reflect the actual grid
you are on.
- 12-Mar-2014: hop://grid:port/region or hop://grid:port/region/ on
its own is not recognised as a hop:// link in chat. The X/Y/Z/ has to
be given. Otherwise hop:// is chopped off the front and rest is
converted to an http:// clickable link.
Testing in Firestorm 4.5.2 OS Nightly (39517)
- Testing Underway as at 22-Nov-2013.
- Launch of program via an external hop:// link launches the
program (after initial selection of it as the preferred
program), selects the grid involved and puts the region/X/Y/Z in the
initial location box.
- The :80 port in an OSGrid hop://does not match the Firestorm
OpenSim grids entry for OSGrid which does not have port :80
appended. If :80 is in the external HG link then a message "Your start
location did not specify a valid grid." is given.
- A :80 in the hop:// DOES work if used internally as a link in chat.
- If hg.osgrid.org is used it adds a second entry with same grid
name of OSGrid to the Firestorm OpenSim grid list (default being
login.osgrid.org).
- hop:// to a second grid worked fine in chat. (Openvue -> OSGrid)
- hop:// in address bar does not seem to work in this version. It brings up the search window.
- hop:// to SAME grid still fails to remove the grid name to allow
it to work.
- After returning home from a foreign grid to original grid (OSGrid
to Openvue grid), the hop:// link added to chat puts in the HOME grid
rather than than the foreign grid
hop://virtual.aiai.ed.ac.uk:8002/Sandbox%20Plaza/128/128/22
when it should have put in
hop://login.osgrid.org:80/Sandbox%20Plaza/128/128/22
- When inside Firestorm OSGrid hops:// from
hop://login.osgrid.org/region/X/Y/Z/, hop://login.orgrid.org:80/region/X/Y/Z/,
hop://hg.osgrid.org/region/X/Y/Z/ and hop://hg.osgrid.org:80/region/X/Y/Z/ all work.
Testing in Firestorm 4.5.1 OS Beta (38838)
- 31-Oct-2013: Use of a hop:// external link when viewer is already
running or not running brings up an empty dialog box that has an "OK"
button. if this is pressed, the Firestorm 4.5.1 OS Beta viewer
crashes.
- 31-Oct-2013: A teleport WITHIN one OpenSim grid gives a return
location including the grid URL. This cannot be used to return to the
original location. A message "Grid: No regions found with that name."
is given instead.
- hop://grid:port/region or hop://grid:port/region/ on its own is not rtecognised as a hop:// link in chat. The X/Y/Z/ has to be given.
Testing in Firestorm 4.4.1 OS
- 26-Jun-2013: The above hop:// URLs will work to launch the viewer and set the
initial startup region correctly.
- 26-Jun-2013: If you are logged in already paste the above hop:// URL for a
different destination grid into the location bar at the top of the
viewer. Trying to use a hop:// to the same grid will fail in 4.4.1.
Issues in Firestorm 4.4.1 OS
- 26-Jun-2013: In version Firestorm 4.4.1 OS hop:// appears not to work between
grids now - in 4.4.0 OS it did. Instead the lookup on the region name
is done on the local grid only. If the region exists that is
selected. Otherwise a "Null" region at (0,0) is found for example on
OSGrid. Jumping to that from within 4095 range crashes Firestorm
4.4.1 and gives the error message "ERROR: newview/llsurface.cpp(1347):
LLSurface::getPatch: Asking for patch out of bounds".
- 26-Jun-2013: In version Firestorm 4.4.1 OS the hop:// works on the local grid also.
On 4.4.0 this gave an error on the LOCAL grid return hop:// link.
- 26-Jun-2013: In version Firestorm 4.4.1 OS the hop:// appears to translate
properly to the X/Y/Z location given when the viewer is launched from
the hop:// link. But if that same link is used when the avatar is
logged in, the location is set to 128/128 on the destination region
even where "anywhere" teleport routing is allowed.
- 26-Jun-2013: hop:// links used when an avatar is logged into the viewer bring up a teleport window, but the details never resolve. the teleport button and map buttons though are active. Clicking Map does bring up the correct region - but see other issues for it ignoring the grid and X/Y/Z position in this.
- 26-Jun-2013: A means to handle https:// secure Hypergrid grids needs to be
added. At present hop:// will always convert to http:// as the
protocol. Use of hops:// has been suggested.
x-grid-info:// scheme (Hypergrid)
Cinder Roxley has suggested that x-grid-info:// replace
x-grid-location-info:// to allow for functionality beyond just
teleporting and location changing.
x-grid-location-info:// scheme (Legacy Hypergrid)
Cinder Roxley is developing a multi-grid teleport addressing scheme
that works in a similar fashion to hop:// in that it can be used to
launch or communicate with a running viewer and teleport to a specific
grid, region and location, as well as run certain app features. It is
being implemented initially in the
Alchemy Viewer.
More details of the protocol are available at
- Openvue via x-grid-location-info (no longer active)
- AiLand via x-grid-location-info (no longer active)
- Kitely via x-grid-location-info
- OSGrid via x-grid-location-info
Partial x-grid-location-info URLs...
Special Test x-grid-location-info URLs...
Issues in Alchemy 3.8.2
- In version Alchemy 3.8.2 (36473) (x64) clicking a
x-grid-location-info link correctly launches the Alchemy Viewer if its
selected as the scheme handler, and correctly selects the grid, region
and x/y/z location is specified.
- In version Alchemy 3.8.2 (36473) (x64) clicking a
x-grid-location-info link for a grid that is not already set in the
grid list in Alchemy does not add the grid to the grid manager, or ask
if you want it to be added as a confirmation, which would be a nice
feature. If you are already running Alchemy it reports "No regions
found with that name".
- In version Alchemy 3.8.2 (36473) (x64) a mistakenly written link
such as x-grid-location-info:hots:port/region/regionname (missing //)
launches a second instance of the viewer rather than trying to use a
currently launched version and leave the grid and location set to
whetever it last was at.
- In version Alchemy 3.8.2 (36473) (x64) trying to jump to a
location with a negative Z value fails, it launches another copy of
the viewer if it is already running, but also does not set the grid
correcrtly, it stays at the last used grid, and does not set the
location, it stays blank. -ve Z is allowed in OpenSim. Alchemy does
allow movement below Z = 0m.
- In version Alchemy 3.8.2 (36473) (x64) trtyig to jump to a
location with a negative x or y fails, it launches another copy of the
viewer if it is already running, but also does not set the grid
correcrtly, it stays at the last used grid, and does not set the
location, it stays blank. Negative X or Y should probably be changed
to enforce X = 0 and/or Y = 0.
- In version Alchemy 3.8.2 (36473) (x64) a partially specified
x-grid-location-info with "/region" on the end sets the location to
0/0/0/0. This will allow a login at the grid's "Fallback" region so is okay.
- In version Alchemy 3.8.2 (36473) (x64) if no X/Y/Z is specified then 128/128/0 is used. That is probably not a bad default.
- In version Alchemy 3.8.2 (36473) (x64) using the Previous, Next or
Drop-down history choices to try to teleport to a region on the SAME
grid that you are already on fails. In this case currenmtly you muist
edit the address bar to remove all but the regionname/X/Y/Z
part.
- In version Alchemy 3.8.2 (36473) (x64) when already in Alchemy and
an externally provided x-grid-location-info:// link for a location on
the CURRENT grid is clicked, a "Place Profile" popup tool does appear
and if its a valid location the teleport button will take you to the
selected location. But the Place Profile box says "Loading..." and
never resolves the information for the given region.
- In version Alchemy 3.8.2 (36473) (x64) when already in Alchemy and
an externally provided x-grid-location-info:// link for a location on
a DIFFERENT grid is clicked, a "Place Profile" popup tool does appear
but a "No regions found with that name." popup also shows. If the
foreign grid region name happens to be identical to a region name on
the current grid, the system thinks you mena the region with te shared
name on teh CURRENT grid. The Place Profile box says "Loading..."
anyway and never resolves the information.
- In version Alchemy 3.8.2 (36473) (x64) an extra trailing "/" can
be on any URL which is good.