Yup. Grass does that for me as well.

Guess I'm hanging out for the Friday update.

Question to the Devs.

Have you had a chance to investigate the issues COD has with Windows 8? If so is there any information you can pass on?


Cheers!

Before they'll work about Windows 8 and COD, maybe they had to finish with the all troubles with COD on XP and 7...... :rolleyes:

No more updates. BlackSix said goodbye to the CoD forum last week.

Who is BlackSix and how can they issue a broken patch and say goodbye? I had a working game before the patch and now I don't. No way to roll it back thanks to Steam.

I can understand they might be fed up with working on this mess but they can't just walk away.

They can and they do... simple as that.

I am sorry for you. But I guess they just don´t have the money to support CloD any longer.

What is your problem with the game btw.?

Welcome to the forum kevinh,

BlackSix works for 1C Maddox (the developers) and was their forum communication go-between. He got us answers to many questions on CoD problems etc.. He has dropped that role now because there will be no more patches for CoD (except that some of the improvements to the game core may improve CoD if you buy the sequel, they install to the same directory structure). And yes, they've walked away from CoD.

You might get help from us (the community) if we recognise the problem(s) so fire away. Tell us your system specs, like under my signature, and what is/isn't happening.

I've gone into detail about the problem on other threads, but basically Launcher.exe quits as a mission reaches 100% loading. Event viewer says the problem is an unhandled exception in .net framework. A secondary issue is exiting the game from the main menu (or auto-restarting after changing graphics settings) does not stop Launcher.exe. The thing is bugged.

I was running the game quite happily on Win XP SP3 pre-patch. If you have any suggestions I will gladly try them. Some members here say XP is the problem. My answer to that is the game is supposed to be compatible with XP SP3 and if the patch makes it incompatible, the patch has a bug and should be fixed. If they can't make the current version work on XP then they should make the previous version available to download. No way would I consider upgrading to Win 7 without some official confirmation from 1C that XP is no longer compatible. But I don't think they will ever say that. That would be admitting their software does not meet their own specification.

I can understand they want to stop development on this and move to the next version, but that's flawed decision making, as well as bad commercially. On the face of it it's an attractive idea. But they'll only end up biting off more than they can economically chew yet again. Also there was always the chance that no matter how well tested the patch was, it won't work for everyone. In which case they should hang around and fix it before cutting us loose. I think it's a sick joke to release a major update like this and just run away.

All would not be lost if I could roll back my game to the previous version. But because updates are handled by Steam I can't.

Did you try re-installing dotNetFx40_Client_x86_x64 in folder DotNetFx40_Client under the redist folder?

Yes, I've tried repairing .net 4.0, complete uninstall and reinstall with the version supplied with CLOD, install with latest download from microsoft site. Still get the same Launcher problem.