17 replies to this topic

[Igor Draskovic]

You need to understand how broken this game really is. Check this out:

I just played a game with my double AC/20 jagger. I encountered two mechs. The first was a stalker that I cored out with five hits from my cannons. Second encounter was a raven. A one on one battle insures. First salvo, direct hit. No components blew off. I thought, "ok, his armor must be full". Second salvo, direct hit. Nothing. Third, forth....and so on. A duel lasts about 2 full minutes until I run auto of ammo and he cores me out with his ML's.

I looked at the scored board and it indicated I did 327 damage. So, this means that my five hits caused 200 damage to the stalker. This leaves 127 points of damage dealt to the raven which he somehow survived.

[LtZerge]

Damage registration does seem wonky some of the time, but keep in mind it's rare you properly nail a raven with both AC20s. The convergence when leading usually means you hit with one and then one shell barely misses, especially given how far apart your cannons actually are on a jager. Obviously not a problem against bigger slower targets. Sounds like you're getting hits with half your rounds and the damage was spread, ravens with max armor can take a beating.

Any indication on what his paper-doll looked liked after that brawl?

[TheGreatNoNo]

Had a one on one brawl where I did 423 damage to a dragon and his armor was orange once, but that was once. Aside from that I have notice people receiving little damage taken but the end of match damage being high, so something is pretty damn off. There was also that one time where I legged a raven with lasers then belched 180 srms into him before the srm nerf and he still lived just fine, in fact he was about to kill me.

I say that because there is this lovely little glitch where I fire my SRMs but they do not render or sound off on my screen but I use ammo and build up heat and the enemy which I believe would have been hit by them takes no damage, so am I firing them or am I not? Been getting that glitch A LOT more then what I used to.

[Purplefluffybunny]

I have also noticed issues with ballistics post-rewind. That said I kinda expected to see some of them return given that they were there pre the latest tinkering (rewind not included of course!).

Edited by Purplefluffybunny, 29 April 2013 - 06:05 AM.

[aniviron]

Ballistics state rewind is not working as intended (or at least, it had better not be). There are still lots and lots of duds going on. OP, I advise you to check your crosshair instead of the visual impact. The impact means nothing; the only confirmation of a hit is the crosshairs turning red. If they do not turn red, you didn't hit, even if you should have and there is a huge explosion on the other person's mech.

[Deathlike]

HSR in general is working, but not in the way that you would anticipate.

Compare two players... one that has low latency (50ms) and one that has mediocre latency (250ms).

Let's say you are the one with 50ms in a Dragon, and your target is a Stalker with the 250ms ping.

