Doesn't change profiles for keypad

[MF-JEWM]

Not sure if this is known as I think the keypads are just now starting to arrive for people in the mail.

I also don't know if there is even proper support for choosing which of the two devices would be controlled considering that version of Wootility is in beta still.

Figured I would just try to make you aware of this though in case you weren't 100% sure whether the program would or wouldn't work properly.

So to clarify, I have a Wooting 60HE and a UwU keypad plugged in. The program can change the profile for my Wooting 60HE, but not my UwU keypad. I even have the profile names matching the ones on my keypad instead of my 60HE and it still won't do anything in relation to the keypad.

[ShayBox]

Try unplugging your keyboard and see, the RGB SDK as far as I know never supported more than one keyboard, I know Wootility Beta has support now but afaik RGB SDK hasn't been updated. And the new Wootility Beta introduces a new RGB Effects system that this program is incompatible with right now.

[MF-JEWM]

Ahh darn. Sounds good then. Hope updating the program for that stuff goes smoothly if you choose to continue developing it with Tony and whoever else is involved

[ShayBox]

Actually never mind, unplugging your keyboard wouldn't work because the RGB SDK doesn't have the UwU device PID. I don't think Wootility uses the RGB SDK so until that gets updated and I can figure out any command changes needed to use the new RGB Effects I can't support the UwU or Wootility Beta, but it is planned.

[MF-JEWM]

I went over to the Wooting RGB SDK repo to check out what you were referencing and found this branch that might have some information you could find useful

https://github.com/WootingKb/wooting-rgb-sdk/tree/feature/uwu

[ShayBox]

Oh nice, I always forget about branches. I'll try to update it and publish a release.

[MF-JEWM]

For having it so the program is able to work properly with multiple Wooting devices plugged in, I think this SDK maybe be of use? I took your word for it and didn't bother looking through the RGB SDK at all.

https://github.com/WootingKb/wooting-analog-sdk/blob/1564f0270959884c14cff50a9a46dcaba6cf06d9/wooting-analog-plugin/src/lib.rs

Also did the ability for the software to pull profile names from Wootility get removed? It doesn't seem to work for me, unless it only functions on the initial generation of the config. And if that function is still in the software it would definitely (idk how to idk why i say definitely here) need the SDK for identifying which device each profile belongs to.

[ShayBox]

I haven't tested it with the new Wootility yet, I'd bet the JSON config has more data that my program isn't expecting yet, but that's a guess.

I think I'm going to add a device index to rules, each device can have its own rule; otherwise, I would have to keep a list of a list of rules and have a device drop down like Wootility, which is less optimal, but what are your thoughts on how to interface with multiple devices?

EDIT: Another possibility could be to change the profile index on rules into a hashmap of device id and profile index, it would allow for multiple device profile index changes per rule instead of creating a rule per device.

[MF-JEWM]

I think trying to integrate this of this other SDK but again I don't really know much about coding unfortunately

https://github.com/WootingKb/wooting-analog-sdk/blob/1564f0270959884c14cff50a9a46dcaba6cf06d9/wooting-analog-plugin/src/lib.rs#L39

[ShayBox]

I wish I could use the Analog SDK which is in Rust now but I have to use the RGB SDK which is still in C/C++ but I forked and updated a bindgen wrapper. I think the functionality already exists in RGB SDK but I never used it because it was unlikely anyone would have two keyboards plugged in.

[MF-JEWM]

EDIT: Another possibility could be to change the profile index on rules into a hashmap of device id and profile index, it would allow for multiple device profile index changes per rule instead of creating a rule per device.

This latter part sounds it would maybe the more efficient way of those two? For instance it would very easily allow you to do something like disabling the RGB on one device while also setting the other device specific profile or something like that, right?

Edit: That also makes me curious if would be possible to add the ability to simply auto set brightness of a device when launch a game rather than swap the entire profile? Sorry though thats not even what this software is 🤣 thats probably more a question for the devs of Artemis or something

[ShayBox]

I wouldn't mind having a brightness slider for rules, but I believe it's part of the RGB matrix for each key, though Wootility has a per-key and a global slider per-profile so you can change that and it will apply with WPS.

Artemis can detect active process and swap lighting profiles so that's probably a better option, but that doesn't save to the device like Wootility.

EDIT: I realize now that my first idea wouldn't work because my program is only designed to find one matching rule at a single time, not multiple. so a HashMap is the only option.

[ShayBox]

The latest release adds multi-device support, still not beta and RGB effects, that's waiting for Wootility to be released stable. let me know if there's any bugs with the update.

[ShayBox]

I released a pre-release that should support everything, but you have to uninstall Wootility and install Wootility Beta

https://github.com/ShayBox/Wooting-Profile-Switcher/releases/tag/2.3.0

[Ejz85]

I released a pre-release that should support everything, but you have to uninstall Wootility and install Wootility Beta

https://github.com/ShayBox/Wooting-Profile-Switcher/releases/tag/2.3.0

Not sure if this belongs in a separate topic or not. But mine does not switch either with my TWO HE keyboard. Using latest beta Wootility and Switcher.

I can't even pick profile in the app for some reason. My config does not have any device info in it (even if I delete and restart the app).

Wootility v4.6.4-beta Firmware: v2.7.0-beta.2 Wooting-Profile-Switcher 2.3.0

Edit: Also tried with the new updates Wootility v4.6.5-beta Firmware v2.7.0-beta.3

https://i.imgur.com/r1GchHt.png

[ShayBox]

Make sure you have the stable wootility uninstalled and delete the wootility-lekker folder in appdata roaming, and delete the WPS config in appdata roaming too. It should pull device info from beta first time you open WPS as long as wootility isn't open.

[Ejz85]

wootility-lekker folder in appdata roaming

Thanks, seems the issue was the "wootility-lekker folder in appdata roaming". :)

Edit: I can choose profiles with the slider now, but it still won't switch profiles. It does switch profile If I select a profile via the menu in WPS.

Edit: If I remove the "default fallback" it switches in game. But then when I close the game it dosent switch back to a default.

[ShayBox]

It seems the fallback rule had priority over the other rule(s), what position was it in before deleting it? I thought I made new rules insert from the top to keep the fallback at the bottom and tested it (top/highest to bottom/lowest priority)

[Ejz85]

It seems the fallback rule had priority over the other rule(s), what position was it in before deleting it? I thought I made new rules insert from the top to keep the fallback at the bottom and tested it (top/highest to bottom/lowest priority)

I think it was on the bottom.

[ShayBox]

I'll do some testing, I also remembered that I forgot to add buttons to move the rules around and an indicator for active rule.

[ShayBox]

I found the bug, it was checking for properties then rules instead of rules then properties. so it would match the first rule that had a matching app name, then bin name, bin path, and win name. That will be fixed in the next update.

[ShayBox]

Try this version https://github.com/ShayBox/Wooting-Profile-Switcher/releases/tag/2.3.1

[Ejz85]

Try this version https://github.com/ShayBox/Wooting-Profile-Switcher/releases/tag/2.3.1

Thank you, I can confirm that this new one works for me. :)