Its being used before the race, then changed in the pen but still being used. Its the previous pen glitch that has never been fixed.
In my experience that is a visual bug only. Like if someone joins the pen on a TT bike, switches to a road bike, they see themselves on the road bike, everyone sees them on the TT bike, but the performance of the bike is determined by the bike they switched to, not the one they joined with. It’s usually not hard to tell who is apparently on a TT bike in an event but easily staying with the group without excess power.
But what happens in the case mentioned by Jason?
Zwift may calculate draft from the bike others see, not the one actually in use.
I was fan viewing a rider and as soon as he would get behind the recumbent bike, draft gauge dropped to 0
As a former recumbent racer, that would be about right for a trike, if Zwift had a high-racer 'bent, draft would probably be 50 -75%, depending on the size of the rider drafting. I usually ended up with the smallest rider right behind me while on training rides, races were TT format so it wasn’t an issue. I never raced a pack race on my 'bent.
As for how they are used in Zwift, some people will always try to take any advantage they can get
TT bikes provide draft to others the same as a road bike so that isn’t an issue. And the game is all client-enforced on position so your copy of the game only cares what it’s seeing. So if your ZwiftApp sees someone else on an undraftable hand bike, your ZwiftApp will not provide you any draft. This has only been a visual bug until now. Good way to give yourself an unfair advantage in a race.
Glen, that might be related to Windows’ ransomware protection system, Controlled folder access. Maybe when you recreated the appdata directory, Windows didn’t see the memo about Zwift being on the blacklist? ![]()
These steps are on a Windows 11 box. You’ll need an admin password:
Open Settings / Privacy & security / Windows Security / Virus & threat protection.
Click Manage ransomware protection. See if Controlled folder access is turned on. Fwiw, I keep that turned on, but it causes trouble sometimes. Keep Ransomware protection or Controlled folder access in mind when something doesn’t work or breaks from now on. [Sigh]
If Controlled folder access is off, this isn’t your problem*. If it’s on, click Block history (admin password required). Look for “Protected folder access blocked” or similar with a timestamp corresponding to when you zwifted (or when whatever went wrong).
Easier, and you might have to do this anyway, Click Allow an app through Controlled folder access, then + Add an allowed app, Recently blocked apps.
I hope those hints are useful. No doubt Microsoft will have rearranged the menus again by next Tuesday. ![]()
It’s a bit of a clumsy system, but MS had to do something to address the ransomware attacks. You might want to look around that section. Click Protected folders to see and or modify what’s protected. Be careful about what you allow through. Sometimes I come back and remove an app (eg, cmd.exe) from the list after I’m done using it, cuz I’m worried that a hacker could make use of it. I don’t think that’s unnecessarily paranoid, right? ![]()
*If you found that Controlled folder access was off and decide to turn it on (might be a good idea), it might break stuff. Look for the Blocked History and Recently blocked apps buttons.
Good luck!
