:k_rofl:

Infact it is well documented that Mayan calendars were little more than Aztec sun stones, and similar in many respects to modern day's big burgers:

http://www.featurepics.com/FI/Thumb3...7674ced9d8.jpg

The only known difference is that McDonald's provided its products with a longer expiry date :yep:

Trevally :timeout: you stole a quarter an hour of my life with your button
:har:

Gap, I will report a bit later.. some interesting things happens with new hydrophone settings :D

With the appearance of new fix this one is not actual anymore, isn't it?:ping:

:o
WHAT things?!

yes, the final fixes are to be found here:

http://www.subsim.com/radioroom/show...&postcount=130

and here (no hydrophone on surface version, only for NewUIs/IRAI users):

http://www.subsim.com/radioroom/show...&postcount=153

Thanks the GapVol team! :yeah: Those fixes overwrites each other, is there any order of their using!

Enable just one of them:

R.E.M. - hydrophone mute for player fix if you are not using New UIs
R.E.M. - hydrophone mute for player fix (TDW compatible) if you are using New UIs


R.E.M_by_Xrundel_TheBeast_1.2 - no hyd on surface - NewUIs-IRAI compatible is "unofficial". I made it on Sober request. It is a mix of R.E.M. - hydrophone mute for player fix (TDW compatible) with no hydrophone on surface settings.

You can use it if you prefer, but I haven't done a "no-TDW" version yet, so you need to enable it on top of New UI's (and R.E.M, indeed)

Grate, all clear now:yeah:
I think this information and DLlinks should be placed at first page in this thread, otherwise later You'll have to answer many questions silly like mine one:yep:

Agreed. Ditto. Fixed similar issues with JSGME.

PM Neal Stevens to get the links to the 1st post if desired by all.

Before editing the first page I think we should at least PM TheBeast :yep:

Nothing.. just glitch..

Well..

5th SensorData:
PreciseRange=0
Max Range=4,000
MinSesorHeight=-500
MaxSesorHeight=-2
SweepPeriod=44
ProbInsideArc=0,77

3,700 | 3,900 | 3,900 | 3,900 | 3,850 | 3,850 | 3,900 | 3,650 | 3,900 | 3,900

4th SensorData:
PreciseRange=0
Max Range=14,000
MinSesorHeight=-56
MaxSesorHeight=-8
SweepPeriod=35
ProbInsideArc=0,85

13,700 | 13,800 | 13,800

3rd SensorData:
PreciseRange=0
Max Range=28,000
MinSesorHeight=-80
MaxSesorHeight=-32
SweepPeriod=31
ProbInsideArc=0,89

27,900 | 28,000 | 28,000

2nd SensorData:
PreciseRange=0
Max Range=39,200
MinSesorHeight=-104
MaxSesorHeight=-56
SweepPeriod=29
ProbInsideArc=0,92

34,800 | 35,000 | 34,900

1st SensorData:
PreciseRange=0
Max Range=45,500
MinSesorHeight=-500
MaxSesorHeight=-80
SweepPeriod=28
ProbInsideArc=0,93

I don't see sense to test it, because I told you that the world's limit is about 40 km.. :yep:


Bad news:

Now the targets are human audible at any depth and.. at any range up to the world's limit.. :nope: even when I don't hear the target (at a distance of 30 km), I see it in the AI-operator's book (in the top left corner) as Unknown..

My glitch.. AI-operator does not heard the signal and right in front of me, at a distance 100m, appeared the ship from the fog.. :o

http://s19.postimage.org/rr65g67en/S...6_22_51_07.jpg . http://s19.postimage.org/cwhk1zxtr/S...6_22_51_38.jpg . http://s19.postimage.org/unt6ggd8f/S...6_22_52_09.jpg

EDIT: forgot to say, in the second mission (-10m) avatar appears on the bridge and under water

My proposals:

1st SensorData:
PreciseRange=0
Max Range=45,000 or 55,000 or 100,000
MinSesorHeight=-500
MaxSesorHeight=-78
SweepPeriod=30
ProbInsideArc=0,95

2nd SensorData:
PreciseRange=0
Max Range=30,000
MinSesorHeight=-500
MaxSesorHeight=-28
SweepPeriod=35
ProbInsideArc=0,85

3rd SensorData:
PreciseRange=0
Max Range=15,000
MinSesorHeight=-500
MaxSesorHeight=-8
SweepPeriod=40
ProbInsideArc=0,75

4th SensorData:
PreciseRange=0
Max Range=5,000
MinSesorHeight=-500
MaxSesorHeight=-2
SweepPeriod=60
ProbInsideArc=0,50

You told me that once you were able to hear a target at a range of 55,000 km :hmmm:

Isn't the the same in stock game, or with our R.E.M. fix?
I don't see anything in these new settings that could cause the proble you are describing, but I will nonetheless investigate.

:haha:

dreadful screenies :up:

Really? :o

wait, I will create a configurable spreadsheet for calculating smooth range curves.

P.S: was the hydro-operator sweep speed slower at low depth and progressively increasing at higher depths?

P.S2: I start thinking that overlapping SensorData are working at the same time, so giving extra high detections at higher depths. This could be related with the problem you have reported.
Maybe we should decrease accordingly ProbInsideArc settings... what do you think? :hmm2:

Yes, but I immediately explained why it happened..
It was wolfpack and the closest boat already been in the "world's limit" circle (40km)

Perhaps this is a stock bug.. I didn't check it..

:yep: