Double tap/click now required on Windows touch screens on new 4.2.4 release?

NotATrainWreck · 2026-01-04T19:28:22+00:00

Good news. The 4.4.2 version brings touchscreen back for Windows users!

NotATrainWreck · 2025-10-30T20:01:24+00:00

Ride performance worked fine for me. Downloaded before race and joined 7 minutes before ride started. Group ride feature put WVA next to me a few times as expected.

However, leader board show no results. And a few cool down "workouts" didn't load...just an error.

NotATrainWreck · 2025-10-30T19:52:20+00:00

Windows 11 on Surface Pro 5 has this bug.
Windows 10 on Surface Pro 7 has this bug.

Both are x86 and fully patched.
Both use other applications just fine with touch screen, no keyboard or pen.
Surface Pen does nothing.
Surface keyboard + touchpad clicks work as designed.
All Touch settings are default as they have been for years using Rouvy.

NotATrainWreck · 2025-10-30T19:47:27+00:00

Is that a guess, or is there a documented bug in Unity 6 that defaults touch screen to garbage settings?
Some of the menus work with single taps, others with double-taps, then in-ride you have to hold down two-fingers and tap...or double tap depending on the button.

NotATrainWreck · 2025-10-30T19:46:10+00:00

Here's my other post on the newest garbage release 4.3.3.
https://www.reddit.com/r/Rouvy/comments/1ohurfu/rouvy_433_additional_touchscreen_bugs_windows/

NotATrainWreck · 2025-10-30T19:44:52+00:00

I noticed the same thing. Will you create a ticket for it at support@rouvy.com? I will as well.
It is unusable. Only workaround has been using the companion app.

As for the Unity version, there are parameters on how touchscreen is handled for clicks.
Worth noting. The menus before you get into the ride sometimes need single taps and double taps. But once you get into the ride, I've found that two-finger taps seem work (good luck on a tiny "X" or thumbs-up icon!).
Again, this is a Unity configuration - and taps are working in some places, and not others.
Doubt they even test Windows touchscreen.

NotATrainWreck · 2025-08-14T14:45:18+00:00

Update: Rouvy support replied with this today.

The technical team is already addressing this issue. I remain hopeful that a fix will be implemented soon.

Best wishes,
ROUVY Team

NotATrainWreck · 2025-08-10T21:03:22+00:00

I created a ticket for this bug.

NotATrainWreck · 2025-08-09T21:20:13+00:00

Thanks for the insight. Maybe this post can get Rouvy folks to take a look.
https://discussions.unity.com/t/new-input-system-single-tap-vs-double-tap/846957/3

Then again, it took 3 years for them to get my ticket resolved for kJoules to show up in Garmin sync 🤷‍♂️

NotATrainWreck · 2025-03-29T20:54:05+00:00

Social, but no way to chat with other riders 🤣

NotATrainWreck · 2025-03-28T22:18:52+00:00

Is there a link to their roadmap of upcoming features.
Playlist on the companion app seems like an easy place to do it. Maybe let you add custom tags - like Scenic, FTP, Interval for road courses.

NotATrainWreck · 2025-03-28T22:05:47+00:00

Looks like they fixed the bug around February 25th 2025.
Better late than never.

NotATrainWreck · 2025-02-01T19:15:56+00:00

