From: Sydney, Australia
Tried to think how to 'subject' this.
We had an issue which I thought was code, but upon closer examination, it was found to be some conflicting conditions within the scenario itself.
See D's comment http://www.matrixgames.com/forums/fb.asp?m=4533944 in relation to a AI-side sub not behaving as expected.
Had another look at this. The fix that we applied here caused a much more serious issue elsewhere: http://www.matrixgames.com/forums/tm.asp?m=4532318
Digging into the scenario, the problem appears to be that, although the Romeo patrol has set depths for transit and on-station, the sub is also given a manual depth order (40m) which overrides these settings.
If the manual depth is removed, the sub correctly rises to periscope depth, remains there to fully charge its battery, and then dives again to continue its patrol at the mission-specified depth.
So this looks like a scenario author error. Given that this is an AI control side, the sub should not be given a manual depth override.