

#21
Posted 08 September 2023 - 08:12 AM
#22
Posted 05 August 2024 - 03:42 PM
Atlas Warlord; Red-Orange CT, no armor, entire dual ER LL burst into his CT
no damage

Edited by VaelophisNyx, 05 August 2024 - 03:43 PM.
#23
Posted 07 August 2024 - 02:15 AM
i just chalked it up to the usual bugs instead of any kind of cheating. (though i never completely rule out Cheating as we all know it does happen)
#24
Posted 07 August 2024 - 09:43 AM
VeeOt Dragon, on 07 August 2024 - 02:15 AM, said:
i just chalked it up to the usual bugs instead of any kind of cheating. (though i never completely rule out Cheating as we all know it does happen)
I think lights not taking damge from thunderbolts at close range has been an issue since their introduction(have seen it come up more than once). Tbh haven't used them much myself but in testing grounds they don't seem to lower in time to make contact. So u have to add this ontop of the games hit detection issues
#25
Posted 07 August 2024 - 12:24 PM
Edited by VeeOt Dragon, 07 August 2024 - 12:25 PM.
#26
Posted 07 August 2024 - 12:45 PM
North America, European, Oceanic?
I forget the command line, but there is a way to traceroute your connections as your ISP hops from server to server to get better data about your net stats between your ISP and the Mechwarrior server, or any server for that matter.
#27
Posted 08 August 2024 - 06:08 AM
VeeOt Dragon, on 07 August 2024 - 02:15 AM, said:
some friends have gone into small 2v2 matches and such and tested, they feel they've determined that the issue is mech dependent. certain mechs firing thunderbolts will glitch and miss targets while other mechs seem to be glitch free. i called BS, but they showed me the recorded streams and it seems legit.
#28
Posted 08 August 2024 - 09:13 AM
Stewbawl, on 08 August 2024 - 06:08 AM, said:
some friends have gone into small 2v2 matches and such and tested, they feel they've determined that the issue is mech dependent. certain mechs firing thunderbolts will glitch and miss targets while other mechs seem to be glitch free. i called BS, but they showed me the recorded streams and it seems legit.
Would your friends be willing to share the recorded streams, and inform PGI about their findings ?
Edited by Besh, 08 August 2024 - 09:13 AM.
#29
Posted 08 August 2024 - 05:53 PM
#30
Posted 09 August 2024 - 04:57 PM
Stewbawl, on 08 August 2024 - 06:08 AM, said:
some friends have gone into small 2v2 matches and such and tested, they feel they've determined that the issue is mech dependent. certain mechs firing thunderbolts will glitch and miss targets while other mechs seem to be glitch free. i called BS, but they showed me the recorded streams and it seems legit.
my main TB mech right now is the Nightstar- Wolf Phoenix. its missile mounts are very high mounted. thats the mech i was having the issue hitting the lights with. can't remember the mechs i was having trouble hitting but i think one was Flea.
#31
Posted 10 August 2024 - 10:51 AM
#32
Posted 08 November 2024 - 05:54 PM
#33
Posted 08 November 2024 - 09:24 PM
Something is seriously broken!!!
This is even happening on direct hits. I hit a mech 3 times in a row with PPCs and zero damage is registering
#34
Posted 09 November 2024 - 11:20 AM
reflectorjones, on 08 November 2024 - 09:24 PM, said:
Something is seriously broken!!!
This is even happening on direct hits. I hit a mech 3 times in a row with PPCs and zero damage is registering
PPC hit registration is known to be unreliable sometimes.
#35
Posted 09 November 2024 - 05:10 PM
but its very pronounced certain times during game play. dealt with this over the years.
A recent experience, demonstrated how bad it can be. was in a vindicator, and confronted a stone rhino, it nailed me with a full alpha. after the confrontation i expected, to be near cored. however looking at the paper doll i still had armor on my ct.
i knew i had taken the brunt of his all his guns. but some how his damaged was nullified.
Now,
If this had been the dragon i usually pilot, it would have been cored. or its side blown off. i know this from repeated experience.
#36
Posted 07 December 2024 - 08:59 AM
Krashbox, on 08 August 2024 - 05:53 PM, said:
I hate when my PPC bolt or Gauss Rifle round "sneaks" between the enemy 'Mech's arm and torso.

