@ Molon Labe: would it work, then, if torpedoes assigned to a solution are fired on an intercept course, to take the solution generated by TMA, set the target's speed to zero (leaving course, bearing, and range unchanged), and enter THAT solution for firing? At that point, an "intercept course" would be a course straight for the target's current position, wouldn't it? And the target can't NOT leave a wake where it currently is.
For good measure, would it make sense not only to set speed to zero, but also to alter the LOB a little, to put the torp behind the target?
Unfortunately, the problem for me is that "snapshot" is actually unselectable, given the mouse issue I mentioned. From the Fire Control screen, I can click on the dropdown menu for "target" to assign a tube to a given target, but I have to use the "tab" key to cycle through targets that already have an alphanumeric designation. Since "Snapshot" does not correspond to any of those, I am literally unable to select it. You can see my impatience with the guy writing Wineskin wrappers for this game; the mouse issue is crippling.
Please tell me if I'm understanding all of this correctly, though: a solution with speed set to zero renders course irrelevant, leaving only bearing and range, which is, effectively, a snapshot. I'm just as well to put the numbers into the TMA myself. The added advantage is that if I've taken the trouble to stack the dots, I have accurate range information on which to base my RTE, without having to raise the periscope. It's a reasonable workaround, isn't it?
Of course, I'd be happy to use the stadimeter for range, but because of the same stupid mouse issue, I can't actually drag one side of the image to match the waterline to the masthead. Yes, this is frustrating. But this game has the distinction of being worth the trouble. And in any case, range information generated by passive sonar is more stealthy than the periscope.
Let me know if my thinking is sound. Or crazy. Either way...
And thanks for the welcome!
|