still waiting
Thanks for the welcome gentlemen (I may be wrong but I don't imagine there are many (if any) female sub-gamers). I'm still waiting for the postie to deliver the game.
My interest in subs started when I was about 12 or 13 years old (which was in the very early 1960s) and a RN submarine visited the port where I lived; the town was (still is) a commercial seaport but naval vessels would visit occasionally on "public relations" tours.
I went aboard the sub for a tour and was absolutely transfixed. It became a sort of background interest for many years until I visited museum boats at Liverpool and at the RN Submarine Museum in Portsmouth and I was given SH1 as a present.
Bothersome—I'm surprised you say that. Maybe I wasn't doing it right 'cos in SH2 the destroyers seemed to know my precise depth every single time; above or below the thermal, and even when running silent. A young student of mine at the time who was a dedicated gamer and read all the mags etc., told me that Ubisoft had bought the company that produced SH1 (I disremember their name for the minute) and they (Ubisoft) wanted the game out onto the market even though the developers said it wasn't ready. If that's true then that would explain why it was such rubbish.
Along the lines of general curiosity and touching on Sailor Steve's comment about depth charge modeling in the games, I have often pondered on how these things are modeled. It's a computer programme after all and whilst it is fun to role-play when playing the game it is a virtual world we're dealing with here—its just some very, very fast number-crunching that's going on.
I know nothing about programming but have always assumed that it depends a lot upon probability calculations. For example, concerning detection, which is a factor of speed, depth and water conditions primarily, I figured it probably goes something like if speed is x, depth is y or less than y then detection is 100% probable. However if speed is less than x, depth is greater than y but not z then detection is (for example) 75% probable, and so on along a sort of sliding scale.
I did do a bit of work with the mission editor in Sub Command and detection there seems to be largely to do with speed and distance from the detecting platform; ie—if speed is x or greater and distance is y or less, detection is certain. Therefore assuming that you know these parameters you can zoom up to the distance limit then slow to below the speed limit and remain undetected.
Does anyone have any inside info on how these things work?
|