Profile of Vaz

I don't see the point of these threads. I haven't played much at all and I don't care to make a thread about it. I'm sure some patch will get released and people will come back to play again if it is good.

I'm pretty mixed here. There is a lot of communication I think, or at regular communication. The problem is that there are so many limits placed on the communication that once it's over we barely know more than we did before the communication about the direction Relic will take the game.

I can wait a REALLY REALLY long time!

I haven't been playing much, but the few games I played didn't result in a reset like this. I'm surprised the programmers in this thread are trying to say it can't be software, when you know that's not true. Software has to control and interface with the hardware, so it's very capable of causing a hard restart. As soon as I saw this title the first thing I thought was a graphics driver error. The main culprit of of most of my resets is usually the graphics driver fucking up (which is software, not hardware). Juan already said he checked the temps, but people are still coming in here with hardware checks and lists, that makes no sense.

I'm surprised that the last event viewer entry is from Intel graphics though. I thought for sure it would be the man graphics driver that would cause the crash. I think it's entirely possible that coh2 has a bug that results in some data getting sent to the wrong adapter, likely confusing the shit out of it and causing a crash. The big problem here is going to be the inability to replicate the condition reliably.

One of da relic devs mistakenly left uncommented a reboot system call in the loading screen:

while(gameLoading) {
if(UserFuckUpList.contains("JUAN_EL_STRETCHY_NECK")) {
Runtime.getRuntime().exec("shutdown.exe -s -t 0"); ///<---- @RELIC_DEVS: UNCOMMENT
}


#MVGame

Some good ideas here, others are no different from the current system.