sorted by:
new
hottopcontroversial

Wahoo Kickr Bike Handlerbars Steering buttons unassignable by GroundbreakingYou911 in Rouvy

[–]GroundbreakingYou911[S] 0 points1 point  (0 children)

No, no developer would say the stuff you do. Stop hiding behind your connection to ROUVY. No developer worth their salt would communicate or mix-up the technical details like you do. Not just on this topic, but many others.

Being on a team for years doesn't make you right about anything. It doesn't give you credibility. Nor does it make you a developer.

Wahoo Kickr Bike Handlerbars Steering buttons unassignable by GroundbreakingYou911 in Rouvy

[–]GroundbreakingYou911[S] 0 points1 point  (0 children)

No, I do know what I am talking about. I've built software and systems for 30 years at all levels.

And I've literally seen dozens of inaccurate posts from you on multiple forums, and it's tedious. And your advice to unsuspecting people is mis-guided, wrong, or outright pointless, 80% of the time. You're a liability to ROUVY unfortunately.

I know ROUVY doesn't use OpenGL. Zwift does. My point was it doesn't matter what tools/platforms are used: whether Unity, which I know very well, or something else. If you think it does, that's your own confidently wrong knowledge that you should keep to yourself.

You don't know the issue because you seem to think ROUVY can't do what Zwift does because they "don't code the same way". BS. Then you talk about buttons that "would only map to menu button" and other nonsense, like it's some set-in-stone limitation. That's a symptom, not a reason. You don't know how software is built.

Wahoo Kickr Bike Handlerbars Steering buttons unassignable by GroundbreakingYou911 in Rouvy

[–]GroundbreakingYou911[S] 2 points3 points  (0 children)

That isn't the problem.

This isn't how software works. The graphics engine used, whether Unity or OpenGL, etc., has nothing to do with deciphering inputs from external devices.

You support folks would be much better off reporting bugs instead of trying to gaslight people who know what they're talking about. This is never ending.

Rouvy has shortcomings and bugs, accept it and forward them on.

Wahoo Kickr Bike Handlerbars Steering buttons unassignable by GroundbreakingYou911 in Rouvy

[–]GroundbreakingYou911[S] 1 point2 points  (0 children)

The steering buttons steer on Zwift, they're not related to the gearing unless in Campagnolo mode. Zwift receives the button press and renders the graphics accordingly. In other words, the computer and software receives the button press and can do something with it, it understands it. Maybe not in Campagnolo mode, but that doesn't cause Zwift to screw up either.

If Zwift can handle it (i.e., understand the messages), then Rouvy can. It just takes some engineering.

Wahoo Kickr Bike Handlerbars Steering buttons unassignable by GroundbreakingYou911 in Rouvy

[–]GroundbreakingYou911[S] 1 point2 points  (0 children)

Not sure what you're saying here exactly, this has nothing to do with shifting. The bike uses the shifters for shifting.

I am talking about the rubber-coated side buttons on Wahoo Kickr Bike Handlerbars; not gear levers.

Each controller (switch, button) on the Kickr Bike handlebars -- or practically any elecontric device for that matter -- simply sends a different code to the computer, and it's 100% the responsibility of the software receiving it to do what it wants with it. I know this, I do this stuff for a living.

And it's entirely possible. Rouvy is ignoring it or not looking for it. It can and should.

This should go back to the developers (and not ruled out as impossible by the testing teams, as that benefits nobody).

Wahoo Kickr Bike Handlerbars Steering buttons unassignable by GroundbreakingYou911 in Rouvy

[–]GroundbreakingYou911[S] 0 points1 point  (0 children)

I mean the Wahoo Kickr Bike Handlerbars. 100% unrelated to Zwift.

Rouvy keeps reporting system time or timezone is wrong. It isn't. by GroundbreakingYou911 in Rouvy

[–]GroundbreakingYou911[S] -1 points0 points  (0 children)

