*PS4 SUPPORT (t500s best Config) Overwatch Linear Config Without Micro Stutter

[GoodAimButATankMain]

Definitely mess with window size over any other setting. The Xbox curve made me realize that low window size like 20 actually feels stronger than a window of 70. Because when inside the window you still hit the turn cap and are limited. A mouse swipe will never be able to handle aim assist because the swipe is emulating stick tilt. And there's no way to swipe consistent enough to match a stick tilt of the same value. So window size effects more than just when it kicks in. It also effects how strong the aim assist grabs. Test it out on a target at long range with flicks. Far easier to flick on low window and its more magnetic where high window causes just a larger window of inconsistent movement.

Exactly. But the aim ease in can affect when the aim assist actually starts kicking in so its good to mess with both to your liking The way the aim assist ease in works if no one knows is the higher the value, the closer to the target the aim assist will start kicking in harder. For example, if u use 100 aim window, and 0 aim assist ease in, the second ur crosshair touches the aim window you will have 100% aim assist strength, but if u use 100 window and 100 aim assist ease in, the aim assist strength will be really weak the second u hit the window, and slowly ramp up till ur on target to max strength once u hit the target. Its good to find a good balance between the 2 so your flicks are still pretty consistent, but u also keep good tracking when needed Good example is hanzo, where sometimes u track, and sometimes u flick.

[BeeDee]

These settings are FIRE! Only got to play for about an hour after getting the config set up but I could already tell how much of a difference this config felt to the one I was using. Thanks for sharing!

[Lowkeeloki]

Can I actually get the ps4 config please, DPI, INGAME settings and xim settings, I understand I only have to download the ballistic editor curve but what about the rest of the settings??

[GoodAimButATankMain]

The in game settings are the exact same as my xbox config The xim settings are completely personal preference though. However, I do think that using any boost will mess with the 1:1 feel so id suggest not using boost, but u can certainly try it

[Malinkadink]

Trying out these settings now after not playing for a year or so. Not bad so far.

One thing i'd recommend for the ADS heros (ana,widow,ashe) turn scoped sensitivty to 100% and use AUX in the XIM. Take your base sensitivity value and multiply it by 0.614 for Ashe and 0.452 for Ana/Widow. The game uses a FOV of 93
on console and to get as close to 1:1 while scoped you use those values.

You can check it here:
https://jscalc-blog.com/overwatch-zoom-sensitivity-calculator/

[GoodAimButATankMain]

Yup, exactly what i do too. You can try using the hero sensitivity multiplier in game instead since I think it would offer a bit more accuracy (i know some widow players did this a while back), but u will be giving up the faster flick speed for it and it might make flicking up close challenging. I tried both, and found using the xim aux was better for me personally since it fit my playstyle (aggressive flank style), but if ur more of a sniping widow sitting in the back then u might find the in game scoped sens to be better. I suppose if u really wanted to, u could use some math to find a good middleground value using the aux and ingame sens multipler combined, that way u could keep relatively fast flicks while gaining a bit of accuracy This probably most likely isnt needed though, just throwing it out there if anyone wants to try it!

[Boomboks]

Yup, exactly what i do too. You can try using the hero sensitivity multiplier in game instead since I think it would offer a bit more accuracy (i know some widow players did this a while back), but u will be giving up the faster flick speed for it and it might make flicking up close challenging. I tried both, and found using the xim aux was better for me personally since it fit my playstyle (aggressive flank style), but if ur more of a sniping widow sitting in the back then u might find the in game scoped sens to be better. I suppose if u really wanted to, u could use some math to find a good middleground value using the aux and ingame sens multipler combined, that way u could keep relatively fast flicks while gaining a bit of accuracy This probably most likely isnt needed though, just throwing it out there if anyone wants to try it!

This is also a good method if you want to have widow and ashe on the same aux. Set the aux to 0.614 of your hip sens, and then go in game and lower the widow scope sens to 73.6%. You wont be able to flick as fast on widow but your ashe and widow sens will feel close to 1:1 on the same aux

[Malinkadink]

