I wonder why speed limit dropped at 7:40. My guess would be that there used to be some kind of road constructions at this spot and slower speed limit was there for some time.
It would also mean that speed is not always based on vision data only. And that is a bit concerning, but could be connected to lack of long term memory managed by the FSD alone, not by the navigation module or data.
Thanks for checking out the vid @Kaipiso. Yea, it seems like it's a problem that's been there for a while. Even last year i noticed it w/ FSD 11. There were no recent road constructions and presence of slower speed limit signs. That said, another person commented in one of my vid w/ the same issue and was able to reproduce what I encountered but still unsure why
@@FSDobserver I think you should keep disengaging there and voice reporting, as it seems as a local issue. And pray that someone will notice that one day. You can also try to disable FSD before that spot. And drive manually with a proper speed. In theory, FSD runs in shadow mode in the background and compares its prediction to your drive style. If a huge difference is found, it might be reported or somehow corrected.
I wonder why speed limit dropped at 7:40. My guess would be that there used to be some kind of road constructions at this spot and slower speed limit was there for some time.
It would also mean that speed is not always based on vision data only. And that is a bit concerning, but could be connected to lack of long term memory managed by the FSD alone, not by the navigation module or data.
Thanks for checking out the vid @Kaipiso. Yea, it seems like it's a problem that's been there for a while. Even last year i noticed it w/ FSD 11. There were no recent road constructions and presence of slower speed limit signs. That said, another person commented in one of my vid w/ the same issue and was able to reproduce what I encountered but still unsure why
Yes, that's what I was thinking too. it's not always based on vision data only and it could be for the reasoning you pointed out
@@FSDobserver I think you should keep disengaging there and voice reporting, as it seems as a local issue. And pray that someone will notice that one day. You can also try to disable FSD before that spot. And drive manually with a proper speed. In theory, FSD runs in shadow mode in the background and compares its prediction to your drive style. If a huge difference is found, it might be reported or somehow corrected.
@@Kaipiso yes, I should do the voice reporting. That's the one thing i haven't done yet. Will do that for next time. Thanks!