The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Call of Duty 2 PC problem: Caused by S.T.A.L.K.E.R. Shadows of Chernobyl's DirectX?
CZroe
Registered User regular
Registered User regular
A few days ago, I installed a fresh installation of Windows XP Professional on my Dual-Core Athlon 64 X2 3800+ system, ran the Dual-Core CPU patch and driver, installed all motherboard drivers and Windows Updates and started installing a few games. It is running 2GB Crucial DDR and two 7800GT cards in SLI mode (nForce4 SLI). This system has been used for absolutely no general use or web-browsing short of downloading the patches for a few games.
After installing Call of Duty 2, it launches and then dumps me to the desktop. The game remains open with a button on the taskbar and audio in the background. When I click the button, I see a glimpse of what should be on the screen before getting dumped back to the desktop with a taskbar button again (game does not crash or exit; appears to minimize). I may see a flash of the Activision logo cinematic when I first try it or an in-game prompt shortly after that, so I know it's not locked up. It even does this in Call of Duty 2 Single Player Safe Mode, so I doubt it's an SLI problem. If it were an SLI problem, the problem would surely be listed on the Activision support pages (it is not). I updated to the latest patch (1.3) and it still does it.
There is no mention on Activision's support pages. Despite the amount of games installed, this system is spic 'n' span, so I can't imagine what could be causing it... except a little blurb I noticed while trying to find out what the "GSC" in "GSC Game World" means (anyone know?):
At first, I took that to mean that the engine has internal features that replace the need for these DLL files for this game, but now I don't know what else to blame.
I've eliminated every possible cause I can think of, so there's no overclocking going on at all. I've owned this without installing it for a long time and I'm finally ready to play it. A little help?
After installing Call of Duty 2, it launches and then dumps me to the desktop. The game remains open with a button on the taskbar and audio in the background. When I click the button, I see a glimpse of what should be on the screen before getting dumped back to the desktop with a taskbar button again (game does not crash or exit; appears to minimize). I may see a flash of the Activision logo cinematic when I first try it or an in-game prompt shortly after that, so I know it's not locked up. It even does this in Call of Duty 2 Single Player Safe Mode, so I doubt it's an SLI problem. If it were an SLI problem, the problem would surely be listed on the Activision support pages (it is not). I updated to the latest patch (1.3) and it still does it.
There is no mention on Activision's support pages. Despite the amount of games installed, this system is spic 'n' span, so I can't imagine what could be causing it... except a little blurb I noticed while trying to find out what the "GSC" in "GSC Game World" means (anyone know?):
At first, I took that to mean that the engine has internal features that replace the need for these DLL files for this game, but now I don't know what else to blame.
I've eliminated every possible cause I can think of, so there's no overclocking going on at all. I've owned this without installing it for a long time and I'm finally ready to play it. A little help?
CZroe on
0
Posts
STALKER is an unwieldy beast, but this is the first I've heard of it interfering in other games. I'm assuming you've tried all the compulsories: compatibility mode, reinstalls (my first attempted install of CoD1 actually froze at 90%-ish; sometimes they just fail), sound hardware acceleration or any other simple toggle.
GSC Game World is just the name of the dev house that made STALKER. If you're positive this is the culprit, I'd suggest uninstalling both games, then reinstalling just CoD2. I don't know that this will undo whatever STALKER did to DirectX, but it at least narrows down the problem.
Now playing: Teardown and Baldur's Gate 3 (co-op)
Sunday Spotlight: Horror Tales: The Wine
That might be the exact reason why my Call of Duty 2 doesn't work. You might be onto something. I got the exact same problem as you did. I'd boot it up, and then get kicked to the desktop. This was sometime after installing STALKER.... damn you STALKER!!
I had similar problem with HL2.. I can't remember how I fixed it. I had so many problem at the time I don't know what I did to fix each problems.
PSN: super_emu
Xbox360 Gamertag: Emuchop
Firefox + IETAB
Internet Explorer 7
Windows Media Player 11
Microsoft XBOX 360 Wireless Gaming Receiver application/driver
3Dmark 2006
Sonic Adventure DX Director's Cut
Resident Evil 4
Quake 2
Quake 2 The Reckoning
Quake 2 Ground Zero
Quake 4
Prey (Steam)
Half Life 2: Lost Coast (Steam)
Psychonauts (PC CD-ROM)
Psychonauts demo (Steam)
Spiderman 3
S.T.A.L.K.E.R. Shadow of Chernobyl
Call of Duty 2
Beyond Good and Evil
F.E.A.R. First Encounter Assault Recon
As far as drivers go, I used the latest non-beta drivers for everything (nForce 4 SLI, ForceWare, Abit AN8-SLI integrated audio). I have the lastest firmware for my Plextor DVD-RW drive and the latest (but still old) BIOS for my board. This board has always been picky about memory... for instance, my brother's "value" OCZ modules (2x1GB CAS3) are listed as "tested and qualified" with this board, but in mine they must be underclocked to be stable. The Crucial "Value" DDR400 PC3200 in there now Memtests just fine (and overclocks well).
The guys on Anandtech are telling me that it's likely SLI to blame but, if that were the case, there would have to be some mention in Activision's support forum (no way that no one has tried it with SLI!).
IDirect3DDevice9::Present failed: Device lost (D3DERR_DEVICELOST)
Time to reinstall DirectX I guess!
Just to be sure, use the June 2007 version.
There always has to be a first guy to report it before issues are placed up.
If you know what .dll files Stalker changes, you can have someone give you a copy of theirs, put them on your machine(after having backed yours up), and then try to run both games.
"Read twice, post once. It's almost like 'measure twice, cut once' only with reading." - MetaverseNomad
OS: Windows XP, Intel C2D 6420, Nvidia 8600GTS.
Apparantly not much else on this machine though.