Dread,
Our calculations have been repeatedly tested with live fire testing. These "correct" methods are only "correct" if they reflect what actually happens on target. We have continuously proven our system to "correctly" account for these effects. This is the benefit to a solver supported by a full time ballistics lab.
The problem with these claims of first to do it "correctly" or the other claims you mention of ours not being done right from other sources, is that those were all done on paper so to speak. We are not claiming that their method of calculation isn't "technically" correct. But that their method rely's on PRODAS estimations that have historically been unreliable for high levels of precision. So what is "technically correct" and what is "practically correct" are two different things. Our solver uses much simpler methods that don't rely on estimated data that may or may not be accurate, but our method has been proven by live fire test to be accurate within the ability of any shooter/weapon's capability.
Long story short, we have been calculating these "correctly" for years. And by "correctly", we mean where the bullets actually go on paper.
We haven't attacked the science behind the Hornady solver or anyone at Hornady personally. What we did do was call them out on their marketing claims and that they are trying to patent something that already exists.
I think anyone that reads Bryan's latest statements in response to comments from Hornady, will realize that this isn't about us just trying to knock Hornady out of the game. Our mission from the start was to keep the truth at the surface, which yes, does somewhat defend our own product. But if the truth is labeled as biased, I guess so be it. Trying to keep the industry focused on reality and truth isn't unprofessional.
We are all for giving credit where credit is due, but we understand the complexities of these solvers and the realities, as well as what has already been accomplished, by others and by ourselves.