Nope... You shot. The first time you showed up to check things out was before that....and I spoke to you on Doug Millers phone while you were there.I said nothing about seven times....I don't know where you are getting that.....although I have been there six times since last September.Mike
I'm in a profession that suffers greatly from the delusion that a layman can understand the nuances of my day to day.
Quote from: MicErs on August 23, 2015, 12:31:17 AMQuote from: rsterne on August 23, 2015, 12:18:14 AMNo idea what the BC is, but assuming the bullet loses no velocity at all, 82 yards is 246 ft., so at 1050 fps that would take 0.234 sec.... Maybe 1/4 second?....I'm thinking anyone watching a video could probably notice a quarter second difference between the shot and the impact??? Longer ranges more noticeable lag...Of course videos are shot at some number of frames a second, so if someone were so inclined, they could establish the number of actual frames between the shot being fired and the impact of the shot, if someone were so inclined...Or they could just do it the ez way....trust I do not see the benefit to deceive?
Quote from: rsterne on August 23, 2015, 12:18:14 AMNo idea what the BC is, but assuming the bullet loses no velocity at all, 82 yards is 246 ft., so at 1050 fps that would take 0.234 sec.... Maybe 1/4 second?....I'm thinking anyone watching a video could probably notice a quarter second difference between the shot and the impact??? Longer ranges more noticeable lag...Of course videos are shot at some number of frames a second, so if someone were so inclined, they could establish the number of actual frames between the shot being fired and the impact of the shot, if someone were so inclined...
No idea what the BC is, but assuming the bullet loses no velocity at all, 82 yards is 246 ft., so at 1050 fps that would take 0.234 sec.... Maybe 1/4 second?....