Go to Start, Run and type: services.msc , then click ok. Then you'll see a list of Windows services. Find the DCOM service in the list and make sure it's enabled.
Hmmm....I tried it, seems it's started, startup type is automatic, Log on as Local System. I checked with task manager and it doesn't show up there though...:3eyes:
missing rear wheels threw me thought they had been blown off untill i came across the next vehicle. I then shot where the rear wheels should be and blew the tyre and the wheel rim apeared... nice
And I thought it was just me! The ordinary civvy pick-up vehicles are OK though, it's really strange...:gape:
lol, see? I was saying the glitches still here like the missing rear wheels. The 1642 error can be remedied by reinstalling.
uh oh... just installed and am downloading the patch now. I left Punkbuster off (I don't play online). This is starting to sound like Stalker...
Y'know, they definately tweaked the physics this time, because the good'o "kill General Kyong with ammo crate" trick won't work anymore, and with 1.2, it works like crap for me (using 174.20 beta now, heard that the new 169.44 beta works specifically for this, will try it later), benchmark is the "Paradise Lost" stage... Update: Ok, there's definately improvment in the game, but noticably there're hicups in some areas previously not there in ver. 1.1. And benchmark got 37 fps average, a whole 10fps short against ver.1.1 in my case.
So punching General Kyong into a pulp in strength mode, like I did, may not work either then? Or could take a bit longer I suppose......I did give him a damn good thrashing :smack:
That still works, which I've tested it out, just that it won't be a one-punch deal anymore, a few more clobbering is needed, preferably after you've knock him off the platform, get close and then start to land punch after powered punch. 4 punches the last I tried.
i just grabed a machine pistol on the floor.. the guy has a mini-gun.. no way im getting close to him..lol
I never knew cars looked so funny without rear wheels. HAHA. Some massive patch. Who is willing to take a bet on the fact that some dudes at crysis working on the patch were trained by microsoft?
I just ran the 32bit and 64bit benchmarks with my 3870 X2 in Vista64. On both sets the Min Framerate and the Average Framerate went up. The best playable rates were in the 32bit with DX10. I have not tried it forced in DX9 mode yet. This is at 1680x1050 with no AA and all settings at medium.
That's happen when you run a pre-1.2 save, once past that point, everything will back to normal. Start a new game, and those Humvee will have wheels as they always do.
I've completed this game once already pre the 1.2 patch. I played at 1360x768 and V high settings. It was mostly ok apart from a few painful framerate moments. The framerate was mostly around 20-30. Memory usage was reported in the games console at around 1GB to 1.4GB. I've installed the 1.2 patch and started to play through again.........Although I can't. Memory usage starts at around 1GB but creeps up and after 20mins or so memory usage is around 1.8gb and my framerate is in the single digits. If I quit back to the menu and load a save where I know framerate was ok memory usage will still be 1.8gb and climbing with the framerate dropping even further. Anybody else getting this? I've tried 3 different Nvidia drivers to no avail. I have just installed the March DX update and the patch so it could be those causing the problem...... I'm stuck.
definitely is the patch...the dx march edition couldn't cause such issues...play it with 1.1, there's no difference anyway.
