3 replies to this topic

[Sneaky Ohgoorchik]

Every time im using mrm build on any mech, it shows heat unproperly. My mechs just keep overheating at 40-70% (depends on build), while im shooting mrms. It looks like heating from mrms not shown while it fires with other weapons simultaneously. Its not ghostheat (i have mrm30x2 at most, never use mrm40), it just shown wrong.Today i died of heat while overheating, while it shows like 50% heat (2mrms30+2LL build). Please, somebody, fix it. Two patches pass, and it still there.

Edited by Sneaky Ohgoorchik, 21 December 2017 - 07:42 AM.

[Koniving]

Reporting it to players isn't going to do anything. You need to report it to support.

You should also keep track of what time you were playing the match (roughly), what mech, the loadout, and any information possible.

Go to here, and copy the link to "Technical" and give the feedback there with "MRM Overheat bug".

To mention it: 2 MRM-30s do not produce ghost heat but if they are chained fired they easily can and will produce ghost heat.
At 18 heat, this is usually 30%+ heat per volley, depending on your heatsinks and skill tree. So four times in a row will probably overheat you.

[epikt]

Koniving, on 21 December 2017 - 12:21 PM, said:

To mention it: 2 MRM-30s do not produce ghost heat but if they are chained fired they easily can and will produce ghost heat.

No they can't.
Their cooldowwn is 4.3s so you'll need 9 of them "chained" (with a macro, because the in-game chain fire will never produce ghost heat) to fall below the ~0.5s limit of ghost heat.

Anyway, if I understand correctly it's not a problem of ghost heat, but of overheating before hitting the 100% mark. It happenned to me before, without MRMs (edit: actually it was on last year word championship client).

Edited by epikt, 22 December 2017 - 08:08 AM.

[Tarl Cabot]

epikt, on 22 December 2017 - 08:06 AM, said:

No they can't.
Their cooldowwn is 4.3s so you'll need 9 of them "chained" (with a macro, because the in-game chain fire will never produce ghost heat) to fall below the ~0.5s limit of ghost heat.

Anyway, if I understand correctly it's not a problem of ghost heat, but of overheating before hitting the 100% mark. It happenned to me before, without MRMs (edit: actually it was on last year word championship client).

The ISSUE not actually overheating, only the graphical UI interface is not reflecting the actual status. It is the graphic UI not updating correctly even though the server/system knows you approaching overheating, ie Betty warning but the player ignores it/does not pay attention.

The question is the issue within the code itself, or package loss and PGI does not have code in place to verify current IU level?

Also means the more people who report it to PGI, not just on the forums, the possibility of getting it pushed up the ladder.

Edited by Tarl Cabot, 22 December 2017 - 10:52 AM.