I’m curious to hear from any Zwift engineers on this question:
Zwift sends resistance due to gradient to the smart trainer, but does not send resistance due to to wind (i.e. if you are on a 5% slope in Zwift you will feel the same resistance to your wheels at 10 kph as you would at 40 kph). This is especially noticeable when drafting, since in IRL you really strongly feel when you are in draft vs. aren’t as actual resistance your legs are pushing against. In Zwift, since wind resistance is only modeled to calculate in-game speed, but not trainer resistance, you feel nothing when you go into draft.
I fully understand that watts are watts, and that in terms of leg output mapped to speed in Zwift, it doesn’t matter. That said, I’m curious why it isn’t implemented (especially because the other platform I’m familiar with, RGT, also does not implement it, which leads me to think there’s a technical reason not to do it). My question, then, is: Is there a technical reason why modeling wind resistance in the trainer isn’t feasible? Is it simply because the trainer APIs only take gradient information? Or is it something like the update lag between Zwift sending new resistance to a unit and that resistance actually being set by the trainer and felt in the legs is too long for it to feel real? Or is it just that it’s added complication and the current situation already works well enough?