Hello All,
We are releasing a beta 1.2.5 today. This upgrade includes several bug fixes and club parameter change functionality, TGC full upgrade and several under the hood fixes etc. If you choose to use this beta and still having problems, you can enable the debug mode so that we can see what is wrong. The debug mode allows us to get your raw data directly via cloud so that we can dig deeper into the problems since we are not able to reproduce every problem you reported here. (The system has been tested over 10K swings by different people but we believe some of the peculiarities in your swings trigger sanity checks and result in no trigger. These swings are not necessarily bad, they are simply not compatible with the current version of the algorithms.). How to enable debug mode is explained below.
If you upgrade to 1.2.5 and not happy, you won’t be able to downgrade to 1.2.3, instead, you can further upgrade to 1.2.6 which is identical to 1.2.3.
Once we get enough feedback (via Debug) and fix remaining issues, we will release 1.3 which hopefully be the golden release for some time to come.
We also acknowledge the issue with the holders and we will provide an update in the coming week or so. In the meantime, if you are one of the few who had broken clips, just drop an e-mail to support@rmotiongolf.com and we will send you extra clips.
Thanks for your support and patience. We take your feedback very seriously.
Links for the releases are below.
1.2.5 release:
1.2.6 release:
How to enable Debug Mode:
Debug mode is enabled by replacing the “UserSettings.txt” file in your installation folder. Once you replace the file, you need to restart the application. Please note that, if you enable debug mode, you are disabling all the sanity checks and you may see occasional shots that may not make sense, or see false triggers.
UserSettings.txt:
We are releasing a beta 1.2.5 today. This upgrade includes several bug fixes and club parameter change functionality, TGC full upgrade and several under the hood fixes etc. If you choose to use this beta and still having problems, you can enable the debug mode so that we can see what is wrong. The debug mode allows us to get your raw data directly via cloud so that we can dig deeper into the problems since we are not able to reproduce every problem you reported here. (The system has been tested over 10K swings by different people but we believe some of the peculiarities in your swings trigger sanity checks and result in no trigger. These swings are not necessarily bad, they are simply not compatible with the current version of the algorithms.). How to enable debug mode is explained below.
If you upgrade to 1.2.5 and not happy, you won’t be able to downgrade to 1.2.3, instead, you can further upgrade to 1.2.6 which is identical to 1.2.3.
Once we get enough feedback (via Debug) and fix remaining issues, we will release 1.3 which hopefully be the golden release for some time to come.
We also acknowledge the issue with the holders and we will provide an update in the coming week or so. In the meantime, if you are one of the few who had broken clips, just drop an e-mail to support@rmotiongolf.com and we will send you extra clips.
Thanks for your support and patience. We take your feedback very seriously.
Links for the releases are below.
1.2.5 release:
1.2.6 release:
How to enable Debug Mode:
Debug mode is enabled by replacing the “UserSettings.txt” file in your installation folder. Once you replace the file, you need to restart the application. Please note that, if you enable debug mode, you are disabling all the sanity checks and you may see occasional shots that may not make sense, or see false triggers.
UserSettings.txt:
Comment