Mtnmn and humble are confusing separation (the physical separation between two objects) and flight path separation, which is the difference in future position as determined by velocity vectors. In other words, if you are going to collide there is zero flight path separation. Zero flight path separation results in zero physical separation. Flight path separation greater than zero results in greater than zero physical separation.
The confusion seems to be...
Yours...
You stated-
You don't always want separation at the merge. It depends on the fight you are planning. You wouldn't give turning room to a bandit you know wants an angles fight.
and-
Nope...That is incorrect.
He (mtnmn) stated that you need enough separation not to collide, which is a bit of humor I would think.
He implies that you have to have separation at the merge to prevent getting shot. That is demonstrably false. All you have to do to prevent getting shot at the merge is not provide the bandit a shot opportunity. That is geometry not distance. In fact, once you are inside the bandit's turn circle he CAN'T shoot you. Closer is better in this case. Maybe he doesn't know how to pass close aboard a bandit at the merge without getting shot. Maybe he does. I don't know.
I know how to do it and it is a useful tool when I want to deny the bandit turning room for a lead turn. And you want to be as close as you can when you use it because the closer you are to him when you pass the more out of position he will be if he goes angles at the merge.
It is a very big part of 2 v 1 tactics to be able to execute a merge close aboard without getting shot in the face. It is the basis for setting up most of the follow on maneuvers following an offensive split.
...and now you seem to have realized how that looks, so have launched into "flight path" separation.
Which is fine I suppose, but you never mentioned "flight path" separation, so we didn't infer that you meant "flight path" separation. And then you re-state what we've stated, in an attempt to show that we're confused?
If both pilots start pure pursuit at 6000 yards there is 6000 yards of separation and effectively zero flight path separation.
And build on our "confusion", by supporting my statement...
You bring up a very important point though. While separation is good, and necessary, you can have too much of a good thing! Merging too close gets you face-shot. Merging close, but with too much space can allow your opponent to turn into you using lead pursuit to gain a shot or a good position (although at a cost in E, which he may or may not be able to afford).
with...
An angles fighter will want to create physical separation pre-merge to set up a lead turn. This pre-merge separation is created by flight path separation. Before closest point of approach the angles fighter needs turning room so that his lead turn will apply offensive pressure on his opponent. Once the flight path separation creates the physical separation the angles fighter is going to want to reduce the physical separation in order to gain offensive position. That is the entire point of lead turning. The defense against this is to take away the physical separation by maintaining near zero flight path separation until the merge, resulting in a merge (closest point of approach) with very little separation.
Beyond that, we're talking about defending against the HO. Reducing your "flight path" separation would seem to "fly in the face" of that idea...
You make some good points, which could be discussed. I believe Shaw even goes into those ideas in his book if I recall correctly (it's been a LONG time since I read it). However, that's not the topic of this thread, so I've been avoiding get too detailed there.
Not a big deal... Your earlier posts just left out some information vital to their proper interpretation..