hey ZOS

Dragonphart · May 2015

Your weak wonky coding is causing the random black screen crashing again, and again and again and again. Sure hope you coded the console version's better. I know I am getting flamed from the forum but I am very salty right now. Just letting loose on the bad coding and the fact that there is no 64 bit version.

Ranique · May 2015

Dragonphart wrote: »

Your weak wonky coding is causing the random black screen crashing again, and again and again and again. Sure hope you coded the console version's better. I know I am getting flamed from the forum but I am very salty right now. Just letting loose on the bad coding and the fact that there is no 64 bit version.

The lack of information and the tone indicate that you have no patience, but I'll try to explain what is wrong with your opinions here.

1: wonky coding is causing random black screens
A: just wonky code in a program is never causing a blue screen. A blue screen is caused by an error where a program tries to use a memoryblock that it shouldn't be using AND where windows is unable to resolve this. In most situations of just wonky code, windows will reply to the program with a nono and it will either give it's own error code or will crash (as a program, without influencing windows). A black screen happens if windows is unable to block it. This is most common when several parts are working against it together. For example, directx, the graphics driver and the game, all adressing the same info in the memory (as they all need it) but mixing things up. Cause windows can't tell anymore what program did wrongly, so can#t block that behaviour with a nono and so it has to crash.

2: Why is this not ZoS's programmings fault?
A: It actually is, but it also isn't. It is the programmers of all party's involved it's fault. It just so happens that it is the gamestudio who looses customers and make a bypass to the issue quicker. But in many cases it is actually something caused by a third party.

3: But all my other games are running fine!"
A: that doesn't change a thing to the fact that it isn't just the game code going wrong. Think about it. If it is the bad code and a reinstall doesn't solve it, then it should be affecting everyon. As this forum would then explode, this is clearly not the case. So it is the cooperation in your specific system between the drivers, windows, support software (e.g. directx) and the game.

4: Crashing again, and again and again and again.
A: if this isn't the first time this is happening and you have resolved it (with the help of ZoS), then it is likely it is more due to your system then to the program then allready illustrated. I would strongly recommend getting a full check-up of your system. Even if you are only experiencing errors with ESO, then it is also a matter of time that other programs will give errors.

5: you give very limited info, but did you recently get any driverupdate?? I'm asking cause my nvidia driver updated this morning and it was a dissaster driver. Had to revert it inmediatly to avoid some very serious issues.

6: No 64bits version of the game.
A: The only advantage of a game running on 64bits is that it can use more then 2GB of memory (this limitation is per program if you are running a 64bit windows). So as long as ESO doesn't require more then 2GB memory, that is no bad coding or crappy work. It is just a matter of saving a lot of time (and effort) to make a 64bit client that doesn't give any performance-improvement. As long as ESO runs fine without needing more then 2GB of memory, it is no problem that it only has a 32bits client and I'm happy that they invest the time in more important things to do.