An important bug found in GWX?

[reaper7]

Originally Posted by ***1074;***1086;***1083;***1082;

Here is the table that shows comparison of stock SH3, GWX and Olamagato improved sensors (alpha):.

Looks Interesting. Can't download mod to have a look as registration has to be approved by forum admin.
Any chance to upload here to check it out

[Volk2]

Originally Posted by reaper7

Looks Interesting. Can't download mod to have a look as registration has to be approved by forum admin.
Any chance to upload here to check it out

Yep, I've updated links, here it is: http://dl.dropbox.com/u/4055585/GWXP...%20eskorty.zip

[Volk2]

And here is the latest version of Olamagato mod ("2.2", JSGME compatible) extracted from http://ja.gram.pl/blog_wpis.asp?id=4756&n=19

http://dl.dropbox.com/u/4055585/GWXP...ampanii%29.rar

There is also an excel spreadsheet with changes listed inside the archive.

Google translation of readme:

Mod improves the performance of detectors escort V.2.2
-------------------------------------------------- -

Cause of this fashion were observed inconsistencies in the behavior of the escort ships (with an attack on a submerged submarine) with relations submarine crews. GWX extension failed to correct this behavior, but only hindered attempts to avoid detection.
The tests (with a single compromising eskortowcem and selective detectors) showed that almost 100% of the detection is done by a hydrophone or sonar passive, very often in the posterior semi-zone eskortowca. Coverage hydrophone / sonar passive zone included a full 135 ° -135 .. without any restrictions as to the depth of the search target. It was enough that the goal was for 1 or 2 seconds in the range of the hydrophone (up to 7 km in GWX!) In low-impact and noise waves (calm sea) to become fully detected by an escort with no chance of loss of contact. This effect did not occur in the original SH3 because the range of default hydrophone was there to just 600m handicapped. GWX correct the manifest error causing an extremely high difficulty to avoid flooding. It boiled down to a random factor with a very low chance of success in the case hit the escort of a combination of the best devices.
At the same time a marginal role in the discovery he was active sonar, which range scan boiled down to just 10 degrees vertically in front of semi-zone and required in practice to detect the full 40 seconds (red light) to track the depth of submarine periscopes (only). Apart from this narrow area of ***8203;***8203;the scan sonar eskortowca was practically blind. In the extreme case of active sonar Type 123A/128A goal to be detected had to be on for 20 seconds just to 48m/75m from eskortowca, at a depth of 10-15m. Such conditions could never be met for a moving warship escorts. Even at the border range sonar Type 123A (1200 yd.) U-boat submerged to a depth below 212 m was completely safe from any chance of being detected by sonar.

That the game was in clear contradiction with the manual for GWX 3.0 - both with a description of the detectors as well as ways to avoid the escorts described in the Appendix.

This amendment eliminates these problems by reducing the possibility of a real submarine detection by passive sonar hydrophone and escorts, and a significant increase in the possibility of active sonar - in accordance with the historical realities and the manual for GWX 3.0.

Additionally, the game active and passive sonar are separate detectors, which probably can exist without each other. In fact, it was a complex device whose elements closely cooperate with each other in different ways. Passive sonar to scan the environment around eskortowca, and these were "illuminated" by the various types of acoustic beam with active sonar. Some of these beams was heard, some interferowa***322;a in waves of audible frequencies, and the others were at all beyond the human hearing range. Bundles of long-range active sonars have low angles of taper, and these short-range rather high cone angles.

Changes
------
- Extended detection time was excessive noise or sonar reflections from 1 to 5 seconds at a distance of up to 390-570M and from 2 to 10 seconds in the rest of the distance up to 6,5-9,5 km.
- Was introduced level temperature inversion layer depth of water, which in GWX and SH3 was at sea level (0 m).
- Deterioration factor hydrophone scanning from too much speed namierzaj***261;cego ship was restored with 20 nodes (in GWX) to 15 knots true (as in SH3). This index to rise slightly to the already abnormally high efficiency scanning hydrophone / passive sonar.
- Reduced Vertical angles were scanned hydrophone / s.pasywnego from 80-170 degrees (only without the 10 degrees from vertical) to the max 90,29-155 degrees depending on the severity of passive sonar. This means covering a depth of 0-250 m already at a distance of 536 m from eskortowca and the inability to detect the U-boat the hydrophone (without beam sonar), standing at a depth of 4-5 km above the periscopes
- The maximum ranges of active sonar have been converted from yards to meters.
- Default Active sonar has ceased to be blind than 100 m from the target. Limit was 10 m just like any other passive sonar.
- The horizontal angle of the cone were urealnione active sonar from the original 180 sec to 70-130 degrees in accordance with historical data and interpolated for intermediate types of angles. However, tests show that these angles are probably hidden in the code (on hard).
- Default vertical angle of the cone of active sonar has been reduced to 16 deg
- The vertical angle of the cone active sonar have been enlarged to historical values: 90-155 ° Both of these changes to better simulate the closed minimum range active scanning sonar default.
- Increased sensitivity coefficients were active sonar to 0.25-0.90, which increased the area a thorough scan to 569-910m from the bow eskortowca, depending on the type of sonar.
- Was reduced by half (to 0.3) coefficient of wave impact on the quality of the active sonar detection.

