Jump to content

Flamers Are Either Broken Or This Guy Is Cheating.


69 replies to this topic

#1 Sader325

    Member

  • PipPipPipPipPipPipPipPip
  • 1,181 posts

Posted 19 February 2016 - 12:54 AM

Someone explain to me this footage. Watch it very carefully.




So either the last hotfix broke flamers, or this guy is cheating.

#2 Mcgral18

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPip
  • CS 2019 Top 8 Qualifier
  • CS 2019 Top 8 Qualifier
  • 17,987 posts
  • LocationSnow

Posted 19 February 2016 - 01:10 AM

Tee Hee...
I was called a (possible) cheater


As to Why you overheated? Probably a glitch. The SRMs were only bringing you up ~30%, so overheating at 50% makes little sense.
Maybe related to coolshot not registering. Your JJs alone would only cancel your dissipation.

Edited by Mcgral18, 19 February 2016 - 01:48 AM.


#3 Tarogato

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Civil Servant
  • Civil Servant
  • 6,558 posts
  • LocationUSA

Posted 19 February 2016 - 01:14 AM

I wonder if this is related to my mech automatically shutting down at 98% all the time...

#4 Appogee

    Member

  • PipPipPipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 10,967 posts
  • LocationOn planet Tukayyid, celebrating victory

Posted 19 February 2016 - 01:15 AM

It wouldn't be the first time a hotfix needed to be hotfixed.

But we can't complain about quality control at PGI. Because basically, there isn't any :)

Edited by Appogee, 19 February 2016 - 01:15 AM.


#5 Johnny Z

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Knight Errant
  • 9,942 posts
  • LocationDueling on Solaris

Posted 19 February 2016 - 01:31 AM

Same thing happened to me once so far. Except my mech instantly shut down on contact with the flamer. The guy then ran away and stopped attacking me. This was before the hotfix.

Also one time my mech just went boom without taking a hit. My mech had a red side torso but it didn't take a hit. I put it down to some extremely serious lag. Both within the last 3 days. Other than that the matches have been great aside from players doing 20 damage in matches and no penalty.

Edited by Johnny Z, 19 February 2016 - 01:34 AM.


#6 Sagamore

    Member

  • PipPipPipPipPipPipPip
  • The Blood Bound
  • The Blood Bound
  • 930 posts
  • LocationCanada

Posted 19 February 2016 - 01:33 AM

Until I rebound my keys, I accidentally hit "P" while trying to hit "O" a few times. That was unfortunate.

As your video, that does seem odd. I'd chalk it up to the flamer rework. Mcgral is a good shot and knows his stuff. He's no cheater.

#7 Johnny Z

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Knight Errant
  • 9,942 posts
  • LocationDueling on Solaris

Posted 19 February 2016 - 01:37 AM

The video looks like lag of some sort, but definitely a problem.

#8 Kin3ticX

    Member

  • PipPipPipPipPipPipPipPipPip
  • The People's Hero
  • The People
  • 2,926 posts
  • LocationSalt Mines of Puglandia

Posted 19 February 2016 - 01:43 AM

you were 90% cooked by flamers but it didnt reflect that in your hud

#9 Juodas Varnas

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 7,537 posts
  • LocationGrand Duchy of Lithuania

Posted 19 February 2016 - 01:47 AM

And here i thought PGI couldn't break the flamers any more than they were.


PGI does love surprising us, don't they? Posted Image

#10 Johnny Z

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Knight Errant
  • 9,942 posts
  • LocationDueling on Solaris

Posted 19 February 2016 - 01:48 AM

View PostKin3ticX, on 19 February 2016 - 01:43 AM, said:

you were 90% cooked by flamers but it didnt reflect that in your hud


Yep that's what it looks like. I had another fight with a flamer mech and it went all good. He kept me at 90% and I just used 2 medium lasers to fight back. That Nova looks really OP being able to shut down a mech like that and still do massive damage.

+1 for removing coolshot from the game.

Edited by Johnny Z, 19 February 2016 - 02:09 AM.


