Questionable CPU Baserunning Decisions

Collapse

Recommended Videos

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Maestro23
    Rookie
    • Feb 2003
    • 140

    #16
    Re: Questionable CPU Baserunning Decisions

    Those were when I was in my EA Brainwashed years. Thank the baseball gods that I finally saw the light.. Forgive me..

    Comment

    • Maestro23
      Rookie
      • Feb 2003
      • 140

      #17
      Re: Questionable CPU Baserunning Decisions

      Those were when I was in my EA Brainwashed years. Thank the baseball gods that I finally saw the light.. Forgive me..

      Comment

      • Leebo33
        Rookie
        • Jul 2002
        • 194

        #18
        Re: Questionable CPU Baserunning Decisions

        Sully,

        I am playing at the All-Star level. Hopefully, last night's game was just an aberration. I could handle these occasionally as baserunning mistakes happen in real life too. It's just the frequency of mistakes in this one game that alarmed me.

        Comment

        • Leebo33
          Rookie
          • Jul 2002
          • 194

          #19
          Re: Questionable CPU Baserunning Decisions

          Sully,

          I am playing at the All-Star level. Hopefully, last night's game was just an aberration. I could handle these occasionally as baserunning mistakes happen in real life too. It's just the frequency of mistakes in this one game that alarmed me.

          Comment

          • alangst1
            Rookie
            • Mar 2003
            • 27

            #20
            Re: Questionable CPU Baserunning Decisions

            I would have to agree that once the opposing team reaches 3rd, they seem to become a little more conservative. The only questionable AI in baserunning I have seen is that with 1 out and a man on third, with a grounder to the right side the runner will stay, whereas in the real life, in most cases the runner would go home. I've also tried to get a DP with a man on first and third, and an infield grounder, and the man will stay on third.

            In every other instance, though, the AI is smartly aggressive, hard to throw out, and will take the extra base if you screw around.

            Great Game.

            Comment

            • alangst1
              Rookie
              • Mar 2003
              • 27

              #21
              Re: Questionable CPU Baserunning Decisions

              I would have to agree that once the opposing team reaches 3rd, they seem to become a little more conservative. The only questionable AI in baserunning I have seen is that with 1 out and a man on third, with a grounder to the right side the runner will stay, whereas in the real life, in most cases the runner would go home. I've also tried to get a DP with a man on first and third, and an infield grounder, and the man will stay on third.

              In every other instance, though, the AI is smartly aggressive, hard to throw out, and will take the extra base if you screw around.

              Great Game.

              Comment

              • rock85
                MVP
                • Jul 2002
                • 3146

                #22
                Re: Questionable CPU Baserunning Decisions

                Alan i had the same thing man on first and third they went for the double play and the runner on third stayed

                Comment

                • rock85
                  MVP
                  • Jul 2002
                  • 3146

                  #23
                  Re: Questionable CPU Baserunning Decisions

                  Alan i had the same thing man on first and third they went for the double play and the runner on third stayed

                  Comment

                  • Brando70
                    Pro
                    • Jul 2002
                    • 646

                    #24
                    Re: Questionable CPU Baserunning Decisions

                    </font><blockquote><font class="small">Quote:</font><hr />
                    I would have to agree that once the opposing team reaches 3rd, they seem to become a little more conservative. The only questionable AI in baserunning I have seen is that with 1 out and a man on third, with a grounder to the right side the runner will stay, whereas in the real life, in most cases the runner would go home. I've also tried to get a DP with a man on first and third, and an infield grounder, and the man will stay on third.

                    In every other instance, though, the AI is smartly aggressive, hard to throw out, and will take the extra base if you screw around.

                    Great Game.

                    <hr /></blockquote><font class="post">

                    That's been my experience for the most part. The AI is pretty conservative on infield hits, but reacts--for the most part--pretty well on outfield hits. I would say the CPU manufactures about 75-80% of its runs, and a lot of that is because its aggressive on balls to the outfield.

                    Comment

                    • Brando70
                      Pro
                      • Jul 2002
                      • 646

                      #25
                      Re: Questionable CPU Baserunning Decisions

                      </font><blockquote><font class="small">Quote:</font><hr />
                      I would have to agree that once the opposing team reaches 3rd, they seem to become a little more conservative. The only questionable AI in baserunning I have seen is that with 1 out and a man on third, with a grounder to the right side the runner will stay, whereas in the real life, in most cases the runner would go home. I've also tried to get a DP with a man on first and third, and an infield grounder, and the man will stay on third.

                      In every other instance, though, the AI is smartly aggressive, hard to throw out, and will take the extra base if you screw around.

                      Great Game.

                      <hr /></blockquote><font class="post">

                      That's been my experience for the most part. The AI is pretty conservative on infield hits, but reacts--for the most part--pretty well on outfield hits. I would say the CPU manufactures about 75-80% of its runs, and a lot of that is because its aggressive on balls to the outfield.

                      Comment

                      • famousmortimer
                        Rookie
                        • Jul 2002
                        • 337

                        #26
                        Re: Questionable CPU Baserunning Decisions

                        The problem, as I see it (25 games played) is two things:

                        1. Outfielders arms too strong
                        2. Too many well hit line drives.


                        I was having the same problems as you other guys. Hit after to hit to right field was not moving the runner from first to third. Hit after hit to the outfield was not moving the runner from second to home.

                        Popup after popup to right or left field wasnt making the runner on third tagup.

                        Now i know these things dont happen everytime in these situations... but i would argue they happen the majority of the time.

                        But, I played on anyway and I finally did see a tagup (on the warning track in left). I finally did see a baserunner move 2 bases on a single. The thing was, those singles were lightly hit.

                        To balance the game I changed all of my outfielders arms to being rated 30 (down from near 90 for all my players). This has helped a little.


                        Seriously, next time you play this game see how long it takes for a ball to be thrown from deep in the outfield to third base. It's insanely quick. Couple that with the fact that the vast majority of hits are solidly struck line drives and you end up with a game where the CPU doesn't want to run from first to third.

                        Bet aware, though, that it does happen. Just not nearly enough.



                        And too all of you who don't see it, i don't think you are looking for it. It's very clear cut.

                        Comment

                        • famousmortimer
                          Rookie
                          • Jul 2002
                          • 337

                          #27
                          Re: Questionable CPU Baserunning Decisions

                          The problem, as I see it (25 games played) is two things:

                          1. Outfielders arms too strong
                          2. Too many well hit line drives.


                          I was having the same problems as you other guys. Hit after to hit to right field was not moving the runner from first to third. Hit after hit to the outfield was not moving the runner from second to home.

                          Popup after popup to right or left field wasnt making the runner on third tagup.

                          Now i know these things dont happen everytime in these situations... but i would argue they happen the majority of the time.

                          But, I played on anyway and I finally did see a tagup (on the warning track in left). I finally did see a baserunner move 2 bases on a single. The thing was, those singles were lightly hit.

                          To balance the game I changed all of my outfielders arms to being rated 30 (down from near 90 for all my players). This has helped a little.


                          Seriously, next time you play this game see how long it takes for a ball to be thrown from deep in the outfield to third base. It's insanely quick. Couple that with the fact that the vast majority of hits are solidly struck line drives and you end up with a game where the CPU doesn't want to run from first to third.

                          Bet aware, though, that it does happen. Just not nearly enough.



                          And too all of you who don't see it, i don't think you are looking for it. It's very clear cut.

                          Comment

                          Working...