Home Blog Page 499

Castelli Ride Series Skillz and Drillz, January 11

0

Castelli Ride Series Skillz and Drillz, January 11

Another big group this week, as we jumped back into the subject of working efficiently as a group.  Today’s focus was how to efficiently chase down a small break, expending as little energy as possible.

We were able to show that with just a little extra effort and a lot of control, the big group could easily bring back a rider who had a 30-second advantage.  Some punishments were doled out when the group violated the parameters of the drills, but we’ll get to that later.

Here’s a replay of the ride:

First, like usual we got in a good warm-up while practicing to work in a group.  I cannot stress how important of a skill this is, which is why we start with it every week.  The ability to “feel” where you are in the group is really about controlling your position to be able to respond to changes within the dynamics of the group.  When working with teammates in a group, the ability to maintain your position can allow you to control the pace and the tactics of the race.  If you are unsure of what I mean regarding positioning, I encourage you to take a look at the video of the Magnus Monday race from 16 January.  TeamODZ had numbers in the break and set about to control the front of the race.  Because of the numerical advantage, TeamODZ  members were able to move to the front to control the pace and chase any rider attempting to escape, and others were able to drift to the back, following wheels to recover.  This sharing of the workload allowed the team leader to spend the first two-thirds of the race as protected as possible, saving precious energy to win the race on a sprint finish.

After the warm-up, we immediately got down to business.  Like I said at the beginning, today was about controlled chasing of a small break.  By small, I mean I sent one rider up the road.  The ever faithful Chris V. went up the road on a moderate-hard attack for 90 seconds then dropped back to a steady 2.0 for the chase.  I put a ceiling of 3.0 on the group, and we began working together to bring Chris back.  Those who were able to do so took turns working the front of the group to maintain the pace, and those who couldn’t stayed in the draft. Keeping the pace steady meant a much smoother ride with fewer significant changes of pace.  This allowed many of the riders with lower FTPs to be able to stay with the group, even at efforts greater than the riders could normally sustain on their own.

On iteration number two, the front of the group had a little more trouble controlling the output, so we had to put some punishment out there when the group exceeded the maximums for more than a few seconds.   During the third run, the attacker went off the front and settled in, just as during previous iterations.  However, every time the group violated the ceilings, I had the attacker launch a 15-second full-out attack.  By the third attack, the will to violate the w/kg ceiling had gone out of the bunch.  We chased down the attack in no time with a nice steady effort, largely keeping the group intact.

After a few more iterations, I moved to the front to play the surging game.  In the surging game, all riders had to stay behind me and try to stay on my wheel.  Meanwhile, I set about moving the pace from 2.0-3.0 w/kg in a completely random manner.  Any rider who passed me had to stop pedaling, go to the back, and work their way back up to my wheel.  Most riders found that period of time fluctuating back and forth to be much more difficult than the harder, steady efforts that we had been doing.  This drill was simply to show everyone that keeping things steady is a much more efficient way to operate.

We closed off the ride with a couple short sprints, just so everyone could say that they got a decent workout.  As we went through our cool down, we conducted a brief wrap-up of the evening’s lesson.  First, hard but steady is way easier than constant surging over your limits in the long run.  By maintaining a steady tempo, riders have more opportunity to share the workload.  If the riders at the front are constantly jacking up the pace, there is little incentive for others to contribute to the chase.  If only 3 riders are willing to do the work, it doesn’t matter if the chase pack is 3 or 50.  It will still only have the strength of the 3 riders putting in the work.  On the contrary, a steady pace will likely invite contributions from other riders, even it is not tactically smart to do so.  The desire of most riders to stay near the front will inherently create space for the mistake of overshooting the leader now and again, meaning that there will be some contribution to pace setting.

Remember the theme that we have been hammering for the last few weeks.  Riding smarter will give you many more opportunities to finish with the group or even compete for the win.  Being efficient is a key component to being a smart rider.  Keep practicing these skills when riding in groups or races, and until next time, Ride On!


GCN takes over KISS Europe Night Race tomorrow

0

GCN takes over KISS Europe Night Race tomorrow

GCN’s Si Richardson, an ex-pro rider

Tomorrow’s KISS Europe Night Race will be a special one, with live commentary from the guys at GCN and GCN’s own Si Richardson joining the race. Come battle Si and hundreds of other racers over a lap of Watopia’s Figure 8 route!

The live broadcast will be available on GCN’s YouTube channel and will include the new “ZwiftOnBoard” feature which lets us see live streaming video of Zwift racers before, during, and after the race.

