SUBSIM Radio Room Forums - View Single Post - Destroyers Discussion (getting rid of pin point drops)

caspofungin · 11-29-05, 08:10 PM

i don't think AI_hydrophones link gets used.

Reasons
1. check the sens file for enemy ships. theres a link to AI_visual for the visual node, but then every other sensor has a link to the named sensor in AI_sensors eg linkname type 144p

2. changing the ai_hydrophones values -- other than noise level and detection time as above -- has no effect at all -- at least, not one that i've detected.

i also feel we're repeating some of the early work done by cb, redwine, and self. not that there's anything wrong w/ it -- the more info we have, the better, and it would be nice to actually confirm things. but i agree w/ gouldj -- we need to all test on a standardized mission (there's links earlier in the thread to mine and someone elses, or we should agree on 1 of the single missions), and tweaking 1 variable at a time. it's no good to change 2 or 3 things, then report that there's changes. we need to figure out which *1* thing, which single variable, does what. once we do that, we can start changing weather conditions etc.

re which mission to use -- i think we should make a mission w/ a single escort, elite crew (or no crew rating), calm weather, set time. that way, there's less confounding variables.

also, when reporting results, we need to give lots of info -- range detected on hydrophones, range pinging started are probably most important.

sorry if it seems that i'm ranting or trying to be bossy -- i just don't want you guys to spend a lot of time and effort doing the same stuff that was done a while ago. forgive me if i've misinterpreted peoples' intentions.

11-29-05, 08:10 PM	#279
caspofungin Commander Join Date: Apr 2005 Posts: 459 Downloads: 41 Uploads: 0	i don't think AI_hydrophones link gets used. Reasons 1. check the sens file for enemy ships. theres a link to AI_visual for the visual node, but then every other sensor has a link to the named sensor in AI_sensors eg linkname type 144p 2. changing the ai_hydrophones values -- other than noise level and detection time as above -- has no effect at all -- at least, not one that i've detected. i also feel we're repeating some of the early work done by cb, redwine, and self. not that there's anything wrong w/ it -- the more info we have, the better, and it would be nice to actually confirm things. but i agree w/ gouldj -- we need to all test on a standardized mission (there's links earlier in the thread to mine and someone elses, or we should agree on 1 of the single missions), and tweaking 1 variable at a time. it's no good to change 2 or 3 things, then report that there's changes. we need to figure out which 1 thing, which single variable, does what. once we do that, we can start changing weather conditions etc. re which mission to use -- i think we should make a mission w/ a single escort, elite crew (or no crew rating), calm weather, set time. that way, there's less confounding variables. also, when reporting results, we need to give lots of info -- range detected on hydrophones, range pinging started are probably most important. sorry if it seems that i'm ranting or trying to be bossy -- i just don't want you guys to spend a lot of time and effort doing the same stuff that was done a while ago. forgive me if i've misinterpreted peoples' intentions.