Quote:
|
Originally Posted by ReubenJames
Q1: What separation do you use normally when you create a mission?
|
Depends on the scenario. If I want to do something quick I start with both sides within sensor range. The Mission Editor has an overlay that allows one to see the maximum sensor ranges.
That doesn't really teach one much, though. A lot of naval warfare is just FINDING the enemy. Usually, I ask myself "What is everyone trying to do?" and build from there. I usually also take advantage of dynamic locations and dynamic groups so that I can have some surprises.
Quote:
|
Q2: What is the fundamental technique to look for possible contact? Right now, I make turns in steps of 45 degree at roughly 5 knots. Is that a good method? I can't think of anything otherwise. Would you suggest some other methods?
|
That's actually a deep question. It really depends a lot on what you're trying to do. Optimum employment of sensors is heavy stuff. A mathematician during World War Two named Koopman wrote a book about it called
Search and Screening. He was trying to find German U-Boats. It's good stuff, but not simple.
How I'd employ my sensors in a transit scenario, is very different from how I'd do it in a barrier search, or for area clearence. It might also depend on things like how fast I needed to go, what I needed to defend against, and what else was working with me. It might also depend on how much I wanted to frustrate the enemy's ability to find me. It might also depend on the SSP and bottom type.
For a fast transit scenario, for example I might not NEED to see very far, because just by kinematics, only submarines within a limited angle are dangerous or alternately I might sprint and drift. Sprinting a period of time to maintain a certain average speed of advance while being nearly blind, then drifting a period to ping or listen.
A good scenario will force one to make compromises. That's what makes it interesting. If there was a clear answer regarding what to do, the game would be a whole lot less fun.