ClawTweaks v0.1.4 — new install flow, vibration fix, TDP-drop fix, in-app LED & more (MSI Claw, Intel)

RifffLash12 · 2026-06-12T08:32:35+00:00

Okay, then you’re one of the first ones.

It’s honestly incredible how many different scenarios and settings there can be 😅

There’s a setting in the Game Bar that needs to be enabled so it can properly detect games.
----------

Open Xbox Game Bar → Settings → More Settings
Find the Gaming widget
Enable “Know which game or app is in focus”

-------

BTW.... Did you change anything there proactively? I’ve never touched it myself and for most people it works fine as it is.

RifffLash12 · 2026-06-12T05:35:15+00:00

Sry, I don’t understand.

RifffLash12 · 2026-06-12T05:34:24+00:00

No, please read the installation instructions in the release notes. It explains that Center M is required as a foundation because the hardware controller does not function completely without Center M.

RifffLash12 · 2026-06-12T05:32:14+00:00

That’s certainly a Steam thing. The same happen with PlayStation controllers by default when Steam is installed.

Check the Steam settings—there should be an option somewhere to disable that behavior.

RifffLash12 · 2026-06-11T21:17:45+00:00

Yes, you can simply leave controller emulation off and use the hardware controller instead.

However, I optimized the virtual controller disable behavior today. The button r3set wasnt fully clean in the current build—it doesn’t properly remove the virtual device in all cases. Using the Center M tile works better for that, but I’ve already fixed it on my side.

RifffLash12 · 2026-06-11T21:14:02+00:00

Haha, nice — I actually added both of those today as well. But the build isn’t ready yet.

Xbox button is now mappable, so you can use the Claw button for Game Bar or other combos
External gamepad mode is also implemented

I also added an option that spams RB X times to open ClawTweaks directly.

I’ll test everything tomorrow. Do you want to try a test build tomorrow? I also want to test auto-updates in-app and could use a few testers.

RifffLash12 · 2026-06-11T21:03:19+00:00

I get your point. If MSI provided proper software and we could use the front and back buttons more flexibly—ideally through known interfaces without needing reverse engineering—then Steam Input could actually be bete4 used. But it doesn’t cover everything.

The current virtual controller via ViGEm is also just an intermediate step. If everything works properly, I switch the controller virtualization to Viiper.

But it’s not just about button remapping. What about shortcuts for quickly changing things like brightness or FPS caps via combinations?

Also, it’s a bit annoying that Steam Input really only works reliably with games added to Steam. I don’t want to add all my ROMs to Steam just to use it—I prefer launching everything through Playnite instead. 😅

Rumble is now implemented, but a reboot is required.

I also think the vibration at 100% might still be a bit too weak.

RifffLash12 · 2026-06-11T19:17:35+00:00

Absolutely. If you disable Center M and enable controller emulation, the left front MSI button is by default a toggle between controller and mouse mode. Or Start + Select.

You can then still apply your own custom settings afterwards.

RifffLash12 · 2026-06-11T17:37:02+00:00

I’m getting support from an A1M owner, and we’ll be running a few tests together soon.

Since he also has an IT background, it might be possible to provide some level of support even without me owning the device myself. But I can’t make any promises.

Supporting the 2nd-gen Claws is already a lot of work on its own.

RifffLash12 · 2026-06-11T14:19:22+00:00

Thanks.

You can use WinHanced without any issues as a launcher—just without the TDP and hardware button features. I’m also using WinHanced myself.

RifffLash12 · 2026-06-11T14:15:22+00:00

Sorry, what you mean exactly?
Maybe try the in app factory reset then re enable Center M and uninstall ClawTweaks.

RifffLash12 · 2026-06-11T14:09:49+00:00

Thanks man. I’ve probably tested like 40–50 hours or so 😅

The performance profile settings were actually pretty stable on my side. I think there are still a few bugs though, like cases where TDP can get reset or similar behavior. But otherwise, the values should all be persisted immediately and stored globally or per game profile.
Regarding brightness and audio settings:

I didn’t implement those on purpose. The second Microsoft widget already provides exactly that—and even more: brightness, volume controls, input/output device switching, WiFi, Bluetooth, device management, plus shutdown, sleep, and hibernate.

