137 replies to this topic

[Hotthedd]

Paul Inouye, on 19 July 2016 - 03:32 PM, said:

Looking into this.

Just remember, the only change made to the C-UAC10 is the amount of extra heat generated through HeatScale. That being said, if the double tap is now registering extra heat, that is a bug and will be fixed asap. It could have been the case all along, just that the C-UAC10 wasn't spiking heat like it is now. Either way... being actively investigated.

My single biggest gripe in MW:O is the feeling that the MW:O forums are ignored by PGI. (and perfect convergence).

Thank you, Paul, for the very timely response! Little things like this can go a very long way to help this game survive.

[John1352]

Templar Dane, on 20 July 2016 - 12:13 AM, said:

There is no penalty for firing 2x UAC10. At least there isnt' supposed to be. There is, however, a penalty on firing 2x UAC20. If you double tap a UAC20 there would be ghost heat if what you say is true, yet there isn't.

With the UAC20, the behavior seems to be different in testing grounds/academy vs in matches. Stick some extra ammo on and have a mess around in an actual match. Ping may influence this as well, if you can't reproduce on one server, try a further one.

Edited by John1352, 20 July 2016 - 07:43 AM.

[Metus regem]

Templar Dane, on 19 July 2016 - 11:20 PM, said:

I checked single UAC20 double taps and did not see ghost heat so I believe that's fine, but 2x UAC10 is registering ghost heat pretty much every double tap.

You can trigger ghost heat on the UAC/20 if you double tap with in the window of .5 seconds, it's tricky to do, but it can happen. This .5 second window is the window in the code of MWO that is considered simultaneous fire by the system.

[Templar Dane]

John1352, on 20 July 2016 - 07:42 AM, said:

With the UAC20, the behavior seems to be different in testing grounds/academy vs in matches. Stick some extra ammo on and have a mess around in an actual match. Ping may influence this as well, if you can't reproduce on one server, try a further one.

I mostly play FW and have played thousands of matches. Every mech in my invasion dropdeck has a UAC20. I've probably double tapped a million times and have not seen ghost heat on a double tapped UAC20.

[Paul Inouye]

Mister Blastman, on 19 July 2016 - 05:23 PM, said:

Double-tapping a single UAC/20 has the bug, too, FYI last time I checked.

Yes it would. The investigation/solution is still being performed from engineering. There's a lot of 'tricky' legacy code in there but the fix will be a little tricky. The intent and design is that the 2nd tap of a UAC should not be triggering HS. It's firing multiple of the same weapon that will. Essentially, it's about the number of weapons be fired, not how the double tap works that will trigger HS.

Still no ETA yet but it is an active task that is still being directly worked on as of this writing.

[Gas Guzzler]

Paul Inouye, on 20 July 2016 - 10:05 AM, said:

Yes it would. The investigation/solution is still being performed from engineering. There's a lot of 'tricky' legacy code in there but the fix will be a little tricky. The intent and design is that the 2nd tap of a UAC should not be triggering HS. It's firing multiple of the same weapon that will. Essentially, it's about the number of weapons be fired, not how the double tap works that will trigger HS.

Still no ETA yet but it is an active task that is still being directly worked on as of this writing.

That is great to hear.. I have been aware of this but I thought it was intentional.

[Chuck Jager]

What it feels like is happening is the coding for each pellet has part of the heat and possible GH applied. The multiplier is not being split properly along each pellet.

OF course what I read in the notes was a fix in the way the GH is applied, but what I see is a raise in the modifier. So it is hard to say if it is really just a huge raise in the GH penalty that we are not used to. So was the wording in a fix really the implementation of a significantly higher scale to fix a problem.

[L3mming2]

Paul Inouye, on 20 July 2016 - 10:05 AM, said:

Yes it would. The investigation/solution is still being performed from engineering. There's a lot of 'tricky' legacy code in there but the fix will be a little tricky. The intent and design is that the 2nd tap of a UAC should not be triggering HS. It's firing multiple of the same weapon that will. Essentially, it's about the number of weapons be fired, not how the double tap works that will trigger HS.

Still no ETA yet but it is an active task that is still being directly worked on as of this writing.

so if i am getting this right, after the fix i will be able to double tap 3 uac10's without ever getting anny GH?

[Templar Dane]

L3mming2, on 20 July 2016 - 10:37 AM, said:

so if i am getting this right, after the fix i will be able to double tap 3 uac10's without ever getting anny GH?

Anything after two.

[Gas Guzzler]

L3mming2, on 20 July 2016 - 10:37 AM, said:

so if i am getting this right, after the fix i will be able to double tap 3 uac10's without ever getting anny GH?

Considering that 3 UAC10s triggers ghost heat, you will get ghost heat. You just won't get ghost heat for firing 6 UAC10s like you would currently for double tapping 3 UAC10s as fast as possible.

[Lily from animove]

EasyPickings, on 19 July 2016 - 02:31 PM, said:

Yep, it's going to turn quad C-UAC-10 KDK-3s into quad C-LBX-10ers.

