We're not anticipating any big problems with the FulGaz 4 Beta, it's core source code has been used for over 15,000 successful rides already. However, in the world of I.T "shouldn't be a problem" and "absolutely never, ever" are not the same thing.
If you do run into an issue, please post a comment below so every other beta user can get the same advice.
Finally, you've been given exclusive early access to FulGaz 4, so please don't fill the FulGaz riders facebook group with beta feedback and questions, everyone without the beta will just get confused and we want to keep the numbers strictly limited at this stage.
Known Issues 12th Sept 2020
The beta won't work with older Kinetic trainers that use their own proprietary trainer control protocol.
FulGaz may randomly crash while browsing for rides or uploading to Strava, (This won't happen during rides, it's caused by FulGaz not being able to find a trainer or sensor that has gone to sleep).
We are waiting for Microsoft to approve an update that fixes this.
14th September release (iOS Build 317, Windows 4.05)
Crash affecting some users is fixed. Caused by a bug in the external display support in iOS.
Crash that can occur at random, usually towards the end of a ride, is fixed.
Incorrect HUDs on external displays bug fixed.
External display support on iOS is now turned on by default.
Crash in Ride Management settings fixed.
Ride Resume now works correctly on appropriate rides.