oh..it will...first time round....now start switchin back and forth.Pre,enable,pre,enable etc etc...see what happens.

I just did a small test in my 688(i)

Simple mission I made for myself to do some simple TMA Practise, 1 friendly sub in the area nothing else. Shot 1 adcap with a snapshot at 000. Torpedo ran fine and I let it run for a while. I enabled it on the friendly and the friendly deployed countermesures. I then pre-enabled it and turned the torp back on myself and I was getting pings while it was pre-enabled. I hit the enable button and it continued to ping me. I pre-enabled it again and still had the ping. I turned my boat 185 and started to run away from it and when it got close enough to lock onto me I enabled it again, the torp was dead silent with no pings and with a lock on me. I pre-enabled it before it was about to hit me and it passed through me and didnt kill me. Those where my findings...

Wolfy

exactly what I've been doing(except in the akula)..and I get the same thing happening.

You called?

Geeze that would be a pretty good nick, if it wasn't already taken by one of the more respected members of our community.

I might just steal that line as a sig however!

JCC

OK, here is what I'm seeing - let me know if you see the same.

- When the torp (I tested the 53cm and 65cm on the AK) is in Pre-Enable mode and the target is WITHIN the acquisition cone, the Ping will emit as if the torpedo were Enabled (and increase in frequency as the torpedo closes).

- As soon as the target leaves the acquisition cone, the Ping will stop (in Pre-Enable mode).

- I haven't seen a torp that HASN'T pinged while Enabled, you guys will have to help me reproduce that. :doh:

I just ran another test.

You don't hear pings that are directly behind you to a certain degree, some kind of shadow zone or whatever where you can't hear pinging.

So there's another issue.

For the test I ran that I posted above when the torpedo was locked on me it was coming at me at 180 degrees or almost directly behind me, but when it was pre-enabled and I was out of its lock range I was getting a ping every once in a while from it, as if it was an active in search mode. When it got close and I knew it would lock onto me right away I enabled it and it went silent with no pings at all.

I have posted a reply of what I did in my testing, you can atleast see the angle the torpedo was coming at me if it matters...

Replay
http://www.megaupload.com/?d=ZMT04N6N

Wolfy

********NOTE NOTE NOTE********

Stock DW has a REARWARD BAFFLE for ALL ACTIVE INTERCEPT systems.

LWAMI removes this baffle.

So when you are testing these torpedoes using the stock database, make sure you keep the torpedo in front of you. :know:

And thanks a lot for helping us test. :rock: :arrgh!:

Well, I finally got it to behave as you describe and again it seems as though it was due to the fact that I (in this case ownship, as I am the target) had left the acquisition cone... Then I heard nothing when the torp was Enabled or not.

Seems like something is awry, I will try to work with Hutch and figure out what the issue is.

If anyone has any additional info, please feel to comment. I can take it... :sunny:

Jamie, once the torpedo has been reenabled (this is only for wireguided torpedoes utilizing the preenable/enable feature) and locks on ownship, the pinging frequency does NOT increase based on my tests. For torpedoes launched by the AI that simply enable at their enable range the ping frequency increases as normal.

Thanks a lot Jamie, if I have further info ill post it for you asap. :up:

Wolfy

ok, so the shadow zone is supposed to be there, but wouldn't you still be able to hear the ping in reality?

And a torp coming at you in search mode (not acquired already), you lose the ping when it its at the end of the snake movement.
There is a +- window of 60 degrees you hear the ping.

If you could hear the pings then there wouldn't be any shadow zone, or am I missing something here ? :hmm:

What I'm trying to say is that the crew of the sub would hear the ping, like in WW2, but the sensor to detect which direction it came from doesn't cover that arc.

Hope that clears it up.