6 replies to this topic

[FunkyT]

Video evidence:

https://clips.twitch...ousDogFutureMan


As seen in the clip, the pilot in question incurred overheat damage while seemingly at 50% of his heat capacity.
The part not shown in the video is him being shortly grazed by a Nova with several flamers. The short exposure brought him up to ~18% heat, after which he continued to fight and end up in the situation shown in the clip.

It seems that being hit by flamers can glitch out your heatscale, incurring false shutdowns and overheat damage or possibly only a false display of your actual heat level.

As seen, this can easily cost you the mech.
PGI, please look into this.


Has anyone else encoutered this issue and can maybe add information?

Edited by FunkyT, 13 August 2017 - 10:38 AM.

[Tarl Cabot]

First, turn off override. Besides the benefit of not shutting down in front of someone else's guns, is there another reason to have override activated? Has the player's mech previously shut down when the heatscale says otherwise?

On the other side is that the issue may be the client's heat scale is not being updated properly due to package loss or said info was not transmitted, but PGI servers are seeing it properly and sending the resulting info to the client, the internal damaging, etc.

[FunkyT]

Tarl Cabot, on 13 August 2017 - 02:51 PM, said:

First, turn off override. Besides the benefit of not shutting down in front of someone else's guns, is there another reason to have override activated?

That is exactly the reason why you activate override. Going to 100% heat, incurring minor to negligible heat damage and still being able to reposition is far more valuable than shutting down immediatly when barely touching 100% and sitting ducks in front of the enemy.


For the rest of the stream the heatscale seemed to work as intended, no unexpected shutdowns or overheat damage. He was playing on the european servers (he's german) and never complained about latency. Furthermore, I could never see any sign of latency related issues during his almost 3hrs of streaming.

The only thing that was different this game was the short run-in with the flamer nova. So the only clue I have is that there was some glitch caused by flamer damage.
Maybe the new flamer nodes can create some unintended interaction causing the heatscale to glitch out? Don't know, this is actually the first time I have seen anything like this.

Edited by FunkyT, 14 August 2017 - 12:07 AM.

[Tarl Cabot]

Get a private lobby and turn off override and drop with those mechs and test it. Is he able to repeat it?

The actual heatscale (not the picture/UI) is working properly or the system would never have said override/shutdown 2x before he spoke up and the mech would never have self-destruct. And even though it kept repeating he continued firing his weapons.

Now the heatscale UI is an approximation of what the server is seeing, provided the client receives that portion of the information. The UI not updating could have been due to packet loss and/or at that time the server itself failed to send the packet.

Someone occasionally reports similar issue with the HS UI visible representation not reflecting properly while receiving the BB voice of overheating/shutdown/etc, but none have attributed the issue to the flamer itself.

He should send in a report it with the video, with date/timestamp.

[FunkyT]

Didn't find any opportunity yet to try and reproduce the error, and I think he didn't try either.

Regardless of the source of the problem, I think this is an issue that needs to be resolved, preferably fast (if possible, of course). Getting grossly false information on your heatscale is nothing you can play around and can easily cost you your mech. In that situation, I don't think anyone could have said how high his actual heat level was. Plus, even if he tried to, it's a very frustrating experience I'm sure.

My theory that the flamers have something to do with it just came from the fact, that the flamer incident happened right before this bug and his heatscale worked perfectly fine up until that point. He already took part in some fighting before that, not getting any false heat warnings.
It also didn't happen again for the rest of the stream, while there was also no other run-in with any flamers.

[Tarl Cabot]

That is why a report needs to be sent, date/timestamp of video, etc. We can post all we want about an issue but they need visual information to help track it down as it may be a hiccup that only happens when x does y @ z time.

[FunkyT]

Alright, for reference: Here is the complete stream where the bug occurred.

https://www.twitch.tv/videos/166698911

He started streaming at 7pm CEST (5pm UTC) on August 13th. Adding up from the time stamp, the match likely happened around 20:20 CEST (18:20 UTC). Hope I calculated that correctly.

The match starts at 1:19:00, the aforementioned run-in with the flamer Nova happens at 1:21:50. What follows is the situation shown in the clip in my first post in here.

Again, nothing like that happened before or after this match during his 3 1/2 hrs of streaming.

Tarl Cabot, on 14 August 2017 - 03:08 PM, said:

That is why a report needs to be sent, date/timestamp of video, etc. We can post all we want about an issue but they need visual information to help track it down as it may be a hiccup that only happens when x does y @ z time.

So how do I send a report? Thought posting it in the Patch Feedback thread would be the closest thing, since there doesn't seem to be a dedicated Bug Report forum.
Any specific Bug Report email adress I have to write at, or something of the likes?

Edited by FunkyT, 15 August 2017 - 10:34 AM.