Commander DIY - NAVIGATION HUD

PLEASE NOTE THAT IT MIGHT TAKE A LONG TIME TO FIND THE WAY IF THERE ARE MANY POSSIBLE ROUTES!

Do you want to make your own database for navigation? These are the steps:

<1> WRITING THE DATABASE

1. Make a notecard. Open it wide (screen wide).
2. For each navpoint, write as follows:

Achemon/rail#<135,175,0>,Vine/rail,Didugua/rail

where,

Achemon - the name of the sim where navpoint is in

rail - something to differentiate navpoints one from another

#<135,175,0> - map coordinates of a navpoint. The Z component MUST be zero.

Vine/rail - navpoint where you can arrive from the navpoint you listed

So, a ROW consists of:

home navpoint # coordinates , navpoint 1 , navpoint 2 , navpoint 3 etc

A NAVPOINT consists of:

sim name / navopint description

DO NOT USE BLANKS. Do not write a navpoint like this:

Achemon /rail #<135,175,0>,Vine/ rail ,Didugua /rail

DO NOT put blanks at the end of a row.

3. You can add up to 300 rows on a notecard.

<2> CHECKING NAVPOINTS FOR ERRORS

1. Drop the COMMANDER DELETE script in a prim and click.

2. Drop your notecard in the prim.

3. Drop the COMMANDER TESTER script in the prim and click.

4. Listen in chat for mistakes.
- Wrong coordinates
- Blanks
- Sim names or navpoints not spelled properly
- Missing links

5. Correct the notecard.

6. Repeat until there are no more errors.

TIP: For a complex network of navpoints, you will need many notecards. If navpoints from one notecard link to navpoints on another notecard, just ignore the errors regarding them.

<3> EDITING THE HUD

1. Drop the COMMANDER DELETE script in the HUD.

2. Drop the notecards with navoints in the HUD.

3. Drop the COMMANDER LOADING MULTIPLE script in the HUD.

4. Insert the commander script you need:
- COMMANDER 1 for a HUD that starts working from the sim you are into
- COMMANDER 2 for a HUD that starts working from any sim.
- COMMANDER 3 for a memory relay whose data can be downloaded into the REMOTE HUD .

LIMITS

1. The system will not work if scripts are disabled.
2. Be aware that a complex network will require long times to find a route.
3. The process is painful and long. It might take days to get all navpoints for a continent.
4. A HUD or a relay has a memory of about 1400 nvpoints. Anything beyond that will cause memory losses. A notecard can host roughly 300 navpoints. Anything above will cause memory losses.
5. Gaps in database can compromise the whole search.