Mit 8.05

0 views

Skip to first unread message

Debra Necochea

unread,

Aug 3, 2024, 5:56:40 PM8/3/24

to gorbolare

So the odd thing is, that instead of recording laps at 1.00 mile intervals it decided to do so at 8.05 mile intervals and I can't for the life of me understand why. I suppose it could be a bug related to the heart rate zone or alerts I set up, but it seems like a really weird thing to happen.

So I guess the next logical test will be to delete the custom heart zone and disable heart zone notifications and see if it goes back to 1.0 mile laps. Will try that in the next day or two. I hope it does because I only want the heart zone alerts to help me pace a time trial. After that I will want my 1.0 mile laps back to normal.

I'll look at that. I've always programmed the settings using Connect on the web and then syncing via my phone. I've not touched it on the Edge 25 itself. But I'll see if I can fix that setting directly on the device.

I still have 8.05 mile autolaps. As aweatherall has pointed out that 8.05 is the number of km in 5 miles, something is up here. The device is set to miles and autolap is set for 1 mile. I'm not really sure how to proceed here. Possibly backup, then delete config file and resync?

The other thing I might try is to mess about with the units. e.g. deliberately set it to km and change the autolap distance. Or just switch off autolap completely, do a ride, then turn it back on again and see if it clears up the issue? It's a puzzle, but clearly something has got corrupted or is a little bit buggy somewhere.

Part 4 and we have a solution. Not completely sure what put things right, but I re-enabled heart rate alerts, switched it to zone 1 away from custom heart zones, then disabled heart rate alerts again. I also fiddled with the settings directly on the Edge 25 changing to autolap OFF and then back on again.

Then this morning, riding to the gym I get my 1-mile beep back again. YAY. So, thankfully it is reversible by means of one or both of the above actions. As I said originally, I think it's a little bug in a little-used feature, which is probably why I couldn't find anything about it anywhere.

Can someone explain to me (b) below... Reading this seems to imply that with R1 an inside move to second could be performed even if R1 is not advancing or creating the intent to advance. So long as it is not deemed by the umpire to be intentionally delaying the game.

(b) With a runner on first base the pitcher may make a complete turn, without hesitating toward first, and throw to second. This is not to be interpreted as throwing to an unoccupied base.

What's confusing is the instruction not to interpret it as throwing to an unoccupied base, which is exactly what it is. It would have been better to say, "This [throw] to an unoccupied base is a permissible exception when it is a play on a runner."

Where does the rules state that this is assuming R1 is stealing. Not to be argumenative but, looking through the OBR it doesn't mention driving back the runner or the runner stealing anywhere in the comment or the sub points. It specifically mentions in 8.05(d) the pitcher can't throw to an unoccupied base except for the purpose of making a play.

But then this comment says if the pitcher makes a complete turn, without hesitating at first (inside move), and throws to second this is not throwing to an unoccupied base.... If the comment was assuming that R1 was stealing, then it would be unnecessary comment because that situation is covered by rule 8.05(d)

Without the comment, we'd have multiple conversations here about whether the outside / spin move to second was legal because, after all, the first move was around past first and so that has to be the same as "to or toward first", doesn't it and a move to first has to be followed by a throw to first or it's a balk.

The rules were not written by lawyers for lawyers, so they contain many apparent contradictions and many instances where the syntax could be improved. They have to be read together, and even so often require additional authoritative interpretation.

Update 8.05 of Valorant is starting to roll out and players will soon be able to play with the new agent, Clove. After spending a few days in the test servers, the patch is finally coming out and it brings more changes on top of the addition of a new playable character.