69 replies to this topic

[pwnface]

Ghogiel, on 19 February 2016 - 02:18 AM, said:

Could be everything on the HUD can take 2secs to update with the server.

Pretty unlikely for there to be a 2 second hiccup. That is a really long time. It also happened twice back to back, it's too big of a coincidence..

[Appogee]

Paigan, 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.

Me too. And it's software developers who use excuses like "gosh coding is really hard" and "I'm using agile development techniques" to do poor quality work and release buggy products that drives me crazy.

But if you're going to sit there on your island and hold up PGI as a case study in quality control, then we're going to need a whole new tribe of hula girls to keep you company.

Paigan, on 19 February 2016 - 01:53 AM, said:

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

My advice is: stop making excuses for shoddy software development. You'll stay employed longer if you don't make mistakes in the first place.

Edited by Appogee, 19 February 2016 - 03:24 AM.

[Lily from animove]

Ghogiel, on 19 February 2016 - 02:18 AM, said:

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.

I thouhgt so too, but wouldn't this mean when he is coming back that the heat would be shown correctly I doubt he really cooled off 50% heat in this short time. Seems to be a bit more buggy than juts client-server delay.

@Paigan softare when games weren't available online was odften WAY better because patching was nearly impossible afterwards, so its clearly a decision to have less proper testing between finidhing coding and bringing the software live.

Seems to be, especially in gaming, a very often used and condoned behavior. But if you wer einvolved into Software development where its about REAL BIG money and you have custoemrs with SLA contracts then you would surely not get such a lazy testing. If we would make such a "quality" here where I work we could close already due to SLA violations.

Edited by Lily from animove, 19 February 2016 - 02:30 AM.

[Ghogiel]

pwnface, on 19 February 2016 - 02:22 AM, said:

Pretty unlikely for there to be a 2 second hiccup. That is a really long time. It also happened twice back to back, it's too big of a coincidence..

hiccup? All dmg updating on the paper doll takes at least 1 sec even with 100ms ping, so it's very much within the realm of possibility that the server is tracking heat build up generated on your mech from other players, ie not your own heatgen at a similar delay. The server could have just had his heat at 90% when he fired.

[Karamarka]

MikeBend, on 19 February 2016 - 02:16 AM, said:

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

edit: silly me, cant even post a picture

yup happened to me too.

Nova with 6ml and 6 flamer just insta heat you in 1 second and you have zero recourse but run away... like an i-win button in 1v1

[Ghogiel]

Lily from animove, on 19 February 2016 - 02:24 AM, said:

I thouhgt so too, but wouldn't this mean when he is coming back that the heat would be shown correctly I doubt he really cooled off 50% heat in this short time. Seems to be a bit more buggy than juts client-server delay.

Not at all. That could what the actual bug is.

[Widowmaker1981]

Karamarka, on 19 February 2016 - 02:29 AM, said:

yup happened to me too.

Nova with 6ml and 6 flamer just insta heat you in 1 second and you have zero recourse but run away... like an i-win button in 1v1

Pssssh.

SCrow with 6 Flamer pack in the right arm and ASRM24 with 6 tons of ammo and 4 extra DHS. King of 1v1.

[Lily from animove]

OP, mage a bug report in the bug section about this, . It's pGI's job to investigate this further.

[pwnface]

Ghogiel, on 19 February 2016 - 02:29 AM, said:

hiccup? All dmg updating on the paper doll takes at least 1 sec even with 100ms ping, so it's very much within the realm of possibility that the server is tracking heat build up generated on your mech from other players, ie not your own heatgen at a similar delay. The server could have just had his heat at 90% when he fired.

Plenty of people have been testing the new flamers and nobody else is noticing this "delay".

I'm pretty sure the paper doll is designed to not try to instantaneously update, it's always a second later in my experience.

However, from testing flamers over the past 2 days heat generation seems to be instantaneous.

Widowmaker1981, on 19 February 2016 - 02:49 AM, said:

Pssssh.

SCrow with 6 Flamer pack in the right arm and ASRM24 with 6 tons of ammo and 4 extra DHS. King of 1v1.

Or you can just headshot people like Mcgral18.

[Mcgral18]

pwnface, on 19 February 2016 - 02:51 AM, said:

Or you can just headshot people like Mcgral18.

Sader was #10 successfully headshot due to a Flamer induced Coma....though I've since modified to ERMLs and 5 Flamers due to the infuriating sub 300M tickle range (even though it was good there). Wondering if the burn time will cause me to be worse, even with the +6 damage.

