Any PC Crash Issues Left?

[Sarge]

Does that fix include the issues I posted [&:]

[puresimmer]

Not the crash dump. To be honest that helps very little. The biggest help is an exact set of steps for me to follow and a saved copy of the association that demonstrates the crash. At this point 99.9% of remaining crash issues with PureSim are extremely spurious and very difficault to reproduce, or they are related to environmental/configuration issues.

I'll keep plugging though, so the more reports the better!

[33sherman]

I've gotten this crash twice now, since the career-ending bug was resolved.

When I'm simming a month at a time, if one of my players gets a career ending injury, the prompt comes up that I have to adjust my roster. When I click OK, the game crashes and I have to close it out and restart, at which point the computer has already signed a replacement on my roster and the roster has been auto-assigned by the AI.

[kennsing]

I hope I posting this in the right place. I dowloaded version 135 and am having a crash problem. I just finished a season and am attempting to start the off-season. The program prompts me that the association is being backed up and then it locks up. I have to control alt delete and end task. It happens if I try to go to the post season or run it in unattended auto run.

Any help would be appreciated.

I love this game and this is the first real problem I have had.

Thanks

Ken

[puresimmer]

ORIGINAL: kennsing

I hope I posting this in the right place. I dowloaded version 135 and am having a crash problem. I just finished a season and am attempting to start the off-season. The program prompts me that the association is being backed up and then it locks up. I have to control alt delete and end task. It happens if I try to go to the post season or run it in unattended auto run.

Any help would be appreciated.

I love this game and this is the first real problem I have had.

Thanks

Ken

How long did you wait? Can you try the whole process again and be sure to wait a long time? Also, if you have an aggressive virus scanner, you may want to set it to not scan files in the PureSim folder.

[Sarge]

ORIGINAL: puresimmer

Not the crash dump. To be honest that helps very little. The biggest help is an exact set of steps for me to follow and a saved copy of the association that demonstrates the crash. At this point 99.9% of remaining crash issues with PureSim are extremely spurious and very difficault to reproduce, or they are related to environmental/configuration issues.

I'll keep plugging though, so the more reports the better!

I have found that if I minimize the game and close out the main option screen that loads my saved games my crashes are by far more frequent.

[Woodruff]

ORIGINAL: Woodruff

Funny you should mention this, as I just had a crash.

Tie game 3-3, top of the 8th inning. Fly ball to left field with one out, it asked me if I wanted to have the guy at 2nd (with a 12 speed!) tag up and move to third. I hit either the space bar or N (I was reaching for N, but not positive which I hit), and the game gave me the "Puresim must close, anything you were working on may be lost" error message.

Shaun, I just had this error happen again (this time with a player who was a 61 speed at least, so should be running). Other than that, the only difference is that this time I'm certain I selected "N" (for no). Same error message and everything.

So there's apparently something going on with this.

[Woodruff]

And it just happened again, though this time the baserunner was on THIRD base. The other difference is that this time, I selected YES to try for home.

So apparently, the yes/no option has nothing to do with the problem.

This is the third or fourth time I've seen this "tag-up crash" however.

[Woodruff]

New one here...

Bases loaded, no outs
Batter hits grounder to 1B
Unable to turn DP, but now 1 out
But bases still loaded with batter on 1B and previous runners still on 2nd and 3rd
Runner who was on first is gone, but guys on 2nd and 3rd didn't move?
I find that unlikely. <smile>

[Woodruff]

ORIGINAL: Woodruff

And it just happened again, though this time the baserunner was on THIRD base. The other difference is that this time, I selected YES to try for home.

So apparently, the yes/no option has nothing to do with the problem.

This is the third or fourth time I've seen this "tag-up crash" however.

Shaun, just had this one happen to me two more times today, and I'm using the latest RC 1.37. It ALWAYS happens on a tag-up, either from 2nd or 3rd.

I don't have any changes to the .xml file, so I'm sure it's not caused by that.

I have 2GB of memory, so I'm quite sure that's not the issue either.

[Woodruff]

Shaun,

Tag-up crash still there in 1.38.

I'm not pointing this out to nag or to imply you need to get on it. I just want to make sure you know that using the latest version, it hasn't gone away.