Wooting-Profile-Switcher Crashing at launch with latest firmware

[thowtue]

Hello,
I've installed latest firmware from Wooting on my 60HE+ and after a restart the app starts and crashes within seconds.
I wonder if you are still gonna update your software since there was no update since february, i hope so since it's quite effective at what it does.

I would have downgraded the firmware on my KB but it seems it's no longer supported since Wootility 5.1 unfortunatly..

[CorTav]

I am using the Wooting 80HE with Wootility v5.2.1 and can also confirm that the profile switcher fails to start.
If you activate the second or any other non-standard profile in the Wootility software, the program can then be launched, but the automatic profile switching still doesn't work.

[thowtue]

Alright,
Thank's for letting us know, i understand it's time consuming to have to reverse engineer undocumented things...
And knowing the framework you're using is deprecated is clearly not helping to dive back into the process of updating and maintaining the app unfortunatly :/

I'm also waiting for them to implement "basic" things like what you did into Wootility, most of the competitors have similar things for years now, i also need integrated macros too, still waiting, we don't even know if it's in the works unfortunalty.

Compared to Logitech Gaming Software (yeah, the old app still much better than the new one btw) it had all that for probably over 10 years now and i'm still using it for my old G700s.

[CorTav]

Thank you very much for your effort and the excellent work!
Let’s hope Wooting will add this feature to their own software.
The latest update includes a separate background service …

[0x464e]

I can confirm that downgrading to Wootility v5.1.2 and firmware v2.11.0 worked (I'm on 80HE).
I had to reboot PC after the downgrade (and also removed the current profile-switcher config) and then it started to work again.

I guess now I'll just never update again before Wooting gets their shit together and finally implements native profile switching. The first version of the background service has been released, so maybe soon it will also include profile switching.

[thowtue]

@0x464e How did you managed to downgrade to firmware 2.11 ?
I think this is what's causing the issue here, because i've downgraded to Wootility v5.1.2, and still had the bug, i'm on firmware 2.13 beta, and i've downgraded to 2.12 but can't downgrade more than that unfortunatly.

[0x464e]

@0x464e How did you managed to downgrade to firmware 2.11 ? I think this is what's causing the issue here, because i've downgraded to Wootility v5.1.2, and still had the bug, i'm on firmware 2.13 beta, and i've downgraded to 2.12 but can't downgrade more than that unfortunatly.

Here are steps that I did:

0. I'm using 80HE and I was on Wootility v5.2.1 and firmware v2.12.1 (not sure if that matters, but it could be they don't allow downgrade further down from certain firmware versions)
1. Uninstall Wootility (it asks if you want to keep settings, I selected yes)
2. Installed Wootility v5.1.2 from the changelog
3. Backup your onboard profiles (and to be safe, maybe all profiles) Easy way to backup is to upload your profiles to Wooting servers and note down the share code (i.e., just press "share" on the profile and note down the share code)
4. Restored the keyboard (Wootility -> Help -> Troubleshoot)
5. This rolled the firmware back to v2.11.0
6. The whole thing was buggy now for a bit, showing ghosts of my old onboard profiles. I did multiple restarts of Wootility and unplugged and plugged the keyboard back in. Then finally Wootility and they keyboard was making sense again and Wootility showed the default onboard profiles. I imported my own onboard profiles back.
7. Deleted wooting-profile-switcher's config %appdata%\wooting-profile-switcher.json and tried starting it. Still crashes however.
8. I deleted the config one more time and rebooted my pc. And then it worked. PC reboot did something relevant. I wish I tried rebooting PC after downgrading just Wootility, maybe firmware rollback would not even have been needed.

[thowtue]

