-= Gametoast.com =-

This has been happening a lot lately - I would launch up BF2 to test some changes I made, and it doesn't start. The icon appears briefly down on the taskbar, then vanishes. I'm not sure what's causing it. Sometimes I close out all other programs and then it works, but other times it launches fine with music playing in the background, XFire running, IE up and with a couple tabs, and a few Windows Explorer windows to boot. Sometimes it works when I turn audio recording off for XFire video, sometimes it doesn't work even after I turn off audio recording. I don't think it can be a memory issue, as I've actually gotten rid of 20+ GB of unneccesary and unrelated files when emptying the recycle bin. Does anyone know how to fix this?

EDIT - The debugging utility seems to run fine, though the normal game itself doesn't.

I had a similar problem once (a few weeks ago, actually), except my game refused to properly close instead of open. It'd sit in the processes until I manually ended it myself. It's ironed out now and I have no idea what caused that to happen, but I am glad it was fixed...somehow.

Perhaps you have one of those issues where it will iron itself out, but if not, I am sorry.

May I ask a simple question? Did you try rebooting to see if that would fix it? If that doesn't help, I apologize. Usually I try that when I troubleshoot a problem. I hope that was not an annoying question.

Are we talking about windows 7 here? I doubt it'd make a difference, but have you tried reinstalling the game? its worth a shot... if its only just been happening for like a week or two, you could also try a system restore to get rid of it.

Apart from that, i've got no idea..

We are talking about Win7; but I've had 7 for a while now and haven't had much trouble with it. I'm familiar with the basic Win7 troubleshooting - compatability mode, running as admin, etc. - and that didn't seem to have much of an impact over whether it started or not.

Anyway, it seems to be running fine now. I've got no idea what caused that issue, but it seems a reboot was the best solution. I guess this can be marked solved. Thanks for the help!