@k4el said:
@wolf_blitzer85: Sorry man but I'm going to shoot that comment down. You're clearly speaking from an uninformed position.
I guarantee this wasn't "missed" by the testers. They brought it up, it was shot down higher up the chain. QA departments in every company everywhere have to struggle against business and design decisions in order to get issues addressed.
If you're going to put the blame on some one I'd look at Bethesda or higher up the chain at ID and of course ATI may not be completely guilt free in this as well. It's not like they're known for being on the ball lately.
+1 to this. Beat me to it, but you forgot this comment;
@InternetDetective said:
How did they not know about these problems, did the play tester not notice?
I am 99% sure all the issues are sitting on a bug data base right now.
If this is truly just a driver issue then a driver update is going to fix it, I hope there is a combo of further optimization in support of better drivers. Terrible that it has released this way though...but we don't know how it happened. Maybe id brought these issues up with AMD or Zenimax/Bethesda but they pushed the current version anyways.
PC will be the best version eventually. I think now more than ever id Software should deliver on the "maybes" Carmack talked about during his keynote at QuakeCon 2011. Such as a high resolution texture pack and what not.
@wolf_blitzer85said:
If this is how game development works, then things are just going to get worse. I would think that the QA (especially for bigger games) would have a stronger pull in the development process since I would also think that the team would ideally want to put out a fully working game. I also wasn't trying to put the blame on anyone in particular either. I'm just amazed that this technical issue managed to make it out into the open, especially when the textures are a big draw to the game.
That is how it works, mostly, haha. QA has little pull because they are not designing, developing, etc. so the “value” of anything brought up falls in someone else's capable hands to make a decision on changes or fixes. Personally everywhere I have been, QA do their damndest to stop the bugs before they get to you, trust me.
It is still kind of amazing how this got out in the open right? I agree with you there. Like I said earlier in this post we have no idea where the fuck-ups began. Maybe AMD didn't even reply to id's emails.
@tapoxi said:
@James0890: Because Rage is an exclusively OpenGL game. I can't remember the last time a AAA titles used OpenGL instead of DirectX's Direct3D.
I can't remember either maybe pre-2005. Despite the problems so far I am glad it is OpenGL 4.2. Hey maybe there will be linux build because why not and id Software traditionally does one.
Log in to comment