DoctorPringles wrote...
NYHoustonman wrote...
I love Bioware, but how do these game-breaking bugs keep making it through so late in development? Granted, I'm an engineer, not a scientist, but one would think these things should not be so hard to diagnose ahead of time.
This entire thing is bordering on ridiculous at this point. Saw the threads this morning and thought maybe I'd have some RtO action on PC when I got home... NOPE!
EDIT- Double Post. This forum is pitiful.
Being an engineer, you work with hardware which normally has some sort of visual identifier that lets you know when something isn't going right. With programming, it's more complicated than that. There are plenty of errors that can go unnoticed well after release, such is the problem with programming. You can input a line of code that the software can read perfectly well, but does the exact opposite of what you intended, and you may not notice it until a customer is calling complaining because their timed oven confuses 5 minutes for 50. I imagine such is the case here. A user-created glitch in the code that created potentially game-breaking bugs, like the bug that was found on the 360. Best we can do is wait until the developers fix it, and are content with the quality of their product. I trust their judgment well above Microsoft's marketing team.
I suppose I don't know enough about the situation to judge, but if this glitch 'breaks' specializations... One would think that this should be very easy to see in testing? That would be my beef... For sure, I hate programming, and from what experience I have you occasionally run into bugs that are a nightmare to find/debug, but if this happens with any kind of significant percentage of installations, IMHO it should have been caught before release.




Ce sujet est fermé
Retour en haut




