rawaccel VS qmk_distro_msys

This might help you out https://github.com/a1xd/rawaccel

Raw Accel is hands down the gold standard of mouse acceleration. If it's possible to just drag and drop it directly into Steam Input, that's pretty much exactly what I would want. Either way, I'll go ahead and explain the reasons why I like Raw Accel by sharing my observations about accel after using it for so long.

First i will make a couple of corrections to your previous post: 1. Most players will find it easier to recoil with edpi above 800 up to a certain point since most grips generate friction against the mousepad 2. If you have the right setup (good mousepad, good mouse, mouse feet and arm sleeve) your edpi range will go up, so you can go from controlling between 700-1000 to 400-1600 (as long as you understand what friction you need) About your problem: 1. You could use raw accel (although idk if its bannable by faciet, so post on their reddit). 2. You could do the math to get the right ratio by increasing the edpi of your vertical axis with the correct m_yaw. 3. Buy a mousepad with higher vertical speed or an arm sleeve to reduce friction. 4. Buy a razer mouse or one that has the option to change the axis sensitivity. 5. Search for some software in r/MouseReview

I use old trackballs such as this one with RawAccel on Windows. Tweaked the libinput acceleration settings on Linux. Haven't tried on OSX.

Remember that Raw Accel is open source, so anyone is free to point out where Raw Accel would change other mouse drivers or affect any changes once uninstalled. https://github.com/a1xd/rawaccel/tree/master/common

I don't know if it would help, but RawAccel lets you make a custom setup for mouse acceleration. It requires a good amount of fiddling and adjustment, but it might be able to help you move your crosshair farther while still using a small area on your mousepad.

I don't know why you're asking in r/piracy but RawAccel what you're asking for

- QMK MSYS: you'll need it for many things, for compiling your firmware file and for flashing, especially if flashing with QMK Toolbox isn't permitted in firmware settings (in this case QMK Toolbox just won't recognize your keyboard);

You don't need the GUI though, you can write the simple code yourself, then using QMKMSYS you can compile these flat text files into firmware. Using the appropriate flashing software for ypur microcontroller, you then flash this firmware onto your keyboard.

First, install QMK MSYS from here. Once installation is finished, DO NOT DO "QMK SETUP". I will explain this later.

Download QMKMSYS.exe from https://github.com/qmk/qmk_distro_msys/releases/tag/1.7.2

QMK MSYS: What we will be using to compile the firmware

You don't really need to be able to program though. (Assuming you use Windows) QMK MSYS will help put all the QMK code on your PC and make it ready to make the firmware file, you will just specify which keyboard make & model you have, edit the file line that controls the timing behaviour, and your PC will build the firmware. Then the Toolkit GUI app will help you sync that onto the keyboard.

Download and install latest version of QMK MSYS

a) Installed git for windows. (If you don't know how to use it - don't go this way. Just download qmk-vial as ZIP, extract in "C:\Users\URUsername\qmk_firmware\vial-qmk", install QMK MSYS. Run it from shortcut in installed folder, run "qmk setup -H C:\Users\URUsername\qmk_firmware\vial-qmk" and change directory "cd C:\Users\URUsername\qmk_firmware\vial-qmk" for next steps.) b) Had an error with gh, so installed cli. Cloned qmk-vial with github desktop in the end. c) Had an error with "make", so installed it and cloned submodules. d) Still had an error with "make" when compiling fw "No rule to make target".