Hey natu, can you try to describe what you don't like about the acceleration? Are you talking about Hip or ADS? Are you using a KB or Sony Nav?
I just got home from a party and TBH, I'm dead tired. But I will follow up with your answers in the morning.
One quick suggestion. Some people have had issues with my setup because they're using a KB and assigning ADS to right click. That can be an issue because I assign ADS to the trigger of the NAV.
So, if you're using right click for ADS make sure you chg. ADS activation to right click.
I hope that helps.
Thanks for the quick reply, I'm just using a keyboard and mouse (logitech g400s @4k dpi, 500 hz). Hip is fine, to be honest, it's the ADS. I already switched the keys to right click so the ADS would activate (before I complained about the MA).
The hip has the same kind of problem, but for hip it doesn't really matter to me, it's just the ADS that makes it pretty annoying to snipe.
Edit1: I don't know if the sensitivity is the issue as per the above posts, but I can't really test a higher sens right now (servers are down), but the MA is pretty bad. I have a QcK+.
So, imagine a number line up to 10, if I swipe slowly it will go from 1 to 10 (covering a longer distance), if i swipe quickly it will go from 1 to 5 (covering a shorter distance).
Edit2: What is your DPI exactly when you made this Destiny setup? I know your signature says 4K, but in the pictures where you show your key setup for your mouse its set at 8K.
Thing's I've tried, upping my sens to 50 / 22.25 (doubling it, assuming you had 8K dpi) -- makes the acceleration kind of worse but a bit easier to handle the ADS, I suppose, but it's just an insane amount of MA
Also, just to clarify your sensitivity setting in destiny is set to max (10), correct? I'm just trying to figure out if I looked over something,
Edit3: Before, I go to bed, the only thing I can think of is maybe the release candidate firmware (20160104) and manager is a bit different in copying and pasting the code (I use a PC for the manager).
I set this up at 8,000 DPI. I switched to 4000 dpi for BO3, I haven't tested 4000 dpi with Destiny but by doubling your sens you should be close to what I was experiencing at 8000.
I added the acceleration to ADS because of Aim Assist on consoles. Sniper rifles are a bit of a known issue with a curve like this, I used to have other settings just for sniper that I removed because things were getting a little too confusing.
You can simply remove the acceleration by removing the ballistic curve.
It should be noted that ALOT of people never use Advanced Settings and swear by pure 1:1. I'm not one of them! However, my setups aren't for everyone. We all have our personal preferences. I will never use 1:1 with Destiny because the turn speed with HIP, Sparrow and Sprint is just TOO slow for me. ADS is a possibility for using the Vanilla ST, but you would have to raise your sens even higher then my settings and Aim Assist will be stronger. Still, some people like strong AA and in your case with sniping that may be true for you. The key to getting your sensitivity as high as possible really comes down to TWO things.
1. Riding the red light. It's ok to get the red light flash for exceeding the turn limit just don't over due it. Another words, I don't care if it's flashing so long as my mouse movement reflects what I'm seeing on the screen. If you feel like your wasting movement, then your sens is too high. OR
2. Use consistent mouse movement. I've said this now probably a thousand times on this forum and it's probably the single most important rule for all XIM users. You need to use slower consistent mouse movement in order to achieve the fastest turn speed possible. I suggest not swiping your mouse further then 6 inches per second. Twitch movements (like on PC) will not register properly with XIM. This is because of the console games Turn speed limits.
The bottom line is this isn't PC and IMO you pretty much need MA to make this game more enjoyable to play. I'm not pleased with it either, but it is the nature of the beast with games like this on console unfortunately.
You can only use these curves and codes with the latest firmware/manager. If you go back to 1114 you won't be able to paste them correctly, it will just be squiggly lines!
Is it possible to bind a button twice so it will activate as if I double tap?
Also, will the curves in the first post work with the newest firmware/manager?
This is only possible with a macro, see a few post back for your first answer. Second answer, YES and only with the latest firmware/manager. By latest I mean the latest in the release candidate section.