It all happens at 8PM UTC Tuesday the 17th. Don’t miss it!

Learn more on the Zwift event calendar >

About GCN

The Global Cycling Network delivers action, analysis and unparalleled access every week, every month, and every year. Their videos show you how to be a better cyclist with maintenance lessons, tips for improving your cycling, cycling top tens, and of course the weekly GCN Show. With nearly 1 million followers they are YouTube’s biggest and best cycling channel… and they’re hilarious as well!

 


Zwift coming to Apple TV

0

Zwift coming to Apple TV

UPDATE 3/28/17: Yesterday ZwiftHQ put out the call for Apple TV beta testers. Read more here >


We’ve heard talk of Zwift coming to Apple TV for several months now, but the major barrier was Apple limiting the app bundle size to 200MB, forcing Zwift’s programmers to break the app into different pieces before it could run on Apple TV.

Last Thursday (January 12) Apple announced they have increased the app size limit from 200MB to 4GB. While this wasn’t major news in Apple’s world, this move eliminates the main barrier ZwiftHQ was facing in bringing Zwift to Apple TV, so it has certainly moved Zwift’s tvOS launch date up significantly.

Quoting Game Master Jon Mayfield:

… tvOS lets you have huge applications, however the .app file could only be 200MB before. That meant you had to chop things up into pieces and manage these pieces coming down. It was going to be the same MB as iOS, just a lot more hassle to deal with.

Now that hassle is gone.

ZwiftHQ has already showcased Zwift on Apple TV publicly, but there is still some work to be done on the interface before it can launch.

What’s the Big Deal?

With the 32GB Apple TV available for $149US, this puts Zwift within reach of even more users.

Zwift running on Apple TV is important because Apple TV is the lowest-price new device which can run Zwift. Yes, you can find used computers or iDevices more cheaply, but there are no new systems in this price range which can run Zwift at a decent level of quality apart from Apple TV.

#RideOn!


Zwift Europe Tour: (nearly) Midnight in Paris

0

Zwift Europe Tour: (nearly) Midnight in Paris

“Be stronger than your excuses” setup at the Km0.

January 12th, the Zwift & Tacx European Tour makes its last stop in Paris, at the Km0 bikeshop. For the casual passer-by, this building is like any other. For the Zwifter though, it’s the place where magic happens. The moment you pass the front porch, you get transported in another dimension where London is seconds away from Paris, and where the entire world awaits to ride with you. Let’s take a quick “tour” of the place, shall we ?

Before anyone arrives, the place has to be set up. The whole crew, speakers included, gets the job done. Murals, decor, loudspeakers… and of course, the bikes. Here in Paris, it’s 3 Tacx Neo side by side, each with a computer running Zwift in front of them, for the Sprint Challenge. On the other side, the Tacx Flux, to test the VR. In the middle is a screen is ready to receive the sprint challenge’s results.

7 minutes in cyclist’s paradise

picture : L.Van Bon ©

Then, the time comes. Speakers review the how-to’s as the crowd arrives. Since the London Course is on, it’s a sprint challenge that the public will take on. It’s hard to describe the ambiance with words, but we’ll try: the crowd roars as the riders sprint side by side under the never-ending “UP UP UP” of the speaker, the dehydrated sprinters and followers make the beer flow in the next room (the water too, french people are not raging alcoholics… or they hide it well), each sprint begins with the sound of the gun as the speaker channeling Freddie Mercury on the microphone screaming the traditional “3…2…1…GO !”

It’s the classic you-against-you battle, the 200-meter sprint on the red road of the Mall, with the crowd cheering right next to you and the expert camera of Leon Van Bon to capture the moment. In a word, it’s the place to be!

Zwift dreams (are made of this)

On the other side of the room, visitors try on the Zwift VR. It can be said, without a bit of hyperbole, that this might be the most amazing thing ever. When you put on the helmet, equipped with 3D glasses and headphones, you’re transported in the world of Zwift. Your head can’t stop spinning to watch every detail of the virtual roads we know so well.

Picture it: it’s raining outside, you get in your cave (or living room, wherever), you put on the VR helmet. Then in a second, you’re in Watopia, alongside the beach. You ride through the water tunnel, you take a left… and you go all the way to the tower. Once there, you stop, and watch the sun rise over Watopia. It took you less than an hour from your cave, and you’re (almost) literally sitting on top of the world.

This said (and some dreams might be broken right here): this VR helmet is not likely to be made public, as a big part of it is made of foam, which doesn’t react well to sweat, and it would become unbearable pretty fast. But nonetheless, great stuff!

