The idea with the virtual gear box is nice. When I ride up a steep climb on Zwift the Fortius can not do it.
Well, essentially I wanted to solve the same problem. I understand you want to simulate two shifters. The factor is -10% steps up/down and nothing else. 10) not an abstract number, but as the number of teeth on the cassette. So I implemented a reductionfactor (after far more complicated options) and visualized the factor (0.1. Since I have a bike with a 50/34 x 15/25 gearing, I cannot ride uphill 20% anyway. My thought on implementing was: I ride Zwift, it goes uphill at 20% and I cannot do that at the speed that the Fortius still works well. And that after some time the chain gets dry and starts to sqeeck (joking). Perhaps it is also neat when you select 50x36 or 34x10 that the derailleur ticks and the chain cracks and complains. I understand you want to have two shifters for your double and the cassette to see the 50/34 versus 10/11/./36 numbers. It's a bit like the knob on the sportschool trainer: turn left/right for lighter/heavier. The up/down goes with +10%/-10% which matches the steps on a cassette: 10 -> 11 = 10% and 32 -> 36 is also (approx) 10%. You can maintain the same cadence and because you produce a lower power-output Zwift will calculate a lower speed. If you ride up and the resistance is too high, press down and the resistance will decrease. The "virtual gear" enables to increase/decrease the resistance when riding up/down a slope. I hated it anyway after hitting it accidentally twice. I stole the cancel button for front shifting, I don't know if this is a problem.
COMPUTRAINER FLYWHEEL FULL
Graphical representation of the chain rings may be nice to have, but it is probably fine as-is.īackward-compatibility/default setting for people who don't want full simulation could be done by configuring a single chain ring in front and an appropriate cassette. I made the text box a little larger to show front/rear teeth, but left the graphical representation basically as is. Maybe it is time for a configuration file (json/yaml)? It also contains some other modifications and definitely needs more work if it is to be merged into the main branch:Įverything is hard-coded right now: there should probably be options to change the number of gears and the chain rings/cassette, as well as the physical gearing ("ReferenceGearRatio"). I decided to take this a little further and simulate a full 2x11 group set to have the same gear range as on a real bike. This solves the stuttering problem with the Fortius at low speeds and I suppose it also enables lower-end trainers to simulate higher gradients. I really liked the idea of having a virtual gear box, so now I keep the physical gear fixed and the trainer can run at an optimal speed all the time.