Ok. I guess my expectations are just a bit lower seeing as I understand what goes into making a game; somewhat understand it as when I look at the file structure of this one, I just shake my head in amazement. I've always been of the opinion to truly appreciate something you have to actually do it. Cooking, for example. To truly appreciate the food you have to actually cook food. Or you have to play music to truly appreciate it. Just my opinion, of course. But I've written code before; oh, nothing of this complexity, but I understand that sometimes a bug is found and you look at the code and look at the code and look at the code and are going, "What in the holy **** is going on here? Code looks good, but there is clearly a mistake somewhere. And you just don't see it. I've seen 2 and 3 people look at such a problem and they started to think it might just be hardware, but all the HW Diags report no problem. Bugs like that do happen and it is extremely frustrating.
I know it's a complex Code Monster what they've achieved. I just wish a bit more direct communication bout the progress.
Even if they would say 'Sorry guys, but we'll not release a patch till we found and fixed bug blah.'
You know. Something. I'd be way less frustrated if i knew what was going on.
If they come up with new Bobbleheads or Paintjobs instead of fixing or optimizing (sure, could be different peeps working on)
it's like a slap in the face.
Like 'Hey, we know, it's buggy as hell, but here, have some new Shiney for some Dollars!'