wrong calculation on fuel flow

That certainly looks odd and seems like a bug. We'll add that to the list for the next version.

Ok, I have to apologize because I gave the wrong answer here.

You will have to set up your fuel consumption at certain speeds in your boating profile. Then we should calculate it correctly.

No ... that does not help.

No ... that does not help.

So i created 2 more speed / fuel flow on my existing boat profile
and even though i use the same speed as the new ones i created in my boatprofile on one or more of the route legs, the calculation is still wrong, meaning the slower i go the more fuel i use and visa versa

You can see it for yourself ... you only need to create a route with 3 or 4 legs
and set the speed on the first leg to a lower speed than your cruising speed it shows the wrong calculatio right away

Btw. i dont understand why this is a option to create more speed / fuel flow sets
they don't work when changing the speed - have you tried it yourself - nothing happens

Regards

Chris

I tried it and it works for me.

Can you give me a screen shot of your boating profile?

You will have to set at least 2 speeds (with consumption) in the profile, HomePort should then calculate correctly (and it will pick up consumption for speeds in between the ones you set as well).

I am not entirely sure what happens when you only have one speed set and then put a different speed in the route. We might do something there that doesn't make too much sense and will into it.

wrong calculations

Chris,
The fuel calculations seem to work correctly for me, as long as I don't manipulate the fuel on board. For some reason, if you manipulate the fuel on board, the speed changes to 0.1 mph (without user input) and then your fuel consumption goes way up. If you review your route, you will notice this change. Also, if you manually change the speed back without re-entering the fuel at start, the fuel at start becomes 0.1 gallons. Something is seriously wrong with this feature. I was going to start another thread, but thought this is the place to address route planning anomalies.