Quote:
Originally Posted by LGN1
Hi John,
I know Ducimus' statements quite well, but I don't know how he came to the conclusions. In one post he mentions that the "AI" always chooses the sensor with the highest probability of detecting you and that it can switch very quickly between the sensors. In this case I'm wondering what's the problem if it can only use one sensor, but knows which is the best to use and switch to it in a fraction of a second (and both sensors provide exactly the same information to the escort).
I have no definite answer on your question concerning the exe, but some general remarks. I regard it always as 'dangerous' to remove expected(?) input. You just don't know what you might break without noticing. Therefore I always prefer to keep the 'structure', but adjust the sensor's parameters. For instance limit the range of the hydrophone to 1m, its depth to -1m and 'deactivate' it (practically remove it from the game) in this way. To make a sensor more sensitive I would increase either the sensitivity parameter (a quite sensitive parameter) or decrease the detection time (less sensitive; basically scales the detection probability in a linear way).
Best, LGN1
PS: Or LinkName=NULL for the sensor in the *.sns file.
|
Appreciate your thoughts. I agree with you on changing parameters, etc. I used the Linkname=NULL for these tests. I know I'm going over a lot of old ground covered by a lot of very bright folks but its fun to tinker anyway, plus I'm the kind of stubborn idiot who if told the sun rises in the east has to see for myself.
One other thought; regarding your test of setting the hydrophone to > -30m do you recall if you were using SH3 Commander with that ?
If so I'm wondering if Hemisent's thermal layers may have changed your hydrophone editing ? Though there's only a 10% chance of that happening.