![]() |
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
![]() |
#1 |
Machinist's Mate
![]() Join Date: Dec 2007
Posts: 127
Downloads: 3
Uploads: 0
|
![]()
This is an odd bug that I haven't run into before, but it ruined the last mission I tried to play (Filipino Convoy). I had been tracking the convoy for a while on sonar while keeping a low profile until the convoy was closer than 10 km. I had been tracking two of the three convoy ships on broadband cylindrical (the third was to hard to seperate out to bother tracking), so I had a very good solution on where they were, but I wanted the exact locations of all three vessels before I fired. Since the range was so short, I figured I could just pop up and get them all easily with the periscope. Well, I was partly right in that all three ships were about 1-2 inches long at max magnification, but that's when strange things started going on.
The plan was to scan right to left and mark/photo/range each ship I saw. I was able to mark the first contact as a cargo ship, but I then was unable to mark the freighter which, though very extremely close to the same bearing, was still completely visually seperate on the scope (about three or four clicks of the peri-handle). So, figuring it was the bearing proximity, I moved on to the last ship, the oiler, which I thought I successfully marked. However, when I looked at the nav plot, the oiler I'd marked was placed on the wrong bearing. After all this nonsense, I decided a little 'show truth' was in order. To my astonishment, the ship I had very definately indentified as a cargo ship on the scope was in the exact location of the real freighter. The oiler which I had marked at a completely different bearing was in the exact location of the cargo ship and the real oiler hadn't been marked at all. So I decided to drop all visual contacts and start again. Again, I was able to mark the first ship, very positively the cargo ship, but was now unable to mark either of the other ships even I (half blind as I am) could see. So I got fed up and quit. Any ideas? Anyone had a problem like this or any problems with the periscope? |
![]() |
![]() |
![]() |
|
|