garyg
Weekend Golfer
Posts: 138
TGCT Name: Gary Green
|
Post by garyg on May 19, 2016 7:06:09 GMT -5
I've only been playing this game a few weeks but I've noticed a weird issue with replays. When I occasionally hit a great shot I'll check out the replay, usually saving it as well. I've noticed the shot in the replay often has a different result to what actually happened!
In one instant I nearly got an albatross, hitting the pin with my 2nd shot on a par 5, with the ball dropping within an inch of the hole. I instantly checked the replay and it showed me actually holing the shot, so I thought I'd save that, make it look like I had an albatross haha. When I checked the replay again from the main menu the shot showed the ball missing the pin and going about 50 foot passed the hole! Two different replays for a shot, with none of them actually being correct!
Is this a common issue with everyone, a bug in the game I'm assuming?
|
|
|
Post by TimB on May 19, 2016 8:01:25 GMT -5
Yep it's a bug. Don't know the exact details of why it happens
Here is a replay of another member who asked me to get it for him since he had no way of capturing at the time.
I played his ghost and when the hole came up went to view his replay and this is what it showed. In reality it was a hole in one
|
|
garyg
Weekend Golfer
Posts: 138
TGCT Name: Gary Green
|
Post by garyg on May 19, 2016 8:32:21 GMT -5
That's quite the shot haha, but yeah not quite a hole in one! It's a shame this hasn't been fixed, surely the game has been out long enough for them to do so?
|
|
|
Post by TreeWood on May 19, 2016 13:52:04 GMT -5
Yep.... I've had the same. An ace, but the replay shows the ball just kissing the hole as it rolls a foot past :-(
|
|
|
Post by Brighttail on May 19, 2016 16:10:14 GMT -5
Here is the reason: When you take a shot, the entire shot is NOT saved to the HB servers. The only thing that is saved is everything your golfer is doing, the club, the aim, the swing, ect, everything right up to the point of impact with the ball. The reason is this saves memory. It would take a lot more memory to save the entire flight of the shot from start to finish.
So when you watch a replay or if you are playing someone and watch them shoot their shot, the info that was saved (right up to the point of impact) is sent to the replay engine or to your opponent. At this point the computer has to recalculate the shot based on the information it was given. Things like wind, green slope, the little bug you didn't see walking across your line, are all recalculated and thus the shot you see on replay or from your opponent may be different than actually what happened.
This makes more sense that if you are watching an opponent's shot, the difference between your computer/console and theirs may be slightly different when it comes to GPU/CPU power and thus "rounding issues" may explain why on your screen your opponent's shot misses while on theirs it goes in.
When you are watching a replay tho things like the wind kicking up one MPH or slightly changing direction does effect the shot you are watching on replay. But what about putts? You can watch a replay of a putt 10 times and get several different results. HB claims minute green conditions do get effected by wind in the calculations and a difference of .001 can effect a putt exponentially over a 10 foot putt. I particularly believe that there is a built in set of randomness in every shot. This is why when you hit a default PW for 120 yards with no wind, sometimes it goes 110 and other times 128 yards.
Simply put, it has been around from the beginning and it isn't going to get fixed unless they save more conditions of the original shot. Doing so takes more memory. More memory means more storage needed on their server and more information that has to be transferred to player's consoles/computers. Even if they could save an entire shot (even temporarily) depending on your ISP and internet speed, playing an opponent with full saving would take much longer than it does already due mainly to the increased amount of data needed to be transferred for each and every shot, each player takes.
|
|
garyg
Weekend Golfer
Posts: 138
TGCT Name: Gary Green
|
Post by garyg on May 19, 2016 17:07:10 GMT -5
Here is the reason: When you take a shot, the entire shot is NOT saved to the HB servers. The only thing that is saved is everything your golfer is doing, the club, the aim, the swing, ect, everything right up to the point of impact with the ball. The reason is this saves memory. It would take a lot more memory to save the entire flight of the shot from start to finish. So when you watch a replay or if you are playing someone and watch them shoot their shot, the info that was saved (right up to the point of impact) is sent to the replay engine or to your opponent. At this point the computer has to recalculate the shot based on the information it was given. Things like wind, green slope, the little bug you didn't see walking across your line, are all recalculated and thus the shot you see on replay or from your opponent may be different than actually what happened. This makes more sense that if you are watching an opponent's shot, the difference between your computer/console and theirs may be slightly different when it comes to GPU/CPU power and thus "rounding issues" may explain why on your screen your opponent's shot misses while on theirs it goes in. When you are watching a replay tho things like the wind kicking up one MPH or slightly changing direction does effect the shot you are watching on replay. But what about putts? You can watch a replay of a putt 10 times and get several different results. HB claims minute green conditions do get effected by wind in the calculations and a difference of .001 can effect a putt exponentially over a 10 foot putt. I particularly believe that there is a built in set of randomness in every shot. This is why when you hit a default PW for 120 yards with no wind, sometimes it goes 110 and other times 128 yards. Simply put, it has been around from the beginning and it isn't going to get fixed unless they save more conditions of the original shot. Doing so takes more memory. More memory means more storage needed on their server and more information that has to be transferred to player's consoles/computers. Even if they could save an entire shot (even temporarily) depending on your ISP and internet speed, playing an opponent with full saving would take much longer than it does already due mainly to the increased amount of data needed to be transferred for each and every shot, each player takes. Nice explanation, thanks, makes more sense now. It does make me wonder why they added an option of a replay in the first place if they knew it wouldn't necessary be an exact replay. Anyway it doesn't really bother me, I just found it odd that's all.
|
|
|
Post by Brighttail on May 19, 2016 17:34:22 GMT -5
You should have seen it before they fixed a wind bug. The wind used to be one of those things that wasn't saved at all, especially in tournaments. So you'd be playing a ghost and see the ball fly out of bounds and think, "Wow sux to be them." only to have the next shot appear to be shot from the middle of the fairway, and then miss the green by 20 yards, only to have their next shot being putted from 3 feet away. Very confusing and useless. For saved replays some of my old hole in ones that went in during game play, the replay would show them falling short of the green by up to 40 yards.
|
|
|
Post by TravisC555 on May 19, 2016 20:50:26 GMT -5
If you have an nvidia card you can use shadowplay to record the last x minutes of gameplay. Don't know if their is such a thing for amd cards or not.
|
|
|
Post by Brighttail on May 19, 2016 21:43:37 GMT -5
If you have an nvidia card you can use shadowplay to record the last x minutes of gameplay. Don't know if their is such a thing for amd cards or not. Yeah, but in my experience it can cause lag spikes cause it is literally recording everything in a TMP file and only will save it if you want it to.
|
|
|
Post by mcbogga on May 19, 2016 22:37:35 GMT -5
Here is the reason: When you take a shot, the entire shot is NOT saved to the HB servers. The only thing that is saved is everything your golfer is doing, the club, the aim, the swing, ect, everything right up to the point of impact with the ball. The reason is this saves memory. It would take a lot more memory to save the entire flight of the shot from start to finish. So when you watch a replay or if you are playing someone and watch them shoot their shot, the info that was saved (right up to the point of impact) is sent to the replay engine or to your opponent. At this point the computer has to recalculate the shot based on the information it was given. Things like wind, green slope, the little bug you didn't see walking across your line, are all recalculated and thus the shot you see on replay or from your opponent may be different than actually what happened. This makes more sense that if you are watching an opponent's shot, the difference between your computer/console and theirs may be slightly different when it comes to GPU/CPU power and thus "rounding issues" may explain why on your screen your opponent's shot misses while on theirs it goes in. When you are watching a replay tho things like the wind kicking up one MPH or slightly changing direction does effect the shot you are watching on replay. But what about putts? You can watch a replay of a putt 10 times and get several different results. HB claims minute green conditions do get effected by wind in the calculations and a difference of .001 can effect a putt exponentially over a 10 foot putt. I particularly believe that there is a built in set of randomness in every shot. This is why when you hit a default PW for 120 yards with no wind, sometimes it goes 110 and other times 128 yards. Simply put, it has been around from the beginning and it isn't going to get fixed unless they save more conditions of the original shot. Doing so takes more memory. More memory means more storage needed on their server and more information that has to be transferred to player's consoles/computers. Even if they could save an entire shot (even temporarily) depending on your ISP and internet speed, playing an opponent with full saving would take much longer than it does already due mainly to the increased amount of data needed to be transferred for each and every shot, each player takes. I highly doubt that anything is "recorded" before impact. Most likely it just saves the ball position, lie and launch conditions (or but in other terms - the actual impact data) together with data on what shot it was.
|
|
|
Post by Brighttail on May 20, 2016 2:03:30 GMT -5
I highly doubt that anything is "recorded" before impact. Most likely it just saves the ball position, lie and launch conditions (or but in other terms - the actual impact data) together with data on what shot it was. Sorry for using the wrong term but yes you are correct. What is saved is all the "information" of the shot prior to the swing (save the wind in non-tournaments/tours) and the swing itself up to the point of impact. That is then sent over to the other player or replayed and the CPU/GPU has to recreate the shot using that information.
|
|
|
Post by mcbogga on May 20, 2016 7:17:40 GMT -5
Still not happy. I don't think any swing info up to the point of impact is saved - just the impact parameters themselves. Not like the ghost players have different amount of pause on the top or varying back swing speeds around the green...
Saving more than just position, lie, wind and impact parameters would be a waste of bandwidth.
|
|
|
Post by Brighttail on May 20, 2016 11:41:03 GMT -5
How ever it is done, that is how Anthony explained it to me. There must be a component that is saved that will allow the shots to be recreated because you can come back 1 1/2 later and play against someone. My point was the reason people are getting discrepancies was that the whole shot was not being saved which is a memory hog. They save only part of the shot and just enough of it to have it recreated real time every time it is accessed. The recreations may vary.
|
|
|
Post by mrooola on May 20, 2016 11:52:47 GMT -5
I had an odd bug yesterday that I think is related to the replay bug.
I hit my second shot on a Par 5. Landed a good 5 meters or more left of the flag almost pin high and it took off rolling with high speed across the green. During the rollout on the green that would take me a good 20-30 meters from the hole I got disconnected. Once I got back online and resumed my round I saw my shot slightly less left but much shorter bouncing in the rough and then rolling in to the hole for an Albatros. Replay gave me the same result as the one I first saw.
|
|
|
Post by Brighttail on May 20, 2016 12:38:06 GMT -5
I had an odd bug yesterday that I think is related to the replay bug. I hit my second shot on a Par 5. Landed a good 5 meters or more left of the flag almost pin high and it took off rolling with high speed across the green. During the rollout on the green that would take me a good 20-30 meters from the hole I got disconnected. Once I got back online and resumed my round I saw my shot slightly less left but much shorter bouncing in the rough and then rolling in to the hole for an Albatros. Replay gave me the same result as the one I first saw. Very similar. Most likely when you came back the wind was slightly different and thus yielded a different result.
|
|