Incidently, without cause to close, I've only used the Flamers twice since changing...I haven't thought this through, it seems.

[Ghogiel]

pwnface, on 19 February 2016 - 02:51 AM, said:

Plenty of people have been testing the new flamers and nobody else is noticing this "delay".

I'm pretty sure the paper doll is designed to not try to instantaneously update, it's always a second later in my experience.

However, from testing flamers over the past 2 days heat generation seems to be instantaneous.

That just says you haven't encountered this bug. There is definitely some mis communication from the server and client going on. It seems much more unlikely to me that the PGI code with flamers is triggering powerdown initiation from the reciever of flamers than it is the server telling the player it has overheated but simply has issues updating that fact to the player getting cooked.

[pwnface]

Mcgral18, on 19 February 2016 - 02:56 AM, said:

Sader was #10 successfully headshot due to a Flamer induced Coma....though I've since modified to ERMLs and 5 Flamers due to the infuriating sub 300M tickle range (even though it was good there). Wondering if the burn time will cause me to be worse, even with the +6 damage.

Incidently, without cause to close, I've only used the Flamers twice since changing...I haven't thought this through, it seems.

I'm betting you'll find the short beam duration of SPLs make it easier to headshot. Come drop with us sometime Mcgral18!

[Troutmonkey]

Appogee, on 19 February 2016 - 02:24 AM, said:

Me too. And it's software developers who use excuses like "gosh coding is really hard" and "I'm using agile development techniques" to do poor quality work and release buggy products that drives me crazy.

But if you're going to sit there on your island and hold up PGI as a case study in quality control, then we're going to need a whole new tribe of hula girls to keep you company.

My advice is: stop making excuses for shoddy software development. You'll stay employed longer if you don't make mistakes in the first place.

Another dev here chiming in. MWO has many bugs that would have been avoided with proper coding and QA. Like the random command bug that went unfixed for 3 years even though it would have been a 15 minute fix. Yeah, priorities I get that, but for 2 years no bugs got fixed at all.

[627]

hmm, looks like the coolshot wasn't calculated in or so...

[STEF_]

TBH, HUD bug or not hud bug, it is frankly STUPID overheating as soon as flamers touch a mech.

[oldradagast]

Stefka Kerensky, on 19 February 2016 - 04:06 AM, said:

TBH, HUD bug or not hud bug, it is frankly STUPID overheating as soon as flamers touch a mech.

It is, but we all know how PGI likes to create random, nutty, unbalanced new metas with broken weapons and leave them that way for months or years... unless it's LRM's - those get nerfed down to nearly useless in a day... but stun-locks are okay and "good for the game" or some crap.

[Widowmaker1981]

Stefka Kerensky, on 19 February 2016 - 04:06 AM, said:

TBH, HUD bug or not hud bug, it is frankly STUPID overheating as soon as flamers touch a mech.

Its the age old problem. 1 or 2 flamers is fine and working as intended, but when you boat 6 or more of them the heat gen is crazy town.. which is a big buff to clans actually since it gives an actual viable use for those 6E arms that some mechs have, where IS have to make actual sacrifices to mount 6 flamers, clans really dont.

Flamer heat gen cap of 9 or 13.5 h/s?

[STEF_]

Widowmaker1981, on 19 February 2016 - 04:17 AM, said:

Its the age old problem. 1 or 2 flamers is fine and working as intended, but when you boat 6 or more of them the heat gen is crazy town.. which is a big buff to clans actually since it gives an actual viable use for those 6E arms that some mechs have, where IS have to make actual sacrifices to mount 6 flamers, clans really dont.

Flamer heat gen cap of 9 or 13.5 h/s?

I haven't changed my builts yet, but reading your post ... strangely I was thinking about the crow....
Because doing stupid things sometime can be fun

(still thinking that the instaoverheat sounds a bit weird, tho...)

[CDLord HHGD]

Mcgral18, on 19 February 2016 - 01:52 AM, said:

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)

Holy f*ck.....

On one hand I am glad they are viable weapons now.

On the other... Holy f*ck....

Let me see if I can squeeze a flamer or two on some of my support mechs....

[KodiakGW]

I agree, looks like a new bug. Hopefully they will get this fixed before next patch. MRBC league play starts in 2 weeks. They may have to declare "no flamers" as a new rule.

Who would have thought, having to consider denying use of flamers in league drops.