292 replies to this topic

[MasterBLB]

Excellent work guys.As a programmer I know well what pain in the as.s is debugging a bug with random occurence.
But when you've discovered a way to reproduce HUD issues it was clear the bug's days are counted,as that is almost always a breakthrough in fixing bugs.

Once again,congratulations Karl and don't hesitate to give us similar post regarding other problems you have

Edited by MasterBLB, 14 May 2013 - 11:30 PM.

[Fiona Marshe]

Does this mean that CryEngine are going to pay you for the lost hours in debugging and fixing CryEngine for them?

[debbert]

i survived readin thru that long postmortem. makes me feel i should have paid more attention during programming class.

class job! long and short of it? cryengine was buggy to begin with, and the 3rd party vendor (pgi) was handed a faulty tool.

[MrDrunkenMaster]

Thanks for taking the time to perform such a detailed write up of the issue. I have never seen this from a game company before, for deserve full credit for it. PGI is real short on credibility right now and this has gone a long way to restoring my confidence. Expect to see cash from me coming your way when the fix is in.

[SaRg3nT1]

Hopefully the hud issues are now dead and buried. Can't wait for Dx11.

[twibs]

Well done.

And this is how you communicate with the playerbase. Nothing this detailed and complicated, but something, anything, and we will be that much happier.

I applaud you

[skoot]

I will be copy pasting this thread into every game where someone ******* from now on!

Seriously (another programmer here) great work - that must of been one hell of a relief when you nailed that one down! Congrats guys - beers in Melbourne if you're ever Down Under.

[The Basilisk]

<< Offers a family pack of aspirin
Bugtracing, espetialy in 3rd party modules is the nemesis of every programmer.
I feel deeply for you guys.

[Aim-Bot]

since may patch 7th and hud hotfix no more crashes and bugs here. THANK YOU

[Faithsfall]

Again i have to thank Pgi for one the bug fix which looks like it was a pig to find but also the communication again from you guy's in the last week has been miles better.

So thankyou for this, long may it continue

[ArclightSA]

I'm just going to echo all the other developers who have replied to this post: you guys did a sterling job tracking that down and fixing it. With around 10 years c++ experience, I know that these type of issues - especially memory allocation issues - are a nightmare to find but easy to fix once found.
So, as everyone else has said, fantastic job and great communication on the issue. Keep up the good work!

[KMCA]

Congratulations!

If you posted detailed responses more often maybe you'd see more members of the "whining" community actually support you. See, that wasn't so hard, was it? Yes many members won't understand what was done. (Hell I'm not even sure) but in posting something like this you've reassured many people. Please learn from this experience and keep up the good work.

[Vapor Trail]

Ramien, on 14 May 2013 - 11:22 AM, said:

I'm not sure if Karl's post made me reconsider my chosen field of study (Computer science and software development) or makes me want to do it even more. Either way, an excellent read!

Same here... most of the way through an Associates level degree program for CompSci... and I barely was able to follow the post without getting completely lost.

Does kinda give perspective on exactly how complicated bug crushing gets sometimes though.

[QuaxDerBruchpilot]

I'm proud that I made it to the 5th paragraph until giving up and proceeding to the tl;dr section :-)

There are moments where I begrudge someone for his job. This acutally isn't one of them :-P

For PGI:

Edited by Quax1102, 15 May 2013 - 02:40 AM.

[Fooooo]

Great write up.

Always nice to get detailed insight into how things were / are done, and the difficulties (and joys once finding the problem) in doing so.

Chemie, on 14 May 2013 - 04:36 PM, said:

My take aways:

* "It's complicated" (hence why it took so long)
* It's not our fault (blame cryengine)

However, as others have pointed out, many cryengine games have HUD without issue. Also, for me, this issue started in january. Never saw it in CB or early OB. That tells me you did SOMETHING...not saying it also wasnt the cryegine, but some interaction with how you did things.

As stated before, I just hope ALL HUD issue, like losing friend/foe is fixed too.

Thanks

Whilst I have not noticed crysis 2 / 3 having any of the same hud issues, I'd say that is because they have never used the HUD like MWO is.....afaik, so never run into the problems MWO is.

There is probably other areas where for most games built on cryengine3 atm it never becomes an issue because they also don't really use those areas, or have already modified / used something else for it. (Farcry 3 for example is not exactly running on cryengine3. Its a highly modified version of it and even has a different name.....duro or durant engine or something ?)

[Cest7]

Deep. Anxiously awaiting the hotfix.

[shellashock]

First off, great job on finding the bug, his will make lots of people happy. Second, I hate to spoil the fun, but what are you planning on doing with that case insensitivity issue? Are you going to leave it as is, or will you try to fix it to prevent possible future problems?

[Arcaist]

Wall of text hit critical...

whew....hellofajob to do...

[Nonsense]

Karl: another thank you from me, but not only for the work. Your report was concise, well organized, and very well written. Quite refreshing in an age of lazy grammar, twitter, etc.

They should have you write the patch notes as well. Whoever does them now can't write for poo.

[Adridos]

Fooooo, on 15 May 2013 - 03:22 AM, said:

Farcry 3 for example is not exactly running on cryengine3. Its a highly modified version of it and even has a different name.....duro or durant engine or something ?)

AFAIK Far Cry 3 runs on the upgraded Far Cry 2 engine which was in itself an extension of the original CryEngine. It is called Dunia.

In essence, it is another branch of the Cry Engine development which separated into CryE2 and 3 and these Dunias made by Ubisoft.

Edited by Adridos, 15 May 2013 - 03:54 AM.