Jump to content

Uac20 Do Not Fire All The Time


11 replies to this topic

#1 Serpentbane

    Member

  • PipPipPipPipPipPip
  • Overlord
  • Overlord
  • 485 posts
  • LocationVanvikan, Norway

Posted 08 June 2015 - 08:00 AM

A little to often I experience my UAC20 not fireing. No, it's not a jam. It just do not fire... It's random, and I'm not able to reproduce in testing grounds.

Some times I fire once, but the 2nd round dont work. Some times I cant fire at all for 3-8 sec +-

Edited by Serpentbane, 08 June 2015 - 08:35 AM.


#2 Night Thastus

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 825 posts

Posted 08 June 2015 - 08:36 AM

If you can't reproduce it in testing grounds, I'd imagine you:
1: Ran out of ammo
2: Are trying to use a weapon that got destroyed in battle either by losing that section of the mech or by a critical hit.

#3 Serpentbane

    Member

  • PipPipPipPipPipPip
  • Overlord
  • Overlord
  • 485 posts
  • LocationVanvikan, Norway

Posted 09 June 2015 - 12:24 PM

View PostNight Thastus, on 08 June 2015 - 08:36 AM, said:

If you can't reproduce it in testing grounds, I'd imagine you:
1: Ran out of ammo
2: Are trying to use a weapon that got destroyed in battle either by losing that section of the mech or by a critical hit.

Well, as I’m not a total noob I can assure you that I;
1: did not run out of ammo.
2: did not loose any of those AC’s.

Also, the guns are ready to fire, no jam, no cool down, just not working.

I engage an enemy mech and start shooting, intending to lay down volleys of UAC20 rounds, and I know how to time them. However, some times during engagement the guns just stops firing. Some times one of them, sometimes two. Sometimes the gun do not fire at all, sometimes the first volley is ok, but the 2nd fails.

We’re talking seconds of failure here, but during engagement this can be critical, it’s not like I'm able to break off and run with the DWF. Instead I’m left there as one of the largest sitting ducks available in this game, with perhaps 1/3 of my potential damage output.

I do how ever have a feeling this usually happens during engagement where I’m taking fire myself, but then again it might just be so that I usually shoot at enemies while they shoot back.

I only have this problem with the UAC20, I have not tested the others lately. All other weapons are fine. All other games are fine. And I have not reproduced this in testing grounds.

At first, I thought I messed up my timing or that I tried shooting before the weapon had cooled down. But I have tried paying extra attention to my weapon status when this happens, and everything looks ready.

#4 jaxjace

    Member

  • PipPipPipPipPipPipPip
  • The Merciless
  • The Merciless
  • 987 posts
  • LocationIn orbit around your world

Posted 09 June 2015 - 12:48 PM

I thought i was the only one. Yea im gonna say its a bug. I think its because the UAC is actually supposed to jam that often but the animation doesn't display. sucks.

#5 Omi_

    Member

  • PipPipPipPipPipPip
  • The Blade
  • 336 posts
  • LocationWinnipeg, Manitoba, Canada

Posted 09 June 2015 - 01:56 PM

Can confirm that once in a while, UACs seem to get stuck in a jammed state without any bells or whistles to explain it. Not sure how to reproduce.

#6 Koniving

    Welcoming Committee

  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • The Guide
  • The Guide
  • 23,384 posts

Posted 09 June 2015 - 01:57 PM

View PostNight Thastus, on 08 June 2015 - 08:36 AM, said:

If you can't reproduce it in testing grounds, I'd imagine you:
1: Ran out of ammo
2: Are trying to use a weapon that got destroyed in battle either by losing that section of the mech or by a critical hit.

There's a third option.

At really high pings, there are times when the command to fire is lost or there is a large delay (sometimes up to 3 seconds) between when you try to fire and when it actually happens, even if the weapon was ready to fire at the time you pressed it.

#7 Iqfish

    Member

  • PipPipPipPipPipPipPipPipPip
  • 3,488 posts
  • Google+: Link
  • LocationGermany, CGN

Posted 09 June 2015 - 02:05 PM

Same here but with UAC5 in IS mechs. Does not show the jammed splashscreen, ping is 110-130, Germany.

#8 Myfriendscallmecoach

    Member

  • PipPipPip
  • The Messenger
  • The Messenger
  • 63 posts

Posted 09 June 2015 - 02:08 PM

Same for me as well. Thought at first it was my mouse.

#9 Russhuster

    Member

  • PipPipPipPipPipPipPip
  • The Ominous
  • The Ominous
  • 722 posts
  • LocationBayern

Posted 09 June 2015 - 02:18 PM

Same Prob with UAC20s the weap is not usable at this state

#10 Bilbo

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • The Nimble
  • The Nimble
  • 7,864 posts
  • LocationSaline, Michigan

Posted 11 June 2015 - 08:28 AM

View PostKoniving, on 09 June 2015 - 01:57 PM, said:


There's a third option.

At really high pings, there are times when the command to fire is lost or there is a large delay (sometimes up to 3 seconds) between when you try to fire and when it actually happens, even if the weapon was ready to fire at the time you pressed it.

I had this happen to me a few times in a single match last night with an AC/20 on my Atlas. 1st time I just thought I might have tried to fire it before the cooldown. Second and third time I actually tabbed to check my ping and it was still at 36 where it tends to always be so I have no idea where the clicks ran off to.

#11 B L O O D W I T C H

    Member

  • PipPipPipPipPipPipPipPipPip
  • 2,426 posts

Posted 11 June 2015 - 09:23 AM

Happened on my uac20. first i thought i was unlucky and it jammed a bit to often. then i payed close attention to the weapon hud. seems that the UAC is green but doesn't fire or at least doesn't response to doubletap. 130 ping btw.

#12 Summon3r

    Member

  • PipPipPipPipPipPipPipPipPip
  • 2,291 posts
  • Locationowning in sommet non meta

Posted 11 June 2015 - 11:44 AM

i find they fire ok but literally jam 95% of the time, atleast on my summoner





2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users