but thats not as bad as quad UAC10, because saller emchs at soem emdium raneg won't eat as muchd amage in single locations than the UAc 10 did even with the clan UAC stream damage.

[Night Thastus]

Remover of Obstacles, on 19 July 2016 - 09:15 PM, said:

Not any more. No ghost heat makes it the clear favorite. Unless you prefer LBXs.

You don't have to double tap. However, if you choose the CAC10, you get:

1 more slot

Twice as expensive

Longer base cooldown (2.9 seconds versus 2.5 seconds)

Does that sound like a "better" weapon? No. It's still complete ****. None of the CACs are good. Use the UACs instead.

[Sjorpha]

Just want to say big up Paul for communicating.

If that was a common occurrence you'd have a happier community and probably more players too.

Now all I wanna hear is: "we understand Long Tom isn't a sensible mechanic and are replacing it with alternative X"

[Antares102]

Paul Inouye, on 20 July 2016 - 10:05 AM, said:

... but it is an active task that is still being directly worked on as of this writing.

This is really great news. Thank you Paul.
My hope is a hot-fix next week

[Metus regem]

Paul Inouye, on 20 July 2016 - 10:05 AM, said:

Yes it would. The investigation/solution is still being performed from engineering. There's a lot of 'tricky' legacy code in there but the fix will be a little tricky. The intent and design is that the 2nd tap of a UAC should not be triggering HS. It's firing multiple of the same weapon that will. Essentially, it's about the number of weapons be fired, not how the double tap works that will trigger HS.

Still no ETA yet but it is an active task that is still being directly worked on as of this writing.

Thank you Paul, for finally letting us know that this is being looked at, I think a lot of us here wish were not being kept in the dark so much, making us feel like we are ignored.That being said, I know it's tricky communicating with this player base, but it will only get better with more open communication.

[Paul Inouye]

Problem has been resolved. It's going through testing right now. But I cannot say at this point if it will make a hotfix or not. If there is a hotfix, the notification that will be sent out will include if this is part of it or not.

Some clarity: Hotfixes are meant to fix a newly introduced bug or feature breakage. This particular issue (UACs) is more of a "this system has been broken for a long time and now we may have fixed it but it's a far reaching fix beyond just that singular weapon". Normally, unless we were reallllly certain that there are no knock on effects, we would hold this type of fix until next patch. But I've been reviewing this particular fix with the engineers and we are very confident in the change. Keep an eye out for an announcement if we are going to hotfix this.

Thanks for your patience.

[Revis Volek]

Gas Guzzler, on 20 July 2016 - 10:23 AM, said:

That is great to hear.. I have been aware of this but I thought it was intentional.

I was in the same boat, i would have spoke up earlier if i knew this wasnt the way it was suppose to be.

[Tarogato]

Paul Inouye, on 20 July 2016 - 12:21 PM, said:

Problem has been resolved. It's going through testing right now. But I cannot say at this point if it will make a hotfix or not. If there is a hotfix, the notification that will be sent out will include if this is part of it or not.

Some clarity: Hotfixes are meant to fix a newly introduced bug or feature breakage. This particular issue (UACs) is more of a "this system has been broken for a long time and now we may have fixed it but it's a far reaching fix beyond just that singular weapon". Normally, unless we were reallllly certain that there are no knock on effects, we would hold this type of fix until next patch. But I've been reviewing this particular fix with the engineers and we are very confident in the change. Keep an eye out for an announcement if we are going to hotfix this.

Thanks for your patience.

Cheers Paul for the communication. Glad to see a solution worked out so quickly.


Apologies if derailing, but have the engineers looked into why four SRM2 inconsistently produces ghost heat? Support ticket 199117, I had video evidence included.

[Lorian Sunrider]

Paul Inouye, on 20 July 2016 - 12:21 PM, said:

Problem has been resolved. It's going through testing right now. But I cannot say at this point if it will make a hotfix or not. If there is a hotfix, the notification that will be sent out will include if this is part of it or not.

Some clarity: Hotfixes are meant to fix a newly introduced bug or feature breakage. This particular issue (UACs) is more of a "this system has been broken for a long time and now we may have fixed it but it's a far reaching fix beyond just that singular weapon". Normally, unless we were reallllly certain that there are no knock on effects, we would hold this type of fix until next patch. But I've been reviewing this particular fix with the engineers and we are very confident in the change. Keep an eye out for an announcement if we are going to hotfix this.

Thanks for your patience.

+1 on thanks for communicating directly on the forums.

I know we can be a pretty bitter crowd, but communication likes this goes a LONG way, and I just wanted to add my thanks.

PS, If I were you, I would ironically hang a dartboard in your office/at your desk and make sure it's in the camera frame when you take a picture/video. Just to troll the trolls.

[Antares102]

Paul Inouye, on 20 July 2016 - 12:21 PM, said:

Problem has been resolved. It's going through testing right now. But I cannot say at this point if it will make a hotfix or not. If there is a hotfix, the notification that will be sent out will include if this is part of it or not.

It's ok, as long as you got a solution and it gets fixed at least with the next patch.
Thumbs up PGI.