292 replies to this topic

[Dikaiosyne26]

As much as not having a HUD / having it corrupted in game, was frustrating to me, I can only imagine how frustrating tracking down and fixing the bug was for you!

THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Edited by Dikaiosyne26, 14 May 2013 - 11:48 AM.

[Phaesphoros]

Would you mind replacing "STL" with "Standard Library"? Stop spreading the myth xD

Great work finding that bug.

[Falcore]

First of all thanks for the ultra detailed response. I understood maybe half of that but the transparency was extremely helpful. I hope that you are this transparent with bugs and issues going forward. I think there would have been less complaints if you had been more transparent earlier in the process.

[Sir Stomps A Lot]

Wow, incredible write up! I bet it feels really good to finally find the root cause!

[Ardlen]

Interesting read. Will your fix be integrated back into CryEngine?

[Sprouticus]

zmeul, on 14 May 2013 - 11:43 AM, said:

what tha' **** ?!
this is the initial build of the library, you're telling me that for almost 9 years CryTek didn't rechecked / brushed it's code

From the way I understand it (as a layman), the issue occured because of the scaleform/STL port issue, but the reason it was difficult to reproduce and fix was because of the memory allocaiton in Cryengine (most times it would not use different memory).

My guess is that the memory allocation in and of itself would not normally be a problem (although even I know that direct memory allocaiton is bad under most circumstances). but it made the problem extremely difficult to work out.

[zmeul]

Phaesphoros, on 14 May 2013 - 11:49 AM, said:

Would you mind replacing "STL" with "Standard Library"? Stop spreading the myth xD

Great work finding that bug.

haven't touched C++ in tens of years, isn't it stlib ??

[Shumabot]

What is the level of communication, if any, between PGI and representatives from Crytek? Could this conflict have been known to them or other developers prior to this entire process?

[SenselessNoise]

This is just incredible. I can't understand most of it, but I can certainly relate as a molecular bio major. When something isn't happening, or not working correctly, or just simply screwing up, the process to isolate it in something complex as either programming or genetic code is a real pain in the ***; having to go line-by-line through either to try and figure out what the hell is going on is a frustrating and daunting task. And you feel awful when you think you fix it, and some other issue pops up. It's really discouraging, but you guys kept at it.

Kudos to you Karl.

[stjobe]

Sir Stomps A Lot, on 14 May 2013 - 11:50 AM, said:

Wow, incredible write up! I bet it feels really good to finally find the root cause!

As a professional developer for some 20-or-so years I can vouch for it being one of the best feelings ever (in your professional life, that is).

Once again, well done. Well done indeed. That one was a doozy.

[TruePoindexter]

Awesome job! As a fellow developer I can see how that would have been a nightmare to track down. Kudos!

[Karl Berg]

zmeul, on 14 May 2013 - 11:43 AM, said:

what tha' **** ?! this is the initial build of the library, you're telling me that for almost 9 years CryTek didn't rechecked / brushed it's code

Take from that what you will..

Kaylos Thex, on 14 May 2013 - 11:45 AM, said:

As a follow up question to this. Is the front end patcher completely fixing this, or would a full download/reinstall be more reliable? I have several cryengine games installed. Would those installs have overlapping files anywhere?

Yup, the front-end patcher should work just fine. If you suspect it didn't work then Krist has a repair tool which verifies your install.

[DaZur]

What... CryEngine doesn't have s spell-checker like MS word?

Seriously, I truly appreciate the write-up, even if 93% of it sounded to me like the adults talking in a Peanuts cartoon.

​I echo the sentiments of an earlier poster in that this should be the de facto post to re-post when folks wonder why it takes so long to hunt bugs...

KUDOS!

[Adridos]

zmeul, on 14 May 2013 - 11:52 AM, said:

haven't touched C++ in tens of years, isn't it stlib ??

Yep. That's why he called Karl on spreading a myth that stl translates to standard library and not stdlib.

[zmeul]

Sprouticus, on 14 May 2013 - 11:51 AM, said:

My guess is that the memory allocation in and of itself would not normally be a problem (although even I know that direct memory allocaiton is bad under most circumstances). but it made the problem extremely difficult to work out.

my understanding is that the cryname lib is out of date and inconsistent with the ScaleForm function calls
the ScaleForm lib(s) got updated while portions of CryEngine that use it, did not

[Tannhauser Gate]

To the haters and rage posters... feel stupid yet?

Thanks Karl for the break down. It really showsthe work you guys are putting into this.

[Phaesphoros]

Actually, STL stands for "Standard Template Library" and refers to a library mostly of containers back from the days when C++ has not yet been standardized. The library described in the C++ Standard is not the "Standard Template Library" even though it has been inspired by it. STLPort started from being a port of STL to becoming what they call an implementation of the Standard Library.

[Mason Grimm]

Speaking on behalf of all the smoke eaters out there; WTF?!?!!?

Oh wait,.,. a moment of clarify is upon me... "Ummmm, so my game works right?"

[Scromboid]

Great job, guys! And thank you!

[Shumabot]

LakeDaemon, on 14 May 2013 - 11:56 AM, said:

To the haters and rage posters... feel stupid yet?

Thanks Karl for the break down. It really showsthe work you guys are putting into this.

It also showed that he was hired late into the process. I'd like to have seen the timeframe for when this got prioritized by manaement and when progress started being made. Just because a thing gets fixed eventually doesn't necessarily mean it was done expediently. I'm probably more of a curmudgeon than most though since it seems like I've been hit with every single bug this game has in the last two months, often times several at once.