How does FSD handle heavy rain?

Prompt says use accelerator or gear stalk to continue while the car thinks the light is green but it is red; he refuses to confirm and reports it.

Example robotaxi crash was a bus crashing into a stationary robotaxi.

A pickup/truck merged into the lane and the car reacted late with a hard brake; shortly after, Navigate on Autopilot re-enabled as rain/wipers eased.

He took over to park so he could retrieve cameras, ending the FSD drive.

On the highway in heavy rain, a red take-over-immediately warning appeared and the car slowed rapidly without recovering, so he had to take over.

On the way over, a sudden rain burst at about 80 mph caused red hands; FSD began slowing and he took over after waiting a few seconds, then re-enabled with no further mistakes.

Creator takes over to force a harder right instead of an easy straight; he states this does not count as a disengagement for scoring.

FSD tried to go around a vehicle parallel parking while another road user was in the way; driver took over, arguing you should wait rather than cross the double yellow in dense downtown traffic.

At a signed no-turn-on-red intersection, FSD was about to go while the light was still red; driver disengaged and waited for green (regression after ~1.5–2 years of working no-turn-on-red).

Driver braked and counted a disengagement after FSD was super assertive waiting on a truck/gap; a follow-on aggressive move felt too close, though the light later turned red and the car may have been right to proceed.

Omar reported highway V12 in very heavy rain was not impressive: speed limited to 60 mph and repeated red-hands takeovers saying the car was not able to drive.

At the final busy intersection the car needed to nudge through, started then hesitated again under honking and pedestrians; Chris pushed it through and it wanted to go straight, becoming a full disengagement.

Food truck blocked the lane so the car entered a left-turn lane to go around, then kept turning left per NHTSA-style left-lane rules and looping; Chris took over after multiple cycles.

After waiting for a pedestrian, the car tried to drive into a closed lane with traffic barrels, mistaking construction for moving traffic, and Chris stopped it.

At a backed-up four-way stop beta was very slow, got confused with other drivers, got too close, and he took over in a substantial disengagement.

Driver takes over when the car tries to go around a vehicle waiting in the left-turn queue, thinking it is parked; also reports it.

He accidentally disengages and says it was a total accident, not an intentional intervention.

After frantic wipers and a spray, system showed poor weather / Autosteer unavailable and would not re-enable FSD until after parking briefly.

After a too-hesitant move, he reacts to a really bad unexpected action and notes it as a bad disengagement requiring hands on the wheel.

Autopilot says take over immediately; he takes over because the system is confused in intense rain.

Even after snow eased, wetness covered the cameras so FSD could not be enabled and he had to drive manually into the final charger.

He says the only disappointment with the Tesla was on the way to New York when Autopilot kept giving up in the rain.

In heavy rain Autopilot repeatedly shows a big red take-over warning and seems to keep driving until he wiggles the wheel, which turns it off; he links it to water spray especially near semis.

A hanging truck-related object swung near the path; FSD waited, nearly had a close pass, then did not go when a person waved and later stood in front of the car.

FSD barely clips a large pothole edge and rides a bit of curb; creator hits the report button but does not count it among the two interventions.

Crept hard on a no-turn-on-red; Chris thought it might turn on red but it only went after the light turned green.

Passed a parked car so closely that the proximity alarm triggered; Chris called it too close though it made it through.

Chris dropped a pin on the map to force a specific parking spot after the wrong-store nav path.

With the barn selected, FSD entered a wrong office parking lot, parked smoothly there instead of the destination, then kept picking spots in that lot until the driver reselected/pin-routed.

FSD navigated into a police-station lot and appeared headed toward restricted parking; driver took over to avoid parking in a police-vehicles-only area.

On a 35 mph road FSD stayed more than 10 over; Chill did not slow it, so driver switched to Sloth which finally reduced speed.

Driver took over to force a right turn FSD was not taking; FSD had been driving fine and re-engaged instantly mid-maneuver.

Before a tight alley FSD thinks something is in the way (red phantom object); creator taps the accelerator again to proceed.

In a tiny janky parking lot FSD shows 'Object and path detected. Take over to proceed'; creator taps the accelerator once to continue.

Driver took over because navigation had been changed after the fact and the car was not set to go the intended straight path.

On the v10 branch in rain, Chris’s car tried to dodge barrels that were only reflections on a wet road at an intersection; Tesla later noted improved wet-road reflection handling in release notes.

At a roundabout it slows too much and feels timid with an approaching car; he takes over and redoes the roundabout to check it was not a fluke.

At a four-way stop on its turn it stops in the intersection, so he pushes it through; he notes possible rain influence.

He taps/pushes through because the car stops at the prior destination until it figures out a new route.

He presses the accelerator because the car was going to stop at the set destination; he says it was his fault for not editing the trip.

Driver says he was surprised it stopped at a kind of diverged right turn and had to press the accelerator.

After flying into another roundabout, the car brakes inside it; driver presses the accelerator to prevent that.

At the first of a difficult triple roundabout, the car is hesitant and goofy with messy lane changes; driver pushes the accelerator to get through.

On the way home FSD hit the brakes hard with nothing nearby, producing rotor squeak; another instance of unexplained rain-related hard braking.

FSD stops far back for a child and only gently accelerates once clear.

Final yield/turn scenario handled perfectly after earlier assertiveness concerns at another intersection.

On a tough final left with endless pedestrians and cars taking their turn, FSD waited then asserted through; Chris called it sick and great with zero intervention.

Pedestrian alarm triggered for someone on the sidewalk without any speed change from FSD; Chris found the alarm disconnected from driving behavior.