Forums

Bug Report Submissions

• AlaCowboy 1,321 Posts

  Wed, Jun 23 2010 3:12 PM

  WGT should send an email to the Bug Report sender to let them know what has been done to resolve the bug. That would let us know that our voices are heard.

• WGTniv 1,788 Posts

  Wed, Jun 23 2010 3:32 PM

  Hi Ala,

  Hundreds of bug reports are sent in daily, however, a large percentage of what is reported as a bug is often not a bug or the report itself is not very clear.  We often receive bug reports where the text says something to the effect of "Fix This!", but no details are provided so the guys have no idea what they are supposed to look for.  Also, in many cases the same bug is reported by numerous different players.

  Emails are not sent because they simply do not have the time to send them, but also because player identity is not sent along with the report.  It's not necessary for the devs to know who are you in order to locate the bug itself. They just need the shot data sent in the report.  It would not be good time management if they had to send out numerous emails to every single player for each report because they would spend their day writing emails instead of working on fixing the actual bugs. 

  Unfortunately, we're not going to able to share every single thing we are doing, but bug reports are certainly not ignored.  Some may take higher priority over others and low priority bugs may be visible for a while, but they will all be taken care of as soon as is feasible.

  The best thing you can do is provide the most detailed bug report that you can, much like MisterWGT has shown in his example here.  The most detailed bug reports are usually the most helpful ones.

