Stage 1 is a touch too fast to manage micro-movements and the reticle doesn't stick in aim-assist. Now, based on that assumption, in Destiny at the sensitivity of 40 HIP & 30 ADS on Xim 4 -ġ. It may be closer to 100%, 75%, 50%, 25% and 12.5% because the last two stages are significantly slower, but it's a subjective guess at best. Whatever the case, the Sensitivity Stages seem to align roughly with this. Don't trust what Synapse is telling you, it might not transfer to the Xim. It doesn't matter what values you punch into each Stage, the outcome in-game on a Xim is the same.Īt a *guess*, the mouse either accepts the DPI and Polling Rate you assign, or it defaults to some unknown value. While Sensitivity Stages exist on the mouse and do save in Synapse, they don't seem to be stored on-board the mouse. But there's something weird going on with Destiny's aim-assist, which led me to experimenting instead with Sensitivity Stages.Ģ. It'll be guesswork, depending on your Xim's sensitivity.Ĭonventional wisdom would dictate that you simply follow mist's advice and tweak sensitivity to the point where you're not red-barring the Xim. When connected to Mac, my Ouro is 8200 DPI and 1000 Hz, so it's saved in Synapse, but there's no way to accurately tell what those values when connected to a Xim. Set the DPI and Polling Rate in Synapse, it *probably* saves on the mouse.
To save buggerising around, let me summarise a couple of hours of tweaking sensitivity for a Razer Ouroboros in Synapse 2 on a Mac.ġ.
0 kommentar(er)
