Sabre10

Guys, I'm sick of ERROR CREATING DIRECT3D 9 GRAPHICAL ENGINE. This error occurs spontaneously, usually after I exit the game and then want to rejoin. Any idea? I'm on WinXP Sp3, nVidia 9800X+, recent driver, nothing special. Can't figure out any reason, sometimes it starts, sometimes it does not. Thanks, Sabrefly.

I appreciate your time and help, y2hippy. Thanks, Sabre.

It's not the case with my card. It's a single-core GPU. I've roamed through the recent posts on the boards and the Error occurs both on SLI and non-SLI configs. So it's not the cause. Thanks, Sabre. ---------- Post added at 01:05 PM ---------- Previous post was at 12:59 PM ---------- Here's my ArmA2 config: adapter=-1; 3D_Performance=-4194304; Resolution_Bpp=32; Resolution_W=1440; Resolution_H=900; refresh=60; Render_W=1440; Render_H=900; FSAA=3; postFX=2; HDRPrecision=8; lastDeviceId=""; localVRAM=511528449; nonlocalVRAM=258998271; Have no idea of the localVRAM and 3D_Performance meaning and influence. Pls anyone to comment on the above? Thanks, Sabre. ---------- Post added at 01:18 PM ---------- Previous post was at 01:05 PM ---------- It's crazy, I just rebooted and launched the game. It ran. I didn't enter 3D, just visited settings, didnt change there ANYTHING, backed out from the game. Then I'm launching again now and it gives me the DX 9 Engine Error. I guess we'll be waiting for the next UPDATE. Thanks, Sabre.

It's GF9800GTX+. Sabre.

This error still occurs very random, no matter latest DirectX or 1.02 patch. I had it right from the DVD vanilla. Imagine, I manage to launch the game, play it, then exit. Then I want to reenter and it gives me the ERROR, no matter what. Then after many reboots and casting curses it launches again. Sick and tired of it. Thanks, Sabre.

I found suggestions to use SLI option. Is there anything special? I don't use/have SLI. Thanks, Sabre.

I've always cleaned previous drivers in Safe mode with Driver Sweeper and installed newer as per nVidia recommendations. My current drivers 182.50, and I have a reson to keep them. If anyone reports that 182.50 is the culprit, I'll take the trouble of updating it. Thanks for your attention to it. Sabre. PS: Forgot to mention I have the latest ArmA2 update 1.02 and DVD.

I'm not on SLI, I got the newer DirectX of March and 182 series of nVidia driver. The error is quite random but regular. Thanks, Sabre10.