Several people wearing orange shirts ride stationary bikes indoors, facing large screens, while another person in an orange shirt stands nearby watching. The setting appears to be a cycling event or competition.

Now, you’ve done the challenge, you’ve experienced the VR, you’ve had some drinks with fellow riders… how do you improve on a night like this? Answer: you can’t. But you can attend the next one! USA, Canada, England, Scandinavia, Benelux, France… Zwift Tour‘s events go all around and only get better with time. So next time you see one in your area, don’t hesitate: you have to be there !

-the q/l Report-

Special thanks to the Zwift Tour crew, Dan, Jesper, Leon, Tom and Bohdan, for letting me in on this.


Interview with Frank Garcia of Cycligent Virtual Rankings

0

Interview with Frank Garcia of Cycligent Virtual Rankings

Yesterday I posted about the launch of Cycligent Virtual Rankings (CVR) at ZwiftRankings.com. Read that post for details, but to summarize, CVR is a powerful tool which can be used to rank and categorize Zwift Racers.

As a followup I’ve interviewed Frank Garcia, the man who led the charge in CVR’s development. He is a longtime elite Zwift racer and the CEO of Cycligent, and I wanted to get a better feel for how this project began, who worked on it, and where Frank would like to see it go.


Frank, I know this project was your “baby.” But I’m sure many more people were involved in many ways. Can you tell me who they are and what they did?

Lots of people involved and I have not event listed everybody!

  • James Gill (Team X) – was responsible for marketing.  He was responsible for messaging and provided the logos and handled social media.
  • Sharon Hackathorn (Cycligent Management) was responsible for coordinating the entire effort.
  • Carolyn Sulivan (Cycligent Management) was responsible for support (via Cycligent help desk) which was designed to support racers across the globe (8 help desk people where trained with a target of having 4 available most of the time).
  • Tyler Church (Cycligent Software Architecture) was responsible for continuous integration processes, infrastructure tuning, load testing. He also pitched in on coding when things got a bit tight as well.
  • James Hodges (ZwiftPower) for making tweaks to support our effort.
  • Mark McIntosh, Christian Wiedmann,  and Casey Schumm (all Team X) have been handling community outreach (talking with organizers, etc) and also responding to items on Facebook.
  • Team X. The whole team bounced around ideas, argued, came up with enhancements, reviewed prototypes and documentation, commented, etc.  It is amazing the amount of time and dedication the team had to the project.  Special mentions to Neil Law, Kim Little, Francois Coppex and Daniel Schmidheiny.

There are so many within the Cycligent organization that have done so much. The have been amazingly supportive.  I owe a debt of gratitude to them all.

Tell me about the genesis of this project. What inspired you to begin, and how long ago was that?

I get joy out of racing and want more people to enjoy it as well.  I wanted people to appreciate the importance of race craft (drafting, tactics, attacks, chases, etc) on their performance versus just raw watts.

After a bit I thought the best way to approach this was a ranking system to help illustrate the importance of race craft and that would also allow people to feel a sense of accomplishment, not just by making a podium, but by improving relative to other people with similar performance levels. I also wanted to create a system that would inspire continuous improvement versus, “Oh wow I don’t want to be promoted to the next category where I will get trashed.”

As for how long ago, the ideas around what this might look like started to formulate six to nine months ago. It became a serious effort the week before Thanksgiving in the US (middle to end of November).

I know the decision is up to specific race organizers, but do you know if there are specific races which will be using the new divisions in the near future?

It is up to the race organizers but we have talked with some that are looking into it.  I don’t want to put anyone on the spot so I won’t call out any by name.  I can say, however, I was surprised by the level of interest so I think it may be coming to some races soon.

How did your team come up with the overall points/divisions/ranking system–is it based on something which already exists, or are you all just geniuses? Or both?

Many of the concepts come from motor racing.  iRacing (online motor racing simulation) follows the same concepts.  We know it works and works well (100,000s of people on iRacing for instance).  We wanted a flexible system that would allow for racing times across the globe and for people of varying ability racing together.  The concepts had to be adapted to the physical nature of cycling.  You can’t really race 10 times a day on a bike (well not well anyway).

What would you like to see this project accomplish? Or to put it another way: if we were to fast-forward one year, and this project has “succeeded” by your definition–what would that look like?

Success would be:

  • acceptance by the community and
  • more enjoyment and more participation in racing on Zwift and
  • people seeing there is more to racing success and enjoyment than just being a watt monster.

