All I've done so far is read guax's link on the coordinate system, but I think the intended workflow goes like this:

1. Plot the point where you currently are on the map.

2. Flag that point; you only get two Grease Pencil Points, but you need to remember this forever.

3. Plot the point you want to get to. Flag that one too. (You'll need to clear the grease pencil in order to do this. Flag your location before you do.)

4. Set Point 1 to location and Point 2 to destination. Open the protractor and read the azimuth from Point 1 to Point 2. This is based on Grid North.

5. Apply the adjustment between Grid North and Magnetic North.

6. Use your compass to orient yourself along the correct azimuth. The compass uses Magnetic North. You had to make all the measurements with your fat, stubby fingers, so hope they were accurate.

7. Start walking, tracking the distance you've gone.

8. Encounter obstacles.

9. Step off the track.

10. Wander into the wilderness and starve.

(You also get a notepad; I assume the notepad is there to give you some hope of recovering if you plan out the path around an obstacle carefully.)

I'm surprised they give you the option to move forward deterministically; that's not actually a thing that humans operating outside can do.

A key thing may be overlooked right at the beginning: you're supposed to enter a conversion factor of paces per 100 meters. Easy to miss and will leave you feeling like everything is too close together. Also the way the counter works when you're walking around is baffling.

>> I'm surprised they give you the option to move forward deterministically; that's not actually a thing that humans operating outside can do.

Absent distant landmarks?

You can do a pretty good job if you can see mountains, or the sun.

The path generation is pretty nonsensical though, nothing here follows the terrain, they are only good as some sort of blurry guides.

The formatting of the MRGS coords is horrible.

Just give the easting and northing is blocks please like 1234 5678.

Feels like 90 of the time is wasted on parsing this and making sure your in the right square kilometer.

Also the waypoint could give you there ID when getting near them, so you could just assign them to the waypoint number, having to type seems overkill.

> Also the waypoint could give you there ID when getting near them, so you could just assign them to the waypoint number, having to type seems overkill.

I assume the point of the simulator is to train the user to complete a similar exercise in reality, so I don't agree here - you have to write down the waypoint code in the real exercise, and it's not good for the simulator to encourage you to overlook doing that.