#11 MrMadguy

    Member

  • PipPipPipPipPipPipPipPipPip
  • 2,307 posts

Posted 19 February 2016 - 01:50 AM

Same happened with me yesterday: met at least 2xFlamer TBR, shot AC/2 - overheated instantly. I told you, that Flamers are broken, but you didn't believe me.

Edited by MrMadguy, 19 February 2016 - 01:52 AM.


#12 Mcgral18

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPip
  • CS 2019 Top 8 Qualifier
  • CS 2019 Top 8 Qualifier
  • 17,987 posts
  • LocationSnow

Posted 19 February 2016 - 01:52 AM

https://youtu.be/s8tRwricsAU?t=1m6s

There's what 3 Flamers does to a normal 10 TrueDub mech (using JJs would make that go faster, as it almost cancels your dissipation)

Edited by Mcgral18, 19 February 2016 - 01:55 AM.


#13 Paigan

    Member

  • PipPipPipPipPipPipPipPipPip
  • The Blazing
  • The Blazing
  • 2,789 posts

Posted 19 February 2016 - 01:53 AM

View PostAppogee, on 19 February 2016 - 01:15 AM, said:

It wouldn't be the first time a hotfix needed to be hotfixed.

But we can't complain about quality control at PGI. Because basically, there isn't any Posted Image

If I may: I'm a software developer myself and spiteful ignorance like that drives me crazy.

Let me tell you, how it really is:

Software is incredibly complex. Spaceshuttle-start-like complex.
Changing or extending it is similarily complex.
If a developer changes something, there are bugs, yes.
Say for a major change, there are 100 bugs (against like 1000 lines of code that work perfectly fine on the first attempt. Already an incredibly good performance from the developer there.)

At first the developer tests himself ("most" of the time) and finds and fixes, say, 50 bugs on his own.
Very good and thorough developers maybe find 70 or 80 bugs (just fictional figures here).
QA then does its testing.
Depending on how good everyone is, something between 80 and 95 bugs are found.
Or maybe 96. Or maybe 97 if you're lucky.

So customers like you (like "us" here) only see 3-5 from originally 100 bugs.
Of course 3 out of 3 bugs are 100%.
You ALWAYS see 100% of all the bugs you see.
That does NOT mean there was no quality control at all. That's a perception thing, not a measurement of code quality.
"Almost all" bugs were long fixed before you ever had a chance of encountering them.
And nobody is perfect.

Personally, I'm amazed how GOOD the quality management in PGI is.
Patches run smoothely and quickly 99% of the time.
I have hardly any client crashes.
I hardly ever disconnect.

If I compare it with Eve-Online, for example:
They have a daily downtime of 1 hour because they are too stupid to get their memory leaks fixed at least back when I played.
Patches take HOURS over HOURS just to deploy, even AFTER they did all the testing.
Their client hangs up on a regular basis even in character creation (i came back last year to toy around with it and the client is still HORRIBLE, even after ... 15 years or so)


So, my advice: If you don't know what you're talking about, just don't say anything in the first place.

Edited by Paigan, 19 February 2016 - 01:59 AM.


#14 pwnface

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 3,009 posts

Posted 19 February 2016 - 02:00 AM

View PostSader325, on 19 February 2016 - 12:54 AM, said:

Someone explain to me this footage. Watch it very carefully.






So either the last hotfix broke flamers, or this guy is cheating.


Maybe he was stream sniping you. Posted Image

Really though, there seems to be a new bug. Probably a HUD glitch with the flamers maybe caused by cool shot. Alternatively, it could be something not related to the HUD at all?

Someone should probably try to reproduce this in private lobbies.

Edited by pwnface, 19 February 2016 - 02:01 AM.


#15 MrMadguy

    Member

  • PipPipPipPipPipPipPipPipPip
  • 2,307 posts

Posted 19 February 2016 - 02:04 AM

View PostPaigan, on 19 February 2016 - 01:53 AM, said:

If I may: I'm a software developer myself and spiteful ignorance like that drives me crazy.

Let me tell you, how it really is:

