[zroger73]

I fear the worst.

I don't because I fully expect that Tesla has been spending months training and validating a limited service area in Austin to ensure the vehicles perform much better than all other Teslas in other areas. These robotaxis will be running newer versions of FSD with Austin-specific models or at least tuning of the models to be Austin-specific. I'm also confident that Tesla has a system in place to allow vehicles to stop and wait safely for teleinstruction in case they get stuck.

Safety; Is this repeatable?

It made this same turn correctly Monday, Tuesday, Wednesday, and Thursday, but not Friday.

 

[Bigriver]

I am really excited about the more reasonable driver attention monitoring on FSD 13.2.9. I have chimed in on many threads on how unreasonable it has previously been on my HW4 model S. I think some have assumed I am a quack because I have reported that it will sometimes nag for just looking at the ETA. But that has absolutely been true. (I have to note that on the refreshed model S the ETA moves around on the screen depending on the map view and length of the turn instructions and is sometimes obscured by the steering wheel. I don’t know if the monitoring was misinterpreting necessary head movements or what.) Anyway, I have only been out driving for a day on 13.2.9 and it was a totally nag-free day even though I was responsibly interacting with the map in ways that would have previously resulted in nags. I am very hopeful!!

As an aside, I drove my HW3 model 3 on FSD 12.6.4 through heavy traffic on the way to the airport last week. In the car for over an hour. I consulted the map and considered different routing often. Not a single nag. That same behavior in my HW4 model S before 13.2.9 would have given me many nags, and probably a strike.