Are there other features coming soon which you can share with us?

We hope to introduce features for non-racers (challenges – distance, climbing, etc) to have some fun with rankings.

What can the Zwift community do to help support this project?

The community can help us by providing feedback on how we can make it better and then being patient with us as we tweak things according to that feedback.  Rankings may shift and we are most concerned about people accepting that so we ask that they be tolerant of that while we are in beta.

If any Zwifters find CVR bugs or have questions or suggestions, who should they contact and how?

There is a questions or contact us tab on the site (may not appear on mobile currently we are looking into that).  We are also in the process of setting up a forum.

Who is Cycligent and what do you do?

Cycligent sponsors Team X and that is how it came be involved in Zwift and rankings. Cycligent is a framework, tool and cloud company dedicated to making web application development easier. We provide a visual, graphical Git dashboard for instance that allows you to push projects to the Cycligent cloud. Once there Cycligent Cloud runs your application with messaging, competing consumers, redundancy, etc, even though you did not code for those items. The rankings site is built completely on this platform (which by the way runs on top of AWS).

Is there anything else you’d like me to mention?

Two out of the three biggest things you already mentioned in yesterday’s post.  That is this is built on some outstanding work by the pioneers and that we don’t intend this as a replacement for any existing system we are aware of (i.e. we intend to continue to work closely with ZwiftPower and the community).

The other thing is that for a period of time the rankings will shift, not due to just race performance, but as we make tweaks based on community feedback.  This might be unsettling and we ask people to be tolerant as we improve the system.


ZwiftRankings.com (Cycligent Virtual Rankings) beta launch

0
Yesterday a new service was launched which we predict will change the face of Zwift racing. Available at zwiftrankings.com, the Cycligent Virtual Rankings (CVR) is a new way of ranking Zwift Racers.  Its creators have been very careful to explain that CVR “is not intended to supplant or replace any existing system.” It is simply a different way to rank and categorize racers on Zwift (or any other platform, for that matter.) The system is still being developed, but is already very powerful and functional. It is clear that much thought and many, many hours have obviously gone into its development, and for that its creators should be commended. It builds on the incredible work of James Hodges (ZwiftPower.com), Jonathan Lemon (zLogger), Glen Knight (KISS races and more) and Christian Wiedmann (ZTR races and more), using the existing community-developed race results tracking infrastructure which is most commonly accessed through  ZwiftPower.com.

Why Is It Needed?

There is much debate in the Zwift racing community about how to best rank and categorize racers. Currently most races group participants by FTP watts/kilogram using these scheme: Category A: 4.0 W/kg FTP or higher Category B: 3.2 W/kg to 3.99 W/kg FTP Category C: 2.5 W/kg to 3.19 W/kg FTP Category D: Under 2.49 W/kg FTP While this categorization scheme works decently well, it has several problems, including:
  • Lighter racers may be at a disadvantage on flat courses where pure wattage is a larger factor than w/kg (see Why am I getting beat by people with lower w/kg?)
  • New racers are often unsure how to categorize themselves, leading to races where rookies get quickly dropped or blow away the field
  • Racers can “game the system” in a variety of ways, including keeping their wattage just low enough (or weight high enough!) to stay in a particular category instead of moving up
The CVR system has the potential to eliminate these and other shortcomings of the current FTP-based categorization system.

How Does It Work?

Here is a quick summary, but we recommend you visit zwiftrankings.com, enter your name, and browse your dashboard. Then if you want to learn more, read the Overview to fully understand the system.

Points/Rankings 

The points system is clearly and completely explained on the Overview. It is not a simple system, but no accurate ranking system would be, given the many factors which must be included to achieve a high level of accuracy. The results, though, are quite simple–and that is the important part. You don’t have to understand the number crunching as long as the rankings produced are good!

Divisions

Racers are grouped into divisions based solely on race performance. The divisions are as follows:
  • Pro
  • Elite
  • Divisions 1-9
  • Rookie
There are separate division rankings for different race types, which currently include:
  • Flat & Climbing
  • Flat
  • Climbing
  • TT
  • Team TT
So while you may be a Division 4 flat racer, you could be a Divison 2 climber. This will allow for more competitive groupings across different race types. Racers begin as rookies, then are automatically placed in the correct division once they have enough enough races of a particular type under their belt. The number of racers in each division is held to a certain percentage of the overall number of racers, and each month racers are redistributed across divisions.

Who Is Behind It?

