abetterrouteplanner.com/?plan_uuid=018c61f3-080b-4583-a2aa-3398b667cc3a. Leads to long detour through Melbourne
I'm not sure if this helps but I loaded the route as linked in Martin's post and it defaulted to the ferry route. This might be resolved?
If there is a ferry line which isn’t automatically selected and included in the planned route, the planner will have deemed it to take too long and thus excluded it from the plan. You may however manually include it this way:
1. Zoom in on the harbor from which the ferry leaves.
2. Find the correct dashed ferry line. If there are multiple ones, it may help to zoom out or look a bit further out from the harbor to see which one goes towards the correct destination.
3. Place a marker on the line. If you’re using the web version you can do so by right-clicking and if you’re using the mobile app place it by making a long press, anywhere on the line.
4. After a marker is placed you’ll be presented with some options, similar to if you’ve placed a marker on land. Instead of the option ‘add guidepoint’ you’ll be able to ‘add ferry line’ select this.
5. The ferry line has been added to your itinerary, have the planner calculate once more and it’ll be included in your plan.
Note that some ferry lines may be marked as closed in OpenStreetMap, which we partly base our map information on. If this is the case, the ferry line might still not be included in your plan.
Also keep in mind that we do not keep track of specific ferry departures. At the moment we only account for the duration of the ferry when calculating a plan.
Here's the plan with this change; abetterrouteplanner.com/?plan_uuid=a93e269e-8870-4361-965c-ebd37f4b06f4
However, it is somewhat strange that we do not suggest using this ferry as it would lower the overall travel time.