-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
FSD v12.x (end to end AI)
- Thread starter Buckminster
- Start date
-
- Tags
- #fixphantombraking autopilot chill is not chill elon is an ass fix fsd extreme late deceleration fsd does not commit to go fsd does not maintain proper speed fsd hard and late braking fsd jerky driving fsd late deceleration fsd stops too early too quickly fsd stops too far behind line fsd tailgating in city streets
diplomat33
Average guy who loves autonomous vehicles
So far FSDS doesn't recognize bar gates without lights, but will slow down/stop for bar gates with lights. It can sometimes navigate out of this hospital's parking garage about 70% of the time, including fully stopping and then going for the bar gate with zero interventions. The other 30% of failure is due to making an incorrect turn and getting stuck before hitting a wall.
It however have navigated out of the top floor of the parking garage at universal studios(1/1). Have to try again later for consistency.
Another challenge I threw at it was a zero intervention drive to home from the Magic kingdom parking lot during park closure. It has fully completed the task yesterday with just 1 accelerator press at a stop sign due to hesitation. First time ever it has done this, also first time it has reached Magic Kingdom parking lot from home with zero disengagement(but had areas with speed issues).
It however have navigated out of the top floor of the parking garage at universal studios(1/1). Have to try again later for consistency.
Another challenge I threw at it was a zero intervention drive to home from the Magic kingdom parking lot during park closure. It has fully completed the task yesterday with just 1 accelerator press at a stop sign due to hesitation. First time ever it has done this, also first time it has reached Magic Kingdom parking lot from home with zero disengagement(but had areas with speed issues).
That stop sign isn't mapped. I have a stop sign that's put in a few months ago and my car would slam on the brakes vs gradual slowing like other stop signs. The system performs poorer the more the car goes above the speed limit.
EVNow
Well-Known Member
Yes - but the question is why doesn’t Tesla get crowd sourced extra metadata like MobilEye does.
There are lots of "training wheels" Tesla put into place and map being the biggest. It still currently overwrites many of the things FSD would want to do. However like I said, if the Tesla wasn't going 7mph over the speed limit, the car would most likely stopped (uncomfortably). No Waymo goes above the speed limit and for good reason.Are you saying that Tesla relies on maps to function?
That doesn't sound safe nor scalable? What about temprary signs and signals?
Musk wants to use as little map data as possible (as the goal per his statement) even though map data currently dictates what FSD has to do. I do feel V11 follows map data way more stricter than V12. So I'll be curious to see if V12 hwy will fix some of the missed turns. Perhaps this is why they are not bothering pouring resources into mapdata sourcing? Who knows, maybe they will find that stupid and change directions, or V14 no longer need map data.
Given that 12.3.4 initially followed the road to the right, it seems to have understood that it didn't need to stop:
But then it realized navigation says to go left/straight, and I suppose by that point, it was already past the stop sign?
Tesla doesn't need the "added safety and reliability" because that's the job of the people supervising. I think people are confused that the goal of the consumer car is to help them build a robotaxi eventually while giving people a good L2 ADAS system. So people complaining about a lack of camera wipers or whatever is missing the point. The robotaxi will have all the redundancy/camera wipers/ etc etc. Our current cars will not cover all scenarios because it's not meant to be robotaxies.
Then you are saying it's coded into the map to ignore the stop sign because the car cannot read "except right turn". If it sees a stop sign on the right hand side, it'll slam on the brake (unless going to fast and it doesn't have enough time to process).
I didn't notice this before. It looks like all my FSD strikes got deleted around the time the FSD demo was rolled out. I got a strike today out of the blue, and when I checked the FSD screen later, I saw the note that FSD had been disabled once, while I'm pretty sure this strike would've been the 4th.
Our current car lacks a lot of redundancies which are most likely required for full autonomous driving. People also pointed out there's a lack of camera wipers. Many things are required to be added onto the car being revealed on 8/8 vs what we have today for the sake of safety and performance without a driver. The bar becomes a lot higher if a driver is not meant to be in the driver seat unlike our cars. So yeah, knightshade will point out that the cars we buy today are no longer worded to be any kind of robotaxis which means Tesla can cut a lot of corners using us supervisors as clutch.
Uhh yes? Didn't I talked about this already a few pages back?
FSD v12.x (end to end AI)
I suspect they will fix the late lane change problem fairly soon. That just doesn’t seem hard.
teslamotorsclub.com
Similar threads
- Article