You are shooting at the Stalker, and let's say you decide that you are shooting the mech's CT. On your screen, you might actually be shooting into the CT (it's not that hard, despite their side torsos) and it probably hits where it should more often than not.

As with most dragons, they like to hit and run, so let's say you never really turn your back to the enemy, but probably half your mech facing perpendicular to the Stalker, lowering your profile size a bit. What happens on your enemy's screen, since the updates are more delayed is that you are turning your back more to enemy, so it fires into your back, and your back suddenly takes damage.

So, like most people, you go, WTF?!?!?!

That is HSR.. there a technical "disconnect" to what you see and what is actually happening. I still see Gauss Rifles and PPCs still missing me (including lasers) despite those projectiles hit me... whereas there are other instances where these weapons are "missing me" according to my screen, but my paperdoll says I'm actually taking damage.

The network code is probably doing what it is should, but the client code isn't "correcting" the visual representation of the what you see is what you shoot.... which actually is more like, where your enemy is shooting at is not necessarily what you are seeing.

[Kiiyor]

I'm ping challenged, and HSR works perfectly for me. Makes the game far more playable. I've noticed very occasional wierdness in hit registration, but nothing that makes me scratch my head. Maybe you should submit a support ticket in the off chance it has something to do with your client.

[TheGreatNoNo]

I don`t think that is the case for my missing SRMs, but probably would be the case for the God mode raven.

[Rackminster]

Last night I was in my Catapult K2 and running a new build. River City. We went high and took the upper city across the bridge and I was playing peek-a-boo with hostiles. I kept getting shot but not getting hurt. At one point I stopped trying to duck back into cover and just stayed out in the open. I wasn't taking damage.

I then proceeded to walk down into the furball and started chasing down hostiles and crushing them.

Ended the match with 4 kills, 2 assists, and zero damage taken.

[TheGreatNoNo]

Probably out of range.

[TOGSolid]

Igor Draskovic, on 28 April 2013 - 03:58 PM, said:

You need to understand how broken this game really is. Check this out:

I just played a game with my double AC/20 jagger. I encountered two mechs. The first was a stalker that I cored out with five hits from my cannons. Second encounter was a raven. A one on one battle insures. First salvo, direct hit. No components blew off. I thought, "ok, his armor must be full". Second salvo, direct hit. Nothing. Third, forth....and so on. A duel lasts about 2 full minutes until I run auto of ammo and he cores me out with his ML's.

I looked at the scored board and it indicated I did 327 damage. So, this means that my five hits caused 200 damage to the stalker. This leaves 127 points of damage dealt to the raven which he somehow survived.

It's been noticeably weird today. I, and all my corpmates were commenting that we were seeing an unusually high amount of ballistic shots just completely fail to register like in the bad old pre-HSR days.

I'm theorizing that something goofy was going on with the servers today. If this behavior persists through tomorrow then I highly suggest everyone send in a support ticket so that PGI is aware of what's going on. Things were working fine post patch and then suddenly went apeshit today for an unknown reason.

[3rdworld]

Hits often don't register to the enemy, but I believe they are still added to your total damage.

[Rackminster]

Lost One, on 29 April 2013 - 02:33 AM, said:

Probably out of range.

No way. I'm talking about a Stalker shooting Lasers at me from 300m away, a Hunchback shooting AC's at me from the same, and me getting right in a Highlander's face and him not being able to hurt me. I was chasing him through the streets, past his own team, to kill him. No one could touch me.

Either everyone on their team was absolutely terrible for aim, or I was invulnerable. I literally ended the round with 100% pristine armor. Nothing had even turned yellow.

Edited by Rackminster, 29 April 2013 - 05:22 AM.

[Ralgas]

delayed reaction from the servers, or fluctuating ping.

I've had second+ delays on killshots post ballistic hsr, it's just the server lolcats taking a cheezburger break from scaring the hamsters.....

and if your ping is not stable (which could be a net problem at either end or anywhere in between and could even come down to server load) it actually makes things worse.......

Essentially you just have to pray to the net gods on the day

[H Seldon]

Yeah, I notice weird things too. Had a highlander hitting me with ppc (poptarting of course). I was in a highlander too and I was perpendicular to him while running to cover. All shots registered on my CT. Would have thought LA/LT would be getting hit, but not once. Also had times where I'm behind cover but still taking damage. Other times shooting a side torso weapon, it hits the building I'm next to (worse with arm mounted weapons), but then I take a shot from an enemy in the same torso. Very strange stuff.

[MeiSooHaityu]

Not just ballistics.

I have been using a Splatcat for a few days and they are USELESS against lights. If a light is moving, you simply can't damage it with missiles (even though you are registering direct hits on your screen). Nothing is more frustrating then launching 6 SRM4s with Artemis into a light and seeing his armor flash and not change color hit after hit while you are slowly being cored by their Streaks.

It sucks when a light's missiles work and yours don't

[Neverther]

The targeting reticle turning red with ballistics does not necessarily mean a hit.
Ive had bot the reticle turn red and impact on target, but paperdoll showed no damage.

Laser hit detection is wonky at least, firing a a spider (5K) with bright red internals on RA and RT, CT and entire left side has armor on yellow.
Fire two MPLs at his right torso while he is pretty stationary (and Im missing a leg). Hits detected on RA and LT (LT taking most of the damage judging by the color change) and then the spider took out my other leg with 4MGs.
Got this recorded.
Submitted a report to support on similar case where I was receving the fire. Also happened then other side of mech was fine and other was on internals

Other time I remeber encountering a dragon and a treb in the beginning of match, fired and they died pretty quick, managed just to start recording before the dragon died. No damage to armor at all, all shots went straight to internals on both mechs.

[Purplefluffybunny]

Look, the most recent iteration of the ballistic code, the one that has be 'rewound', was an attempt to fix all the weirdness that we are experiencing now?

Thing is I see the velocity and engine caps, collision and the mech knock down mechanics AND these changes with the ballistic code as indicative of the wider problems and limitations, with the net code more generally. It is not a good sign.

Edited by Purplefluffybunny, 30 April 2013 - 04:29 AM.