EVE General Discussion

As far as I could tell after reading both threads, you still haven't done the DirectX repair. Just re-run it from the link in the previous post.

You guys are talking wayyyy over my head but he's going to reply. Don't shoot the messenger.


Perhaps you need to provide your definition of someone with a clue. I am not exactly sure from where you have acquired your false sense of expertise. You seem somewhat versed in the scheme of things so I will save you semantics.

Your statement that most games do not fill video ram is blatantly ignorant. The vast majority of modern video games use a LOT more memory than the graphics card's video memory can provide. Textures ALONE will fill graphics memory many times over.

Where are you getting this from? This is absolutely not how any modern-day directx based gaming engine functions. I am also uncertain whether you mean video ram or system memory in this statement. How it is designed to deal with corruptions in memory? There is absolutely NO FAULT TOLERANCE in programming. The vast majority of games are programmed in C++. If a chunk of memory assigned to a variable becomes corrupted, when whatever method processes that variable tries to, the program will reach a segmentation fault and crash. Trying to perform checksums on all returned memory would put us at atari graphics.

In DirectX you have ABSOLUTELY NO CONTROL over what texture gets loaded where in what order and whether it fills the graphics card or not. The game loads all of the assets it needs to display a certain scene and Direct3D handles whether some of it gets paged into RAM (technically even to HDD, but that rarely happens). Most developers are smart enough to put in load screens and to minimize rendering distance to ensure not too much RAM paging occurs, but you still do not have control of what DirectX does in the long run.

For your reference, the method generally used is D3DXCreateTextureFromFile and it takes the graphics device, source file, and a texture pointer as parameters. D3D decides where to put it on the graphics card.

Therefore, even if the statement that "most games won't fill your Video RAM, [whereas] incarna will" were true, the likelihood that you would encounter a bad portion of RAM in another video game is extremely high.

I doubt it is CCP's code that is at fault. It is most likely something in the Windows/Driver/DirectX configuration that has gone awry. Also, I'm not sure how many software development companies you have worked for, but 9 times out of 10 it is your job to support the customer even if it is their own fault the game does not work.

With the advent of the advanced die surfaces and heatspreaders on modern packages, hot spots are very unlikely to occur unless a manufacturing defect occured. If that were the case, it would be a very large batch of cards that would be affected and this problem would spread to far more than just EVE.

Funny how he or his buddy continues to argue about the schematics of how game graphics takes up memory rather than trying out solutions...

Just saying...

Son, I said borrow a buddy's card or something, I didn't say buy a brand new one. Take your computer to your local computer shop and ask them to test out the game with a different video card. I don't think you're aware but when Incarna first came out, it cooked alot of people's card and made the game useless on some older cpu/video card.

The idea is to eliminate the possibilty of where the problem is coming. Once you're sure that it isn't your video card, we can move onto looking at something else that may cause your problem. This is fairly standard operating procedure for PC techs to fix computer problems.

Then it stands to reason that the issue is on your end, with your computer, not with Eve.
Folks have been nothing but helpful with you here. Take the advice, try and fix your problem, or sit here and sulk and spit venom. Either way, get out.