I've read up on it. I still don't see how it accounts for wind direction. I am far less experienced or technical than most of you at long range. I typically input a rough generic wind in and compensate 1 way or another based on where I think the wind actually is. Typically 5mph and split the difference on direction difference. If I think its closer to 10mph, I double my #. If I have all the time in the world, I will input exact guessed wind and send it. My weakest link in LR is guessing wind across varying terrain. Shooting in different locations has helped me a ton, but I still do not consider myself a great wind caller.
I'll tell you my method, it may not be 100% perfect according to the experts but it has proven to work for me, at least within my abilities as a wind caller and a shooter. I'll start with the equation we're solving in our heads, broken up into terms intentionally to show how I think about the problem:
Wind hold in mils = (
range/100)*(
wind speed/rifle wind rating)*crosswind component
- Range/100 is what it sounds like, you can basically just round the range up or down to the nearest 100 and take that first digit. So 390 = 0.4, 220 = 0.2, 560 = 0.6 and so on. This is referred to as the "base", and it's what your wind hold in mils would be for a full value wind at the gun wind rating speed at this range (by definition of the gun wind rating).
- Wind speed is what it sounds like, your best guess of the wind. This could be a range of speeds such that you can bracket the error and hopefully center that error band on your target.
- Rifle wind rating is one number for your rifle/cartridge that you determine ahead of time using a solver, or estimate using some other tricks. So for my 284 it's a 7mph gun. I actually almost prefer my 6mph 6CM since it makes the mental math easier, but that's just me being weird. This number will also change with DA.
- Crosswind component is the cosine of the relative wind angle. I try to make this simple by using "oclock" directions, and either 0, 50%, 90%, 100% for (12,6), (1,5,7,11), (2,4,8,10), or (3,9) oclock respectively
I broke the terms in the equation up intentionally to show how I approach solving the problem. Fundamentally, it's my BASE multiplied by 2 factors, one after the other.
The first factor is what I call the "wind ratio", which is wind speed divided by rifle wind rating. All day while I'm walking around I'm constantly guessing wind speed and calculating my wind ratio. Direction doesn't matter yet, since we don't know which way we'll be shooting. This wind ratio number is always floating around in my head. So for example, I guess it's a steady 6mph breeze, and I'm carrying my 7mph gun, so my wind ratio would be 0.9. It might be 0.9 for 3 hours, then the wind changes or I crest a ridge and feel some new wind, and maybe I decide its a 9mph breeze, so I calculate a wind ratio of 1.2ish. It might be gusting up and down, so I might call my wind ratio anywhere from 1 to 1.2.
Now let's say I spot a target and I decide to shoot. After I set up my position I pull out my rangefinder, get a range, use my quickdrop math to get an elevation hold, and dial that on my scope. Then I move on to wind. While that range is still fresh in my head, I calculate my base, let's say it's a 420yd shot so my base is 0.4. Then I apply the first scaling term, the wind ratio. Using 1.2 from above that puts me at a 0.5 hold. Now I think about direction and pick my last scaling factor. Let's say I decide it's an 8 oclock wind, so I pick 0.9, and I end up with still 0.5, maybe shading 0.4.
Running real numbers for my 284 in this scenario of 3kft DA, 420yds, 9mph wind, 8oclock, the correct hold is 0.47mils.
As the shot conditions change, you can easily update this hold very quickly. You can re scale relative to your initial hold, or you can recalculate from scratch. I may have made it sound complex but I'm really trying to be precise with my writeup. In my mind, it goes like this:
420 is 0.4
0.4 times 1.2 is 0.5
0.5 times 0.9 is 0.45 call it 0.5
Wind died down by a third, pull it back to 0.3
Wind is switching more towards 7oclock, pull it back to 0.2
And so on and so forth.