Bug found re. current location

[Astronut]

I don't know if this has been noticed by anyone but I'd be surprised if it hasn't. I've had a quick glance through past posts regarding bugs and have not found any reference to this so I apologise in advance if I'm raking up old ground.
I've not used TT3 for any routes I don't know yet. I've only had it a few days so the opportunity hasn't come up yet. Therefore, the routes I've tested it on are well known to me.

The problem is this:
On the navigation screen, the bottom of the screen is supposed to show the road you're currently on - yes?
I've found this isn't always the case. If the road you're on has instructions such as keep right or go straight on at the next roundabout, ie. you're still on the same road after the next instruction, then the current road is shown correctly. However as soon as the next instruction is to exit onto a different road, the current location displays incorrectly as the next road ie. the road you will be on after the next instruction.
For example:
Travelling north on the A483, near Wrexham, towards Chester, the road intersects the A55 with a roundabout and then the A55 (eastbound) becomes the M53. Now before the A55 roundabout, on the A483, there is another roundabout. Approaching the first roundabout, the current location shows correctly as the A483 and the top right of the screen says A55 (the road you're travelling towards). As soon as you negotiate the first roundabout (across the roundabout, 1st exit), the current location displays A55, even though you're still on the A483. There is only one more instruction at this point and that is to leave the A483 and enter the A55. I've noticed this pattern on all the routes I travel so it isn't peculiar to this particular route.
The pattern is always the same: When the next instruction is to leave the road you're on and join another road, the current location displays incorrectly as the next road you're about to join. It's as if a counter in the program is one higher than it should be. I'm an ex-programmer and I imagine there is an array held in memory for the current route with a list of all the road names or numbers (A483, A55, M53, M56, M6, etc) for displaying at the bottom of the screen (current location) between each navigation instruction. It would seem that the array index is pointing to an element in the array above the one it should be displaying ie. the road displayed as the current location is the one that should be displayed AFTER the next navigation instruction.
This may seem a long winded explanation and I hope it makes sense but there is definitely a bug there. An array index has been incremented by 1 too early in the program (a common mistake in programming)
Another example:
I'm travelling up the M6 northbound to join the M62 eastbound. The next instruction is to keep right (to avoid the M62 westbound turnoff) and the current location is shown correctly as the M6. As soon as you pass that, the next instruction is to turn off the M6 and join the M62 and the current location then shows incorrectly as the M62. I won't be on the M62 until I've executed the next instruction. Now as this is only a short distance, it hardly seems worth mentioning but it falls into the same pattern.
Every route I've travelled on, the pattern is always the same.
I'm running the latest version (3.03) and I'm now wondering if this bug has always been present or it's just appeared in this latest release.

Apart from this niggling little bug, I'm very impressed with this app.

[joejoe123]

[Astronut]

[barryd]

Not sure what the manual says, but you're right in what you've seen TomTom do.

The top right box shows the next main road you need (different to the one you're on), which may be the next turn or several ahead. The bottom line shows the road you need at the next turn.

For example, if you're on the A1 London Road, and at the next turn want the A1 North Road, and at the one after that want the M1, you'll see "M1" showing top right and "A1 North Road" showing on the bottom line - two different levels of detail of where you're going. Having originally been confused by this too, I now find it very useful.

If you do want to see your current location while navigating, just touch the screen - it is then shown in the bottom area.
_________________
Barry Davies

[joejoe123]

Astronut

Sorry
you are right , i just mixed between navigation view and map view.

[gacrane]

I agree with what barryd says in the way it acts. If you are using Navigator with a route in the bottom line shows the road you will be on after the next instruction. But if on the other hand you are in the Navigator screen and have no route planed the bottom line will show the current road you are on.

I do use the Navigator scrren with no route when I'm doing routes I know but want to see the POI's on that screen.

Bug or not I don't know

Graham

[Astronut]

It is definitely a bug. I've just been away driving my artic for 3 days now and have had the opportunity to backup this fact. If you're on a route and the next instruction is to join a new road, the bottom line indicates the new road as has been said. If you then hide the map so that the safety speed screen is shown, the top line shows the road you're heading towards as on the nav screen but the bottom line shows the road you're currently on, which is correct. The nav screen shows 'current location' + 1 which is incorrect.
Try going down a route that takes you from the M53 to the M56 and then the M6. As soon as you join the M56 from the M53, the bottom line shows current location as M6 for the next 17 miles! So if you forget which motorway you're on (though you'd have to be a complete muppet to do that) you have to lean over and touch the screen to check which road you're on, which, when you're driving a 44Tonne artic is not a safe thing to do. The nav screen is very well designed and gives a great deal of information at a glance but having to touch the screen to double check which road you're on before joining another one is distracting to say the least.
I think this needs to be brought to TomTom's attention as it is very irritating and needs sorting asap. I know it would most likely be a simple thing to fix for the next update as the safety speed screen (map hidden) is correct in that it always shows the current location and not current location + 1.

[alix776]

m56 to m53 for 17 miles no it doesnt i was there this week unless mines got something wrong with but it didnt do it to me on wednsday
_________________
currently using aponia truck navigation on windows phone. Good bye IOS don't let the door hit you on the way out .

Oh the joys of being a courier.
device Lumia 950 xl

[alix776]

astronaut try using the safety screen as this will show your current and intended location personally i used the navigator mode as i prefer too glance the screen just before or at a junction

but if you know what you turning on to then the issuse shouldnt be problem

incidently im seeing more pda systems in trucks on my travels and saw at least 10 systems on the way up from dartford on friday night

the bottom line of nav veiw shows the name of the next road you truning in or on to
_________________
currently using aponia truck navigation on windows phone. Good bye IOS don't let the door hit you on the way out .

Oh the joys of being a courier.
device Lumia 950 xl

[barryd]

[Astronut]

[Astronut]

[alix776]

are you on about the top box in the right hand corner of the srceen
_________________
currently using aponia truck navigation on windows phone. Good bye IOS don't let the door hit you on the way out .

Oh the joys of being a courier.
device Lumia 950 xl

[Astronut]

[alix776]

no worries just a thought
_________________
currently using aponia truck navigation on windows phone. Good bye IOS don't let the door hit you on the way out .

Oh the joys of being a courier.
device Lumia 950 xl

We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?.
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!