i don't understand, the bot for hitscan works great however when i try to use widow it fails me everytime i'm getting silver/low gold results from it, and i've contacted sharpeye about this multiple times already and i cannot get it to work, the results are horrible compared to how 76 tracer sombra and all the other hit scans work in fact i'm more confident playing hanzo then widow, so if anyone can magically help me out and get this to work and have me not be on a 50% rendering that would be amazing
im using a dpi of 800
with 100 fps - 130 fps
1080
with widows scope acc being at a 35
f2,AimKey=1
f2,TriggerKey=2
f2,ScanWidth=80
f2,ScanHeight=70
f2,OffsetLeft=50
f2,OffsetUp=59
f2,TriggerWidth=20
f2,TriggerHeight=40
f2,ToleranceWidth=0
f2,ToleranceHeight=0
f2,MaxSpeed=60
f2,MinSpeed=4
f2,Deceleration=2
f2,InvertedMouse=false
f2,ScreenLock=false
f2,PauseKey=122
f2,HealKey=89
Last edited by Rentaru; 07-29-2018 at 03:15 PM.
Hello everyone,
Wonder if anyone has settings for a 2560x1440 resolution? I tried with support to get to something, but he doesn't have a monitor with that resolution, so can't test it fully.
Thanks
Anyone have good Tracer, Widow or other settings?
I have one.
Edit: Restarting my game fixed it. Weirdest bug.
Anywho.
Tracer:
f3,ScanWidth=90
f3,ScanHeight=50
f3,OffsetLeft=65
f3,OffsetUp=80
f3,TriggerWidth=0
f3,TriggerHeight=0
f3,ToleranceWidth=0
f3,ToleranceHeight=0
f3,MaxSpeed=40
f3,MinSpeed=7
f3,Deceleration=4
Edit2:
900 mouse sense, 9 ingame
Last edited by MisterZeek; 08-01-2018 at 07:42 PM.
Anyone have settings for screenlock? I'm screenlocked and the settings suggested are terrible even with some tweaking. I do better without it and I'm normally silver - gold. If it matters I use a widescreen monitor but set my resolution to 1080 on both OW and my PC.
BIG DISCOVERY
After a lot of testing with the bot, I finally came down to the solution of why the tracking doesn't center properly. It's because ToleranceWidth = 0 doesn't actually work. You need to set it to a minimum of 1. It wasn't a problem with deceleration as I initially thought but with ToleranceWidth = 0.
The setting of Tolerance is also a bit confusing. It is actually the margin of pixels or units that the crosshair is allowed to travel off the center of the offset.
I hope you guys try out the ToleranceWidth = 1 vs 0. It will solve a lot of your issues with tracking if this particular has been affecting you as it has been affecting me for a long time.
Last edited by Shostak; 08-02-2018 at 11:51 AM.
Height works as intended. Honestly 0 ToleranceWidth must've been a huge headache for a lot of people. It needs to be fixed or at least explained in the settings guide
Last edited by Shostak; 08-02-2018 at 03:31 PM.
Other than ToleranceWidth 0, it does work the way I think it does. It provides a margin of tolerance, measured in scale of units/pixels, around the offset that the crosshair can roam. ToleranceHeight 0 does work. It locks on dead center on the offset locations.
Last edited by Shostak; 08-02-2018 at 06:44 PM.
Had you explained at the time that ToleranceWidth 0 doesn't work as it seems and that it needs to be set at 1 that would've been more helpful than being vague
Can somebody please explain to me how offsets work/some good offsets?? Thanks!
ToleranceHeight/Width operate the exact same. Both could be set at 1/1 for the "most accuracy" but it'll shake it's ass off and get you called out in no time.
No point in arguing with that Fact. :P
You could always email us at support for an explanation instead of expecting one on OC *Shrug*
"May all your bacon burn"
That's not the issue I was speaking of. The issue is that ToleranceWidth = 0 is bugged, so it needs to be set at 1, whereas ToleranceHeight = 0 is working as intended and does not need to be set at 1. It's not about making settings for a legitimate looking crosshair. It's about the fact that ToleranceWidth = 0 doesn't work.