@Challengers I think I have fixed the Lindsay-Parsons route in RunGo after @Petorius mentioned that it had a problem—I swear RunGo turn points sometimes jump from one line to another. I think it’s correct now, but let me know if it needs more tweaking.
Also, I added a warning about the off-camber muddy slope on FH Fox that wants to take you down (and claimed a couple of people on the group run).
@jennarice and I just ran the Hoctathon. The directions are plenty clear but RunGo was announcing each turn at least 5-10 minutes before we actually reached it. It was incredibly confusing and we ended up relying just on the map and disregarding the spoken directions. This was going on for both of us using RunGo on two separate devices. Ran over a mile extra because of wrong turns happening before we realized this.
I also ran Treman by myself yesterday and had almost no issues but that will be a separate post!
Whoa. 5–10 minutes? I wonder if there was some sort of server problem since it affected both devices. We’ll see what @Petorius says, since he ran it in the dark this morning.
It’s not inconceivable there’s some data corruption within that course on RunGo, because there are two spots where I had to move points far from where they should have been to get them to display the right distance into the course. It was a situation where I had points A, B, and C, but B was being spoken well after C due to having a higher mileage number, even though it was visually earlier on the map.
Worst case, I’ll redo it—it won’t be hard.
We followed our progress on the map using GPS and the map always looked accurate to where we actually were. Clicking into the turns as shown on the map (with the arrow icons) also showed the right data. Just a matter of when they were being announced
After Pete reported the same thing, I decided that route was probably corrupt on the server, so I’ve rebuilt it from scratch.
Yes, it was as if the arrow cues with the correct text/verbiage were randomly strewn around the route map and some of the turns reversed (i.e. “turn left” was now “turn right”).
@adamengst From what I see in the app, the correct version of the route is now visible and looks accurate. The corrupt one is still visible though.
Truly nuts. I’ve reported it to RunGo support, so hopefully they’ll delete it from whatever cache the RunGo apps keep.
Hullo - I ran Treman Trailipop this morning. Just to say that the voice instructions to go in and out of the field on the way up are bang on, so ‘check this instruction’ can be removed. For the way down, the one telling you to go into the field is also correct, but the one telling you to go back into the forest should say ‘Go left back into the forest’ rather than ‘Go right back into the forest’ as it does currently. It’s at the right spot though.
As you come to the stone steps to cross Lake Treman (around 3.87 miles according to my phone RunGo) there is a direction telling you to go slight right and look out for the steps (or something similar) - I think this should be slight left. I also think this is where Heather and I intended the ‘turn left at the sign’ addition to be made, as it is at the ‘Trail Around Lake’ sign (see photo). The ‘turn left at the sign’ voice instruction that is currently in place should be removed (it has a ‘check this instruction’ addition currently).
If none of that makes sense, feel free to let me know and I can call you tomorrow to talk through it? 
Nope, this all makes perfect sense, and I believe I’ve made all your suggested changes. There are still two “Check this instruction” prompts in there around the stairs on Lake Treman, so the next time someone runs this, let me know if those prompts are in the right place and saying the right thing.
I’ve added “Updated 2024-04-22 at 10 AM.” to the end of the description so people can know when it was last touched.
Thanks for the on-the-ground playtesting!
