Quote:
Originally Posted by TheDarkWraith
open the sub's cfg file and edit this parameter:
[Properties]
PeriscopeDepth=12;meters 12.5
SnorkelDepth=12;meters 12.5
CrashDepth=71;meters - is actualy 70, and will never reach 71, it will dwingle at ~70.5 - fix for updating interface. [Saitan Catalin]
MaxDepth=200;meters
DiveDepth=40;meters
SurfaceDepth=5;meters
TorpLaunchMaxDepth=20;meters
StormConditions=11,0.4;max wind speed [m/s], max rain intensity [0,1]
|
Thank you for your help TDW, but unfortunately this hasn't corrected the problem. I set the SurfaceDepth as you indicated and had some interesting results. When set lower than original (4.5m with your New UI mod) it made the sub bob more up and down. When set higher (5.0 - 5.5m) it seemed to add stability, but again the slightest waves pushing the sub below 6m and it indicates underwater. I even tried extreme numbers (1.5m and 10m) just to see the difference, but it really only affected what depth the sub would try to reach when I pressed surface.
Looking at this post
http://www.subsim.com/radioroom/showthread.php?t=165687 I notice that lucagaeta has his sub at 6m, clearly showing water over the decks, and he doesn't have the familiar "We are underwater" indication (although it does show he's in Shallow Water and that his CO2 is high, strangely). This leads me to believe that something in one of the mods/settings has changed what his sub considers to be underwater.
I'm using your (TDW) decks awash and have it set to 7.0m. Would this have anything to do with it? I've searched high and low on the Subsim forums, including through your .EXE fixes where it's mentioned about decks awash and the use of binos.
It also seems that the OP and myself seem to be the only ones who have this problem, as I can't find any reference to this elsewhere. What's confusing though is I'm using the same mod list and settings as many others (sobers current list), so maybe I'm just the only one who's bothered by it.