Just completed my first OWS and here goes. Firstly let me acknowledge that I also had OWS issues with the F6 but not prior to the F6. In other words 910xt, F3 and F5 I had no issues with OWS, my issues started with the F6 and continue with the Epix. Also, I had GPS set to All bands plus multi, one sec recording and I wore the watch on my left hand. So, for my swim today the track looks ridiculous compared to what I actually swam, however the distance was fairly close. This is a swim along a parallel boardwalk and should have been around 1 mile. The Epix recorded 1925 yards which is 1.09 miles. All good there. But the track is no where near the actual track. I mean way off. Link below. After loading the GPX to a FIT decoder, the truth comes out. During a 40 min swim, the watch only had a GPS signal for the first 2 min or so. The rest of the approx 38 minutes, the decoder shows that there was no signal and the watch used a fixed distance per stroke algorithm and that's why the final distance is close to real. The real issue, or the root cause of these continuous errors comes down to NOT having good GPS signal and relying on approximation algorithms, etc. By comparison if I dig up GPX files from the F3 or F5 I can clearly see that GPS signal is available 99% of the time. This is the root cause of this issue, the newer GPS chips which consume much less power that started with the F6 and now Epix simply don't do as good of a job maintaining GPS signal in the OWS conditions. Results will vary based on used swim style but I swim a fairly standard freestyle and again, my swim style was a none issue in OWS for the 910xt, F3 and F5. Garmin, you may not be able to do much but I would be curious of the FR945 which has a plastic housing will behave better in OWS.
https://connect.garmin.com/modern/activity/8967810636
From the image below, I actually swam to the right much further than is shown (as far as the end of the parking lot) and back to where I started. This track is way off.
