10-20-2004, 01:49 PM
I'm sure when I run it in Direct3D it runs flawlessly because well... I have before. If I can play Unreal 2004, Far Cry and Doom 3 no problem, it should run Diablo 2 like nothing, like it used to before this error came up.
I also have the latest video drivers (as I stated in the first post) and nothing has changed. I forgot to mention it said this before, but I tried it again in an hour and it went away. Doesn't seem to want to go away this time.
I also have the latest video drivers (as I stated in the first post) and nothing has changed. I forgot to mention it said this before, but I tried it again in an hour and it went away. Doesn't seem to want to go away this time.