![]() |
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
![]() |
#16 | |
Silent Hunter
![]() Join Date: Jun 2004
Location: Along the Watchtower
Posts: 3,810
Downloads: 27
Uploads: 5
|
![]()
Let me try to take a stab at some of those others too. Again though, I don't speak doctrine so these are just guesses.
Quote:
2. I think the range/orderalt code section orders the weapon begin to descend to the bottom when it is 500m from the destination. 3. I think the range/destination code sets a variable which is fed into the decleration/overshoot bug fix. 4. refer back to 2. 5. From the documentation, it sounds right. On 2 and 4 generally, I don't think there is anything programed in the doctrine to prevent use on slopes or to impair the detection cone. As far as I know, the sensor has a given range and will explode when you are within that range. It's possible that terrain is a contraint, but I'm not aware of that. As for working on slopes, I don't think the mines are intentionally programmed not to work on them, but I think that in getting the weapon to hover, that sometimes the bottom where it is programed to stop is shallower than the bottom where the descend code was triggered, and this causes the weapon to bottom out and dissapear.
__________________
![]() |
|
![]() |
![]() |
![]() |
|
|