Frank Garcia, longtime Zwifter, CEO of Cycligent, member of Team Experimental and author of the #RideOn Philosophy is the main force behind the new system. Many others were involved in its development. We will be featuring an interview with Frank soon.

What’s Next?

Our prediction is that we will begin to see Zwift races using the CVR divisions soon, but this decision is up to the organizer(s) of each race.  
Zwift Insider editor Eric Schlange’s CVR dashboard

How to: make Strava show your Zwift runs as a run

2

How to: make Strava show your Zwift runs as a run

Editor’s note: this post is outdated. Runs on Zwift are now saved to Strava properly as a “Virtual Run.”


Runs on Zwift (you did know Zwift running is a thing, right?) currently upload to Strava as Virtual Bike Rides. This obviously isn’t ideal, since athletes want to track runs separately from rides, and you don’t want your running times used for riding segments, etc.

Strava and ZwiftHQ are working to fix this problem, but for now here’s a quick video showing how to force your Zwift runs to show up as runs in Strava:

The steps are as follows:

  • Download your Zwift activity file (from your zwift.com account or anywhere else it’s saved)
  • Upload it to Garmin Connect, where it will be classified as a treadmill run
  • Download the file from Garmin Connect as a .gpx
  • Upload that .gpx to Strava, where it will be classified as a run.

One interesting result of this is that your Zwift run times will be ranked on the Strava leaderboard against real-world segments. This won’t be the case forever, though, as it appears that Strava is having ZwiftHQ “offset” the GPS coordinates of Zwift runs so they don’t line up with real-world roads in Richmond and London.

But until then, have fun!


Rickrolled in Richmond

0

Rickrolled in Richmond

It’s official, folks. Zwifters have been rickrolled, Strava-style.

If you’ve ridden Richmond in the past few weeks you may have noticed the segments, which run the entire Richmond 2015 UCI Course and whose titles comprise the full chorus of Rick Astley’s iconic 1987 hit single, “Never Gonna Give You Up.”

In fact, just this morning I PR’d “Never gonna tell a lie and hurt you.”

Here’s the full list:

I’m not a big fan of all the crazy Strava segments people create for Zwift routes, but these, I’ve got to say, are pure gold. Nicely done.


Castelli Ride Series Skillz and Drillz, January 4

Castelli Ride Series Skillz and Drillz, January 4

Welcome to 2017 and a new edition of the Castelli SkillZ and DrillZ Ride. We had a good-sized group of about 75 riders, and today was different for a whole lot of reasons. First, I am still in Santiago, Chile, visiting family, so I do not have my bicycle, Wahoo Kickr, or normal computer setup. That was challenge number one.  Second, we introduced a different form of the ride today, one that did not necessarily have us riding together as a group after our warm-up period.  In the end, we pushed through the obstacles and got a good ride in to start the new year.

As I stated earlier, I have been out of town, so this SDR was an exercise in improvisation. I put my Stryd power meter on my shoe and connected it to my iPad as a power meter, which worked well enough to get me out of the pen with the group.  Typing while jogging back and forth on my mother-in-law’s patio was a bit difficult, so I had to drop from the group to make sure the instructions got out.  All in all, it seemed to have worked out just fine, and it served as a good test for a SDR later in the month when I have to travel for work.

Ok, enough discussion about my connection isssues and work-arounds.  On to the class!  Like normal, we got out of the gate at a 1.5 w/kg pace. Due to some last minute changes, I did not have a beacon over my avatar, and that made for some difficulty in keeping the group together and not hammering. Some of our newer riders did not understand that SDR is not a race, but with the help of a few regulars, we were able to keep the group more or less intact. After a few minutes of warm-up and working in the draft, we got down to business.

Today was all about pacing and efficiency.  Now, I don’t mean pacing from a standpoint of holding the same effort for a long time, as is commonly thought for triathletes.  In this case, I wanted riders to take a look at how well they were able to pick a target effort and stay within 10-15 Watts of that effort over a two-minute period.  Often times, I see riders take off, whether it be for a bridge, an attack, or merely a hard interval, only to see a quick spike in power followed by a continuous reduction in power over time.  Sure, the initial surge may open or close a gap to some degree, but the resulting decline in power means that the gap never fully closes, or the escape never comes to fruition.  We approached the problem by picking efforts well below threshold effort and attempting to keep a very small range of deviation.  Let me tell you, it is not easy to do!  At threshold, every small change is noticed because the change in effort is perceived as exponentially harder or easier.

