Is loading a save; not the same as execution?

MarkShot · 11-22-20, 03:39 AM

RA 1.49

I have a close approach in a sub to destroyer. I have like 2 NB harmonics on DD, but solid (no faint ghost lines). I load 5 minute earlier save, I can play through and not be detected.

But if I load and save even closer, loading is instant detection; despite I can execute through that distance without detection.

Why?

I can think of 2 reasons:

(1) The doctrine files on a load are re-initialized, therefore I might during execution slip by undetected due to where the AI is in running the detection doctrine.

(2) A load results in a base noise level initially emitted which is then re-adusted for sea state, layer, flow, weather, and bottom. (If this true, then one should avoid saves when running on the edge of a razor.)

Anyone else experience this?

Thanks.

11-22-20, 03:39 AM	#1
MarkShot Ace of the Deep Join Date: Jul 2002 Posts: 1,134 Downloads: 93 Uploads: 0	Is loading a save; not the same as execution? RA 1.49 I have a close approach in a sub to destroyer. I have like 2 NB harmonics on DD, but solid (no faint ghost lines). I load 5 minute earlier save, I can play through and not be detected. But if I load and save even closer, loading is instant detection; despite I can execute through that distance without detection. Why? I can think of 2 reasons: (1) The doctrine files on a load are re-initialized, therefore I might during execution slip by undetected due to where the AI is in running the detection doctrine. (2) A load results in a base noise level initially emitted which is then re-adusted for sea state, layer, flow, weather, and bottom. (If this true, then one should avoid saves when running on the edge of a razor.) Anyone else experience this? Thanks. __________________ War games, not wars! --- Only a small few profit from war (that should not stand)!