Staude said:
nightsurge said:
Staude said:
nightsurge said:
Staude said:
Look. I can't be bothered to argue this with you because i'm right. Most people haven't felt it was a issue, the few people who did however has gotten awry and started whining all over the internet. But if it's any consolation we shouldn't even be having this argument since reviewers has said that this isn't in the final build.
|
Ah, so it is just the demo then? I guess we shall see once the final game is out and if I can notice it.
Sorry, but you are wrong, still. At least in regards to the demo which is of what I was speaking about (only reference to go by). So go ahead and don't argue anymore if you "think" you are right. It doesn't matter if "most" people haven't felt it an issue... what matters is that most people have at least noticed it, and to some of the more serious shooter players (I would consider myself in this category) it is an issue.
So since you don't speak for everyone, nor the majority either, don't speak at all.
|
they only noticed because of the incessent whining. I only noticed because of that.
Your last sentence goes for yourself aswell. Especially when making such remarks as you did above ^in your argument towards a reason why it is like it is. It's not even a remote possibility.
|
Really? I noticed from the very first time I pulled the trigger. Even before watching the videos on the "lag" I had seen it first hand. How can you say it isn't a remote possibility? I didn't realize you were behind all the code involved and could check for the source of errors on this game. While you are there, can you tell me what IS causing it then?
|
If you would think for one second. You would realise that you have to INSTALL the demo. That means that everything. Yes everything reads from your harddrive. That rules out the possibility that it was stored on the disc in some akward place and that somehow it wasn't being read properly.
Secondly it's still not on the actual game which is on a disc so i would simply assume that it's the build, since the build is from 2008. The demo is a unfinished build so "bugs" are present. I still don't see it as a issue though.
But your whole argumentation is for naught cause again. You have the demo 100 percent on your harddrive.
|
*facepalm* Wow... I seriously did overthink that for a while. I guess the only explanation then is that the location for which the event was stored and the code used to trigger it, were not in an ideal configuration. I am glad to hear it is not on the final product, though. Now it is just the momentary stutters during checkpoints/loading on the final product, but that is normal for a non-installed game.
I'm gonna get a hounding for this one for sure... 
