Taptic Engine not working

Definitely. It's just one of a number of things that work, then don't work, then work sometimes. I was getting no location updates yesterday. Today it's no taptic engine feedback (which you find is a really crucial thing with the watch--esp. with the sound turned off!). I guess I'll try restarting the watch again, but I'm afraid something else will go wrong....

Same with my watch. No haptic feedback. But after I turned off the the watch and made a reboot it works now.

Same here.

I have a BR filed on this. They requested taptic data along with continuity data so we will see what else they request after the engineers take a look. They know it's an issue with this build, and are looking into it.

it seems to fail during the time the watch is off wrist. If I reboot the watch right after putting it on taptic works again.

I fixed it on mine in the settings on the Watch this way:

The ALERT volume is affecting the HAPTIC engine in a weird way. There are 17 Alert volumes (0-16) and 3 Haptic strengths (0-2)

If ALERT=0 then HAPTIC=1 is deactivated (0 is too, but should be);

If ALERT=1 then HAPTIC=1 deactivates the Alert and Haptic;

if ALERT=2 then HAPTIC=0,2 deactivates the Alert and Haptic;

if ALERT=3 then HAPTIC =1 deactivates the Alert and Haptic; and so on, all the way to

if ALERT=16 then HAPTIC=0,2 deactivates the Alert and Haptic.

The only way to be certain is to tap the UP/DOWN toggles (don't use the digital crown because you won't beable, easily, to get the correct EVEN Alert volume setting to activate Haptic Level 1, or the correct ODD Alert volume to activate Haptic 2.

**Now i'm going to **** your mind**:

If you toogle HAPTIC to 1 and toggle ALERT to 0, and hit the DOWN again (essentially going to -1) then HAPTIC=1 WILL WORK (but not 2).. and come to find out, that it will auto revert bact to the initial outline as above. So you'll be like, "oh it works now" but then it doesn't

Thanks for this. I feared my (faint) Taptic Engine m had truly given up. I still think my watch has a fainter than expected behaviour since the first day or two of owning it - A friend has one and it died seems more prominent - but this latest issues could be part of the fun of having a Dev platform on my wrist ! Anyway, I'll see what it's like when the final version is like before sending it off for AppleCare.

Same here. Fixed after reboot.