[CaptainHaplo]

Here is the problem - the key is TIME COMPRESSION. When you kick in time compression, the normal math formulas the game uses for detection are not used like they are at lower speeds. At most do not go above 4 or 8x. Honestly I would say don't use it at all - but I know that for some the "super slow" speed of "realtime" isn't what they want to play for.

I have a .... working hypothosis on how the game does this. The game randomizes somewhat - but basically is extrapolates a "range" of noise levels that you "might" make - at which point it compares that to the detection values required. Because its at TC - the detection values are increased greatly to compensate. This is valid as otherwise at high tc and low speed you would be undetectable. However, what it creates is a situation where as you get higher and higher TC values - you also get lower and lower "real" detection thresholds - to the point that even dead stopped at silent running you can be detected below the layer at long ranges.

Remember that - while this is a hypothosis only - every test I have done indicates that I am correct. I strongly suggest that - if your 20km out and on the line of the TF or convoy, go ahead and turn toward them and close that distance on the surface - as the above only applies to subsurface detection. You can safely use some TC like this - 32 or 64 - until you get near visual range - about 10km. At that point go ahead and dive, go to Silent Running and turn TC either off entirely, or down to as minimal as you can stand it.

Your facing 2 issues - your range is so high that you need TC to make the attack "playable" at some very soon time, and your fighting the natural gamer instinct of "I want to do this now!" - both of which mean your reaching for the + key by default.

USE TC on the surface to close the gap - and consider the remaining "slow time" a realistic attack and part of the fun. As long as you don't use TC "waiting" on the enemy to approach - you should be ok.