Video Review Gets it Wrong? - Operation Sports Forums

Video Review Gets it Wrong?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • 5th_fathom
    Rookie
    • Sep 2009
    • 60

    #1

    Video Review Gets it Wrong?

    Has anyone else had the Umpire's get a video review of a Homerun wrong?

    Playing in Texas, the CPU bashes a flyball straight down the line, just barely foul (missed the pole by a few feet). The original call was HR, but the umps did a a review. On the replay, it's clear that the ball was foul, but the crew cheif called it a HR anyway.

    If anyone else has seen this, do you think it's a "bug" that needs fixing, or just another part of the game? (video reviews aren't perfect in real life).

    Thoughts?
  • countryboy
    Growing pains
    • Sep 2003
    • 52635

    #2
    Re: Video Review Gets it Wrong?

    I haven't had a call be blantly wrong on a replay, but I would chalk it up to just part of the game. Sometimes, even on a review, the verdict is incorrect.
    I can't shave with my eyes closed, meaning each day I have to look at myself in the mirror and respect who I see.

    I miss the old days of Operation Sports :(


    Louisville Cardinals/St.Louis Cardinals

    Comment

    • IR0NS1N
      Rookie
      • Apr 2010
      • 5

      #3
      Re: Video Review Gets it Wrong?

      I had a game where Braun hit a foul ball and it was very easily foul and they called it a HR even after a video review, I didnt care cause we won the game cause of it.

      Comment

      • bubba22plus
        Rookie
        • May 2009
        • 248

        #4
        Re: Video Review Gets it Wrong?

        I really have only seen the review animation once.

        Most of my Home Runs have been to left or right field, not down the line.

        Comment

        • ckarlic
          So Real!!
          • May 2003
          • 5003

          #5
          Re: Video Review Gets it Wrong?

          Originally posted by 5th_fathom
          Has anyone else had the Umpire's get a video review of a Homerun wrong?

          Playing in Texas, the CPU bashes a flyball straight down the line, just barely foul (missed the pole by a few feet). The original call was HR, but the umps did a a review. On the replay, it's clear that the ball was foul, but the crew cheif called it a HR anyway.

          If anyone else has seen this, do you think it's a "bug" that needs fixing, or just another part of the game? (video reviews aren't perfect in real life).

          Thoughts?
          Most of the time they get it right...Unlike Madden's reviews, the Show's are much better
          PSN: ckarlic
          Xbox Live: dab1gg00ch
          Twitch Channel (Main Gaming Page)
          New Youtube Gaming Channel -- SpicyChicharron
          Follow me on Twitter

          Comment

          • 5th_fathom
            Rookie
            • Sep 2009
            • 60

            #6
            Re: Video Review Gets it Wrong?

            Good to know I'm not the only one.

            It was a little frustrating, as it really hurt my pitchers confidence early in the game, but I just chalked it up to being a part of the "experience", and carried on.

            I don't think it's worth a mention in the "Bugs" thread... unless they get the next one wrong and make me lose the game... in which case I'll proclaim the game is "broken" and throw a hissy-fit.

            Comment

            • bonannogiovanni
              MVP
              • Oct 2004
              • 1339

              #7
              Re: Video Review Gets it Wrong?

              The same thing happened to me today, here's a foul ball called HR after review

              <object width="480" height="385"><param name="movie" value="http://www.youtube.com/v/vJKIPz94nSU&hl=en_US&fs=1&"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/vJKIPz94nSU&hl=en_US&fs=1&" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="480" height="385"></embed></object>

              Comment

              • jim416
                Banned
                • Feb 2003
                • 10608

                #8
                Re: Video Review Gets it Wrong?

                Your video is a graphical glitch. Look at it again. It's not foul, stop the video at 37 seconds. It goes through the mesh. It appears it should have hit it and bounced away. Definitely a fair ball.

                Comment

                • jobforacreebree
                  Rookie
                  • Jun 2010
                  • 35

                  #9
                  Re: Video Review Gets it Wrong?

                  Originally posted by jim416
                  Your video is a graphical glitch. Look at it again. It's not foul, stop the video at 37 seconds. It goes through the mesh. It appears it should have hit it and bounced away. Definitely a fair ball.
                  i clearly do not see what you're seeing. seems like a foul ball to me, not once does it appear to go through the mesh, IMHO

                  Comment

                  • Spring Rubber
                    Rookie
                    • Jan 2010
                    • 477

                    #10
                    Re: Video Review Gets it Wrong?

                    Originally posted by jobforacreebree
                    i clearly do not see what you're seeing. seems like a foul ball to me, not once does it appear to go through the mesh, IMHO
                    I concur. It looks like it goes completely to the right of the pole. The only thing I can think of is that the game registered the ball as barely clipping the pole, but I'm pretty sure that would have resulted in a "doink" noise.

                    Comment

                    • Phoenixmgs
                      Banned
                      • Feb 2009
                      • 773

                      #11
                      Re: Video Review Gets it Wrong?

                      Originally posted by jobforacreebree
                      i clearly do not see what you're seeing. seems like a foul ball to me, not once does it appear to go through the mesh, IMHO
                      I agree. The ball never goes behind the pole. Even if it went through the mesh, it should've still went behind the pole.

                      Comment

                      • bonannogiovanni
                        MVP
                        • Oct 2004
                        • 1339

                        #12
                        Re: Video Review Gets it Wrong?

                        Originally posted by jim416
                        Your video is a graphical glitch. Look at it again. It's not foul, stop the video at 37 seconds. It goes through the mesh. It appears it should have hit it and bounced away. Definitely a fair ball.
                        Hey Jim, 37 is the length of the video, where should I stop it then? However as the above posters have stated, there'so no way the ball went through the mesh. At most there's a collision detection glitch, the game registered the ball to have grazed the pole.

                        Comment

                        • jdmorgan3
                          Banned
                          • Apr 2008
                          • 254

                          #13
                          Re: Video Review Gets it Wrong?

                          I had one that I couldn't even tell if it was a HR or not and it wasn't reviewed. The ball scraped over the wall and it was right in the corner at ... Coors Field. At first I thought it just got over the wall and hit the pole, upon watch countless replays it seemed like it hit the top of wall and bounced back without hitting pole. I spent nearly 5 minutes trying to decide and didn't come to a conclusion.

                          I had a faint idea that the ball cleared the wall, but was foul. Seemed like it bounced just to the left of the pole, but it wasn't obvious. THey called HR and there was no review. This is what led to my investigation. It tied the game at 2-2 in the bottom of the 7th so it was a big play. I won in 11, but it was a shame that replay wasn't used, it was the perfect situatuion.

                          Comment

                          • ZoneKIller
                            MVP
                            • Mar 2009
                            • 1394

                            #14
                            Re: Video Review Gets it Wrong?

                            Thats why I'm not an Umpire
                            Find out the Truth http://www.amazon.com/Secrets-Heaven...1163314&sr=1-1

                            Comment

                            • Woodweaver
                              Developer
                              • Apr 2006
                              • 1147

                              #15
                              Re: Video Review Gets it Wrong?

                              Originally posted by bonannogiovanni
                              Hey Jim, 37 is the length of the video, where should I stop it then? However as the above posters have stated, there'so no way the ball went through the mesh. At most there's a collision detection glitch, the game registered the ball to have grazed the pole.
                              There is a common problem in 3D rendering called Z-buffer draw order glitches. When drawing 3D objects onto a 2D screen, renders obviously want to draw the closest objects to the camera last (so they appear "in front" of objects "behind them"). The problem occurs when objects are close together (a la colliding). It can be difficult to determine (or impossible depending on the camera angle) to draw the objects in the right order to accurately depict the "real world" interaction. I don't want to speak for Jim, but I think this was what he's getting at...

                              In any case, after looking at the video, I think you are probably right that this is most likely a collsion detection bug. It appears that the ball's path changes direction slightly as it passes the foul pole like it is grazing some phantom collision polys. Often times, an "invisible" set of collision geometry of lower poly count (for optimization) is referenced for collision detection. If that geometry does not closely enough match the displayed polys or if it does not "line up" correctly, then you can see bugs like this one.
                              "Yeah, well, you know, that's just, like, your opinion, man"

                              Comment

                              Working...