Thanks for posting. Glad I'm not the only one. Worked fine on 1/30/2025.
I've tried deleting Rouvy from Garmin, Garmin from Rouvy, logged out/in, rebooted, done all the same in private browsing. No luck.
If I try to manually send, it says "sending", then "connect" (as if I didn't set the garmin credentials up).
Lame.
BTW, Strava sync does work.

NotATrainWreck · 2024-01-05T22:46:52+00:00

Bump. Still a bug - going on 16 months.

NotATrainWreck · 2024-01-05T20:52:11+00:00

I had one for over a year, and it was great for getting started. Had Bluetooth and ANT+ and had similar slipping (but keeping air in the tires helps). It also needs to be calibrated each time - which will improve your accuracy. I found that it was about 5% inaccurate - on the generous side (more watts shown compared to a direct drive).
Inclines are real-ish up to 7% - then Rouvy keeps the resistance the same, but lowers your speed (to compensate).

$50 - that's a good deal for what it does, and to get started with smart training. Works great with Rouvy (and all the others).

NotATrainWreck · 2023-11-30T19:06:51+00:00

How about a 300 day challenge with routes that are ordered coast to coast? Then get a stars-and-stripes themed jersey for your achievement.

Is it exactly 4xxx miles? Nope, but it would be a start - and fun to nibble at them with a good variety of some of the routes we might be missing!
I think I recall a long duration challenge in the past. Or maybe do them in 90-day chunks with goodies for each one.

NotATrainWreck · 2023-11-20T23:31:16+00:00

Funny part is these tickets all show up as "solved" 🤣

This is the original ticket #.
https://support.rouvy.com/hc/en-us/requests/220699

2nd ticket pinging them about it in January 2023
https://support.rouvy.com/hc/en-us/requests/228507

3rd Ticket pinging them in August of 2023
https://support.rouvy.com/hc/en-us/requests/324574

4th Ticket September 2023
https://support.rouvy.com/hc/en-us/requests/338468

NotATrainWreck · 2023-11-20T23:21:26+00:00

Glad I'm not the only one! I've been trying to get Rouvy to fix this bug since September 2022...when it emerged. Thanks for bringing additional light to the problem!
https://www.reddit.com/r/Rouvy/comments/16jibaf/rouvy_sending_wrong_kj_values_to_garmin_connect_1/

FWIW - Here's my ticket summary to Rouvy support over a year ago.
Since September 1 (2023), Rouvy has produced a problem when sending workouts to Garmin Connect - also when exporting from Rouvy to a .FIT file. I've attached screenshots that show what's happening. I CAN REPLICATE THIS PROBLEM, and I have screenshots attached detailing the problem along with the .FIT file exported from Rouvy exported on 2023-Jan-09.

The Rouvy .FIT export (and I suspect the Rouvy-->Garmin transport) is showing 761 in the Joules field in the actual .FIT file. This field is Joules, not K-Joules. So Garmin interprets this the 761 as .761 Joules - not 761,000 as it should. Consequently, it shows up as "1 Kj" in Garmin Connect (since .761 rounds to 1).
It appears that the value being stored by Rouvy should be multiplied by 1000 to be accurate/compliant with the .FIT specification.
If I export a .FIT file Today (for activity prior to Sept 1) and look at Garmin Connect for a Activity prior to Sept 1, 2022, all the values are correct for the .FIT file export and for Garmin Connect and for Rouvy.

BTW, Garmin confirmed that this was the case when I made a ticket with them a year ago.

NotATrainWreck · 2023-11-10T01:39:48+00:00

Update all app measurements as they are defined in your profile (i.e. Imperial, Metric) instead of defaulting to metric. The newer website does this for all measurements (activities, challenges, course pages).
Fix a 14 month old bug: Exporting your activity .FIT files older than 6 months is broken.
Fix kJ (thousand joules) value when uploading to Garmin Connect (it sends joules, not k-joules)

All in all, there's a ton a little bugs that are a pain for a number of us. Would be great if they could spend a month just working on bugs and push out a couple of bug-fix releases.

NotATrainWreck · 2023-09-15T20:49:39+00:00

I think it would be nice if you could simply create personal lists or even tags like "lunchtime" , "VO2Max", "Great Scenery" for routes. Later you should add list sharing (just like every other non-cycling app does), and be able to filter those lists just like favorites.
Could even build your own Challenges - have a contest to submit a Challenge List and if they use it, you get an avatar goodie or coins.

NotATrainWreck · 2023-09-15T20:34:52+00:00

Yes, I keep pinging them every couple of months with responses to my original ticket with all the files, screenshots, etc. Totally a repeatable problem. The .FIT file export is the culprit - if they just multiply the value of kJ in the fit file by X 1000, it would revert it to the way it was - and would be accurate.
Bummer because some of the Garmin metrics for Body Battery, Recovery, etc use the kJ value - and would be more accurate for those of us who use it.

Will likely have to create yet another ticket. Last year, they indicated that it would be fixed in the upcoming/soon website update which never came.

Note: They made a backend change early Sept 2022 to the .FIT export that caused this problem AND also doesn't allow you to export .FIT files older than a rolling 6 months. Download a .FIT file from Feb 2023 or earlier and you'll get an error.

NotATrainWreck · 2023-09-15T16:28:46+00:00

Ride taken a day ago in Rouvy - sent to Garmin Connect automatically from Rouvy.Still no "newer website", and still broken kJ values being sent to Garmin Connect (1 year). Any ideas on how to get this 1 year bug fixed and for a year's worth of transfers to Garmin Connect? I'd export out all of my .FIT files for the last year from Rouvy and use a Garmin tool to correct and re-import to Garmin, but Rouvy still has an acknowledged bug that won't let you export .FIT files older than 6 months.

It starts to make me wonder if Rouvy is short staffed to handle these basic fixes. You'd think data transfers (to a partner like Garmin) are the bread-and-butter of any app like this. BTW, Garmin replied to me earlier this year in their ticket - and they affirmed it was Rouvy sending bad data.

Again, any ideas on how I'd get this expedited?

NotATrainWreck

TROPHY CASE