I think its easier to just have multiple configs in xim. I use the F keys to swap between configs and just color code them ie purple xim lights = widow/ana, red = ashe

[GoodAimButATankMain]

I think its easier to just have multiple configs in xim. I use the F keys to swap between configs and just color code them ie purple xim lights = widow/ana, red = ashe

This can work too, but the disadvantage to this is u need the app open to swap config's, and if u have many config's it could get confusing trying to swap between them. If u dont mind swapping config's, then u can do this, but if u get annoyed with it or if u flex and play multiple different heros, it can be easier just to have a sniper contig, and a normal config that will work with everyone All down to personal preference.

[GoodAimButATankMain]

Yup, exactly what i do too. You can try using the hero sensitivity multiplier in game instead since I think it would offer a bit more accuracy (i know some widow players did this a while back), but u will be giving up the faster flick speed for it and it might make flicking up close challenging. I tried both, and found using the xim aux was better for me personally since it fit my playstyle (aggressive flank style), but if ur more of a sniping widow sitting in the back then u might find the in game scoped sens to be better. I suppose if u really wanted to, u could use some math to find a good middleground value using the aux and ingame sens multipler combined, that way u could keep relatively fast flicks while gaining a bit of accuracy This probably most likely isnt needed though, just throwing it out there if anyone wants to try it!

This is also a good method if you want to have widow and ashe on the same aux. Set the aux to 0.614 of your hip sens, and then go in game and lower the widow scope sens to 73.6%. You wont be able to flick as fast on widow but your ashe and widow sens will feel close to 1:1 on the same aux

Also, if anyone is wondering how he came up with 73.6%, you simply divide the widow 1:1 sens (.452), by the ashe 1:1 sens (.614), which gives you .736, or 73.6%. If any new scoped heros come out in the future, u can use this same thing again to find what the relative aim sensitivity is suppose to be This means that when using 100% ashe relative aim sensitivity, and an aux set to .614 your normal sensitivity, u can swap to widow using the SAME aux and still keep the 1:1 movements as long as your widow relative aim sensitivity is set to 73.6% (this also works with ana, since widow and ana have the same exact scope movements)

[Addytoostrong]

In theory the same aux for widow and ashe makes sense. However, without a delay you'll have awkward interactions every now and then. Delay for widow is 330ms and delay for ashe is 250ms. Would this interfere?

[Addytoostrong]

Also, read something showing high aaw with high aaei being a new thing in linear especially. 100 aaei feels trash in 20 window but because the aaei doesn't have time to do what its meant to in such a small window. I plan on experimenting with 70 aaw and 100 aaei tomorrow morning to see the results. Right now 20 window with 60 aaei seems to feel good then it starts to have issues on consistency. Showing what we've all known. I don't think the xim or set up is ever the issue, the issue is ow aim settings.. having 5 different options and each option changing the aim assist so much, I bet even the developers don't know the amount of holes or issues within their own system. On controller I was still a top widow on Xbox but I remember even then some days high aw and some low aw. Now worth aaei out adds just another layer on top of an already flawed layer of settings. Idk why instead of making set AA windows and just allowing us to adjust strength, they just continued to add more settings.

[GoodAimButATankMain]

Yeah, the deactivation delay can be wierd, but u can get used to it imo. And i think adding more setting's is always a good thing in my opinion as long as people have the time to adjust them.

[Malinkadink]

I think its easier to just have multiple configs in xim. I use the F keys to swap between configs and just color code them ie purple xim lights = widow/ana, red = ashe

This can work too, but the disadvantage to this is u need the app open to swap config's, and if u have many config's it could get confusing trying to swap between them. If u dont mind swapping config's, then u can do this, but if u get annoyed with it or if u flex and play multiple different heros, it can be easier just to have a sniper contig, and a normal config that will work with everyone All down to personal preference.

No need to have the app open, on the first config page you can set a hotkey to swap to that config on the fly i use the F1-F12 keys for this.

[GoodAimButATankMain]

Hmm, maybe im doing something wrong then? I have a samsung galaxy s8, and i have the same hotkeys too, but it only swaps when i have the app open.