I bought a Razer Mamba Elite and it forces me to use Synapse 3. That new version doesn't have a mouse acceleration feature and I'm really used to mouse accel. My aim is trash without it. I've installed Custom Curve from Mouse Acceleration as an attempt to recreate the acceleration curve but I can't do it. .

Edited September 24, 20205 yr by 32165487

The acceleration settings in Synapse are implemented using Windows input APIs, which were removed from Windows 10 by Microsoft itself.

that means moving the slider, even in Synapse 2, would have no effect on your mouse pointer's acceleration and windows will get "raw" input from the mouse in either case.

You'll have to recreate it with third party software OR go the extreme route, using windows 7 and a legacy synapse version, like synapse 2. That should work.

21 hours ago, 32165487 said:

I bought a Razer Mamba Elite and it forces me to use Synapse 3. That new version doesn't have a mouse acceleration feature and I'm really used to mouse accel. My aim is trash without it. I've installed Custom Curve from Mouse Acceleration as an attempt to recreate the acceleration curve but I can't do it. .

http://mouseaccel.blogspot.com/p/blog-table-of-contents.html

this might actually be a better place to loo- for mouse acceleration 

same thing for the kovaaks  discord #inter-mouse -accel

 

^those options actually work pretty well 

Edited September 25, 20205 yr by fortunate reee

You can make any curve in Custom Curve. You are best off experimenting as you will find something better most likely.

In case you want to factually recreate your old synapse accel curve, only option is to do some reverse engineering. Just install the old driver / mouse you are used to at the same time as Custom Curve, and then use an Autohotkey script whilst toggling between the two, measuring the resulting sensitivity using a precise amount of counts from the script, and adjusting the value in Custom Curve until you have the same length of line. You'd need to use the AutoHotInterception Library to send it through the driver, and then just match up the razer sensitivity at each count per update with a resulting sensitivity value in Custom Curve. You could do this using just drawing simple lines in paint until they match to the pixel. It would take a few hours of your time but is straight forward enough to do. Once you have mapped the curve, then just save it for future use on your new mouse / driver.

Here's some simple code I just wrote that would do the task for you in AHK with the AHI library, just read through the dox on the github page to get setup.
 

#SingleInstance force
#Persistent
#include <AutoHotInterception>
#NoEnv
SetBatchLines -1
AHI := new AutoHotInterception() 

; scrolllock to enable
; Left click to start loop
; right click to stop loop
; ctrl-s to save edits in notepad and reload script
; ctrl-esc to close script
; ------------------------------------- Set Mouse ID Here ----------------------------------------------------
mouseid := AHI.GetMouseId(0x046D, 0xC53F) ; This is an example - set YOUR mouse VID/PID numbers here!
; -------------------------------------------------------------------------------------------------------------------
Return
#if GetKeyState("Scrolllock", "T")
LButton::
a := 500 ; Parameter 1 (total number of packets looped - use this to form a length of line to compare between Razer & Custom Curve value)
loop %a%
{
b := 1 ; Parameter 2 (counts sent per packet - start at 1 and increase until you have covered all your hand speed values in Custom Curve)
AHI.Instance.SendMouseMoveRelative(mouseid, b, 0)
DllCall("Sleep", "UInt", 10)
}
Until GetKeyState("RButton", "P")
Return
#if
~^s::
Sleep 100  
Reload
^Esc::
ExitApp