• AlaCowboy 1,321 Posts

  Wed, Jun 23 2010 4:29 PM

  WGTniv:

  Hi Ala,

   

  The best thing you can do is provide the most detailed bug report that you can, much like MisterWGT has shown in his example here.  The most detailed bug reports are usually the most helpful ones.

  Well, I just tried to submit a bug report on a little situation on Oakmont but the program would not allow me to do so. Here it is:

  Hole 13 - 193 yd par 3. Hit drive to back fringe. (looked about 3" to green)

  31 ft putt with 2 ft downslope. Set meter to 15 ft scale and hit putt with 8 ft power. Went "0" ft.

  Same set but hit with 15 ft power. went "0" ft.

  3rd hit same distance and slope hit with 7 ft power - rolled 36 feet past the hole.

  31 + 36 = 67 feet.

  Now, 36 ft uphill with 18" upslope. Hit putt on 45 ft meter with 45 ft power. Rolled 4.5 ft past hole.

  4.5 ft putt with 1" downslope. Hit it with 3 ft power. Rolled 5.6 ft past hole.

  Hit 5.6 ft putt with 1" upslope with 7 ft power. Stopped 6" short.

  Tapped in.

  Routine 8 on Oakmont.

  To WGTniv: why couldn't I submit a "bug report?" was it indeed a bug to not be able to putt even an inch from the fringe on the edge of the green?

  To all others: See why I think the greens are unrealistic here? I have never complained about the other courses or the game but this is completely ridiculous.

  
  

  
  

  
  

• AlaCowboy 1,321 Posts

  Wed, Jun 23 2010 4:32 PM

  WGTniv:

  Hi Ala,

   

  The best thing you can do is provide the most detailed bug report that you can, much like MisterWGT has shown in his example here.  The most detailed bug reports are usually the most helpful ones.

  Well, I just tried to submit a bug report on a little situation on Oakmont but the program would not allow me to do so. Here it is:

  Hole 13 - 193 yd par 3. Hit drive to back fringe. (looked about 3" to green)

  31 ft putt with 2 ft downslope. Set meter to 15 ft scale and hit putt with 8 ft power. Went "0" ft.

  Same set but hit with 15 ft power. went "0" ft.

  3rd hit same distance and slope hit with 7 ft power - rolled 36 feet past the hole.

  31 + 36 = 67 feet.

  Now, 36 ft uphill with 18" upslope. Hit putt on 45 ft meter with 45 ft power. Rolled 4.5 ft past hole.

  4.5 ft putt with 1" downslope. Hit it with 3 ft power. Rolled 5.6 ft past hole.

  Hit 5.6 ft putt with 1" upslope with 7 ft power. Stopped 6" short.

  Tapped in.

  Routine 8 on Oakmont.

  To WGTniv: Why couldn't I submit a "bug report?" was it indeed a bug to not be able to putt even an inch from the fringe on the edge of the green?

  To all others: See why I think the greens are unrealistic here? I have never complained about the other courses or the game but this is completely ridiculous.

  
  

  
  

  
  

• VanHalenLover 1,422 Posts

  Wed, Jun 23 2010 5:48 PM

  AlaCowboy:

  To all others: See why I think the greens are unrealistic here? I have never complained about the other courses or the game but this is completely ridiculous.

  Ala,

  It is an unpopular opinion, but I agree with you. And it isn't just Oakmont, although it is more prevalent there based on the overall greatly difficulty of the course.  There are numerous quirks that have showed up since Oakmont reared its ugly head, and the characteristics of the entire game seem to lean towards building lower scores into the rounds.

  I'm all for a crappy round and can take it in stride if it is because I am hitting badly. What I can't stand is poor programming and a built in deviation that forces bad shots even when the setup and execution is perfect. Unfortunately, this appears to be the wave of the future here, so I think we have no choice but to accept it and go about our business letting the code determine how well we score. I'd personally rather see Jokemont scrapped until it works, but we know that isn't gonna happen.

   

• AlaCowboy 1,321 Posts

  Wed, Jun 23 2010 8:54 PM

  VanHalenLover:

  AlaCowboy:

  To all others: See why I think the greens are unrealistic here? I have never complained about the other courses or the game but this is completely ridiculous.

  Ala,

  It is an unpopular opinion, but I agree with you. And it isn't just Oakmont, although it is more prevalent there based on the overall greatly difficulty of the course.  There are numerous quirks that have showed up since Oakmont reared its ugly head, and the characteristics of the entire game seem to lean towards building lower scores into the rounds.

  I'm all for a crappy round and can take it in stride if it is because I am hitting badly. What I can't stand is poor programming and a built in deviation that forces bad shots even when the setup and execution is perfect. Unfortunately, this appears to be the wave of the future here, so I think we have no choice but to accept it and go about our business letting the code determine how well we score. I'd personally rather see Jokemont scrapped until it works, but we know that isn't gonna happen.

   

  Well, I vote to move it to Latrobe CC. Some history there too.   :)

• 912 Posts

  Mon, Aug 15 2011 5:51 PM

  Dont know if anyone will see this but i was doing a ready go and hit a tree that was not there saved replay will show you

  what is going on?

   

  http://www.wgt.com/gameclient.aspx?view=showReplay&JSON=%257B%2520%2522GUID%2522%2520%253A%2520%2522c6088332-790a-4f3a-bba6-9f400188481f%2522%252C%2520%2522Brand%2522%2520%253A%2520%2522undefined%2522%2520%257D

• SOYEL1 698 Posts

  Tue, Aug 16 2011 6:05 AM

  Can anyone see this and tell me if this isn't a bug? I am still running first in the tournament but I am sure I was robbed of an Eagle in this hole and for sure, a better score. Here is the replay for anyone who wants to watch it, or simply in my replays.. isn't it in?

   How can I write to WGT or start a thread?

  Thanks

• SOYEL1 698 Posts

  Tue, Aug 16 2011 6:06 AM

  http://wgt.com/replay.aspx?ID=297eed09-ec28-4da4-9f07-9f40015e51f8

   

   

  Sorry, had forgotten the link

   

• 1Rodeo 7 Posts

  Tue, Nov 6 2012 8:33 AM

  Howdy,

  I was wondering what is being done with people that forfeit being given the victory because they have the lowest score?... This has been going on for about a week now and would hate to see false reports on average and wins due to this issue.