Hey Emsoy, I think I just addressed that overall issue in the other thread.
I am not sure you really intend to have it to the dimension I experienced it. My units didn't do "some" work outside the patrol zone, they simply ignored it. Also I don't see how the contact should be assumed at some exact location at this time of the scenario. I assumed the ambiguity zone tells us exactly that: that the location is unknown, but inside that zone. So it serves as a perfect visual helper to guide me where to place my patrol zones.
There are times when the ambiguity zone extends for hundreds of miles across Greenland. Of course we know the sub won't be there. But the ASW patrol mission logic ignores that. That is no big deal since we can define patrol zones in that great mission editor you gave us.
But if the patrol zone we defined there is ignored, only because of the enemy contact symbol (serving as indicator which kind of contact is in that huge ambiguity zone) is interpreted by the AI as the exact location of the target, then in my opinion the mission logic does obviously fail to serve our need in these cases.
Right now, there is no way of creating an ASW patrol mission obeying the defined patrol zone, in case it includes the indicating target symbol of some contact which might not even be in the defined patrol zone, but instead somewhere within an enormous ambiguity zone (which might extend outside our defined mission area). So equally there is right now no way to economically do ASW patrol missions across areas which contain ambiguity zones. I guess, that is not wanted?
Looking forward for SR4 in any case
Thanks for your work!
< Message edited by Rongor -- 7/30/2016 10:41:29 PM >