Hello, propbeanie!
Nope, if you start your career or your new patrol in Manila for example, then you'll be in Manila time. Starting from Midway you'll be in Midway time... just like starting in Pearl you'll be in Pearl time. That's the way the game works.
But that's not the problem I wrote about. I have checked sunrise times in Manila and compared them with NOAA data - game is pretty accurate.
The problem is that I have expereinced several times serious celestical system fail during a patrol causing serious offset for both sun position (sunrise times) and moon positions. Like I wrote in the first post, 5 - 6 hrs delays in Apparent Sunrise. And to be clear, this is not due to extensive change in submarines position - within a week (RL) that has happened to me on two different patrols just in home waters before I have practically moved to anywhere. Every time sunrise times have been all right in the beginning of the patrol, but after one or two game days sun might rise suddenly at 1200 compared about 0612 which would be the correct time.
In the mean time I have tried to find out what triggers celestical system fail, but so far I haven't got any luck with that. During test runs (3-5 game days) during which I have stayed near my home base but used frequently very high time compression up to 2000+ (don't remeber the exact number), everything has worked very well and the game seems to be very accurate. But right away when I have started a real patrol, things gets messy very quickly.
At the moment my best quess is that either:
a) the game doesn't like TC used in other stations than map view (during patrols I have used TC32 while in crew management view, which I haven't done yet during test runs) or
b) the game doesn't like very long continous sessions up to 8 - 12 hours at TC1 most of the time (test runs have been very fast thanks to high TC used. That's something I rearelly do while in real patrol).
I'll report in if I'll be able to trigger solar system fail during test runs.
RC
|