Yes we need to tailor the AI for some of these systems. The SS-N-3 and SS-N-12 limitations are already on my to-do list (for obvious reasons hehe) and also needs to be integrated into the mission planning/execution functionality. Complex stuff, so will get to it a little further down the road.
ORIGINAL: CV60
Probably ya'll have thought about this, but the launch altitude info is already in the database. Is it possible to simply hard code the SS-N-3 to require it being at 0 feet AGL to launch, or is this a matter of the AI needing to understand the submarine needs to surface in order to fire? An additional issue to consider regarding the SS-N-3 is that a firing submarine had to remain surfaced for 8-30 minutes until the SHADDOCK's seeker found the target. See:
http://www.ausairpower.net/APA-Rus-Crui ... ocId742062; http://www.globalsecurity.org/military/ ... ss-n-3.htm; http://www.fas.org/nuke/guide/russia/theater/ss-n-3.htm; http://en.wikipedia.org/wiki/P-5_Pyatyorka
On a slightly related point, some of the earlier Soviet ASMs also had fairly stringent launch altitude issues also, so similar AI issues may be present with them.
ORIGINAL: emsoy
ORIGINAL: Der Zeitgeist
There's an inaccuracy with the SS-N-3a Shaddock missile. It currently can be launched by submarines that are submerged, but should only be able to be launched when on the surface. That was one of the main problems with the Soviet Juliett and Echo class subs. I updated my spreadsheet accordingly:
https://docs.google.com/spreadsheet/ccc ... ring#gid=0
Have been checking off a couple more intems in the list.
The SS-N-3a launch depth needs to wait as we need to get the AI to work with this as well.
Thanks! [8D]