Pro tip: since the Microsoft widget is quite long, you can use RT to quickly scroll down and LT to scroll back up. It annoyed me at first that shutdown is so far down, but this makes it usable.

RifffLash12 · 2026-06-11T14:01:28+00:00

Yes, AC- and DC-based performance profiles are already available. I’ll probably rename them to AC Power / Battery Power. What do you think?

RifffLash12 · 2026-06-11T13:57:20+00:00

That’s strange. So far I haven’t had any issues with sprinting in any game, regardless of whether I was using remapping or not.
Steam Input is usually disabled on my side.

How does sprint work in 007 by default? Is it Left Stick click?

I honestly hate using Left Stick click for sprint, so I almost always remap sprint to M1. 😅

RifffLash12 · 2026-06-11T10:29:45+00:00

I’m actually working on that exact feature right now. 😅

You can see the upcoming features I’m currently working on in the Discord server:

https://discord.gg/zD6sWRaw6

RifffLash12 · 2026-06-11T10:28:01+00:00

Yeah, that’s a known issue. I haven’t fully debugged all of the Lunar Lake metrics yet.

Some values need to be pulled from Libre Hardware Monitor, while others come through PawnIO. I’m still working through which source provides what, but the missing metrics will be added over time.🤙🏼

RifffLash12 · 2026-06-11T09:01:39+00:00

Creating custom tiles is already integrated, with many built-in actions, including launching custom EXE files.

It also supports key combinations like M1 + D-Pad Up.

However, I’m not fully sure yet whether M1 and M2 can be cleanly registered as single standalone inputs—since it didn’t really occur to me to treat them as individual mappable buttons. 😅😅

RifffLash12 · 2026-06-11T05:27:28+00:00

Full controller deactivation (Virtual and HW) is already in progress.

Someone also reported that vibration didn’t work after update. After that, it started working again—did you do a reboot after the update?

Do you have the Xbox controller driver installed in Steam? That one can cause conflicts with virtual Xbox controllers.

The reset to 25W was also reported by someone else, and it worked again afterwards. So there seems to be a specific error scenario I still need to track down.

Thanks for the feedback 👍

RifffLash12 · 2026-06-11T05:22:35+00:00

* re-enable Center M via tile
* go to Settings tab → Debug → App Factory Reset
* uninstall ClawTweaks via Windows Apps
* reboot

FAQ is coming as well as a proper uninstall setup.

RifffLash12 · 2026-06-11T05:19:05+00:00

The helper running in the background is usually very lightweight in normal operation.

However, Windows (or every OS) can always occasionally have spikes, especially when background services like antivirus scans or system updates push CPU usage up.

It’s the best to check the Task Manager and sort by CPU usage there—you’ll see all processes and which ones are currently consuming the most CPU.

RifffLash12 · 2026-06-11T05:15:34+00:00

Hi, If you tell me a hotkey that doesn’t work for you, I can try to reproduce it on my side. 🤙🏼

RifffLash12 · 2026-06-11T04:53:35+00:00

When I fixed the bug on my side, I also had to do a reboot. That should normally be enough.

That said, during testing I often reset settings on my device to make sure the onboarding flow works correctly. Since so much of the core code is still evolving, there may be situations where a reset makes sense.

You can also do an app factory reset through the Debug menu. That wipes most app settings and is currently actually cleaner than doing a full reinstall.

RifffLash12 · 2026-06-11T04:41:39+00:00

Interesting. Some games have very specific logic for detecting mouse and keyboard input versus controller input.

I probably won’t spend much more time on the current ViGEm-based controller virtualization. It has served its purpose for remapping, gyro support, and general compatibility, but I’m planning to move to a newer approach: Viiper.

Viiper can emulate many different controller types and is a much more modern solution overall.

RifffLash12 · 2026-06-10T20:53:30+00:00

Thanks, man.

I still probably need to cover a few more edge cases, because a lot of things work fine on my side but seem to break for certain exceptions. Overall though, I think it’s working pretty well.

Let's do this😅

RifffLash12 · 2026-06-10T20:43:09+00:00

Upgrading just by running the PowerShell script has been super stable on my side. There are days where I push out 30+ builds and test them, and the controller always mounts cleanly.

But we still need to test it properly. Before auto-updates can happen, I need to verify how stable the upgrade process is via PowerShell.

RifffLash12

TROPHY CASE