Jump to content

Gauss Cannon Not Registering Damage


7 replies to this topic

#1 pjnt

    Member

  • PipPipPipPipPipPip
  • Philanthropist
  • 425 posts
  • LocationDetention Block 23, Death Star

Posted 20 November 2012 - 12:00 AM

Hey. First off, please leave out the, you missed or you didn't see this comments. Or comments on the Gauss cat build. Cheers.

Just played 10 games with my Gauss cat and in half I point blanked a shutdown mech for no damage. The sparks showed up but nothing registered on the hit mech. A raven at 10 meters took 2 alfa strikes to the cored CT with no damage. A friend I was with took 2 dual Gauss hits to his Catapults ear and it did nothing. Again though, we see the impact sparks, just nothing is registering.

Is this a bug? Hit boxes? Netcode? Obviously the collision is being registered by offering me the lovely impact explosions, but why is no damage corresponding to the hit?

I've shelved my GaussCat. Was this the purpose? Not saying its a conspiracy but everything was fine 3-4 days ago and noobs were falling like leaves.

#2 Elizander

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 7,540 posts
  • LocationPhilippines

Posted 20 November 2012 - 12:06 AM

View Postpjnt, on 20 November 2012 - 12:00 AM, said:

Just played 10 games with my Gauss cat and in half I point blanked a shutdown mech for no damage.


Happens to me all the time with shot down light mechs. :)

I meant shut (can't edit at work stupid filter)

#3 CheeseThief

    Member

  • PipPipPipPipPipPipPip
  • Liquid Metal
  • Liquid Metal
  • 580 posts
  • LocationBeyond the Black Stump

Posted 20 November 2012 - 12:08 AM

The netcode sucks and the hitboxes don't line up with the models.

You pretty much need to spray the landscape with laser fire and watch the reticule to see where you hit them, and then you need to hope that it's a stable connection so the lead distance doesn't fluctuate.



Also the game does everything server side, so nothing you see on your end means a thing unless it's the little crosshair flashing, because thats the server telling your machine that you've got a hit.

Edited by CheeseThief, 20 November 2012 - 12:10 AM.


#4 pjnt

    Member

  • PipPipPipPipPipPip
  • Philanthropist
  • 425 posts
  • LocationDetention Block 23, Death Star

Posted 20 November 2012 - 12:31 AM

OK. Then these are just bugs that need fixing. Lets hope they get fixed sooner rather than later, I'm getting frustrated :)

Thanks for the replies.

#5 lsp

    Member

  • PipPipPipPipPipPipPipPip
  • Veteran Founder
  • Veteran Founder
  • 1,618 posts
  • LocationCA

Posted 20 November 2012 - 12:46 AM

It happens from time to time. It's not often enough to make a thread about. I've been using GR on my drg for months, and it hasn't been that bothersome.

#6 Ashan

    Member

  • Pip
  • 14 posts
  • LocationPoland

Posted 20 November 2012 - 12:57 AM

Yeah, this has been happening to me since way in the closed beta. It seems to be the worst when I shoot both gausses at the same time - often neither of them will register. Conversely, shooting them one at a time and waiting 2-3 seconds before firing the other seems to lessen its occurence (doesn't eliminate it).

#7 Desicator

    Member

  • PipPip
  • The 1 Percent
  • The 1 Percent
  • 34 posts
  • LocationOhio

Posted 12 January 2013 - 07:09 PM

Same. I just had a match where i shot an atlas from 50m dead in the back with 2 double guass salvos(no armor was on his back) an not a single one registered......very frustrating.

#8 Five oh Five Squat

    Member

  • PipPip
  • 41 posts
  • LocationFlorida

Posted 12 January 2013 - 07:46 PM

Bad code is more likely. But to simulate tabletop rules doesn't every shot have a chance to miss/glance off no matter the range? It would be interesting if they had a calculation like that on top of having to aim. :pgi:





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users