Noticed this when i missed like 5 hits on a ulting Mccree… Just dont have the recordings since i’ve never bothered with stuff like that in the 1st place. But i did a little digging after that game and i noticed a lot of people complaining about this issue on reddit and the US forums.
Made the video start at 01:30 (and is about 30 sec long) since its was painfully obvious at that case and its the only clip relevant to this topic.
The same thing happened to me in my game.
So far the only video i found on this matter.
https://www.reddit.com/r/Overwatch/comments/9xveoi/does_ashe_aim_feel_off_to_anyone_else/
https://www.reddit.com/r/Competitiveoverwatch/comments/9ya6y0/ashe_appears_to_have_input_lag_when_shooting_ads/
3 Likes
To me it looks like she is shooting projectiles that are just too fast.
Something similar to battlefield sniper for example but faster.
Whoever that might not be the case.
noticed the same thing, there are times when i could have sworn i should have hit a headshot and its just a miss. theres even been a few times when it feels like i should probably have missed but its a hit. feels pretty weird to fire in the general direction of your target and realise the moment you fire its a miss, but then its actually a headshot. cant say i have noticed the same with other heroes.
1 Like
also, i dont know it that could be hardware problem with my mouse, but does anyone have pretty unreliable quickshots, i pres rclick, and than leftclick and it doesent register it like 1/4 of the time
I think the devs altered something on the sly with her.
Originally I was hitting a lot of headshots with her, headshots that I felt shouldn’t have been and now I have the issue of missing a lot of shots that look like they should have hit.
Never had this problem and I’ve played her 20 hours
This didn’t made it in the live patch or something? Still have shots that don’t register sometimes, like when i’m at range and started shooting at a Rine with shield down nothing was hitting him…, this doesn’t happen often but geez at times it’s hard to determine whether its my aim or this glitch but at some cases it was its more then clear, this doesn’t happen when i’m on Widowmaker the aiming feels so clean on her wish they carry that to Ashe or tell us that she’s not hit scan or something. Because it doesn’t feel right.
See this is really curious to me. I’m a mccree main who plays a bit of Widow. I’m trying to transition to Ashe for more point control and cause her wr is like 5% higher than mccree lol and her damage numbers are much better. But when I play mccree or widow I almost never have bs shots. I never really feel like I shoulda hit something but didn’t. When I play Ashe I’m feeling that twice a minute, especially when going for heads. It’s hard to compare to mccree as he’s unscoped and it’s mostly instinct to click heads at long range but Idk why I can tell when I should hit as Widow or Mccree but Ashe constantly surprises me.
I see lots of people who swear she’s incredibly inconsistent and then lots of people who experience no problems with her. Is it maybe a hardware thing? What are your fps, latency, dpi, ingame sensitivity and monitor hz if you don’t mind me asking? I’m trying to see if there’s a common trend in players that aren’t seeing ‘missed shots’ issues
144Hz, 144 fps capped, 30 ping, 600 dpi, 3,5 in game mause speed, 35% relative scope sense.
1 Like
Do you know if the scoping animation is still 60fps limit or did they fix that?
My set up is lower end than that but not in a way that would make me think there’s an obvious reason why Widow and Ashe feel so differently for me in terms of hit detection.
Idk what my relative Ashe sensitivity is but 35 seems low. What is your widow sensitivity? Only other thing I can think of is possibly render scale or overall game image quality being possible factors. I have 75% and low what about you?
My ping is higher too but it’s all hitscan. Ping shouldn’t make two hitscan snipers feel different in terms of aim detection lol.
Thanks for the info btw
The same but with lower relative scope @ 25% on Widow, if i copy my Widow relative scope acc onto Ashe she feels much slower then Widow.
1 Like
All the Ashe fixes dont see this thou.
“Unfortunately, right now, the patch that it is fixed in is 1.32 (1.31 is on the PTR right now).” Guess it will take one more patch sicne we are on 1.31 live.
Ashe
- Fixed a bug that caused Ashe’s Dynamite to create a second small explosion visual effect a few moments after the first explosion
- Fixed a bug that prevented Ashe’s Dynamite from playing its fire visual effects on enemy abilities (e.g. Junkrat’s Steel Trap or Mei’s Ice Wall)
- Fixed a bug that prevented Ashe’s Dynamite from exploding if it fell into small gaps
- Fixed a bug that caused Ashe’s scoped view to stutter on a high refresh rate monitor with a high framerate
- Fixed a bug that prevented spectators from seeing enemy outline’s through Ashe’s scope
- Fixed a bug that caused Ashe to see Zarya’s Project Barrier visual effects when Bob was the ability’s target
- Fixed a bug that caused Bob to slip off Mei’s Ice Wall
- Fixed a bug that allowed Bob to push Bastion in Sentry mode when hit by his charge
- Fixed a bug that prevented a charging Bob from opening the airlock doors on Horizon: Lunar Colony
- Fixed a bug that caused Bob elbow to briefly disappear when waving
- Fixed a bug that caused Bob to continuously charge into a small piece of collision instead of stopping
- Fixed a bug that prevented Ashe’s Coach Gun from displacing breakables on maps
