XMaverick wrote...
Dhamon78 wrote...
XMaverick wrote...
I have two things to say. First of all, as a consumer, I'm feeling irritated from the Academy bug discovered in the italian port of Mass Effect 3. But, as always, we're acting like a mass of unpleasant people. The argument that Bioware and EA are on the wrong side is a fact. Now, in our very interest, the only logic thing to do as already wrote by other forum members is to post every little detail that we can provide. Only after a solution was found we can ask for some kind of compensation. In fact, we Italian are the only people that continue pressing about the price of the game instead the fact that a piece of the story, small instead but still a piece of the whole story, will be compromised by this bug.
...cut...
Xmaverick I don't go deep in technical details because I'm not a SME but for the first thing that you say I have the impression that all us talk also of the money (but not only about money) because we spent bug-free money for this game and isn't fair that we get back a game with a so great bug that is obviously due to a lack of controls in our localized version.
I also agree with you that we can only provide to Bioware all the details that we need but I think that they simply don't need any other data because they don't request anything to us. In my opionion, partially confirmed by Ryan's posts, they only must find the root cause of the bug and fix it once for all so providing more data is completely useless.
The only question is: when we can get the fix? Only for this question we have, as unsatisfied customers, continue to post and requires update because personally if they don't release a patch in a blink of an eye this will be the last bioware game bought by me and I think that a lot of italian people will do the same thing.
Regards
As my personal experience, there's no way to get a patch fast with this kind of bug. As the Unreal Engine is written using C++ languange, there's no fast way to get hardware state information. The only sure way is to track every line of code, use debugging routines to "read" the state of the console step-by-step and trace the usage of the memory and all of the game variables. Also trace of the code calls is necessary. So, if we're lucky, the bug is really easy to find, maybe afflicting some very global game variables, and all we must wait is just the time that Microsoft take to certify the patch. If not, the developers are in front of some weeks of blood-spilling debug session reading line-by-line code and monitoring all the hardware piaces of the Xbox.
This is why we cannot get an ETA, but only hope that next time we turn on the XBOX we can read of the patch.
So, the patch in a blink of the eye is, sadly, simply a non-possible scenario by the way this bug is acting over our Xbox hardware. I'm sorry.
By now, providing more details che be useful for speed up the team that collect hardware and software profiles for debugging, even if they think to have all the possible data. If something was missed, providing here information can let the team to gather the info without first starting the tests and then figure out that something missed. Obviusly, we don't know if this is the case, but doing so it's surely better than read thread posts like "FUC''''''NG SH''' M3 bla bla bla bla some more profanity here".
By now the game still worth the money. At least some of us can do multiplayer, and we can do some secondary missions before the "critical point of no return :D". Still, there's no excuse for Bioware, as I think some more betatesting at the final stage can possibily avoid this bug. Possibily, because with project like this something can always happen, maybe related to some marketplace app distributed only in Italy like Mediaset Premium, and maybe also after the game was released. This is informatics. This is Sparta.
Thanks for the infos now I know some details about C++ and its implementation on videogames and I agree with you, as said before, that will be useful to provide informations about the bug but, as said by Ryan some posts ago, they not need any other data by us they have to work and debug now so in this case send more information is useless and even if I respect your professional opinion I think that the developers knowns bettere than anyone if they need additional data and if there's someone can provide these data.
Also I disagree with you for the matter "a patch in a blink of an eye": I learned in my little work carrer that almost everithing can be done within the desired due date it only depends on the resources allocated for the project so if the want they can set a due date of a week and assign enought resources to close the project whitin the due date.
Best Regards
Modifié par Dhamon78, 13 mars 2012 - 08:43 .
Retour en haut
:lol:
at least we kwnow that you are working on it 