#37
Posted 07 December 2024 - 09:13 PM
VaelophisNyx, on 05 September 2023 - 12:34 PM, said:
so I put 200 RAC 5 rounds into it at point blank range
and he....took 0 damage!
anyone else ever seen this happen?
(He was also their last surviving man, and highest damage dealt in the match!)
yes I have seen it a lot
nothing I can do about it
#38
Posted 09 December 2024 - 09:32 AM
He had killed 4 of us, all of the dead were onhis hands as he cleaned up those damaged and open armor folks who wandered through his firing line, fell but in doing so indicated his position ... and it should have wrapped up well, but instead he killed the other two lights who went in to kill him and when I got in to shoot him, after dumping my own artillery strikes (the other lights had previously dropped theirs in the same place with him) his paper doll still showed him un-damaged - but with a ping around 30, according to one of the dead lights checking, cause he was crying foul. He also claimed that the ping was reading something like four or five digits at one moment, so that might support "lag", desync, or periodic packet loss from that player.
I jumped and twisted and ran up and down angled rock outcropings shooting at this jaeger, with my lasers, hitscan machine guns and arty strike all on target while he was lighting me back up too and parts of my mech were disintigrating. Dropped off the rock to avoid my own strike and saw it flash red - assumed it did damage to the enemy, since all the lights were dead, I was out of the way and the heavys/assaults were 400 meters away angling to shoot up at him. When I returned to the top of the rock to harrass him some more, it was like he was still undamaged, his ecm still painting him as some superman jaegermech of incomparable density. Alphas seemed to score on him, my reticle went red - but his paperdoll never seemed to update and hitting the same area my 30pt alphas had hit before like side torsos and arms still did not pop them... slight updates would rubber band him ten meters left, or to a spot higher up a rock incline as more arty strikes came in and then he was somewhere else on the other side of a wall on a different perch near this same outcropping in center of tourmaline. Arty strike killed me about then. Was not a team kill, so it must have been his... bravo.
Watching on more, in the same peanut gallery as the other three lights, I watch super jaeger continue to receive punishment from about 8:03 til 14:07 when he kills my last teammate. This was not a case of a light pilot running circles around befuddled assaults, etc., it was just the most annoying and convenient de sync I'd ever seen on behalf of an enemy pilot/enemy team. Yeah, like everyone going through what you expect to be a win being a loss I was taken aback- it smarts a bit, even more when you're like WTF, what am I even seeing and you watch the person coming out of it with an ace of spades or death star level of match.
I can't really say what I saw. At the precise moment we were shooting and hitting, it looked on our ends/screens always like we were hitting and having reticles go red. At the end of the match, the last person to have a view/lock on the jaeger, which obviously DOES NOT have an ecm, showed the jaegermech in question to be pretty evenly yellow damage over his entire mech armor with a few orange areas and red. All from glancing laser burns I imagine. But in cases of what was experienced on our client sides, we were still mechs, looking at things like still target or torso twisting target, dumping 6 er medium laser burns into arms and side torsos, or center torso rear. It was lights with AP Gauss, dropping 28 point warthog broadsides into same jaeger, none of which registered. Some sort of desync between where our machines say WE were pointing and the other guy's machine said HIS mech was resulted in this.
I know I was always told that the netcode of the game pays attention to where our player side aiming was more or less, so if on my client I saw a fast running locust, and fired and hit it's legs or put a laser burn mostly in front of his legs and across his legs, that is going to be updated by the server authorative nature of the netcode to count against the target. But if the target is so far out of sync with the server that his machine is saying no, no, no - that mech isn't actually there where those bullets hit, the pilot hit reverse or turned left or right or put on masc... I got that those sorts of things could make a slight level of desync that make us miss occassionally, where the server and our clients just won't reconcile and tell the target they were hurt.
This must have been that, but to the worst degree I've ever seen without it actually looking like the enemy mech was spazzing out, teleporting or as people used to accuse "haxing". A desync/lag that really really really sucked for us.
(Addendum: You guessed it, we missed that there was an ecm locust up there too, which is why a jaeger had ecm. We had thought the locust dead much earlier in the match, legged, but it crawled up in the perch with the jaeger and had been giving him cover and a bit of support no one ever saw coming. Even with all the arty strikes it stayed alive and somehow at very end, when there was an accounting of all mechs and the locust was dead, so people could see the paper doll easily of the jaeger to see how un damaged he was, it was a surreal experience and aggravating because ecm cannot account for the super jaeger at all.)
Edited by Mad Porthos, 09 December 2024 - 09:54 AM.
#39
Posted 09 December 2024 - 05:45 PM
#40
Posted 09 December 2024 - 05:47 PM
10 user(s) are reading this topic
0 members, 10 guests, 0 anonymous users