To help focus the efforts, we added a small change as we moved up in power output.  At first, I directed riders to chose one of their legs and put special emphasis on that leg to ensure that it moved through the pedal stroke smoothly with consistent power applied to the pedal.  After that two-minute interval, we changed legs and repeated the drill.  Continuing the focus on a smooth stroke, we did a third iteration at the same power before moving up in intensity.  During the third iteration, I asked riders to drop the cadence into the high 70s to remove bouncing and jerkiness from the stroke.

As we continued, the intensity moved up and the interval time increased.  All the while I continued to push the riders to focus on being smooth.  Many of the riders commented that putting the emphasis on the pedal stroke made the effort seem more difficult but actually made it easier to maintain a constant power output.  I tried to explain that the task of keeping the stroke smooth can be a mentally arduous one, but the efficiency meant less wasted energy, which led to the ability to hold harder efforts for longer periods of time.  The smoother pedal stroke helps with maintaining a consistent power output, which, in turn, means fewer surges in power. Fewer surges in power mean more matches remaining for late attacks or that finish line sprint.

During our longest interval of five minutes at threshhold power, the vast majority of the group was able to hold the effort in the designated range.  I am not going to say that it was easy, and I am not advocating that anyone focus on pedal stroke during a race. However, like any other technique-focused drill, regular practice will help with pedal efficiency. Think of it as a little bit of pedaling meditation during your warm-up. Just keep in mind that every time you surge past threshhold power, you are burning a match. Smoothing out that power profile is one way to save that little extra bit of energy for when you need it most.

That’s it from the Castelli SkillZ and DrillZ Ride for the week. I want to thank Castelli for sponsoring the ride and providing some swag to one lucky rider who completed the event. I will be back on the bike for the next session, so  the beloved beacon will be back over my head. Ride on!


How To: start running on Zwift iOS today!

0

How To: start running on Zwift iOS today!

Zwift’s iOS release includes an “Easter egg” (hidden feature) granting access to Zwift’s running mode which is still in pre-beta testing phase. With a Zwift Runners group forming on Facebook and runners seen on course regularly, our guess is Zwift running will be officially released within the next few months.

Getting Started

Want to start running on Zwift? All you need is Zwift on iOS and a sensor which outputs running pace. (Of course, a treadmill is also a good idea, although I tested it with an outdoor run and it worked fine there as long as you’re willing to leave Zwift open on your phone.)

Pace Sensors

I have tested Zwift running using Stryd and Milestone footpods and both work fine (reviews coming soon). Any Bluetooth foodpod should work. Some runners are using Wahoo’s “Gym Connect” module which can plug into certain treadmills and broadcast pace metrics. There are other footpods which can also be used–anything which broadcasts pace over Bluetooth should work.

Getting into Running Mode on Zwift iOS

Once you’ve got your iDevice and pace sensor, the only tricky part is getting Zwift iOS into running mode. This involves tapping repeatedly on a certain area of the pairing screen, which we have highlighted below (the areas are different for different devices, but the areas below work on our iPad Air and iPhone 6s respectively.)

You’ll know you’ve tapped the right place when the top-left box changes to “Run Speed” with a treadmill, as shown below:

Pairing screen in running mode

Tap the “Run Speed” box and Zwift will search for sensors putting out a pace signal via Bluetooth.

Search screen shows it has found my Milestone pod.
Milestone pod is paired and ready for running (the “No Signal” notice is a bug in Milestone’s beta firmware… the pod broadcasts just fine.)

Once you are paired up you are ready to go! Just click “OK”, choose a course, and start running.

Strava Weirdness

Strava is currently labeling Zwift runs as “Virtual Rides.” The folks at Strava say they’re working on a fix, but until then you either have to live with this or hack your fit file and manually upload it to Strava. (Some folks have uploaded their fit file to Garmin Connect, set it as a run, then downloaded the file or had it sync to Strava).

Here’s a note from Strava on this issue:

From our end, we are waiting for Zwift to offset the GPS data on all run files. This would mean that all GPS data is shifted by some degree so as not to match run segments. Then Zwift data can upload as a normal run. For now, we are enforcing all Zwift data to upload as Virtual Ride.

From this comment is sounds like Strava is having Zwift “shift” the GPS coordinates of runs so they don’t match up with Zwift ride routes.

A Note About Pace

One big difference between running and riding on Zwift currently is running speed is based off of your pace (regardless of terrain in game) while riding uses your power and computes speed based on in-game terrain.

So if your running pace is 7MPH, you will be running at 7MPH up Box Hill, down steep hills, and on flats. Because of this, you may find yourself passing riders on steeper climbs!