Created Date: April 19,2009

Created by: JohnRaynes

Confirm same issue

I'm having the same problem, using version 2.41. Simulation worked for a while, then went away. I uninstalled and re-installed the entire program, and that brought it back, for a few minutes, but then it disappeared again.

In my case, when I select simulation, the program goes busy for 10-15 seconds, but never brings up the simulation window. It doesn't hang, but returns you to the main editing screen, no indication of errors.

It doesn't appear to be project file-related either. I started a completely new project, dumped a couple items on a screen, and tried simulation, again, no luck.

This must be a V2.41 version bug. Any response from AD C-more support on this?

Created Date: April 19,2009

Created by: a agnone

I too had problems with the simulator, but just dismissed it as a windows problem. I updated to V2.42. I had one of the windows mess up and just froze or something like that. Sometimes when this stuff happens you just ignore it thinking windows messed up. I am just posting because if enough had simulator problems, then maybe it is a program problem. If it happens again I will post exactly what happened. I am running XP Pro.

Created Date: April 19,2009

Created by: Tubecut

Oh yes, I have had problems with the simulation as well. One of the things that has worked for me is to look at the Windows Task Manager - processes and I locate the EA-RUN.exe (that may not be the actual spelling) and ill the process.

Then I can re-start the simulation again and it seems fine for quite q few simulation runs. In my case, there was just a lock up and task manager in the applications tab would show the process as not responding. I have thought that this is actually a PC software problem and not a direct problem with the C-More Micro software. THis is using the C-More Micro software.

Created Date: April 24,2009

Created by: worknhard9062

Confirm same issue

I'm using C-More 2.42 and had the same lock up with the simulation. Had to use Task Manager to kill the process and like Tubecut, life was good again after that. I suspect that for this to be a BFB (bona fide bug) it must be repeatable. If anyone reading can get a line on the underlying cause or sequence of events that lead up to this then post your results here please. Also recommend reporting directly to AD Tech Support. Not sure these fora are visited routinely enough to serve as a bug report medium.

Created Date: April 24,2009

Created by: Do-more PE

If you look at the pink bar at the top of your page, you'll notice that we don't monitor the forums for bugs. Not to say I won't report them if I see them, but if you want a quick answer, your best bet is to phone or email.

By calling or emailing, the techs can get in touch with you and ask questions a lot quicker. The more folks that call or email about a particular issue, the easier it gets to find the common cause and get to the bottom of it.

That being said, if you have posted about this issue, please call or email Tech Support (see below for contact info) so we can work on what the cause of this issue is.