Olamagato

Some other interesting remarks by Olamagato (e.g. about torpedos) about his changes in mod - sadly, by google translate:

By the way of working on the package managed to detect that in several aspects of simulation, GWX it was not quite as polished, as announced. Parameters torpedoes were not proven, and yet one of the most important issues in the evolution of combat torpedoes, especially manewruj***261;cymi, such as FAT and the SOLDER, was their coverage. The parameters of range and speed were not consistent with each other, causing the older torpedoes were longer range than the newer ones.

Similarly, it appeared from the passive and active sonar. The Allies had a weak passive sonar (and hydrophones), and the worst of the German equivalent of 1939 (GHG) struck on the head tenderly, even those allied with the end of the war, the active sonar is allied with the weapon, which relied on them were murderously effective. Similarly, neither SH3 or GWX did not consider that the acoustic torpedo warheads were 200 kg heksanitu instead of 300 kg as in the other torpedoes, resulting in a third explosion weaker than in the remaining torpedoes.

SH3 gave a huge bonus that allows ordinary hydrofonom allies detect the slightest sound of the U-boat in 1 second (sic), active sonar while making virtually blind - they have to ping the area up to 20 seconds to detect anything at all. SH3 designers probably did not know why the tests SH3 escort was "so good" so drastically okroili ordinary hydrophone detection range up to 600m (sic). GWX "repair" this "mistake" by increasing (as a logical inference based on other models) hydrophone normal range up to 7 km, further weakening, and so ineffective active sonar, which resulted in accurate tracking hydrophone, while causing the pinging was only 40 - second scare sound (less than 75m 20s from the U-boat).

Translation mod of GWX 3.0 offers two options to restore the historical parameters of torpedoes, as well as historically justified set of passive and active sonar, which allow escort behave much more realistically than a murderously effective.

Including (diagnostic) detection rate of U-boot for the first time, you can see all the intermediate colors between red and green, depending on the speed, quiet running, depth and position relative to the U-boat attack escort vessels (picture above). U-boat captain will be able to partly decide what shade of brown, yellow or green will show on the indicator (ie how much the ship will be exposed to detection) and see how traffic escort vessels affects the state of his discovery.

You can also capture the moment when he loses bearing escort (the indicator changes to green) when rushing to the detected target. Of course, if will not have a helper standing. Escort of the end of the war sonar will detect the U-boat periscopes already standing on more than a mile - but only from the bow. The stern of the condition detected is low or zero.

[reaper7]

Excellent thank you ***1074;***1086;***1083;***1082;

[Olamagato]

Hi everyone.
This mod is part of Polish version of GWX 3.0, which is not yet finished, is still in beta, and its settings are constantly fine-tuned. It is therefore not yet been made available as a separate package. There will also be many people who find that by these changes escort became stupid or ineffective in their jobs.
Regarding the above-mentioned data, they are already partly outdated, and the version setting changed several times from 1.0 to 2.3.

@Wolf - Please do not hurt a forum by google translator work. In due time everything will be in understandable language.

[Volk2]

Originally Posted by Olamagato

@Wolf - Please do not hurt a forum by google translator work. In due time everything will be in understandable language.

Yes sir Waiting for your mods!

[ridley]

Did anyone try this? If so is it any good?

Originally Posted by reaper7

Wow if thats the case this is one Major bug. Hopefully easily fixed.

Edit just confirmed this in the AI_Sensors.dat file

Entry 13: For AI_Hydrophone Sensor type is set at 2-Sonar and not 3-Hydrophone

Entry 17: For AI_Sonar Sensor type is set at 3-Hydrophone and not 2-Sonar

Easy Fix - Great catch to find that one

Originally Posted by Anvart

Ne nado skazki rasskazivatj...
...
You must know, that S3D don't correct show AI sensors...
Why..? becouse - wrong enum sequence...
For obj_Sensor Controller Type of sensor must be... enum{LOOKOUT, RADAR, HYDROPHONE, SONAR}.
Error of S3D.

Yes, I saw that too myself and believed it was an error. But it seems that this is an error from S3D only. This is correct in game. So, no fix for this is needed.

[Anvart]

[Aquelarrefox]

I found a fix for sensors wich make much realistic the evasion, it was made by a polish man, yes olamagato. This worked enught right to me. can be used with oit of care.
anyway in 43 the pinging serch by 3 destroyer is so complex to evade, mybe some lucky