Does FSD understand construction zones?

Running HW4 Model Y and HW3 Model S side by side, HW3 went through the cones again and on one run HW4 followed the Model S through after previously stopping.

With cones across the whole street at about 60 mph, HW3 showed cones on screen but did not brake and smoked through them.

In a 'garbage cannon' test, FSD avoided a popping ball and small box but again largely ignored the cone and ran it over—the main object Chris felt FSD wanted to ignore.

With a static traffic cone in the middle of the road, FSD slowed and tried to get around but then ran the cone over rather than stop or move farther off the road, despite the front bumper camera.

Cybertruck tried to drive into a construction zone, prompting a takeover the creator later classifies as a safety disengagement.

He calls a big disengagement after FSD fails around a stop/construction situation near people and train tracks; he reports it and later takes over for a really bad job.

After a yellow light the car seemed to want to move through and ignore the red light until Autopilot was strangely re-engaged/stopped far back; sun was on the signal.

With cones and a construction situation, the planned path went the wrong way toward the blocked area; Chris would not re-enable FSD and had to manually back up and clear the scene.

Entering heavy construction, Autopilot warns him to take over, does not try to avoid cones, and ends up on the wrong side of the road; he re-enables it once there are clearer lines.

In a cone test, FSD 14 Lite kept reversing toward the cone while a HW4 vehicle in the same scenario refused to budge.

He describes recurring highway slowdowns where green arrows/red X overhead lane indicators are treated like traffic lights and cause unwanted braking.

FSD heads into a construction/closed area that looks like it will trap the car; creator disengages and uses Park then re-enable to get out without manually driving.

After succeeding twice before on version 12, this time FSD tried to drive into the wrong area past barrels, forcing a backup disengagement.

After right-then-left on a narrow road, FSD becomes totally stuck with a car behind; narrator takes over and backs up; one disengagement for getting stuck in the middle of the road.

Explicit disengagement when left is blocked, a guy is reversing, and the area is all blocked off; driver turns around and later lets the car go straight.

He takes over again because FSD is going real slow after someone waves him along; he pushes then takes over, calling it a really awkward construction situation.

On a tight construction stretch the car stopped and would not turn through; with nobody behind, the driver pushed and then fully disengaged to clear the area before traffic arrived.

At a closed road with detour signs after a roundabout, beta waited correctly for roundabout traffic then would not follow the detour and stopped, so Chris took over and did the detour himself.

Approaches closed road, cannot go around or detour from the sign, gets stuck so Chris takes over; only counted FSD disengagement of the day.

Near a huge open hole/trench and coned closed lane, the car keeps wanting to stop and tries to go into the closed lane; creator holds the wheel and counts another disengagement.

Saw another closed road and took over again amid heavy construction and many disengagements.

Nav suddenly wanted a left toward a previously closed road while tentacles showed straight; he disengaged/took over rather than let it go past the road-closed opening.

At a busy pedestrian crossing with construction nearby the car is extremely timid; driver reports several interventions and a disengagement so far on 10.69.2.

Car tried to move into a lane/area that was blocked by cones; after being let over it got too close to cones and the creator took over and reported it.

After canceling the route near construction so the car can go straight, the car stays confused on its planned left; creator takes over.

Approaching a left then realizing the needed right turn, the car waited for a cone but missed the turn it had missed before; he started to take over then it rerouted.

With a road closed ahead the car wanted to go straight then signaled left onto a one-way street; Chris reported and disengaged because it did not handle the closed road correctly.

Creator took over when the intended path appeared closed off by workers/cones.

Takes over and turns left at a detour because he knows FSD will handle the detour wrong.

With people around and cones visible on the display, he gives up after more wrong-path behavior through the construction area.

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.

Another driver fully ran a stop sign near construction workers while FSD was stopped at the stop sign.

On the rainy highway, FSD locked speed profiles to chill and misread a 45 mph workers-present limit with no workers, holding about 47 mph in a 60 mph zone, so he pressed the accelerator.

Approaching a signal with backup/construction-related congestion, he tapped again because it was 'too scared' to get up into position; it then moved on the green, and he admits the tap may have been unnecessary.

FSD incorrectly stops as if train-track lights were traffic lights amid construction and a flagger; Chris presses the accelerator as an intervention and notes they briefly go the wrong way on the road while FSD recovers.

FSD made a left turn from a straight-only lane (not a turning lane); he reported it and partly blamed his own late route change, noting the same mistake has happened without nav changes.

Creator initiated a lane change to get away from roadside objects/vehicles after FSD only partially moved over; he said this put them at about four interventions.

Driver took over and set a new destination to force a left through a tougher cone/construction path for testing.

He took over again to put the car through construction (not the car's fault), then re-enabled FSD.

He turned right off the planned path to reach bus-stop lanes he wanted to retest; he notes this was not a system-fault disengagement.

Car went right into construction and got stuck; Chris pressed the accelerator near a barrel, then released, and the car proceeded on its own.

He accidentally takes over for a second as the car moves toward a box truck even though on-screen planning showed it would correct; after re-enable it goes straight through correctly.

While trying to enter a left-turn lane among cones the pathing was very bad and goofy through the construction layout.

In heavy construction he had to hit the turn signal himself because the car was not moving over and counted it as an intervention.

Near construction workers the car was hesitant so he intervened rather than let it drive toward them.

With lefts blocked by barriers and trucks, FSD kept left in nav briefly, then took an available left and successfully rerouted.

In Mad Max, FSD slowed preemptively for a road work crew even though they were not on its side of the road.

In Hurry, car correctly slowed from 80 in a 70 to 70 (10 over) in a construction zone and sped up again after, fixing prior 14.1 bug.