-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V2 to V3 upgrade broken? #196
Comments
Can you please provide more information? What problems are you encountering, have you followed the upgrade guide in UPGRADE.MD? |
Ha! That was quick. Sorry, I accidentally hit enter and now updating the description with details. Bear with me. |
Quick Update: As I was composing this issue description, I thought of just using the V3 version of settings-reset.uf2 firmware to reset both halves of the keyboard (Since I am upgrading from V2 to V3). After doing that, I flashed with the V3 firmware. This time, however, I started seeing more than 1 device when running That said, I am glad to say that I was able to fix the issue on my own. And leaving this issue for documentation. Feel free to close the issue. And thanks for the hard work you put in. |
Glad to hear it's all sorted, we are aware there exists a route for confusion with the multiple settings reset files, and shall be improving this in the future |
What?
I have been using the V2 branch ever since I got my keyboard and have had no issues. I only have minor changes in my keymap (plus two macros). Apart from the annoying merge conflicts every time I try syncing the fork, I have had no issues whatsoever.
However, I tried to migrate to the V3 branch by doing the following (also checked the UPGRADE.md)
adv360.keymap
&keymap.json
) to only remap the keys I changed (mostly first row of the thumb cluster). They are attached belowadv360.keymap
keymap.json
The text was updated successfully, but these errors were encountered: