THEY FIXED IT!!!
Any chance this will be fixed in the June 26th update?
THEY FIXED IT!!!
Yes!! Great job everybody. Thanks Ataashi
t's fixed!!! Thanks! 🙂
Fixed on my end too! One guy commented on a post I made on r/starwarsbattlefront saying he still has issues. I'll pass on the info once I get it but the issue is resolved for me! Good job DICE and the mod who speedily brought it up to the dev team!
EA Staff (Retired)Hey everyone!
I'm glad to see you all happy after the fix for this issue got released 🙂 Once again, apologies that it took such a long time 😳
@RC-3197 if you will have any details about this player's problem with the reticle, please share them here or simply redirect them to me. Thanks!
/Ataashi
@EA_AtaashiI thought it was solved (all yesterday after the update was fine) but I'm having this issue again today.
Just joined a Capital Supremacy game on Kamino, zoomed in, aim reticle wasn't there just like before.
Then I died, respawn and it was back on.
I'll update you if it does it again
I confirm it's still happening, less frequently but it happens.
Capital Supremacy, different maps.
Today 3 times in less than 10 minutes.
This forum should have an undo function for the Solution Label (if it doesn't already). I came here thinking this was a solved issue but it seems it isn't. Unfortunately I never play with these weapons, and rarely I play with trooper classes, so I've never seen this BUG myself.
Can anyone record this BUG after the June 26th patch update and bring this footage here?
If there aren't enough people reporting the issue they won't do anything about it. I just gave up and replaced the improved zoom with explosive shots.
Happens to me every game (capital supremacy), not only with the DC-15LE but with the FWMB-10K with night vision mod as well. It is really annoying.
I want to thank you for pushing to get this fixed initially.
I do not remember the exact date of the patch, but there was a brief period (about a week or so) before the June 26th “Where are those Droideka’s?” update that this bug was 100% consistently fixed on the XboxOne.
Unfortunately, the June 26th update somehow reversed the patch, and this bug is now back and just as bad as it was before.
I was frustrated after the fix ended up being so short lived and just took a break from the game for a while, but I wanted to come back to this thread to report that the June 26th update was what somehow unfixed this bug.
Really hoping you can figure this one out someday... Eventually if this thread can’t get any momentum because it reads as “Fixed” I will start a new thread for this issue.
