94444 creates "Error creating Direct3D 9 Graphical engine"

[Mr11B]

Ok I literally typed this 20 minutes ago and whoops, wasn’t logged in. lost it all. ..So now after 3 beers I will type this thing again…Within the capability of my knowledge I have trouble shot this thing the best I could. So far I have only the conclusion that 94444 is the issue. I have a retail copy of ARMA2 CO. I have steam installed but have never used it, literally. I only downloaded it to see if Day of Defeat was still around. In my library it shows no games and I have not used it for multiplayer or any other possible function with ARMA 2. I did use steam to update my video card driver. I use a virgin game, no mods. I will provide a timeline of what happened and the steps I took to work through it. This only started happening when I downloaded the DayZ mod. However through trouble shooting I have realized it is the beta 94444 that seems to be the culprit. I know they are having huge issues right now, but my problem seems to be due to the ARMA 2 beta version and irrelevant to other solutions for people that have experienced the same error codes. My PC specs are as followed

Windows 7 premium home edition with service pack 1
Intel i7 2.93ghz cpu 64 bit
8 gigs ram
ATI Raden HD5700 with current drivers

Pinned in my task bar are two shortcuts, one for ARMA 2 and one for OA. Both have no mods and my OA shortcut has the following target line "C:\Program Files\Bohemia Interactive\ArmA 2\arma2oa.exe"
This shortcut creates the error, my arma 2 shortcut at
"C:\Program Files\Bohemia Interactive\ArmA 2\arma2.exe" works totally fine.
Here’s how it started and the process I went through.

I heard about DayZ only yesterday, so I downloaded six updater and dayz. I ran it through six updater and had no problems at all.
This morning I played around with my key setup in the mission editor of OA launched using my shortcut referenced above. I had no problems at all. I continued to play dayz through six updater with no problems as well. I backed out and about a hour later launched again with six updater and it notified me that dayz had an update. I updated dayz, then the problem everyone had hit me. Stuck in loading character mode. However now when I went to load ARMA2 OA through my shortcut I received the graphic error.
I launched again via six updater, I could not connect so I disconnected from the server. Backing out to the main menu which allowed me to go to single player. I went into the mission editor and ran into the following problems. I was not allowed to select Men or Soldiers of any kind via the drop down menu (see attached pics). I selected a helicopter and when I launched it only showed a view of the scenery (see attached pic) I was not able to control or change view or use any of the keys.
I backed out and did the following to trouble shoot. I deleted dayz, attempted a launch and had the same problem. I then deleted the arma2/expansions/beta folder. Walla! I can launch using my original shortcut. I restored the dayz folder through my recycle bin, launched fine.

I re installed the beta 94444 using the original download, not the restore from the bin. Same error. Removed dayz again as well as 94444. I re installed 94444 without dayz, same error. So logic says bad bad 94444! I felt it important to type it again so you BI guys could know what’s up. Maybe it’s just some random thing with my config or PC but it’s about as vanilla as you can get. Even with adding SU and DayZ. I’m not bit$&ing or complaining. Hell I’m old, 31 and ordered OFP in 99’ from Europe just to get it early. You guys have a lot to do, but maybe someone can help me with this. That way I can spend more time watching the stripper pole instead of just trying to get a game to work. Yes the last pic is a stripper pole in my kitchen! Back to beer, cheers and thank you again in advance! - Mr11B

No Soldier Selection
http://i1186.photobucket.com/albums/...oselection.jpg

Stuck Scenery
http://i1186.photobucket.com/albums/.../stuckview.jpg

Better Things To Do =)
***unrelated pic removed***

[[FRL]Myke]

Problems with Beta belongs into the related Beta thread.


-Closing-