Some observations - and that pesky error 91 (Full Version)

All Forums >> [Current Games From Matrix.] >> [Sports] >> PureSim Baseball



Message

roo23 -> Some observations - and that pesky error 91 (8/26/2005 6:03:49 PM)

A few quick observations...

I think someone mentioned this before, but after trying it out (a lot) it is still far too easy to steal home. When I began playing I tried once or twice, and probably failed, so I was realistic in my choices and didn't attempt quite so much. But after it was mentioned, I thought I'd check it out. With a guy who has speed in the 90's, it is easy to steal 2nd, 3rd, and home, often with the same batter at the plate. Maybe the solution is for the runner to have a lower chance of 'getting a good jump' - thereby staying put - when the manager calls for steals of successive bases like that (rather than lower the probability of a successful steal). Just a thought...

And I have noticed when stealing bases often the ball/strike count will change. For example, my guy tries to steal second, the count reads 3-1, successful steal. Next line might say that the count is 1-2, batter lines out. I haven't been able to catch whether the pitch counts are tallying correctly (just noticed this one).

And as for the error 91, which popped up for me before, it's back. I had been able to fix that by uninstalling and re-installing the game, but that fix does't seem to work this time. I have a feeling it's got something to do with my dinosaur computer or the association, but not so sure. Running Win ME (ugh), IE 6, RC1 (gold), historical replay (old association - could have been started with any version I can't remember which). There is a new laptop on the way so I was going to wait and see if the problem persists, but I will just throw this out there for you, Shaun... Happy to wait on this.

Chris



Amaroq -> RE: Some observations - and that pesky error 91 (8/26/2005 11:29:21 PM)

I wonder if your observations are somewhat related - e.g., if its not honestly tracking the count but is rather re-generating a random one.

What if the mechanic worked something like this:
User orders a 'steal'
Game determines how many pitches it takes for him to 'get a jump' (J)
Game determines how many pitches the batter can wait for him (e.g., before 2 strike count), and adds one to that number. (P)

If (P < J), then resolve the at bat.
If (J < P), then resolve the steal.
If (J == P), do special case for the resolution of the runner jumping as the at bat resolves - with the added chances of the strike out / steal play, strike-em-out throw-em-out double play, line drive double play, the walk negating the steal attempt, the walk but runner stealing third play, increased base taken play, and the famous 'scores from first on a single' play.

In the "steal second, steal third, steal home" case, then you would continue increasing J - meaning that its possible but unlikely that you'd be able to steal more than one base in an at-bat, and nearly impossible to steal three in a single plate appearance.

... another thought, maybe (J) should have a much larger value for 'steal of home'? Just making it harder to get the jump in a single at bat.



Frozen Stiffer -> RE: ...that pesky error 91 (8/27/2005 3:40:52 AM)

You know... I've been getting Error 91 a few times as well.

It always happens after I do the same thing, but it doesn't happen every time I do that same thing... make sense? It seems that before a game when I'm at the lineup card, since there's no way to tell the players' fatigue levels from that screen (something I've suggested to Shaun before), I go to change the lineup. This takes me to a screen where I can see who's on the card and who's on the bench; this is also how I can see who's tired and who's not. Anyway, all my Error 91 occasions have happened after I've made a change on the lineup or when I have to go back in a 2nd time and make another change. Regretfully, I can't duplicate it on command regardless of what I do, but that's definitely the only time it ever comes up.

Oh, forgot to mention; I'm running Windows 2000 on the laptop and WinXP on the desktop (both of which have the game installed and both of which have received the error under the above-mentioned conditions), IE 6.0 and RC1. The error occurs regardless of what type of association (real or fictional) or what size.




33sherman -> RE: ...that pesky error 91 (8/27/2005 6:33:18 AM)

I get the error too, under similar circumstances(modify roster, then go back to sim some games, then error 91).



MizzouRah_slith -> RE: ...that pesky error 91 (8/27/2005 9:47:34 PM)

I'm seeing the same error. Most of the time when I go to manage a game after looking at my roster.



ChiefT -> RE: ...that pesky error 91 (8/28/2005 12:10:58 AM)

It happens to me frequently. Also, my mouse does not respond sometimes during the game. I'll have to use the keyboard. Once I shut the game down and restart it, it works fine, but, I have to finish the entire game with the keyboard before I can do that. I wish there was a save game option.

This is a fun game, and totally addictive, and I only think I've scratched the surface with it's capabilities. I hope these small but annoying bugs can get worked out. This is the 2nd version I've registered. This one is far cleaner than the previous one.



Frozen Stiffer -> RE: ...that pesky error 91 (8/28/2005 4:18:35 AM)

I'm currently running two leagues simultaneously. With one, I sim in 1-week batches; in the other, I manage each and every game. The error has only happened with the managed games, since that's (obviously) the only opportunity I get to make a change to the lineup card.


Just FYI, I haven't had a mouse problem.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
1.265625