An important bug found in GWX?

[Kpt. Lehmann]

A reminder: GWX enemy sensors are intended to be much more sensitive than Stock SH3. (Remember when you could pretty much surface your U-boat next to a destroyer... and shout at the enemy crew before they would be aware of your presence in Stock SH3?)

Just assuming for a moment that there is a bug, the implications are that it is a Stock SH3 bug. If this is true, it is not just a GWX problem as the title of this thread suggests... but everybody's problem also.

I'll look into it further as my time and situation permits.

[Fubar2Niner]

Originally Posted by Kpt. Lehmann

A reminder: GWX enemy sensors are intended to be much more sensitive than Stock SH3. (Remember when you could pretty much surface your U-boat next to a destroyer... and shout at the enemy crew before they would be aware of your presence in Stock SH3?)

Just assuming for a moment that there is a bug, the implications are that it is a Stock SH3 bug. If this is true, it is not just a GWX problem as the title of this thread suggests... but everybody's problem also.

I'll look into it further as my time and situation permits.

Good to hear Kapt.

Best regards.

Fuar2Niner

[reaper7]

Originally Posted by TheBeast

Has anyone tried loading the SHIII AI_Sensors using GoblinEditorApp and verify if also wrong using that editor?

Great suggestion TheBeast never considered that. And here is the Results:



And this will be handy now to have another tool for the edit of SH3 dat files

Originally Posted by Kpt. Lehmann

A reminder: GWX enemy sensors are intended to be much more sensitive than Stock SH3. (Remember when you could pretty much surface your U-boat next to a destroyer... and shout at the enemy crew before they would be aware of your presence in Stock SH3?)

Just assuming for a moment that there is a bug, the implications are that it is a Stock SH3 bug. If this is true, it is not just a GWX problem as the title of this thread suggests... but everybody's problem also.

I'll look into it further as my time and situation permits.

So yes it is as Kpt. Lehmann posted S3D does indeed read the ennumerators in incorrectly showing the Text value for Sonar as Hydrophone and visa-versa.

This now proves that SH3 (All versions) are set up correctly for Hydrophone and Sonar entries

I shall remove the file above as this is now proved to be false and would have the incorrect results than that intended
Hope I didn't get everybody's hopes up by jumping on the bandwagon to soon without proper testing

[Fubar2Niner]

Originally Posted by reaper7

Hope I didn't get everybody's hopes up by jumping on the bandwagon to soon without proper testing

Drat, drat and double drat........ darn you reaper, just as I was getting my hopes up ! Seems I'll never be rid of these pesky DD's

Best regards.

Fubar2Niner

[reaper7]

Originally Posted by Fubar2Niner

Drat, drat and double drat........ darn you reaper, just as I was getting my hopes up ! Seems I'll never be rid of these pesky DD's

Best regards.

Fubar2Niner

Know what you mean Mate I got all excited when I seen the Thread too, was sure we were on to a winner. Oh well -more evasive manoeuvres practice it is then

[Anvart]

Originally Posted by reaper7

Great suggestion TheBeast never considered that. And here is the Results...
...

Need to know SH3 engine and read the Dev's help... and will not need to buy SH5 to watch SH3 files.

Originally Posted by reaper7

So yes it is as Kpt. Lehmann posted S3D does indeed read the ennumerators in incorrectly showing the Text value for Sonar as Hydrophone and visa-versa.

Obviously the guy a little goofy ... and he does not understand the crux of the matter.

[vanjast]

With hindsite, I've always managed to escape the escorts and thought that this could not be a global problem..

[Kpt. Lehmann]

Well, all is well that ends well. I am sure that no one meant any harm.

Thanks again, Anvart! It is always good to see you!

[skwasjer]

@all, you can change the enum in S3D's controller template. <installdir>\controllers

Anvart indeed informed me a while ago, but I have not looked at S3D anymore since 2+ years. Perhaps privateer (he also posted updated controller templates for SH5) or Anvart can make the adjustments and post a fix for it.

[NGT]

@ Skwasjer

First, I will like to express, again, my gratitude for your marvelous tool. Thanks to this tool "everybody" can be a "moder", everybody can modulate his own supermod.


But, I am perplexed, after your post above.

If this error is so easy to be dressed by others, why you not do that, and by the way, release the version 1.0 of S3D.

I don’t remember other major problems, and after all, your site dedicated to this tool, is always active. This means that some how, you are around SH3, and your post here —yesterday— give proof of that.

Thank you.



(I hope you understand my English)

[Anvart]

Originally Posted by skwasjer

... or Anvart can make the adjustments and post a fix for it.

Better if author does it himself, i think.

Link to edited obj_Sensor.cs:
http://www.mediafire.com/download/5i...obj_Sensor.rar...
Copy this file into X:\Program Files\Silent 3ditor\Controllers\SHSim\ folder and overwrite existing file.

[Volk2]

Originally Posted by Kpt. Lehmann

Just assuming for a moment that there is a bug, the implications are that it is a Stock SH3 bug. If this is true, it is not just a GWX problem as the title of this thread suggests... but everybody's problem also.

Yes, as the original poster said, he only discovered it by playing GWX, but if the problem is true (?) - it is global, not limited to one supermod.

[edit]
Oh, I didn't see the previous information of reaper7 - so it looks like there is no bug. Excuse the storm in a teacup