GC hawk hitting zones

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • SimGuy555
    Junior Member
    • Nov 2020
    • 18

    #1

    GC hawk hitting zones

    In the process of building my sim. I have a 7.7’ x 13’ screen and a GC hawk. Few questions-

    1) at the recommended 9-10’ between ball and screen, i feel like shots with my 56 degree will hit the ceiling before the screen. Am I crazy?

    2) is there any reason a righty couldn’t hit from the left handed hitting zone? If i hit one off the toe I could see it completely missing the screen to the right
  • StalefishFS3
    Senior Member
    • Mar 2019
    • 186

    #2
    I don't have a Hawk, but I asked this same question a while back. I think the answer is if a righty hits from the left zone, it should work, but everything in your stats will be backwards. Thus, if you hit a hook, it will measure as a slice. I wouldn't think this would matter playing a sim, since ball data is all that matters. But for improvement purposes, everything will be screwed up

    Comment

    • mthunt
      Ultimate Member
      • Aug 2014
      • 4746

      #3
      Originally posted by SimGuy555 View Post
      In the process of building my sim. I have a 7.7’ x 13’ screen and a GC hawk. Few questions-

      1) at the recommended 9-10’ between ball and screen, i feel like shots with my 56 degree will hit the ceiling before the screen. Am I crazy?

      2) is there any reason a righty couldn’t hit from the left handed hitting zone? If i hit one off the toe I could see it completely missing the screen to the right
      The hawk is an offset device so it can go in a more narrow room. As for the ball, it’ll hit the ceiling. Add baffles.
      My Courses:
      World Par 3's by mthunt
      Toronto GC (L) mthunt
      Burlington G&CC by mthunt
      Weston G&CC by mthunt
      London Hunt Club L mthunt
      Park CC Lidar mthunt
      Sunningdale GC Robinson L
      Sunningdale GC Thompson L
      Muirfield Village (liDAR) First Ever Lidar course
      Country Club of Castle Pines (liDAR)
      The Sanctuary GC ProTee L
      The National GC L mthunt
      Mississaugua GC L mthunt
      Shaughnessy G&CC L mthunt
      Markland Woods CC mthunt
      Hidden Lake Old L mthunt
      Magna GC L mthunt
      Barrie CC L mthunt
      mthunt Range

      Comment

      • JonH59
        Member
        • Oct 2019
        • 67

        #4
        I hope this isn't too late....

        I just went down and checked my machine with club data. For a righty, hitting on the lefty side, the only thing I noticed is that my draw (as a righty that showed a little in-to-out swing path) turned into an out-to-in path with a fade when hit from the lefty side. The other info looked the same to me but it's been a long day. The machine saw the spin and it registered the flight going in the same direction and it was still called L spin.

        I hope that make sense.

        And, I hit my 60º and the ball hit about 2/3 the way up my screen. My ball sits about 10 feet from the screen and the screen is about 10 feet tall and 17 wide.

        Hope that helps,
        Jon in American Fork

        Comment

        • jbob121
          Junior Member
          • Sep 2024
          • 1

          #5
          Hi, as a follow up to this, I’ve been trying to figure out the distance between the left and right club data zones. I’ve found 2 guides on the Foresight website, one that indicates the distance between them is 12” and another that indicate 6-8” (depending on ceiling height). Their support team has not been helpful at all letting me know which is correct.

          I’d ideally like to hit from a hitting strip (or 2 next to each other) from the center of the room due to past wrist injuries. If the gap is going to be too wide between the club data zones I might go for the Uneekor Eye XO2. I’d prefer the GCHawk if I can make it work though due to Multisport and having read good reviews.

          Appreciate any information anyone can provide. My ceiling height will likely end up being around 10.5’.

          Comment

          Working...