If you are dragging-and-dropping the .hex that was bundled with the windows tool titled "X1-Berserker-Firmware-Test-V3.hex", don't use that one. That was just a test file that wasn't supposed to make it into the final public distribution. (I have since deleted that test file from the .ZIP package to avoid any more confusion). If you ended up loading that test file on your controller, putting the February public beta test file back on your controller was the right move, as that is the latest firmware anyway.
Since your controllers were already at the latest version 3 (since you were actively beta testing), your app didn't prompt you to upgrade from the website when you connected your controller. In the future, updates will be automatic - when you load the app, you'll be prompted to upgrade if an upgrade is available.
Thanks for reporting this, if I had left that test .hex in the distribution, more customers would have tried dragging-and-dropping that file to update their controllers, and generated more tickets and forum posts for help .
What I really should have done is made this version 4 when it went public, then you guys would have had the big "upgrade now" button when you tried out the new windows app for the first time.
Since your controllers were already at the latest version 3 (since you were actively beta testing), your app didn't prompt you to upgrade from the website when you connected your controller. In the future, updates will be automatic - when you load the app, you'll be prompted to upgrade if an upgrade is available.
Thanks for reporting this, if I had left that test .hex in the distribution, more customers would have tried dragging-and-dropping that file to update their controllers, and generated more tickets and forum posts for help .
What I really should have done is made this version 4 when it went public, then you guys would have had the big "upgrade now" button when you tried out the new windows app for the first time.