anonymess Posted July 19, 2020 Share Posted July 19, 2020 I am in the UK. When I plan a route from somewhere in France to elsewhere in France and enter a start time, that time is shifted by an hour. For example: Journey starting in Calais, going to St Omer. Start time set as 0930. Plan is generated with start time of 1030. It is as though ABRP is interpreting the start time as my current local time, which it should not be. Times should (as they are in, eg, airline timetables) be local to the place of departure not the place where the user is currently sitting. I am sure I haven't seen this erroneous behaviour before. In this case I'm using "classic" because I cannot get the new app to work (reported separately). Using a Mac. Same thing happens on iPad using browser. Link to comment Share on other sites More sharing options...
anonymess Posted August 4, 2020 Author Share Posted August 4, 2020 (edited) This is a persistent error. Today I planned a route from the UK to Germany, and set a departure time for a stopover in calais to 09:30. When the map was displayed, the app had changed that time to 10:30. Can this bug be investigated please? Edited August 4, 2020 by anonymess Link to comment Share on other sites More sharing options...
Jason-ABRP Posted August 5, 2020 Share Posted August 5, 2020 This bug is now on our priority backlog, so expect it fixed soon! Link to comment Share on other sites More sharing options...
Ou Boet Posted August 16, 2020 Share Posted August 16, 2020 My plans are in the right time zones, but when I go back and look at My Drives, these are offset by about 8 hours. Seems that when ABRP saves drives it doesn't take account of GMT off set. Is this something that can be tweaked? Link to comment Share on other sites More sharing options...
