Just testing it gives the following impression:
ScanRate: Time between scanning for missiles within it's range. The pdl has a reload time for itself in the weapontemplate but this value determines how fast a missile is detected that is in range.
The only reason I see for the two different scanrates is to make the chance of both pdl's firing at the same missile as small as possible. It are two independant modules, not sharing any info. I could be completely wrong about this though.
ScanRange: Range in whitch it scans for missiles. The pdl itself is limited by it's weapon range however it needs to know in time that a missile is coming.
PredictTargetVelocityFactor: I tried numbers ranging from 0 to 1000000 and I didn't notice any difference. I though it would have to do with the speed and direction in witch the 'dead' missiles travel but it just stayed the same.
So that makes that you can't point to one value and say what influence it has. The pdl can have a good range, if it detects the missiles to late it can't stop them. It can have a good rate of fire, if it does not scan fast enough, it is of no use. Together (ScanRate, ScanRange, AttackRange and DelayBetweenShots) they determine the effectiveness of the pdl.
And for activating the second pdl on the avenger, just activating module 'laser_two' (which is commented out now) should be enough.
|