Instead of the fence kicking riders out there should be an option for event leaders to choose the impact hitting the fence has. Thinking specifically about the option for riders who hit the fence to be transported back to the yellow beacon our to the same time/distance gap behind the yellow beacon that the fence is set (IE if fence is at10sec then when you hit the fence you are transported 10sec behind yellow). Could also be that the nearer you get to the fence a larger handicap is applied so you have to work harder.
The second option might be easier to implement, as it would be like applying a gradient related to how close the rider is the fence. The other option would involve repositioning the rider during a ride, which would create some interesting distance calculation issues. Both might be hard, and probably more than the Zwift devs want to work on. In the grand scheme of things, though, if people want to kiss the fence, or ride behind it, they clearly don’t want to be in the group, so why not just boot them from the ride to do their own thing?
What about the option to make the fence solid so that no matter how much power a rider puts out they can’t go beyond it. A bit like rubberbanding?
Riding past the fence should trigger an un-mutable “Ride On!” every 3 seconds, for your ears only.
I guess the problem with messing with ride position and teleporting people around, or adding “anchors” to people is that it removes the link between effort and distance, and makes it difficult to take Zwift seriously in terms of Strava segments etc. I do think you’ve got to have a realistic mapping between input and distance travelled and not mess with this too much.
Maybe a different option would be simply a “three strikes” rule? Or a configurable “grace” period after hitting the fence? Or some combination of these?
The complaints I see from people is that they got zapped unfairly because they were on a descent (and presumably don’t know about the “brake” function, or can’t use it since not on a PC etc), which this solution could probably overcome?
The electric fence is fine - it should be possible to manage your power/speed enough to stay with the beacon.
I did my first ride with a fence yesterday, and it seemed to me to have a version of both these options. I accidentally hit the fence at the top of a climb, and it gave me a whole minute to get back behind it. I also got the impression from other riders that hitting it multiple times was not a problem as long as they got back behind it within the 60 seconds.
It should be, but because some people seem to take great pleasure in “winning” a group ride it definitely isn’t.
Correct David, my point was not to add these features, but to make them configruable - i.e. to say how long you had to get behind it (eg 30 seconds, or 5 minutes) and how many strikes you had before you were kicked (1, 5, unlimited etc).
Cool … is the only configurable option at the moment the distance then?
I’m far too much of a liability to ever be put in charge of a group event but as I understand it, yes:
The reason for raising the topic was that I have been on several rides over the Christmas period where there was some negativity thrown at the race leader, one ride in particular the yellow beacon was taking some abuse over the fence despite the fact they were riding at or close to advertised pace, and another where quite a lot of riders where kicked off when going downhill. Just got me thinking, given the human nature that seems to come with some Zwift riders (IE everything is a race), could this mentality be put to use to help the group as a whole, accepting that simply working at the front of the blob doesn’t seem to work. In my opinion the fence has helped but think it could be even more effective.
Supposedly fence function is now a configurable option in event setup, the organizer can choose between the original that removes flyers after 60 seconds in front of the fence and the gentler one that just keeps telling you to rejoin the group. During the event, the ride leader can just turn the fence on/off and select how many seconds ahead it will be from three options.