EQ2 Forum Archive @ EQ2Wire - View Single Post

WastedChances · 06-25-2009, 11:04 PM

TSR-DanielH wrote:

You might want to try reinstalling directx 9.0c as well. I have heard some suggestions that this issue could by caused by a corrupt DX install throwing bad keystrokes to the game. That would make sense since it usually doesn't show the same problem if you open up something like a text editor.

Yes, this may indeed help. I found that some of the DirectX installers that were available from Microsoft inthe past included "Final Debug" versions of some of the DLL files which aren't necessarily bad however theyare bloated (ie: slower) due to debug code.DxDiag should report "Final Retail" for all your drivers unless you're playing on a development machine withdebug versions of the DirectX SDK installed.

Also, even if you have all "Final Retail", it is possible that dinput.dll or dinput8.dll have somehow become corruptand may be misbehaving.

06-25-2009, 11:04 PM	#9
WastedChances Loremaster Join Date: Jul 2007 Posts: 138	TSR-DanielH wrote: You might want to try reinstalling directx 9.0c as well. I have heard some suggestions that this issue could by caused by a corrupt DX install throwing bad keystrokes to the game. That would make sense since it usually doesn't show the same problem if you open up something like a text editor. Yes, this may indeed help. I found that some of the DirectX installers that were available from Microsoft inthe past included "Final Debug" versions of some of the DLL files which aren't necessarily bad however theyare bloated (ie: slower) due to debug code.DxDiag should report "Final Retail" for all your drivers unless you're playing on a development machine withdebug versions of the DirectX SDK installed. Also, even if you have all "Final Retail", it is possible that dinput.dll or dinput8.dll have somehow become corruptand may be misbehaving.