FSDtester#1
Large Member
Gonna have to wait on Chuck unfortunately...
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
I last used Autopark on Friday, and it was still very slow to shift between Drive and Reverse. (Quicker shifting in Autopark is one of the changes people have reported for FSD V12.4.1...)THEN the BIG difference happened in AUTOPARK and others need to check this. Before Autopark ALWAYS took about 2 seconds to switch between R-D. Now it is doing it instantly. I even pulled out and parked in a couple of different spots to try.
Yeah so did I and it was sloooooow as hell. But is was different today and more than once. I parked in 3 different spots to test and each one was so much faster and switched near instantly than it was doing just yesterday (Sunday). Maybe anecdotal..... but please try it today.I last used Autopark on Friday, and it was still very slow to shift between Drive and Reverse. (Quicker shifting in Autopark is one of the changes people have reported for FSD V12.4.1...)
Tested and you are right.Yeah so did I and it was sloooooow as hell. But is was different today and more than once. I parked in 3 different spots to test and each one was so much faster and switched near instantly than it was doing just yesterday (Sunday). Maybe anecdotal..... but please try it today.
Maybe its just showing off? Now that its not doing the lane change two step, its become self aware that confident lane changes are fun.The 6 lane changes seemed to be pretty confident in wanting to make the lane change as opposed to 12.3.x behavior of starting a lane change and second guessing if it should complete. This 12.4.x behavior would be consistent with additional training to make it more decisive in completing maneuvers, but in this case it seems to be confused by conflicting map data with numerous turn-only lanes both left and right that it was probably "seeing" both visually and from map data. The final lane change was necessary to get out of a right-turn-only lane, and potentially the closeness of these intersections resulted in mixed signals.
Presumably this comes from focused training on 12.3.x examples of where people had to correct the lane selection, and with enough examples, it's learning to rely more on input signals of upcoming mapped turn lane data. There probably is not as much explicit training on "don't make lane change" / "just stay straight" examples as that's the common case anyway, so this could result in the unnecessary lane changes that now needs additional training to figure out when lane changes aren't actually required. Unclear if this will require more examples from a wider deployment of 12.4.x to get this data as active usage of FSD should help find its current mistakes to fix in the next version.
I don't miss them but Alan probably does. He needs his daily fill of stuff to complain about. You just gave him a good idea!Speaking of "good old days", anyone else miss the complaining about phantom braking?
Sorry, I have dark side lol
I just completed a 3800 mile trip with zero PB events thankfully - multiple 2-3 mph "slowdowns" (which are still unwelcome when there's no hint as to why) but none of the old PB's. Definitely an improvement from last year's trips.Speaking of "good old days", anyone else miss the complaining about phantom braking?
Sorry, I have dark side lol
I never complained much about phantom braking - never thought it was much of an issue. It is regular braking and anticipation of stopped traffic hundreds of feet ahead that still needs tremendous work.I don't miss them but Alan probably does. He needs his daily fill of stuff to complain about. You just gave him a good idea!
Nice to hear something you are happy with something regarding FSD... I will bookmark this to read again on days I am feeling down, just to cheer myself up.I never complained much about phantom braking - never thought it was much of an issue. It is regular braking and anticipation of stopped traffic hundreds of feet ahead that still needs tremendous work.
That discussion is over. Alan and I discussed it yesterday. It doesn't belong in this thread, except for cheat devices, which we both thinkI'm free to recount my experiences in detail for a page or 4 if it will keep us of the "Mug shot" discussion....![]()
Now that we're on yet another and new FSD 12.4.x delay, curious to see what happens with us 2024.3.25 folks. There's no reason to hold us back any longer on the spring update since the latest FSD is on the 2024.15.x branch, yet as of this morning we still sit at 2024.3.5 with zero updates.
On one hand I take it as a good sign we're not being moved up to 2024.14.9. meaning they expect to have the next revision of FSD out very shortly for testing so a few days longer isn't a big deal. If we do start seeing 2024.3.25 upgrade to 2024.14.9, that would be a bad sign in that we will likely be waiting weeks more for an FSD update that will get into the hands of us common folk so they're at least getting us on the spring update in the interim. That said, there is some nice stuff in the spring update I wouldn't mind playing with while we continue to wait.
Based on the influencer videos over the weekend all pretty much being unanimous that 12.4.1 wasn't ready, a bit of a head scratcher why they even released it in the first place. You'd expect those issues must have turned up during internal/employee testing.
It is what it is I guess.
2024.3.25/12.3.6 is only 3 percent of 2024.14.9/12.3.6. That small percentage could be for release testing purposes. If Tesla update all cars with 3.25/12.3.6 to 2024.14.9 then there is no guarantee that the update is successful. And if the update is not very good then they have to release 2024.14.10 again and again. The main goal of 2024.14.x is to let who didn't have fsd 12.3.6 to have it. These people have been crying.
A bunch of people on X corrected me, they all said the same thing regarding FSD. I didn't get any proof, but received like 50 responses to one of my posts about FSD versions vs. Non FSD versions. They all said that every release in the last month or so from Tesla globally has the code for FSD in it.One thing to note is that while only 3% of 14.9 came from 3.25, 15% of 14.8 came from 3.25 and then went on to 14.9. Also a few % went to 14.6 and 14.7.
It is strange how many people are still on 3.25. Maybe there are that many FSD users out there?? 14.9 seems to be a stable version but maybe Tesla isn't fully happy with its stability and that is why they are now moving non-FSD people on from 14.9 to 20.1 (big surge in 20.1 today)
Elon even agreed that 12.4 isn't ready to replace 11.3.6. So I'm not sure what the "arguably version 13" means other than hype.If they really did halt the rollout in favor of a new version, and based on the feedback from those who tested it that showed regressions, I can’t help but wonder what this version can do that makes Elon call it “arguably version 13” because no one that has it seems to have anything to show that would suggest that.
It was a cul-de-sac and it didn't really park. You can see on the visualization, it's basically in the road.