Help Shape the Future of FulGaz!

Please tell us what we can do to make FulGaz the best product for you.

Your feedback drives FulGaz forward! Share your ideas, report issues and vote on what matters most. This is your space to help us improve and ensure FulGaz remains the best experience for the community.

Need direct support? Reach us at support@fulgaz.com or visit the Help Center.

Loss of reactive mode

Hi, I always start rides in reactive mode. However, more often than not my Wahoo Kickr Bike stops responding to changes in gradient at some point during the ride and the resistance stays fixed at whatever level it was when the connection was lost - not too much of a problem if I happened to be riding ‘on the flat’ at the time, but awful if I was grinding uphill. The video continues OK (at the speed of whoever filmed it), but it bears no relation to the ‘feel’. Changing the setting on-screen has no effect: the resistance doesn’t change. Another (though lesser) problem is that the video sometimes ‘hangs’ for a while. Speed, etc., continue OK and then the video resumes some way ‘down the road’.

Peter Scott 25 days ago

💡

Feature Requests

FulGaz error casting to monitor

Hi guys. This is a new issue to me. FulGaz is having problems transferring the ride footage to my second screen, in this case a 4K computer monitor via HDMI cable from an iPad. This was working before Christmas or perhaps a little bit before. What happens is I’ll plug in the monitor, connect FulGaz start a ride and the ride itself will play on my iPad instead of the monitor. If I quit out of the ride and go back to the main menu, the ride footage begins playing on the computer monitor, after the ride is finished. After this I’ll go to another ride and start riding that one and it will show up on the computer monitor. After I quit that ride and even closed on full gas and then reopen it again, and go back to the previous ride, ride itself will display the video running on the computer monitor even though I haven’t actually started the ride. It’s all a bit confusing. I have cleared cache and restarted, with no effect. Hoping the movie file that I have created will transfer to your site, it will explain better than I can.

Gerard Van Ommen About 1 month ago

1

🐛 Bug Reports

Windows: Crashing on first attempt when starting a downloaded ride

I only ride downloaded rides because of unreliable networking so my information only pertains to to the use of FulGaz in that mode. Every time I start a new ride, first time, I am shown a Mercator projection of the whole world; when I start the ride, there is a pause of a few seconds then the application crashes out to windows with no messages or error. When I restart FulGaz the select the same ride, I am shown the actual map of the ride followed by the trace animation, then the ride works fine. While this is not a critical bug, it is certainly annoying to have to start the app connect the device and start the map twice each time. Windows 6.0.5.0

Michael Graham About 1 month ago

1

🐛 Bug Reports

Challenge Mode Crashes & Invalid Leaderboard Data

Hi FulGaz team, I’d like to report two ongoing issues that have been affecting my experience with the app for quite some time. 1. Challenge Mode Crashes Frequently The “Challenge Mode” feature crashes in roughly 50% of all attempts when I try to select a ride using “Select time to ride against”. I’ve reported this several times already, but unfortunately the issue still persists. I’m hoping that by posting it here, other users experiencing the same problem can upvote it so it gets more visibility. The crash occurs on two different iPhones as well as on my Apple TV, which is the device I use most often. The app shows the “Please wait” message for about 20–30 seconds and then crashes. On popular rides such as Alpe d’Huez, this feature never works at all. For context: I never had any issues with Challenge Mode in the older v5.0.x versions — the crashes only started happening with the newer releases. As a software developer, my guess is that the list of available rides might be generated dynamically on the backend, which could be causing long response times. If that’s the case, a more efficient approach might be to maintain a small index file per ride that gets updated after each upload. The app would then only need to download this file and append the latest ride, which should be significantly faster and more stable. 2. Leaderboards Contain Clearly Invalid Data Another issue is that many leaderboards are topped by completely unrealistic rides — for example, riders showing sustained 10 W/kg or climbing Alpe d’Huez in 20 minutes. This makes it nearly impossible to place in the top 10 or even top 20 on most rides, because the leading entries are clearly not legitimate. I would really appreciate it if obviously invalid data could be cleaned up from existing leaderboards, and if some form of validation or plausibility checks could be implemented to prevent such data from being uploaded in the future.

KetteRechts. About 2 months ago

1
💡

Feature Requests

The scaling of the power riden vs the power profile

Klem et al. Loving the smooth running of the latest updates to Fulgaz. Long time since I had any issues with connectivity, though I now have formed the process of downloading all rides to ensure that I have the video loaded locally. I may have mentioned this in a previous report or email, but I thought to log it here, if for no other reason to see if this is unique to me, or whether others have seen this. The attached photos were taken during a ride on Nov 19 so whatever version was running at that date I was running (I have it set to auto update when new versions are launched). You see that the profile of the power I am putting out (which as measured by an independent power meter is what the profile is requesting, shows up offset to the power profile. It is not a constant offset, but may be a percentage of the absolute value of the power profile values (I haven’t verified this, but it the offset is bigger for higher power profile values). Can you advise if this is an issue with the software or is it local to my particular set up - possibly one of the values I have set somewhere in user inputs? Advise would be welcome as I would prefer if the power output followed the power profile more closely!! Happy CHristmas, and all the best for 2026 Sean

SeanD About 2 months ago

2

🐛 Bug Reports

Planned

BlueTooth Connectivity and Upload Bugs

I’m on a Mac running OS 26.1. A couple of bugs still persist after the last update. —Fulgaz fails to connect to BlueTooth on the first effort every single time. It connects to nothing. I hit the refresh button in the lower left, and then sometimes it will connect to all the devices, not all the time. My Mac’s is discoverable on BlueTooth, and I have BlueTooth filters turned off in the Diagnostic Settings in Fulgaz. —When I end a ride and then click the button to upload the ride, a little thing in small black window spins…….and that’s it. The app doesn’t go to another screen as it did in version 5.3.x. it takes another click or two of that upload button to finally get an indication that the upload was completed.

PsiSquared 2 months ago

2

🐛 Bug Reports