Troubleshooting
Solutions for common issues. Find your problem below and follow the steps to resolve it. If nothing here helps, check the log files section at the bottom of this page.
Bluetooth & sensors
Bluetooth not enabled
Open Windows Settings and make sure Bluetooth is turned on. VeloLoop needs Bluetooth Low Energy to communicate with your sensors.
Sensors not appearing in scan
Wake your sensor by pedalling or putting on your heart-rate strap. Check that Bluetooth is enabled on your computer, then try scanning again.
Sensor connected to another app
Another application may already hold the BLE connection to that device. Close or disconnect from the other app first. Alternatively, use ANT+ or Wi-Fi for the other app and reserve BLE for VeloLoop.
Trainer not providing power data
Check that your trainer supports BLE Cycling Power or FTMS Indoor Bike Data. Some trainers only begin broadcasting when you are actively pedalling.
Cadence missing
Not all power meters report cadence. Check whether your trainer provides cadence via FTMS or the Cycling Speed & Cadence (CSC) service. If not, a dedicated cadence sensor is an option.
Heart rate not available
Make sure your heart-rate monitor is broadcasting over BLE, not only ANT+. Some watches require you to enable a separate HR broadcast mode in their settings.
Device keeps disconnecting
VeloLoop reconnects automatically with a gradual backoff. Check your sensor battery. Move closer to your computer and reduce other sources of Bluetooth interference (other BLE devices, USB 3 hubs, microwaves).
Screen feedback
No feedback appearing
Make sure at least one visual feedback mode is enabled — Dim screen or Reduce viewing area. Also check that you have selected a feedback display in VeloLoop settings.
Feedback on the wrong display
Select the correct display in VeloLoop settings before clicking Prepare Ride. The feedback overlay appears only on the chosen monitor.
Feedback not appearing over fullscreen content
Use browser fullscreen (F11) or borderless/windowed fullscreen in your app. Windows Media Player immersive fullscreen is not compatible. True DirectX exclusive fullscreen may also prevent the overlay from appearing.
External monitor or TV setup
The monitor or TV must be connected to your computer as an extended display. Select it as the feedback display in VeloLoop. VeloLoop cannot control independent smart TVs, tablets or phones that are not connected to your PC.
Workouts
Import fails
Check that the file has a supported extension (.zwo, .erg, .mrc, .fit, .json) and is under 10 MB. For FIT files, the file must be a planned workout — recorded activity files cannot be imported.
Too many steps
VeloLoop supports a maximum of 200 expanded steps per workout. Try simplifying the workout or reducing repeat counts.
FTP required
ZWO and MRC formats use percentage-based targets that need an FTP value. Enter your FTP in the import preview panel before confirming the import.
Zone-based targets not imported
Zone-based targets from FIT workout files appear as free-ride steps because VeloLoop cannot resolve zone definitions from the file alone.
Activity recording
Where are my FIT files?
Ride files are saved to the Documents/VeloLoop/Rides folder in your user directory.
Upload rejected by a platform
VeloLoop includes estimated virtual distance and speed in FIT files, derived from a flat-road physics model. If a platform still shows zero distance, check that virtual distance is enabled in VeloLoop settings (Recording > Virtual Distance). When uploading, set the activity type to "Virtual Ride" or "Indoor Cycling" on the target platform.
Installation
Windows security warning on first run
VeloLoop is not yet code-signed. You may see a Windows SmartScreen prompt — click "More info" then "Run anyway" to proceed.
Application won't start
Make sure you extracted the full archive, not just the .exe file. VeloLoop needs its supporting files to run correctly.
Log files
If you need to investigate an issue in more detail, VeloLoop keeps a log file at:
%LOCALAPPDATA%/VeloLoop/VeloLoop/logs/veloloop.logFor more detailed output, launch VeloLoop from a terminal with the --debug flag. This increases the logging level and can help pinpoint connection or configuration problems.