View Single Post
Old 06-09-06, 12:15 AM   #22
Observer
Commander
 
Join Date: May 2005
Posts: 477
Downloads: 6
Uploads: 0
Default

Quote:
Originally Posted by HEMISENT
Quote:
Originally Posted by Observer
While I'm thinking of it, you don't model any torpedo tube failures. That would be a great one to add. A couple of other things while I'm thinking on it. I don't think the RPM effects do much of anything at all. Same with electric engine HP. I've modified both it and never found it to do anything. Not even hydrophone detection. That's controlled by the speed multiplier in the submarine cfg files.
I know the RPM's are not modelled, I only did them so they would be visibly dropping when viewed from control room(eye candy) I've noticed that sometimes the tachometer registers the change and sometimes it doesn't(game bug?)
Also. I too thought torpedo tube failure would be great but have no idea where to look to either "cancel" a tube out or even effect load times.
Any clue in that direction would be appreciated.
Load times are in the NSS_Uboat*.sim files. For the TypeVIIb, the hex offset for the loading time in the bow torpedo room is x0972. The aft torpedo room is x09E8. Fwd external is x0A6C, and aft external is x0AE2.

I'll have to work on the torpedo tubes. I have a couple of ideas I'll have to test to be sure.

Quote:
Quote:
Originally Posted by Observer
Oh one other question. Do you get a warning message, or some sort of notification when starting SH3 Commander that you've had a malfunction? I think that (like the transferred crew message) would be a nice addition if it's not already present.
No, I was dead set against any kind of warning or message as these were supposed to be a surprise. Also, the captain absolutely, positively must make a test crash dive (as in real life) plus a basic test of his major systems at the beginning of every patrol. It would be very unsettling to run into a juicy convoy with no escorts go to PD, raise your perscope and only to find out that the seals are bad and it stays blurred then go to the Obs scope and find a problem there too.(there is only one file that affects both scopes and the Obs scope does clear up after a bit)
I understand what you are saying, and it might be true at the beginning of a patrol on some systems (the controlled dive after leaving port to test systems is a good example where this would be true), but not in the middle of a patrol and not for important system failures. The captain has other crew members to help him keep track of the material status of his boat. He shouldn't find out the optics of the attack periscope have failed for the first time when he getting ready to shoot during a convoy attack (assuming there was a save and exit during the approach and attack phases). I would keel haul my engineer if I found out the attack scope was broke when I went to raise it and he didn't bother to tell me first. It's why submarines have out of commission (OOC) and reduced status logs. It's why submarines have an engineering, weapons and navigation departments. It's their job to keep track of the material status of their equipment and fix it when it's broken or in a reduced status. It's their job to tell the captain when their equipment doesn't work.
Observer is offline   Reply With Quote