FSD's reading of speed limits might be a little off

[Zero Degrees DeLisle]

There is a stretch of E-470 in Denver going north, where my CT thinks it's a speedway. Thank goodness FSD maxes out at 85.

I saw this exact same thing today going both to and from the Denver airport ... and so captured what might be the cause.

It looks like it could be reading the sign saying to "STAY IN LANE" with three arrows as a 100 mph speed limit sign, as it was at this point that I noted the speed limit changing on the screen. This sign (with the 3 arrows) is only present at the toll gate area around mile marker 15.5 as the one at mile marker 22 just says "STAY IN LANE".

It took several miles going North before another 75 mph sign was present for it to change back. Going South it was a little closer.

Captured when going North:

Going North:

Going South:

Sponsored

 

[hemiarch]

I saw this exact same thing today going both to and from the Denver airport ... and so captured what might be the cause.

It looks like it could be reading the sign saying to "STAY IN LANE" with three arrows as a 100 mph speed limit sign, as it was at this point that I noted the speed limit changing on the screen. This sign (with the 3 arrows) is only present at the toll gate area around mile marker 15.5 as the one at mile marker 22 just says "STAY IN LANE".

It took several miles going North before another 75 mph sign was present for it to change back. Going South it was a little closer.

Captured when going North:

Going North:

Going South:

Come on Tesla. This shit is embarrassing. You solved problems that were WAY more complex than determining speed limit to get FSD this far, why snooze on this? It’s not new data. Everyone from the Tom Tom Dutch guys two decades ago had it already. Why stick to your guns about ignoring all that?

 

[Sjohnson20]

I'm driving to Atlanta next week. I really hope it's not slowing for the minimum speed 40 signs again.

 

[Patriot]

I saw this exact same thing today going both to and from the Denver airport ... and so captured what might be the cause.

It looks like it could be reading the sign saying to "STAY IN LANE" with three arrows as a 100 mph speed limit sign, as it was at this point that I noted the speed limit changing on the screen. This sign (with the 3 arrows) is only present at the toll gate area around mile marker 15.5 as the one at mile marker 22 just says "STAY IN LANE".

It took several miles going North before another 75 mph sign was present for it to change back. Going South it was a little closer.

I saw this exact same thing today going both to and from the Denver airport ... and so captured what might be the cause.

It looks like it could be reading the sign saying to "STAY IN LANE" with three arrows as a 100 mph speed limit sign, as it was at this point that I noted the speed limit changing on the screen. This sign (with the 3 arrows) is only present at the toll gate area around mile marker 15.5 as the one at mile marker 22 just says "STAY IN LANE".

It took several miles going North before another 75 mph sign was present for it to change back. Going South it was a little closer.

Interesting. I have never caught exactly where it happens. You could be right. If that is the case, I would think it's trying to set it to 111 and there is a hard-coded 100MPH max, so that's what we see. A developer with access to the logs should easily be able to see if that's what's happening. Nice catch!

 

[Zero Degrees DeLisle]

From recent trips to DEN, this issue appears to have been fixed.

 

[pae1andonly]

Well... it is a truck

When the truck speed limit becomes 20, my CT no longer identifies as a truck. FSD does ... but the rest of the package is all WTF! And STILL doing with @ FSD 14.2.2.5.

Sponsored