Knightshade
Well-Known Member
Dan stage his videos to specially cause fsd to fail.
He also cites lots of OTHER peoples FSD videos running older versions with failures, to which Tesla folks will yell "UNFAIR! that is a version from 3 months ago!" which is the behavior to which I was referring.
Also I would imagine none HD map would have worst performance vs what is shown here with HD maps. Honestly if Tesla gets mapping right fsd is pretty much solved. Mapping is pretty much everyone's issue right now cause traffic negotiations are mostly on point.
Except then you're back to having 2 sources of truth.
Do you believe vision or the map?
If the map says there's a stop sign, but vision does not-- do you stop? Because there's cases where the sign IS there, but overgrown, and vision misses it. So which is "true"?
And how do you create the maps and keep them up to day everywhere? If your answer is using the fleet--- the fleet only has vision. So how do your maps ever end up better than just using vision in the first place? Everyone else doing HD maps is using additional sensors. I could see some usefulness for future lane selection-- but that's about it.
And my biggest lane-selection issue in V12 is not being in the wrong lane (though it DOES do that) it's how it'll bounce halfway between 2 lanes indecisively for way too long-- which definitely seems a traffic negotiation issue.