You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I launch the app, I get a screen that says "No device connected ...Download all VIA definitions". But when try to download these definitions from the file menu, nothing happens. i have checked the Application Support folder and there is nothing in the Vial folder.
The text was updated successfully, but these errors were encountered:
Vial is generally (note: not completely) compatible with "VIA v2" (internal protocol 9 and below) firmware.
Last year, VIA migrated to version 12 of its internal protocol (more commonly recognized as "v3") which completely broke compatibility with Vial. This change also involved modifying the structure and location of its layout definitions.
It's increasingly likely that your keyboard didn't make it in before the "v3" cutoff—you haven't indicated what you're trying to work with—so there may be no compatible layout definition for Vial to download. (...but if that's the case, the firmware flashed on the keyboard is likely also too new to work with the Vial GUI anyway.)
To work with Vial’s GUI your keyboard needs to use a dedicated firmware for Vial.
The manufacturer of your keyboard may have precompiled Vial firmware available for you to flash—you could also ask them to create it. Or perhaps you could create a Vial keymap yourself.
Even after creating custom firmware for my keyboard, Vial App still detects nothing and shows the same message "No device connected ...Download all VIA definitions". Don't know what has gone wrong. I completed all the steps for porting. Please guide if its possible.
When I launch the app, I get a screen that says "No device connected ...Download all VIA definitions". But when try to download these definitions from the file menu, nothing happens. i have checked the Application Support folder and there is nothing in the Vial folder.
The text was updated successfully, but these errors were encountered: