Quote:
|
Originally Posted by HEMISENT
Oh man! Great news! Thank You Observer!
Jeasen, does the NYGM crew/Observer have a copy of the sabotage/malfunctions files (the Sensors.dat files u boat radars max range= has been edited or is this irrelevant at the time)I sure wish I could Dl this but i'm still limited to 169mb.
Off Topic-"DON"T GET DIRECWAY SATELLITE SERVICE!"
|
I've two pieces of feedback on the malfunction and sabotage settings used in the Randomized events.cfg. The first is on the crash dive settings simulating a jammed dive. While I understand the intent, consider the implications for those situations where the crash dive depth is deeper than the crush depth of the submarine. This will result in odd uboat behavior described in the Crash Dive Blues thread here:
http://www.subsim.com/radioroom/show...ash+dive+blues
This is because your uboat will not be able to complete the crash dive sequence - a necessity otherwise it's outside of the ability of the code to really handle this aspect. It's not that bad on the stock uboat models because of the extra positive buoyancy, but with the NYGM model it's a disaster that can't be corrected unless you surface.
The other area is the Front/Rear ratio. Similar to the crash dive problem above, this is an area that probably shouldn't be touched. Again, the extra positive buoyancy of the stock models makes this less of a challenge, but it is still present an uncorrectable, a situation that really not possible since internal trim tanks and dive planes can usually compensate. If not then additional speed will usually solve the problem. This is another area SH3 does not model well.
Finally, is there any consideration to storing the malfunctions or sabotage settings so that:
1) By the freak of random chance you don't keep getting hit by the same problem multiple times when reloading
2) Problems can be compared to a "repair table" so that a certain number of days (or hours) in game must pass before the problem is removed (at the next reload). Malfunctions could also be flagged as not repairable at sea (i.e. persistent). I am troubled by the possibility that I could, in theory have an equipment malfunction, end my session for the night (save and exit) then reload the next day to have the problem magically disappear.
3) Or are all problems persistent? If so then the point I outlined above on the F/R ratio really needs consideration, and I think you should consider that not all "malfunctions" are persistent.
It's a great idea. These are just my thoughts FWIW.