I think this has fixed itself now.
EDIT0: Okay, so it didn't happen for any of the threads I archived in the WIP section, nor did it happen when I re-opened and replied to a bug report, but when I replied to this thread and then moved it to resolved, that subforum exibited the issue.
Finally been able to test it myself and my tutorial still works.
Make sure you follow every step of the tutorial. If you don't create the folder for the aerials to go into, introduce a typo in the link or don't include your API code correctly then it won't work.
Down in the far bottom left there should be a D line to Stanhope and a dashed AD along most of the A and D which only runs in the evenings and early mornings. Good luck fitting that all in with the space available though.
Just above that, drawn very approximately in dotted blue is the G line to...
Temporarily adjust the paths so that you're completing to an end rather than a joint. Inverting the curve radius, or changing the position/length by a couple of metres on one of the paths should suffice.
Type 1 is a track for the whole trip, Type 2 is a trip made up of a series of station links (which are like mini-tracks from each bus stop to the next).
Type 1 is what OMSI 1 supported, Type 2 was added with OMSI 2 to reduce work repetition when creating routes that share sections with each other.
My current intention is to keep applications open indefinitely - we'll check over the submitted applications whenever we find we want more people.
A visual inspection of the packaged file is frequently enough to find the issues we deny files for (e.g. no README, missing files), but not...