RPMs we’re cycling to crazy numbers (170+) intermittently during Stage 4 of Tour de Watopia. I’ve got a first Gen Tacx Neo…road feel enabled, run Zwift on iPad with latest iOS and latest Zwift updates. Companion app on Samsung Galaxy S21 Ultra, also both running latest updates .
Not a huge deal to me because I’m not using RPM for any sort of training metric but if gravel feel is going to become a staple in game going forward, probably need to figure out why RPM were going crazy off and on. Let me know if you need any additional info to diagnose.
I’ll try and remember tonight when I ride to check the firmware number. Was kind of hoping maybe Zwift could grab my ride log from their archives and check assuming all of the connection and software versions from various connected devices would be part of that log but if not, I’ll try and find out soon and report back.
The general consensus from others who’ve reported similar issues is that even on the latest firmware, the problem persists.
There may be a way to determine your trainer’s firmware version from the log files but if so, that’s not information that I currently possess.
Anyhow, the issue is with Zwift’s developers at this time and so no further action or information is needed. All you need to do is keep your Zwift app up to date so that when the eventual fix is deployed in a future update, you’ll receive it at that time.
I appreciate your willingness to help and thanks for being forthcoming with information and a detailed explanation of the issue. You’ve been quite helpful!
Absolutely Steven. Let me know if you need anything else.
For the record, unlike some of the folk who didn’t seem to care for the change , I actually liked it. Cool edition to the road feel feature that us Tacx user’s are fortunate to have and I nice little variation to make Zwift just that much more immersive. So kudos to the development team for coming up with and executing the idea.