![]() |
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
|
View Poll Results: How extreme do you want the torpedo mods to be? (please see the message body for explanation of term | |||
As is: general bug fixing and AI enhancement. |
![]() ![]() ![]() ![]() |
6 | 12.77% |
Above with: Advanced Wire Control and Sensor Modelling |
![]() ![]() ![]() ![]() |
5 | 10.64% |
Above with: Wire Lengths Limited to 10-13nm from launchpoint (reported as realistic) |
![]() ![]() ![]() ![]() |
7 | 14.89% |
Above with: Advanced Torpedo Physics |
![]() ![]() ![]() ![]() |
29 | 61.70% |
Voters: 47. You may not vote on this poll |
|
Thread Tools | Display Modes |
![]() |
#30 | |
Sonar Guy
![]() Join Date: Nov 2002
Location: Poland
Posts: 398
Downloads: 0
Uploads: 0
|
![]() Quote:
I hoped it can be short range or even disabled after own sub is detected... I though that because in Maverick case tgt once locked was not refreshed and homing worked perfectly. I wonder then if a torpedo would still home on a sub if it's sensor was disabled :-) P.S. One day I tried to make a torpedo seeker with two very narrow sensor cones looking to the front-sides in V patter (so NOT to the front) and after target is locked and torpedo turns to it, target is outside seeker cone and target don't get active pings anymore :-) Evil weapon, would work great against non maneuvering surfaces if proximity fuse was added. Only if it maneuvers and gets out of the "blind" front cone, it's detected once again by one of side looking seekers and again homed on... it was working crudely and I planned to improve it later but forgot ![]() P.S.2 Looking at torpedo seeker cone (just wanted to try once more what I described above) I noticed that seeker cone parameters are set only for azimuth (+/- 45 deg for example) but in elevation it's 0 so either not used or... all around 360deg ! For years it was annoying me that torpedos running in level detects targets even directly above them so out of real seeker's cone. I don't remember now if I tried to set seeker cones correct in elevation too and if it worked... Anyone knows if elevation settings works at all for sensors in DW ? P.S.3 AN-SPS-55 has set cone in both azimuth and elevation (+/-10deg) so it should work ! Also CIWS seeker is limited in elevation to 40deg. I think we should set this to correct value for all torpedo and missile seekers (then you can escape torpedo seeker cone not only in horizontal plane, but in vertical too !! And torpedo depth settings become much more important, torp set to wrong depth and enabled too close would have target out of cone in elevation, currently it's impossible !) I would set sensor cone elevation angle for same value or little less than azimuth angle (so for example an ADCAP with cone +/-45 deg in azimuth would have +/- 30-45 deg cone in elevation). Setting this to correct value for air radars (especially MH-60 and P-3, but also EW and fighters) is an option - could have a positive effect on realism, Seahawk and Orion radars would have correct minimum distance if flying high, couldn't detect a close surface tgt from high altitude. But for weapon seekers it's a must ! For sub and ship sonars it's not that important, most sensors have 180+ deg cones so can hear straight down or up also... Maybe for the actives... then you' should have a minimum effective distance for deep submerged contacts... but I can easily imagine that ship mounted active sonar with >180deg azimuth cone, can scan directly underneath too ? Last edited by Amizaur; 05-29-06 at 04:07 PM. |
|
![]() |
![]() |
Thread Tools | |
Display Modes | |
|
|