Yeah okay i see, the issue i have is that the keyboard restoration process doesn't work for me i tried 2 weeks ago, i'm holding the asked keys (backspace and ctrl (or bottom right key) in troubleshoot, and keyboard still starts with RGB on, tried many times but nothing.. So can't go further

[misterpyrrhuloxia]

RIP, thanks for all you've done for this project, @ShayBox

[mxlb-dev]

Sorry guys, I would like to have kept updating it, but it's built on the first version of Tauri v2 alpha using the abandoned tauri-egui framework. I can't get it to build anymore, and I can't update it to Tauri v2 stable without completely rewriting it and switching to a different framework, additionally there's still no way to get the active window on linux Wayland, and I don't use windows or macos. I was told a while ago that Wooting was making their own profile switcher but I guess that never came to be.

It's always been a hassle to reverse engineer the undocumented commands and local storage format from Wootility because they don't want to make them as part of the SDK, and every Wootility/Firmware update breaks things that I have to figure out by looking through minified JavaScript from Wootility.

Thanks for your work! It`s a shame that this is not build-in wootility. The loss of your little app means a serious downgrade of the wooting experience for me. Is there any chance we can fund your work? Have you contacted Wooting? Shall we?

[0x464e]

Thanks for your work! It`s a shame that this is not build-in wootility. The loss of your little app means a serious downgrade of the wooting experience for me. Is there any chance we can fund your work? Have you contacted Wooting? Shall we?

Yes, it's absolutely mind-blowing Wooting still hasn't got their shit together to implement this basic feature. I would definitely have switched back to my old keyboard assuming I could not have downgraded Wootility/Firmware to make this work again. A keyboard is just not useable without automatic profile switching.

But, native profile switching functionality should be coming "soon".
The first step has always been some sort of a Wooting background service, well its first iteration was released in the previous update. (Though somehow it didn't contain automatic profile switching, because apparently it's more important to be able to show RAM usage and Discord mute status in your 80HE led bar 🤣)

To give some hope for this actually coming "soon", the release notes did state:

We’ll be expanding Background Service capabilities in future updates, including profile linking. Your keyboard will be able to detect when you launch a game or an app and switch to the linked profile automatically giving you the perfect setup, right away.

Though the way they wrote that sounds wrong, it obviously needs to be based off active window, not "game running". But surely I'm just paranoid, no way they could mess that up.

[StoyanBorisovBG]

@0x464e How did you managed to downgrade to firmware 2.11 ? I think this is what's causing the issue here, because i've downgraded to Wootility v5.1.2, and still had the bug, i'm on firmware 2.13 beta, and i've downgraded to 2.12 but can't downgrade more than that unfortunatly.

Here are steps that I did:

0. I'm using 80HE and I was on Wootility v5.2.1 and firmware v2.12.1 (not sure if that matters, but it could be they don't allow downgrade further down from certain firmware versions)
1. Uninstall Wootility (it asks if you want to keep settings, I selected yes)
2. Installed Wootility v5.1.2 from the changelog
3. Backup your onboard profiles (and to be safe, maybe all profiles) Easy way to backup is to upload your profiles to Wooting servers and note down the share code (i.e., just press "share" on the profile and note down the share code)
4. Restored the keyboard (Wootility -> Help -> Troubleshoot)
5. This rolled the firmware back to v2.11.0
6. The whole thing was buggy now for a bit, showing ghosts of my old onboard profiles. I did multiple restarts of Wootility and unplugged and plugged the keyboard back in. Then finally Wootility and they keyboard was making sense again and Wootility showed the default onboard profiles. I imported my own onboard profiles back.
7. Deleted wooting-profile-switcher's config %appdata%\wooting-profile-switcher.json and tried starting it. Still crashes however.
8. I deleted the config one more time and rebooted my pc. And then it worked. PC reboot did something relevant. I wish I tried rebooting PC after downgrading just Wootility, maybe firmware rollback would not even have been needed.

Thank you @0x464e !!! - your step-by-step guide worked for me, but the crucial part to make it work, apart from downgrading the firmware, was to delete the config file of Wooting-Profile-Switcher, despite that I don't find any difference to the old one when recreating my apps.

If you don't care about new firmware or Wootility features - that's the guide to follow and restore functionality for Wooting-Profile-Switcher.

Edit: I'm using 60HE+

[mxlb-dev]

More people use this than I thought. Hopefully Wooting can get their software out within the next millennium, until then I managed to get it to build again and updated all the dependencies except Tauri, including Wooting RGB SDK / Bindings. Try it out, let me know if it fixes the issues, I can't reproduce because I have a Lekker, 2.4.0 and 2.5.0 both work for me on the latest Wootility and Firmware, so it's only a newer device issue. https://github.com/ShayBox/Wooting-Profile-Switcher/releases/tag/2.5.0

Will do first thing tomorrow morning! Amazing

[StoyanBorisovBG]

More people use this than I thought. Hopefully Wooting can get their software out within the next millennium, until then I managed to get it to build again and updated all the dependencies except Tauri, including Wooting RGB SDK / Bindings. Try it out, let me know if it fixes the issues, I can't reproduce because I have a Lekker, 2.4.0 and 2.5.0 both work for me on the latest Wootility and Firmware, so it's only a newer device issue. https://github.com/ShayBox/Wooting-Profile-Switcher/releases/tag/2.5.0

Thank you very much for getting back to this - it means A LOT to A LOT of people.

Unfortunately, it's not working for me, it won't even start with the old Wootility and Firmware (2.11) as well as with the new one :(

I am usually using the portable version, but this time tried both portable as well as setup one - no dice with either of them.

When running from CMD it won't generate any output.

I had to go back to Wootility 5.1.2 and revert the firmware to 2.11.0 to use wooting-profile-switcher_2.4.0_x64-portable.exe

If I can provide you with some useful information, please do tell.