Software is incredibly complex. Spaceshuttle-start-like complex.
Changing or extending it is similarily complex.
If a developer changes something, there are bugs, yes.
Say for a major change, there are 100 bugs (against like 1000 lines of code that work perfectly fine on the first attempt. Already an incredibly good performance from the developer there.)

At first the developer tests himself ("most" of the time) and finds and fixes, say, 50 bugs on his own.
Very good and thorough developers maybe find 70 or 80 bugs (just fictional figures here).
QA then does its testing.
Depending on how good everyone is, something between 80 and 95 bugs are found.
Or maybe 96. Or maybe 97 if you're lucky.

So customers like you (like "us" here) only see 3-5 from originally 100 bugs.
Of course 3 out of 3 bugs are 100%.
You ALWAYS see 100% of all the bugs you see.
That does NOT mean there was no quality control at all. That's a perception thing, not a measurement of code quality.
"Almost all" bugs were long fixed before you ever had a chance of encountering them.
And nobody is perfect.

Personally, I'm amazed how GOOD the quality management in PGI is.
Patches run smoothely and quickly 99% of the time.
I have hardly any client crashes.
I hardly ever disconnect.

If I compare it with Eve-Online, for example:
They have a daily downtime of 1 hour because they are too stupid to get their memory leaks fixed at least back when I played.
Patches take HOURS over HOURS just to deploy, even AFTER they did all the testing.
Their client hangs up on a regular basis even in character creation (i came back last year to toy around with it and the client is still HORRIBLE, even after ... 15 years or so)


So, my advice: If you don't know what you're talking about, just don't say anything in the first place.

Depends on quality of code. If it's cattle-code, full of crutches and supports - then yes, you are right. But if code is good - then it should start working almost immediately.

#16 pwnface

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 3,009 posts

Posted 19 February 2016 - 02:05 AM

View PostMister D, on 19 February 2016 - 02:01 AM, said:

When you lost your Torso, you lost enough of your heatcap from engine DHS loss to throw you into shutdown.

The first overheat is sketchy, but the second shutdown makes sense.

Its a plague of Clan mechs since they changed what happens when Clan mechs lose a torso.

You may very well have not been overheated at the moment before your torso blew, but the instant it was gone you were screwed, if you had been in override mode, it would have been instant death most likely and he wouldn't even have had to shoot you.

Especially bad in the case of the Shadowcat, you probably had none or very few added DHS, so your total heatcap was even lower making the percentage lost even stronger.


This is wrong, he overheats the second time before the torso is popped.

#17 Cyborne Elemental

    Member

  • PipPipPipPipPipPipPipPipPip
  • 4,000 posts
  • LocationUSA

Posted 19 February 2016 - 02:07 AM

You're right, looks like a new bug.

#18 pwnface

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 3,009 posts

Posted 19 February 2016 - 02:11 AM

View PostMister D, on 19 February 2016 - 02:07 AM, said:

You're right, looks like a new bug.


Already tweeted at Russ. I hope they spend some time to investigate it tomorrow. Maybe some players will have time to try to simulate this in private lobbies also. After all, we are the QA team right? @Mcgral18 @coel7 @Wintersdark @Deathlike who wants to try to figure out what is causing this? For serious though, some of us ought to get paid for this.

#19 MikeBend

    Member

  • PipPipPipPipPipPipPip
  • Bad Company
  • 536 posts
  • LocationUnderhive

Posted 19 February 2016 - 02:16 AM

Here is the screenshot - look at the heat bar, as it shuts down....

edit: silly me, cant even post a picture :)


Posted Image

Edited by MikeBend, 19 February 2016 - 02:17 AM.


#20 Ghogiel

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • CS 2021 Gold Champ
  • CS 2021 Gold Champ
  • 6,852 posts

Posted 19 February 2016 - 02:18 AM

Could be everything on the HUD can take 2secs to update with the server. Your info isn't quite what the server is seeing in addition to the regular bugginess of MWO. Or the fact flamers have known bugs in addition to the know bugginess of MWO. Especially with this area of MWO> hit reg, updating with server and the HUD. But yeah shutting down at 52% is borked.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users