Destroyers Discussion (getting rid of pin point drops)

[CB..]

Originally Posted by timetraveller

No, I haven't. But it might be possible to up the max RPMs in the sub's SIM file, then also change the speed settings for the engine telegraph in its CFG file. Make AheadSlow very small. I am betting this will keep the RPMs down at that speed. With the max RPMs, say for a VII-C set up to 600, maybe this will work. .05 for AheadSlow might bring the RPMs to 30. Other RPMs at higher speeds will (hopefully) be higher than before and cause greater chance for detection. Worth a try if you guys haven't done it already.

And of course this is in case the RPMDetLevel change goes nowhere.

TT

VII-C .CFG file example-

Original:
[EngineProperties]
AllStop=0.00
AheadSlow=0.40
AheadOneThird=0.57
AheadStandard=0.80
AheadFull=0.94
AheadFlank=1.00

New:
Original:
[EngineProperties]
AllStop=0.00
AheadSlow=0.05
AheadOneThird=0.57
AheadStandard=0.80
AheadFull=0.94
AheadFlank=1.00

outstanding nice one TT

if it all hangs together i reckon that takes care of the lot!!!



COL!!! i think the sytem works of the engine revs per minute rather than the actual speed your travelling at--- so increasing the max RPM in TT's minitweaker or if you want to be a little less easy to detect then decrease the max RPM -- then you adjust the speed at 1/3 standard etc thru the cfg file as TT says to get a good balance---

i aint a terribly good skipper Col-- ive been testing all the time so i've been using the external view a lot--first time i tried without the external view i got nailed---i'm actually going to reduce the max rpm for the sub to hopefully lower the chance i get detected and see how that goes---if all these possibilites have an effect there's an almost limitless degree of flexibility
fingers crossed---if the DD type and or side entrys have an effect as well then we have a tool kit that should do just about anything we need--