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.
Now I need someone to transcribe the release notes into something I can understand
I just want me a "bag of points".Now I need someone to transcribe the release notes into something I can understand
This is a good list. However, my #1 complaint with FSD is this: Wiki - MASTER THREAD: Actual FSD Beta downloads and experiencesThoughts while waiting for 10.9
What I have found after using FSD for several months is when to anticipate a disengagement or an intervention on drives I do repeatedly. Most of the time they are now zero disengagement drives with some go-pedal interventions. These same drives when I first started ended up with disengagements and a frustrated beta tester. Clearly the improvement from my standpoint is the combination of learning how FSD drives since it certainly doesn't drive like I do, plus the slow improvement from FSD improvements over many releases.
Short list of Improvements I'd like to see (no particular order except for #1)
- Eliminate phantom slowdowns and unnecessary braking
- Make decisions quicker. This is especially critical in busy traffic and usually the reason I use the Go-pedal
- Would be a big help when approaching roundabouts along with countless other situations
- Stay to the right on intersections when turning left so your not impeding cars trying to turn onto your road
- Get into the correct lane sooner
- Don't move to the faster lane when there is a turn coming up
- On the highway stop moving into the faster lane when that means the car has to break to let you in. Happens all the time requiring canceling the lane change. Won't change to single stack.
- Recognize School Zones (this of course will take multiple iterations)
- Stay to the right when traveling on narrow rural roads, especially when approaching a slight incline where you cannot see cars approaching
- Poor weather/visibility resulting with FSD disabling itself. Will or won't the hardware work in poor weather?
- High beams- fix them
Agree which is why "Make decisions quicker" would go a long way to help with this problem. With 10.8.1 the decision to enter a roundabout is much quicker now. Still too slow but there is some reason for optimism so it should gradually improve over time. And of course stopping too far back needs to be fixed.This is a good list. However, my #1 complaint with FSD is this: Wiki - MASTER THREAD: Actual FSD Beta downloads and experiences
Specifically, stopping too far back from the stop sign and the 5-10+ second delay when turning left or right at any unprotected intersection, even if visibility is great and there is no traffic in sight.
I don't see anything in the 10.9 release notes that hints at this being improved, but fingers crossed!
For me it's almost entirely for turns involving cross traffic. On the other hand, if it's making an unprotected turn at a green light it can make (fairly) quick decisions about oncoming traffic.Agree which is why "Make decisions quicker" would go a long way to help with this problem. With 10.8.1 the decision to enter a roundabout is much quicker now. Still too slow but there is some reason for optimism so it should gradually improve over time. And of course stopping too far back needs to be fixed.
I did ponder that - was it just a ploy to combat complacency, scare the crap out the drive to make sure they pay attentionSome of these maverick moves sound so blatant that one could wonder if FSD is testing (or even training) the driver’s required awareness and readiness.
In @Jay S case, and possibly in yours, the issue is not necessarily with the FSD Beta code. It is more likely with the vision-only AP code. His Model 3 is still using the old AP code that includes supplemental radar, but all FSD beta vehicles are also pushed onto the less mature vision-only AP code. For this reason, disabling FSD won't necessarily help, and opting out likely doesn't actually help until a non-FSD update is pushed afterwards. However, if one has older vehicles where radars exxist and are supported, and one doesn't want to deal with the vision-only AP behaviors, then opting out is still the best solution for now.It’s probably just the FSD beta code still being inferior to the AutPilot-only code, which has tons more driven miles.
Yes, i did mean opt-out and revert to a non FSD release. Not sure if having a radar or not helps, but between the FSD releases and non-FSD releases I’ve been on, the non-FSD AutoPilot works much more smoothly.In @Jay S case, and possibly in yours, the issue is not necessarily with the FSD Beta code. It is more likely with the vision-only AP code. His Model 3 is still using the old AP code that includes supplemental radar, but all FSD beta vehicles are also pushed onto the less mature vision-only AP code. For this reason, disabling FSD won't necessarily help, and opting out likely doesn't actually help until a non-FSD update is pushed afterwards. However, if one has older vehicles where radars exxist and are supported, and one doesn't want to deal with the vision-only AP behaviors, then opting out is still the best solution for now.
As far as interventions go, seldom do we focus on manual speed changes. I find I am doing speed interventions almost constantly, especially after a turn, when the car doesn't really know the speed limit yet (typically showing the wrong speed on the center screen). As most of the roads I travel are winding 2-lane local roads, most of the time, the car slows below the speed limit to negotiate curves. While it's great that the car is pretty good about slowing before a turn, it's too slow for the driving culture around here, so I'm using the go pedal often.
On these same roads, during straightaways, people generally pick up the pace and are 10-15mph above the speed limit, so I typically use the right scroll wheel to increase my set speed accordingly. By default, I have a +5mph offset, and I'll bump it up to +10/15.
I use that scroll wheel a LOT for speed adjustments to keep FSD beta feeling comfortable for myself as well as other drivers. So much so that I think I'm going to wear it out (my Model 3 is older, so I have the plastic scroll wheels).
I can't tell if the release notes are a sign the technology is so new that nobody has an idea how to parse stuff into statements that actually make sense for users, or if the notes are only to satisfy regulators who understand all of this, or if they're purposely made to sound overly technicalNow I need someone to transcribe the release notes into something I can understand
I appreciate the transparency, even if it's unclear what to expect in all cases. It's fun to watch the guts evolve.I can't tell if the release notes are a sign the technology is so new that nobody has an idea how to parse stuff into statements that actually make sense for users, or if the notes are only to satisfy regulators who understand all of this, or if they're purposely made to sound overly technical
FSD Beta's release notes are the only software updates I've seen where I have no clue what half the stuff even means for an end user, it's like they're written for the five people in the world who are experts in autonomous driving tech
Here is a decent translation. Worth watching.I can't tell if the release notes are a sign the technology is so new that nobody has an idea how to parse stuff into statements that actually make sense for users, or if the notes are only to satisfy regulators who understand all of this, or if they're purposely made to sound overly technical
FSD Beta's release notes are the only software updates I've seen where I have no clue what half the stuff even means for an end user, it's like they're written for the five people in the world who are experts in autonomous driving tech
For me it's almost entirely for turns involving cross traffic. On the other hand, if it's making an unprotected turn at a green light it can make (fairly) quick decisions about oncoming traffic.
It's soooo much slower for cross-traffic.