292 replies to this topic

[Rashhaverak]

Hammerfinn, on 15 May 2013 - 10:47 AM, said:

Yes. That's a zoom-module bug, not a HUD bug.

I'm not using the zoom module. I'm just zooming in regular x3.

[Hammerfinn]

Rashhaverak, on 15 May 2013 - 10:49 AM, said:

I'm not using the zoom module. I'm just zooming in regular x3.

The hud-bugs referenced here refer to disappearing or malfunctioning HUDs from match start. The minimap pointing the wrong way, no IFF indicators ever, no target reticules, etc.

So it's a zoom (module or not) bug. Have you submitted a report ticket?

[Belorion]

Zaptruder, on 15 May 2013 - 09:33 AM, said:

Nope. I'm a designer. But hey, if it's possible to provide a work around, do that first!

I suspect that reinitializing the HUD would be akin to reloading the map entirely... so I guess that would go back to the, let players reconnect to a game problem that hasn't been dealt with yet.

The upside to the reconnection function is that it'll have applications and use even after the disconnects and stability issues are quashed (because after all, a good number of those issues are player side issues, even if network code stability and robustness can still be improved on the server side).

In one of the post about reconnecting it was stated that it is something they would like to do, but that being able to reconnect present a set of technical hurdles. It could very well be that your work around is more difficult than the actual fix for this particular issue.

These things take time.

[Rashhaverak]

Hammerfinn, on 15 May 2013 - 10:51 AM, said:

The hud-bugs referenced here refer to disappearing or malfunctioning HUDs from match start. The minimap pointing the wrong way, no IFF indicators ever, no target reticules, etc.

So it's a zoom (module or not) bug. Have you submitted a report ticket?

Interesting. So if I am walking around on tourmaline like I just was, and the IFF on a friendly mech keeps going in and out with the terrain, like it's an enemy versus being a friend, and it happens when I'm zoomed in or out, and there is not any enemy ECM in sight because the game just started... what would that bug be classified as?

[Michael Costanza]

Remind me to stick to my Visual Basic and SQL world at $80k a year...

[Belorion]

Michael Costanza, on 15 May 2013 - 11:18 AM, said:

Remind me to stick to my Visual Basic and SQL world at $80k a year...

Sounds like a fate worse than death...

<~ is not a fan of VB.

[Volt Corsair]

So the balance of that tree resided soley on reu- for ****'s sake CryTek.

Edited by Volt Opt Construct, 15 May 2013 - 11:24 AM.

[Belorion]

Rashhaverak, on 15 May 2013 - 11:04 AM, said:

Interesting. So if I am walking around on tourmaline like I just was, and the IFF on a friendly mech keeps going in and out with the terrain, like it's an enemy versus being a friend, and it happens when I'm zoomed in or out, and there is not any enemy ECM in sight because the game just started... what would that bug be classified as?

Have you run the repair tool on your install?

[Karl Berg]

Mike Forst, on 14 May 2013 - 01:37 PM, said:

Yep. Karl has been on MWO from the start.

Just to clear up this misconception, this is true; I've been with Piranha for close to three years now in fact. I was originally brought on to help port Duke to PS3. My normal MWO stomping grounds involve extending and maintaining the distributed server architecture that the game and website run on top of, as well as assisting with systems level issues/features in the game and engine.

[Vasces Diablo]

You forgot the part about sacrificing chickens and calling on the great old ones....

This was fantastic, and I only realllllly understood about half of it (I manage IT projects, but am not a developer myself). As others have said, can we just repost this every time someone complains that bug fixes/development isn't fast enough?

...now we just need to wait for the people who want to know much of their money was spent on this, claim it was too much, and say they should get and MC refund.

[Void Angel]

I understood about half of that, but it simply underscores what I keep on yelling at the Professionally Dissatisfied: this stuff is fracking complicated, and PGI's doing a good job of dealing with it.

[Shumabot]

Karl Berg, on 15 May 2013 - 11:56 AM, said:

Just to clear up this misconception, this is true; I've been with Piranha for close to three years now in fact. I was originally brought on to help port Duke to PS3. My normal MWO stomping grounds involve extending and maintaining the distributed server architecture that the game and website run on top of, as well as assisting with systems level issues/features in the game and engine.

Karl Berg, on 15 May 2013 - 11:56 AM, said:

Just to clear up this misconception, this is true; I've been with Piranha for close to three years now in fact. I was originally brought on to help port Duke to PS3. My normal MWO stomping grounds involve extending and maintaining the distributed server architecture that the game and website run on top of, as well as assisting with systems level issues/features in the game and engine.

Could you tell us what the priority for this issue looked like over the past few months? Was it a background issue until tools were developed to deal with it? Did players start encountering the issues more than previously which forced fixes to be expedited? Did staff free up from other development projects and were moved into this nagging issue as able?

[Zphyr]

Just reading it give me headaches from imagining all the wall punching and coffee to stay awake enough to track down the problem... exactly where one would not think it would be.

[Tickdoff Tank]

That was impressive.

I am a medical professional, a paramedic for about 15 years (and a pretty dang good one, at the risk of sounding arrogant) and I can relate to the difficulty in explaining the problem and the solution to laymen. I have often tried to explain what is wrong with someone to another individual that simply does not understand what I am trying to say.

I only hope that I can explain medical issues as well as you explained the bug squashing process. I may not have understood everything that you wrote (or even half!) but I can certainly appreciate the difficulty and dedication that you had.

Outstanding job on a "non-trivial task"

[IceSerpent]

Vasces Diablo, on 15 May 2013 - 12:11 PM, said:

You forgot the part about sacrificing chickens and calling on the great old ones....

You don't talk about Great Old Ones...at least not in public.

[Red squirrel]

There is nothing comparable to the satisfaction of finding bugs in other peoples code.

[Targetloc]

Quote

This definitely threw away all concept of strict-weak ordering.

[Felicitatem Parco]

Red squirrel, on 15 May 2013 - 02:10 PM, said:

There is nothing comparable to the satisfaction of finding bugs in other peoples code.

Finding faults in their lab protocols before they actually perform the experiment

[Chrithu]

I don't know if it is good or bad that I actually understood all of what Karl did explain here.

Sounds like one of those debugging nightmares, where you verify your own stuff over and over based on the fact that you trust on third party code to be tested and flawless, only to find that one should never trust in code provided by others to be free from error.

Nevertheless: Glad you finally found the root of all evil and removed it.

Also for me as a hobbyist programmer articles like that are a fun read and I encourage the team to keep writing such whenever the situation allows for it.

[WVAnonymous]

Karl, if I see you in a drop on the other side, you can have one free shot at me. If you're on my side, I'll try to take one for you.