Wiki MASTER THREAD: Actual FSD Beta downloads and experiences

[Phlier]

To resolve an issue with my telescoping steering wheel that magically happened to occur right after Beta the other day...Service repushed the 5.2 update to my car

Did that actually fix the steering wheel issue, 'cause it kinda sounds like some gearing got stripped from the way you described what was happening.

Man... they can fix anything with software these days.

 

[AlanSubie4Life]

I sent some feedback to the beta team via email .. if anyone else feels the same way you might want to chime in too (the more people who say, the more likely Tesla are to change this). Basically my ask was "manual steering input should revert the car entirely to manual control".

A few of us have emailed the team with this request (it’s one of just 2-3 emails I have sent to them with specific issues/requests). While they added a some configurability in this release, they did not add that.

I suspect it has to do with how this would mean a change in behavior when in NOA and whether they want it to affect that (leaving the vehicle in TACC after steering disengagement seems to be something that Tesla is philosophically married to, and has been for years even though it kind of makes no sense and many would prefer that it not work that way). That probably has something to do with not wanting to inadvertently brake check people on the freeway (I still think it should be an option!). But surface streets seem totally different than the freeway scenario.

Anyway, people who want the option to disable TACC upon steering disengagement - certainly consider emailing them. It might work. Though probably not. They probably don’t much care what we want.

 

[valem]

Is it just me, or do others find the way you can disengage FSD to be troublesome?

Seems to me there are three ways to disengage:

1. Push the shifter up
2. Hit the brakes
3. Manual steering input

Mostly, this is just like NoA, so its consistent (which is good). However, what I dont like at all is that #3 (manual steering input) does not disengage basic TACC, so FSD stops controlling the car, but it continues plowing ahead. I can see that being logical for NoA on the freeway (where the car suddenly slowing down might be dangerous), but that's different from city streets.

When FSD goes wrong, it mostly for me is because the car goes in the wrong direction, and my reaction of to take control of steering to correct this .. but of course this leaves TACC enabled, which I find unexpected (and dangerous). My feeling is FSD is better off treating manual steering input as a complete return to manual driving (like hitting the brakes).

Send an email to the BETA team with your comment/suggestion.

 

[chrislayy]

Updated to 10.3.1 earlier this morning. Cannot engage FSD and the visualization keeps flickering. Sentry mode off, FCW off, but AEB enabled.

 

[hamoneaster]

Updated to 10.3.1 earlier this morning. Cannot engage FSD and the visualization keeps flickering. Sentry mode off, FCW off, but AEB enabled.

Oh lord?? Are you serious? They didn't fix it??

 

[Wnuk]

Does anyone else have an issue since 10.3 where you get an alert that the cabin camera in unavailable. This comes and goes for me since installing the beta yesterday.

 

[drtimhill]

Send an email to the BETA team with your comment/suggestion.

Already done

 

[drtimhill]

Anyway, people who want the option to disable TACC upon steering disengagement - certainly consider emailing them. It might work. Though probably not. They probably don’t much care what we want.

Possibly .. my take is that this should either by dependent on mode (NoA vs FSD) or, if that ceases to exist as they merge the two stacks, it should be speed based.

 

[chrislayy]

Oh lord?? Are you serious? They didn't fix it??

I used the fix for 10.3, which consisted of disabling AEB/FCW/Sentry, and it worked. Once I updated to 10.3.1, AEB was automatically re-enabled, but FSD is non-functional right now.

 

[cantchoosename]

I used the fix for 10.3, which consisted of disabling AEB/FCW/Sentry, and it worked. Once I updated to 10.3.1, AEB was automatically re-enabled, but FSD is non-functional right now.

Have you tried a reboot? (hold the two scroll buttons down on the string wheel)

 

[chrislayy]

Have you tried a reboot? (hold the two scroll buttons down on the string wheel)

Multiple reboots with various options of AEB, FCW, Sentry enabled/disabled. Still haven't found the right combo.

 

[nvx1977]

I used the fix for 10.3, which consisted of disabling AEB/FCW/Sentry, and it worked. Once I updated to 10.3.1, AEB was automatically re-enabled, but FSD is non-functional right now.

No issues for me. I was on 36.5.2 the whole time. Got 5.3 today. everything working fine.

 

[cantchoosename]

Multiple reboots with various options of AEB, FCW, Sentry enabled/disabled. Still haven't found the right combo.

This is probably a stretch, but have you let the car go to sleep. Maybe it's just tired and will be okay when it wakes up

 

[drtimhill]

Multiple reboots with various options of AEB, FCW, Sentry enabled/disabled. Still haven't found the right combo.

I got 2021.36.5.3 pushed to my car this morning, it seems to have fixed the issues people were seeing (so far).

 

[Iain]

I got the new fix and had a fantastic drive home (28 miles) I had cars to follow most of the way and apart from helping with a bit of acceleration, to not piss off people behind me, it was my best drive to date.

 

[EVNow]

I got the new fix and had a fantastic drive home (28 miles) I had cars to follow most of the way and apart from helping with a bit of acceleration, to not piss off people behind me, it was my best drive to date.

28 miles city ? I guess not ...

 

[Iain]

28 miles city ? I guess not ...

City/ highway. Nothing very complicated.

 

[Tindajii]

I downloaded and installed FSD beta 10.3.1 (2021.36.5.3).
Took an 8 mile drive, FSD beta active the whole time, no big issues. A few disengagements where I didn't want people around me to get frustrated while waiting for the car to decide to turn or navigate a tricky situation.

 

[mhan00]

Drove on 10.3.1 to my doctors appointment today in some light rain with traffic. 10.3.1 did very well. Pretty impressed.

 

[AlanSubie4Life]

if that ceases to exist as they merge the two stacks, it should be speed based.

I think this makes sense. Worth noting however that deceleration g force is a bit higher on surface streets than on the freeway, since it's power limited at higher speeds, so you can hit maximum power quite easily, with relatively little force, at freeway speed; F = P / v. So you slow more quickly on surface streets at lower speeds (obviously Tesla puts a substantial limit on power (probably once a certain deceleration (force) is reached they cap it) at low speed, otherwise the stops would be very abrupt, haha) which I guess could end up with people hitting you?

Intuitively though, I still think it makes sense for it to be speed based (continue in TACC above a certain speed, disengage entirely below a certain speed).

I think the other argument against this would be mode confusion. It's probably better for it to be one way or the other. Requires an automation expert to deem what is safest I guess.

I definitely want it to be configurable though (and I would set it to completely disengage in all cases whenever I intervene with steering)!