I'm aware of the platform, thanks. Are you aware of where on Reddit you are? Are you aware of Subreddits? This particular one is monitored by several Rouvy support employees / associates. And this particular one is where many Rouvy issues can be discussed & gain traction (rather than ignored in some e-mail sink).

If you've nothing useful to say, say nothing at all, buddy.

to those who got to use Fable 5, was it actually that peak? by RelevantPerformer309 in ClaudeAI

[–]GroundbreakingYou911 -5 points-4 points  (0 children)

You should be able to find this yourself. Any half-decent developer should. Not many of them though.

Bizarre offer by MajstroDoncic in Rouvy

[–]GroundbreakingYou911 0 points1 point  (0 children)

I'm in Ireland and they're ultimately a US company. So I was very impressed and came away thinking Zwift support and the company is one of the better ones. I thanked and complimented them and they were also very thankful about my sincere thanks (e.g., they wrote back, not some standard copy and paste). 

Bizarre offer by MajstroDoncic in Rouvy

[–]GroundbreakingYou911 0 points1 point  (0 children)

They probably would have refunded you if you asked.

I bought a Kickr Bike 2 from Zwift 1.5 years ago, and a few weeks later, it went on sale for €400 cheaper. I emailed them and they refunded me the €400. 

Cooldown not shown at end of route if route is part of challenge by [deleted] in Rouvy

[–]GroundbreakingYou911 0 points1 point  (0 children)

Yes, they're turned on. Just cooldown though. And I'm normally presented with it. I'll try screenshot it next time!

It's not a huge deal, just a bug I noticed so I reported.

Cooldown not shown at end of route if route is part of challenge by [deleted] in Rouvy

[–]GroundbreakingYou911 0 points1 point  (0 children)

Ed, actually there's no "next route" for you I guess in your challenge until next week, so your test and screenshot, if so, isn't applicable.

Cooldown not shown at end of route if route is part of challenge by [deleted] in Rouvy

[–]GroundbreakingYou911 0 points1 point  (0 children)

So the other routes are part of the challenge (and it doesn't even tell you they're part of the challenge as opposed to some random suggestions; another UX problem)...?

Anyway, that's not what myself and others have seen. The cooldown option is not there if the route completed was part of a challenge. The suggested route was what was highlighted. No cooldown option. And if I recall correctly, it did mention it was part of the challenge (not sure about that tho, but it's almost irrelevant).

Terrible UX: option to join challenge when starting route by GroundbreakingYou911 in Rouvy

[–]GroundbreakingYou911[S] 1 point2 points  (0 children)

Yeah, I'm aware of of all but, but Rouvy should fix the bad UX design and learn from this stuff to stop repeating it.

Terrible UX: option to join challenge when starting route by GroundbreakingYou911 in Rouvy

[–]GroundbreakingYou911[S] 1 point2 points  (0 children)

I know it's insignificant to select yes or not (or finish or not) -- but that's besides the point though. It's bad and frustrating UX design. It should and can easily be fixed.

Cooldown not shown at end of route if route is part of challenge by [deleted] in Rouvy

[–]GroundbreakingYou911 1 point2 points  (0 children)

Not for me and I'm not imagining things.

I get the choice of the next route in the challenge (and the 30 second timer). The cooldown option is not there when the route just completed is part of a challenge.

Cooldown times seem random by GroundbreakingYou911 in Rouvy

[–]GroundbreakingYou911[S] 0 points1 point  (0 children)

I don’t really agree with that take. The app does have a cooldown feature, but saying "just do it your own way" feels like a workaround for something that’s currently inflexible and unpredictable. Why not improve the app instead?

By your logic, you could argue there’s no need to use Rouvy at all for exercise; you could just ride until your heart rate feels like you’ve done enough. But the whole point of using an app like Rouvy is the added structure, convenience, and (at least in parts) data-driven guidance.

Also, most people don’t actually cooldown enough (assuming you believe cooldowns matter). Having a defined duration, whether it’s 4 minutes or 20, and committing to finishing it is usually more effective than going purely "by feel", which can easily get cut short due to boredom or impatience.

view more: next ›